Engagement model 01
Fixed-Scope Delivery
Fixed scope software development where we own the outcome end to end. Discovery sets the scope and the architecture, then we build in sprints against it.
01 What you get
Everything in a fixed-scope build
No line below is an upsell. It is in the statement of work you sign.
Discovery
Weeks 1 to 2
- Stakeholder interviews and a written brief
- Clickable prototype of the core journey
- Architecture and stack decision, with the reasoning
- A fixed scope, and the price that goes with it
Build
Weeks 3 to 14
- Two-week sprints, each ending in a working demo
- A staging environment you can use from sprint one
- Automated tests running on every merge
- A named delivery lead in your Slack
Launch
Final fortnight
- Production deployment and monitoring
- Load and security testing
- Analytics and error reporting wired in
- A go-live runbook your team can follow
Handover
At the final milestone
- Annotated source in your own repository
- Architecture and runbook documentation
- A recorded walkthrough for your engineers
- 30 days of post-launch support
Anything outside this list is priced against the remaining milestones before we start it, never after.
02 Commercials
What it costs, and what you commit to
Discovery is priced on its own, so the build price is set against something real rather than against a guess.
- Term
- 8 to 16 weeks Milestone-based, agreed at the end of discovery.
- Billing
- Fixed price per milestone Invoiced on acceptance, net 15.
- Discovery
- Priced separately Two to four weeks. Yours to keep if you stop there.
- Change requests
- Priced against remaining milestones You approve before we start. Nothing is absorbed quietly.
- Ramp-up
- 2 to 4 weeks Signature to first sprint.
- Exit
- Ends at the final milestone No notice period. Handover is included, not billed.
Figures exclude third-party licences and cloud spend, which stay in your own accounts.
03 Fit check
Right for you if…
The second column is the one worth reading.
Pick this when
- The scope is settled and the launch date is real.
- You want one price and one accountable team.
- You have no engineers to spare for daily direction.
- The product has to exist before it can evolve.
Pick something else when
- The roadmap is still changing every fortnight.
- You want to direct the work sprint by sprint yourself.
- You are still deciding whether to build at all.
- You need to scale the team up and down as budget moves.
Sounds more like the second column? See Dedicated Remote Team
04 Proof
Built this way
Products delivered on a fixed scope and a fixed price.
Change Management
AI-Powered Enterprise Change Management for Large-Scale Organizations
Enterprise change management software letting organisations execute, monitor and sustain change faster, with the progress of every initiative visible in one place.
Construction Management
Real-Time Construction Coordination, From HQ to Field
A construction coordination platform for multi site work, replacing spreadsheets and scattered email with tasks, schedules and on site progress synced in real time.
AI Automation
AI-Powered Content Automation Platform
An AI content engine that turns sales and strategy calls into ready-to-post content, matched to the brand's own voice and scheduled straight to LinkedIn.
In their words
Estimates matched the timeline.
Scope was set up front, the launch hit the milestone billing we agreed, and delivery matched what we were quoted.
Clutch
In their words
On time and on budget.
Two releases, both on the date we set, with no surprise change orders along the way.
G2
In their words
They understood the workflow before writing code.
The team mapped our intake process, flagged the compliance constraints we had missed, and delivered the first working release inside the quarter.
Clutch
06 Compare
How this compares
The other three models, on the same questions.
| Dedicated Remote Team | IT Staff Augmentation | AI Consulting & Audit | |
|---|---|---|---|
| Best for | A long-running product with an evolving roadmap | An in-house team that needs more hands | Deciding where AI is worth it before you build |
| Term | Rolling, three-month minimum | Rolling, one-month minimum | 3 to 6 weeks, fixed |
| Who owns scope | You do, we advise | You do, entirely | We do, agreed up front |
| Team | Cross-functional pod plus a delivery lead | Individual engineers, inside your process | Principal consultant plus an ML engineer |
| Billing | Monthly, per seat | Weekly or monthly, per engineer | Fixed fee, two instalments |
| Ramp-up | 3 to 4 weeks | 2 weeks | Starts within 2 weeks |
| Exit | 30 days' notice | 2 weeks' notice | A costed roadmap, yours to keep |
| Read more | See the model : Dedicated Remote Team | See the model : IT Staff Augmentation | See the model : AI Consulting & Audit |
07 Questions
Before you decide
Ownership, scope changes, and what happens at the end.
Yes, and most long-running clients do. A fixed-scope build that turns into an ongoing product usually becomes a dedicated team at handover, same people, new commercial terms. We re-paper the engagement; you do not re-onboard anyone.
You do, in every model, from the first commit. The repository is yours, hosted in your organisation where you want it there, and the licence transfer is in the contract rather than an invoice at the end.
Discovery exists to find that out before the price is fixed, which is why it is billed separately. If something material surfaces mid-build we price the change against the remaining milestones and you decide, we do not absorb it quietly, and we do not stop work while you think about it.
An audit or a two-week discovery is the usual way in. It is a fixed fee, it produces something you keep whatever you do next, and nothing about it obliges you to carry on with us.
Notice is two weeks for staff augmentation, thirty days for a dedicated team, and none for fixed scope work, which simply ends when the scope is delivered. Offboarding includes a handover of code, documentation and access, so nothing you rely on depends on a particular person still being reachable.
08 Start
Get a fixed quote
Tell us what you are building and when it has to be live. We will come back with a discovery plan and a price.
- 2451 West Grapevine Mills Circle, Grapevine, TX 76051 · USA
- hello@kodertal.com
- We reply within one business day.