Choose a project, ongoing support, or both.

Each engagement defines what we deliver, what happens after launch, and which costs remain separate.

45 to 90 days

Typical project delivery

Final timing is confirmed after scope review.

Choose the engagement that matches the work.

Final scope, team size, and fees are set after a requirements review.

Quoted by scope

A defined system, application, feature, or integration.

Included

* Ongoing maintenance and team training are not included. Post-launch coverage is limited to bug fixes for three months.

Recommended

Project fee, then monthly

A new system that needs continuity after launch.

Included

* New features or modules after launch require a separate project scope.

Monthly engagement

An existing system that needs steady technical capacity.

Included

* New features or modules require a separate project scope.

01
Share the current process
You show us how the work is done, where it slows down, and what the system needs to support.
02
Approve the project plan
We prepare the scope, schedule, deliverables, and acceptance requirements. You review and approve them before development starts.
03
Review working progress
We build in agreed stages. You review working updates and provide feedback at planned checkpoints.
04
Complete acceptance testing
Your selected users test the agreed workflows. We address accepted issues, deploy the system, and complete handover.
05
Set support priorities
You report issues and priorities through agreed channels. We provide the support included in your project or retainer.

BRD: The Business Requirements Document records the business goals, processes, users, and required outcomes.
SRS: The Software Requirements Specification describes the agreed system behavior, functions, interfaces, and technical requirements.
UAT: User acceptance testing lets your team confirm that the system meets the agreed requirements before handover.
Deployment: We configure and release the agreed system to its production environment before handover.
Bug fix: A correction when the delivered system does not behave according to the agreed requirements. It does not add a new feature.
Infrastructure: Hosting and infrastructure costs pass through at cost, with no markup or interest.
Retainer: A monthly agreement for the listed support, maintenance, training, improvements, and bug-fix services.