Solution
Fixed-ScopeProjects
A fixed-scope project engagement for work that has a clear brief — a written scope, a written estimate, a delivery date, with the change process explicit and the codebase and the accounts in the client's name from the first commit.
What this engagement covers
A fixed-scope project starts with a clear brief. Between the brief and the delivered work, the work is the scope, the estimate, the build, the launch and the handover. The engagement is fixed scope, fixed price, with a change process for anything that moves.
We do this for projects that have a clear brief and a clear outcome — a website rebuild, a CRM, an internal tool, a custom build. The codebase is owned by the client, the accounts are in the client's name, and the handover is complete.
How the work is shaped
The first two weeks are the discovery — a 30-minute call, a written brief, a written scope, a written estimate. The next two weeks are the design and the architecture.
The remaining weeks are the build, the launch, the QA and the handover. The engagement ends with a written runbook and a maintenance retainer the client can rely on.
- A 30-minute discovery call before any commitment.
- A written scope and a written estimate within two weeks of the discovery.
- A two-week sprint cadence with a working slice every Friday.
- A complete handover with the codebase, the accounts and the runbook.
What it costs and what you get
A typical fixed-scope project lands between ₹4 lakh and ₹40 lakh, depending on the scope, the integrations and the design. The engagement is fixed scope, fixed price, with a change process for anything that moves.
You get the codebase, the cloud accounts, the documentation, the QA and the operational handover. The codebase is yours, the accounts are in your name, and the runbook is the one your team can use.
Frequently asked
The questions the team asks
- What if the scope changes during the build?
- We have a written change process. Anything that replaces something already in scope is a straight swap. Anything additive gets a written estimate and a revised date before we start it. The change process is the single biggest reason projects slip, and we handle it explicitly.
- How is the estimate calculated?
- Against the written scope, the integrations and the design depth. The estimate is in writing, with a range for the cases the scope is silent on. The estimate is the contract, and the change process is the only way the contract moves.
- Can the engagement be paused and resumed?
- Yes, with a written pause and resume. The codebase and the accounts stay in the client's name, the scope stays the same, and the resume is a continuation of the original engagement. The pause is part of the change process.
Have a project in mind?Let’s scope it together.
Tell us the outcome you need. You get an approach, a rough timeline and next steps within one business day.