Service plans
What this costs, before you ask.
Starting prices for both families of work, the milestone rhythm every engagement is billed on, and the things a fee does not cover. Published so the first call can be a decision rather than an explanation.
Delivery engagements
Four ways to buy a build
Every plan runs the same four-milestone rhythm and ends with the same handover. What changes is how much review you get at each stage, how fast the schedule is, and how long the support window runs afterwards.
Plan / 01
Starter
From
$1,500
per project
One developer on a defined piece of work with a finish line, delivered on the standard milestone rhythm.
Best for
One module, or a focused automation
- One dedicated developer
- One review cycle per milestone
- Standard delivery schedule
- Handover pack at sign-off
Recommended
Plan / 02
Standard
From
$2,000
per project
The plan most projects run on. A second review cycle at every milestone, plus a PM/developer.
Best for
A full build with several moving parts
- Dedicated developer plus a PM/developer
- Two review cycles per milestone
- Three days of post-delivery support
- Handover pack and a walkthrough
Plan / 03
Priority
From
$2,800
per project
Compressed scheduling. Your work goes ahead of other scheduled builds, which is what shortens a timeline.
Best for
A date that genuinely cannot move
- Compressed delivery schedule
- Priority response on questions
- Rush fee quoted upfront, in writing
- Testing and review cycles are not compressed
Plan / 04
Extended
From
$3,500
per project
The long warranty window, for a build that has to stay standing while a team learns to depend on it.
Best for
A system going into daily operational use
- 30–45 days of post-delivery support
- Defect fixes throughout the window
- Handover pack and a walkthrough
- Retainer available for the next phase
All figures in USD and exclusive of taxes. A service-plan fee and the development cost are independent components — neither includes the other.
Plan selection
What differs between them
A dash means the figure is not published yet rather than that the plan excludes it — the terms it comes from are being confirmed.
| Feature | Starter | Standard | Priority | Extended |
|---|---|---|---|---|
| Dedicated developer | Included | Included | Included | Included |
| PM/developer alongside the build | Not included | Included | Included | Included |
| Review cycles per milestone | 1 | 2 | Not stated | Not stated |
| Post-delivery support | Not stated | 3 days | Not stated | 30–45 days |
| Compressed scheduling | Not included | Not included | Included | Not included |
| Priority response on questions | Not included | Not included | Included | Included |
| Four-milestone billing | Included | Included | Included | Included |
| Handover pack at sign-off | Included | Included | Included | Included |
Starter
- Dedicated developer
- Included
- PM/developer alongside the build
- Not included
- Review cycles per milestone
- 1
- Post-delivery support
- Not stated
- Compressed scheduling
- Not included
- Priority response on questions
- Not included
- Four-milestone billing
- Included
- Handover pack at sign-off
- Included
Standard
Recommended
- Dedicated developer
- Included
- PM/developer alongside the build
- Included
- Review cycles per milestone
- 2
- Post-delivery support
- 3 days
- Compressed scheduling
- Not included
- Priority response on questions
- Not included
- Four-milestone billing
- Included
- Handover pack at sign-off
- Included
Priority
- Dedicated developer
- Included
- PM/developer alongside the build
- Included
- Review cycles per milestone
- Not stated
- Post-delivery support
- Not stated
- Compressed scheduling
- Included
- Priority response on questions
- Included
- Four-milestone billing
- Included
- Handover pack at sign-off
- Included
Extended
- Dedicated developer
- Included
- PM/developer alongside the build
- Included
- Review cycles per milestone
- Not stated
- Post-delivery support
- 30–45 days
- Compressed scheduling
- Not included
- Priority response on questions
- Included
- Four-milestone billing
- Included
- Handover pack at sign-off
- Included
Engineering enablement
For teams that already have engineers
You have a team and a codebase; what you are short of is capacity, or an answer. These three are bought by the week rather than by the project.
Plan / 01
Starter
From
$1,000
1–2 weeks
A bounded review of what exists, and a written answer you can act on without us. Often the cheapest way to find out whether you need an agency at all.
Best for
One question blocking a decision
- Codebase or architecture review
- Written findings, ranked by what to fix first
- A walkthrough call with your team
Plan / 02
Growth
From
$3,000
3–6 weeks
We work inside your repository and your review process for a defined block of weeks. The output is pull requests against your standards, not a handover at the end.
Best for
A team that needs capacity, not advice
- Embedded in your repository and your stand-ups
- Delivery through your own review process
- Documentation written as the work happens
- Knowledge transfer before we leave
Plan / 03
Scale
Quoted
Custom
ongoing retainer
Reserved capacity every month, with priorities set together at the start of each cycle. Scale the block up or down as the roadmap moves.
Best for
A roadmap that needs sustained engineering
- Reserved capacity every month
- Priorities reset each cycle
- No re-scoping for every small change
- Ends by written notice from either side
All figures in USD and exclusive of taxes. A service-plan fee and the development cost are independent components — neither includes the other.
Who this is for
- An in-house team that is one or two engineers short of its roadmap.
- A product whose original build team has moved on, and nobody left knows why a decision was made.
- A codebase that works but nobody wants to touch.
- A technical decision your team is split on and would rather resolve with an outside read.
When to choose what
- Starter, when the question is bounded and an answer unblocks a decision.
- Growth, when you need hands in the repository for a known stretch of weeks.
- Scale, when the work is continuous and re-scoping it every month is the actual overhead.
- A delivery engagement instead, if what you want is a product built rather than a team extended.
The small print, in full size
What the fee covers, and what it does not
Every one of these is a line a client has been surprised by somewhere, so none of them is in a footnote.
- The service-plan fee and the development cost are independent components. Neither includes the other.
- Enhancements and scope expansion are quoted separately, by change note, before anything is built.
- Revisions beyond the review cycles your plan includes are billed at our standard rate, quoted first.
- Third-party integrations are in scope only where your SOW names them.
- All amounts are exclusive of taxes, which are applied at the prevailing rate.
- Invoices are payable within 7 days. An unpaid invoice may pause the work.
The full terms are on theterms of service page, and how an engagement runs day to day is on thedelivery policy page.
Milestone rhythm
Every delivery engagement is invoiced against the same four milestones. The percentages are the structure; your SOW states the amounts.
| Milestone | Share |
|---|---|
| Kickoff & alignment | 20% |
| Core feature implementation | 30% |
| Feature completion & UAT ready | 30% |
| Final handover & sign-off | 20% |
Tell us what is slowing the work down.
A short conversation is usually enough to tell whether we can help. If we cannot, we will say so and point you at someone who can.