A real number in 48 hours.
We build enterprise systems, and what they cost depends on what they plug into, what they have to comply with, and what done means for you. Tell us the problem — you'll get an indicative range within 48 hours and a fixed quote once we've scoped it.
Three ways in. All scoped first.
Discovery & Scope
2 weeks
We map the systems, the constraints, and what done actually means. You leave with an architecture, a delivery plan, and a fixed quote.
- System and integration audit
- Target architecture
- Delivery plan with milestones
- Fixed quote for the build
- Yours to keep — build with anyone
Scoped Delivery
Weeks, not quarters
A fixed quote against a locked scope. Small senior team, delivery in milestones, and the source code is yours at the end.
- Fixed quote, written assumptions
- Milestones with acceptance criteria
- Small senior team, no juniors
- Full source-code ownership
- Post-launch support included
Embedded Team
Availability agreed up front
Senior engineers working alongside your team, accountable to your roadmap. We commit to the availability we've agreed — not to a start date we can't hold.
- Developers, QA, DevOps, PM
- English-first, UK-accountable
- Minimum 4 weeks, then monthly
- Rate card on request
- No recruitment fees
Timelines start after scope lock and access readiness (systems, data, and security sign-off in place) — not from contract signature.
“It depends” — on these six things.
Every quote we write comes down to the same levers. Knowing them up front tells you roughly where your project sits before you ever talk to us.
How many systems we touch, and how well documented they are. A voice agent on a modern CRM and the same agent on a 15-year-old switch are not the same project.
Regulated sector, DPIA, penetration testing, accessibility conformance, data residency. Real work with real cost — and non-negotiable when it applies.
A thousand calls a day and carrier-scale throughput need different architectures. Real-time changes the design, not just the sizing.
One channel or five. One language or nine. A pilot behind a feature flag or a full cutover with a migration and a rollback plan.
Compressing a schedule means parallel teams and more coordination. We'll tell you when paying to go faster stops buying speed.
Handover and walk away, or an SLA, on-call, and a roadmap. Both are fine — they're priced differently.
A proposal, not a deck.
Within 48 hours of the first call, in plain English, written by the engineer who'd run the work — not a salesperson.
Request details- Scope, written as what's in and what's explicitly out
- Target architecture and the integration plan
- Milestones with dates and acceptance criteria
- A fixed quote, with the assumptions it depends on
- Third-party running costs, estimated at cost
- The risks we can see, and who carries each one
Pricing Questions
Why isn't there a price list?+
Because every number on it would be wrong. We build into systems we haven't seen yet, and the same feature can differ by an order of magnitude depending on what it plugs into. A price list would either pad every quote to cover the worst case, or set a number we'd have to renegotiate later. We'd rather scope the work and give you one that holds.
How long until I get a number?+
An indicative range within 48 hours of the first call — enough to tell you whether this is worth continuing. A fixed quote follows discovery, once we've seen the systems rather than guessed at them.
Is the quote actually fixed?+
Fixed against the scope we agree, with the assumptions and exclusions written down in the proposal. If you change the scope, we requote that change and you approve it before we build it. No quiet absorption, no surprise at the end.
What isn't in the quote?+
Third-party running costs — cloud hosting, telephony minutes, LLM tokens — are billed at cost, and we estimate them up front so they're not a shock. Everything we do is in the quote.
How do payments work?+
50% upfront and 50% on delivery for scoped packages, monthly invoicing for embedded teams. UK contracts, GBP or USD. The full terms are in our cancellation and refund policy.
Do you take smaller projects?+
We're built for enterprise programmes, and that's where we're worth the money. If your project is too small for us to add real value, we'll say so on the first call instead of taking the work.