The hidden cost of building a product from your consultancy is the client work you stop doing while it gets built: your day rate, multiplied by every hour the project takes away from billing. It is the largest line in most of these budgets and it appears in none of the quotes. If you have gathered prices from development studios, looked at no-code platforms and built a rough spreadsheet, you probably think you know what this will cost, and you probably do not.
Part of our guide to productisation.
Skipping that calculation is how a familiar story plays out. A founder commits to the build on the strength of the development quote, finds the project absorbing far more of their week than planned, and reaches the second year with a half-finished product and an income that has fallen by more than anybody budgeted for. Nothing went wrong with the software. The plan simply left out the largest number in it.
In this blog, Elliott Prince, Managing Director at Ferrous Labs, explains why your own time is the cost that matters most when you build a product, how to put a figure on it before you commit, and why cheaper AI development makes that figure more important rather than less.
Why does development cost feel real but your time feel free?
A development invoice is concrete. Somebody sends it, you pay it, and it appears in your accounts. Your foregone client revenue leaves no trace at all, because nobody invoices you for the work you did not take on while you were writing specifications and sitting in reviews. So when consultants budget for a product, they tend to treat the build as the cost and their own time as overhead, or worse, as free.
It is not free, and the numbers get large quickly. Take a consultant billing £1,000 a day across 180 days a year. If the product takes 30% of their working time for eighteen months, the billing they give up comes to around £81,000. That figure often exceeds the development quote, sometimes comfortably, and unlike the quote it keeps costing you afterwards: the clients you turned away in the first year are not the ones recommending you in the second.
There is a subtler cost as well, which is divided attention. A founder who is half consulting and half building is rarely at their best in either role, and the product needs them at their best. The methodology lives mostly in the founder's head, full of judgement calls and exceptions that seem obvious until somebody tries to encode them. Getting it out of your head and into working software takes weeks of discovery before any code is written, availability for questions throughout the build, and testing not just for bugs but for whether the software produces the outcomes your service does. None of that is in a development quote, and all of it gets squeezed into whatever gaps the client work leaves.
How do you actually run the numbers?
The calculation itself is simple. Start with your realistic annual billing: your day rate multiplied by the days you genuinely bill, not the days you intend to. Estimate, honestly, what share of your working time the product will take across every phase, from discovery and build oversight through testing, launch and the early sales that only you can make. Multiply the two together and you have your annual opportunity cost.
Then you need a duration, which is where most estimates go wrong, and the next section is about why. Multiply your annual opportunity cost by how long the project will run before the product earns enough to replace what you gave up, add the development cost, and that total is what the project actually costs you. Be realistic about the development figure as well: first quotes tend to grow, for reasons our piece on the hidden expenses in a SaaS build sets out.
For most consultancies the result is sobering rather than prohibitive. The product usually still makes sense, provided its own economics hold up as well, which is the subject of our piece on SaaS unit economics for consultancies. The difference is that the founders who come through it well know the real figure before they commit, rather than discovering it halfway through, when client revenue has dropped and the bank balance is doing something nobody planned for.
The clock starts long before the revenue does
Your opportunity cost starts running on the first day of discovery. The product's revenue starts on the day somebody first pays for it, which is after the build, and after however long it takes to find that first customer. Then it has to grow, and the evidence on how quickly software revenue grows is worth sitting with before you put a number into the calculation.
The most useful recent evidence is ChartMogul's 2025 SaaS Growth Report, produced with Kyle Poyar, which followed 6,525 software companies from their first revenue onwards. Only 3.3% of them reached $1 million in annual recurring revenue within a year of first being paid. Within three years it was 13.4%, and within five years 25.1%. That milestone is a long way above what you would need to replace a consultant's lost billing, so I would not read the figures as a forecast for your product. What they show clearly is the shape of the thing: once a software product starts earning, growth is measured in years, and even the companies that do well rarely do it quickly.
So when you choose a duration for your own calculation, count in years rather than months, and remember to add the build period on top, because that is time you are paying for before the revenue clock has started at all.
Does cheaper AI development change the equation?
It changes one part of it, and that part is real. When we worked with Jason Nguyen on AskPhi, he had already built a working prototype of his behavioural-science product himself with Claude Code, and we took that to a production platform with paying clients in three months. A consultant building his own working prototype is the change in a single sentence. Builds are genuinely getting faster and cheaper, and that matters.
What it does not do is reduce your opportunity cost. If anything it makes your time a larger share of the total. Suppose the product in the example above was quoted at £60,000 to build. Against £81,000 of foregone billing, your own time is already 57% of the £141,000 the project really costs. Cut the build by a third, to £40,000, and your time becomes 67% of the total. The build got cheaper; the project became more dependent on you. That is the part of the AI productivity story consultancies rarely hear: as build costs fall, building a product does not simply get easier, it becomes more founder-constrained.
It is also why the partnership model deserves a serious look. If a technical partner co-builds the software and shares in the upside rather than charging a flat fee, the development cost turns from a cash outlay into a share of future revenue. That does not remove your opportunity cost, but it changes the risk: you are no longer writing large cheques upfront against an income that, as the figures above suggest, may take years to arrive.
Put the real number on the table before you commit
It is easy to put this calculation off, because the development quote feels like the decision and your own time feels like something you will manage somehow. That is exactly the assumption that leaves founders a year in with a stalled product and a thinner order book, and it costs nothing but an afternoon to test it.
So do the arithmetic this week, on your own numbers. Work out your opportunity cost over a duration measured in years, add the build, and look at which half is larger. If the build is more than half the total, it is the dominant risk and the estimate deserves hard scrutiny. If your own time is more than half, which it usually is, then that is the real constraint and it needs a plan of its own: fewer client commitments, a hire who takes delivery off your desk, or a build partner whose approach asks fewer of your hours.
Founders who do this go into the build knowing what it will really take from them, and they plan for it rather than discovering it. That is the difference between a product that gets finished and one that is still waiting for the founder to find the time.
Ready to turn what you know into a product?
Our AI Product Build track builds your first recurring-revenue product with you, and it is yours to own, without hiring a product and AI team.
See AI Product Build Talk to a co-founder →Not sure where AI fits in your business?
The AI Opportunity Finder maps your highest-value starting point in a few minutes, with no sales call required.
Find your best starting point