Vibe-to-Production · Pricing

Every engagement, priced up front.

Four ways to engage, published bands for each, and an honest account of what moves a project from one end of a band to the other.

The bands

Diagnose first. Commit second.

Every engagement starts with the audit, including the ones that end there. It is fixed price because it has a fixed scope — 49 checks, evidence for each, and a plan you own.

  • 72 hours

    Diagnostic Audit

    Find out exactly what stands between your prototype and real users.

    $2K – $5K
    Fixed scope, quoted from the audit
    • A production-readiness score against every check in the framework
    • Every finding written up with severity, evidence and the fix
    • A prioritised remediation plan you can hand to any engineering team
    • A walkthrough call with the engineers who did the review
    Where this one stops: The audit diagnoses. It does not change your code — that is the rescue tier.
  • 2–6 weeksMost common

    Rescue & Ship

    Fix what actually blocks launch, then put it live.

    $5K – $25K
    Fixed scope, quoted from the audit
    • Every critical and high-severity finding closed
    • Automated tests around the paths that matter most
    • A real deployment pipeline with staging and rollback
    • Monitoring and alerting wired to a human
    • Full handover — code, infrastructure and documentation are yours
  • 6–16 weeks

    Full Rebuild

    Keep the product. Replace the foundation.

    $25K – $100K+
    Fixed scope, quoted from the audit
    • Your business logic and product decisions preserved and documented
    • An architecture chosen for where you are going, not where you started
    • Migration of existing users and data with a tested rollback
    • Test coverage and CI/CD from the first commit
    • No proprietary lock-in — standard stacks you can hire for
  • from 3 months

    Co-Pilot Retainer

    An engineering team that stays.

    $5K – $25K/mo
    Fixed scope, quoted from the audit
    • A named team that knows your codebase
    • Code review on everything that reaches production
    • Continuous hardening rather than another rescue in six months
    • Capacity that flexes with your roadmap
Every engagement includes
  • NDA signed before you send a link
  • Read-only access, revoked on delivery
  • You own the code, infra and docs
  • Conventional stacks you can hire for

Bands are indicative and quoted per engagement against audit findings — never against a conversation.

Ask about an engagement

Tell us what you have. We will quote it.

An engineer reads every enquiry before anyone calls you, so the first conversation starts from your situation rather than a script. No code access is needed to get a number — and an NDA can be signed before any changes hands.

Phone, with country code

WhatsApp works too if that is easier than a call.

Which engagement you are asking about

Not sure? Pick the audit — every engagement starts there, and it is the one that tells you which of the others you actually need.

We are not asking for your code. Read-only access gets arranged after we have spoken — and under an NDA first if you want one. Everything above is enough for us to tell you whether that is the right engagement for you.

What moves it

Six things decide where you land.

Ranges exist because these vary enormously between projects. Knowing which ones apply to you will tell you roughly where in a band to expect to sit, before anybody quotes you.

  • 01

    Whether you take money

    Payments bring reconciliation, webhook handling, subscription lifecycle and compliance obligations. An application that charges customers is meaningfully more work than one that does not, regardless of its size.

  • 02

    What data you hold

    Health, financial or identity data raises the bar on every category at once — access control, encryption, retention, deletion, audit. Anonymous or public data lowers it.

  • 03

    How much backend actually exists

    A front-end generator leaves you a build rather than a rescue. A full-stack generator usually leaves a foundation worth keeping. This is the single largest swing factor.

  • 04

    Whether anyone is using it yet

    Live users mean migrations run with no downtime and a tested rollback rather than a maintenance window. Safer, and slower.

  • 05

    How consistent the codebase is

    One pattern applied throughout is quick to harden. The same problem solved four different ways in four places has to be reconciled before it can be secured.

  • 06

    Who operates it afterwards

    Handing back to your team means documentation, conventions and a handover we stand behind. Staying on retainer means less of that up front.

Who we've built for

The teams below didn't hire us to be clever. They hired us because it had to work on Monday.

Getting on for 27 years of production delivery — somewhere north of 8,000+ products for 3,000+ clients across 92+ countries. Not one of them was a demo that needed to look good for a week.

In their words

The number is easier to judge once someone else has paid it.

Whichever tier you take, the output is yours — code, infrastructure and documentation, on standard stacks you can hire for. The methodology is published in full and our engagement models cover the commercial side.

Production-grade AI, not a demo.
John CleavesJury Tracker
The AI agent they built saves our analysts 40 hours a week.
Daniel LewisForex Signal
Scaled with us through three growth stages.
Ron Shai & SlavaFEPO Corporation
Crafted a mobile experience that feels premium and calm.
James CurrieBirding Expert
The polish on this release is unreal.
Ghedalia GoldPuzzable Game

Trusted by businesses across 92+ countries.

FAQ

Questions about the money.

QWhy publish a range instead of a price?
Because a fixed price quoted before seeing the code is either padded or a trap, and both end badly. The audit is fixed-price precisely so that everything after it can be quoted against evidence rather than assumption.
QWhat determines where in the range we land?
Mainly whether you take payments, what data you hold, and how much backend already exists. Those three account for most of the spread — the full list is on this page.
QDo you charge for the initial conversation?
No. The first call is scoping — what you built, what it does, what is worrying you. We charge from the audit, which is where actual engineering time starts.
QHow do you bill?
The audit is fixed price. Rescue work is fixed price against the findings, so the scope is agreed before it starts. Rebuilds bill against milestones. Retainers are monthly, from 3 months.
QWhat if the audit says we do not need you?
Then it says so, and you have a report confirming it for a fraction of what the work would have cost. That is a good outcome — the alternative is us selling remediation nobody needed.
QCan we do the fixes ourselves after the audit?
Yes. The report is written to be handed to any competent engineering team, with each finding carrying enough evidence and reasoning to act on without us. A meaningful number of clients do exactly this.
QDo you offer escrow or milestone protection?
For rebuilds, yes — milestone billing is the default and escrow is available on request. For an audit the amount rarely justifies the overhead, but we will if you prefer.
Before you share anything
Your IP · 100% yours, in writing

Nobody has ever regretted sending us their repository.

Handing private code to anyone is a real decision, so everything below is settled before the audit starts rather than on request.

  1. An NDA is signed and returned before you send a linkStep one, every time
  2. Access is read-only, scoped to one repository, and time-boxedRevoked on delivery
  3. Our copy of your code is deleted when the report landsNothing retained
  4. We build for clients and never launch anything that competes with themNever has happened
No-obligation diagnosis

Send us the repository. We'll tell you what's missing.

Fixed price, 72 hours to findings, and a report you can act on with or without us. Nothing is committed until you have read it.

NDA signed before you send anything · read-only access, revoked when the report lands · our copy deleted on delivery.