Three engagements, taken in order.
Every project starts with a fixed-price assay. You only commit to a build once you've seen what we found and what it will cost.
1
Assay
Two to eight weeks
[Assay price is confirmed before launch]
Every engagement starts here.
- A review of code, data and systems, done with your team.
- A written assessment and an architecture proposal.
- A fixed-scope plan and budget for the build.
- The findings are yours to keep, and to take elsewhere if you choose.
2
Build
Two to nine months
[Build pricing model is confirmed before launch]
Building or rebuilding a system to production standard.
- Scope, budget and pass criteria agreed after the assay.
- A working release every two weeks.
- The temper stage: load, security, failure and recovery testing.
- Every change gets a written note with its cost, approved before work starts.
3
Service agreement
Twelve months, renewable
[Service agreement pricing is confirmed before launch]
Keeping a production system healthy after launch.
- Monitoring, with agreed response times. [Response times are confirmed before launch].
- Security patching and dependency updates.
- A monthly health report.
- A quarterly improvement plan, with a set allowance of engineering days.
Commercial terms, in plain words
The assay is fixed price.
You know the cost before we start, and the findings are yours whatever you decide next.
Build budgets come from the assay.
We quote once we've seen the system. Before that, any number would be a guess.
Third-party costs are yours, at cost.
Cloud, licences and model usage are billed to your own accounts. We add no margin.
Invoicing and notice.
[Invoicing terms and notice periods are confirmed before launch].
Questions about cost
How do you price?
The assay is fixed price. The build is quoted after the assay, against a scope and pass criteria we agree together. The engagements page explains each one.
What if the scope changes?
It will. Each change gets a short written note with its effect on cost and dates, and nothing starts until you've approved it.
Do you mark up cloud or licence costs?
No. They're billed to your own accounts.
Bring us the system you can't afford to get wrong.
30 minutes. Bring the problem, and we'll tell you whether we're the right shop for it.