A clear process from modification request to deployment.
The sales and delivery process is designed to stop software modification becoming an informal chain of messages, moving estimates and undocumented additions.
Modification request
You provide the software, business context, requested change and contact information.
Qualification
We confirm the request is legitimate, technically relevant and within the kind of work we handle.
Technical review
We identify affected areas, dependencies, unknowns and any access required to scope accurately.
Written scope
The requested behaviour becomes explicit deliverables and acceptance criteria.
MU assessment
The modification is scored using our standardized pricing factors.
Quote & approval
You receive the scope, fixed price, payment stages and estimated delivery window.
Development & testing
Work is completed against the scope and prepared for your testing.
Acceptance & deployment
Scope-related issues are resolved, final payment is completed and approved work is deployed/delivered.
Payment structure
Standard projects use a deposit before development and the balance after client testing but before final production deployment or source-code handoff.
Standard
50% to start
50% after testing
Larger projects
40% start
30% milestone
30% completion
New scope
Handled as a separate written change request.
Communication channels
Email is the formal project record for scope, approvals and invoices. WhatsApp or Telegram can be used for convenient conversation when configured, but commercial decisions are confirmed in writing.
This keeps the company responsive without turning the project into an unstructured chat thread.