I want you to do me a favor before you read the rest of this.
Pull up your last serious estimate of what it would cost to build the digital product you've been thinking about. Whether you wrote it in a board prep doc, a back-of-napkin email, or just a number in your head. Find it.
Got it? Good.
Now I'm going to tell you something that is going to feel like a trick, but isn't.
That number is wrong by an order of magnitude. Not because you did the math poorly. Because the world the math was based on no longer exists.
You are running 2022 math on a 2026 economy. Almost every operating executive I talk to is doing this, and almost none of them realize it. So let me walk you through what changed, what it means for your specific situation, and what the smart move looks like from here.
The mental model that's quietly broken
Every executive at your level carries a rough internal calculator for technology projects. It was built from experience. It is mostly tacit. You pulled it from years of watching IT projects go sideways, hearing your peers talk about their digital initiatives, getting pitched by agencies, and seeing what your CFO will and will not approve.
Here is what that calculator typically says about a new digital product:
- Six to twelve months minimum to build anything credible.
- Half a million dollars at the low end. A million if it has any real complexity.
- A team of five to seven people, either hired or outsourced.
- Significant disruption to your existing operations and engineering team.
- High risk that the spec changes mid-flight and the budget balloons.
- Maybe one shot to get it right before the board loses patience.
If those are the numbers running in the back of your head, then your hesitation about your side project makes total sense. You are not being a coward. You are being a responsible steward of capital. The juice has not been worth the squeeze.
But here is the problem. That calculator is calibrated to a world that ended about 18 months ago. Nobody told it. So it is still spitting out 2022 numbers in a 2026 economy.
What the new calculator actually says
Let me re-run those same line items with current economics.
Time to build a credible v1: No longer six to twelve months. Now closer to 90 days for most B2B applications, longer if it's deeply technical, but rarely over six months.
Cost: No longer half a million. Closer to $40,000 to $80,000 for an MVP that proves whether the market wants it.
Team size: No longer five to seven. Now one or two operators using AI-assisted tooling. The work compresses because the tools compress.
Disruption to existing operations: Effectively zero, because the work happens entirely outside your organization with one outside operator.
Risk of spec drift: Dramatically lower, because the iteration cycle is so fast that you can build, ship, learn, and rebuild in the same quarter that you used to spend just writing the spec.
Number of shots: No longer one. You can now run two or three different bets in the time and budget that used to fund a single attempt.
This is not a marginal improvement. This is a step-function change in the economics of testing whether a new business idea is worth pursuing.
If you ran your bet through the old calculator and got "no," you owe yourself the favor of running it through the new one.
Why your usual advisors are not telling you this
A practical question. If this is true, why isn't your usual circle ringing the alarm bell?
A few honest reasons.
The consulting firms. They make their money on multi-quarter engagements with six-figure invoices. A 90-day, $50K project does not move the needle for them. So they are not pitching it. They will continue to pitch the version of the work that requires the version of the budget that pays their bills.
The development shops. Their model is people-hours. A project that requires one third the hours produces one third the revenue. They are quietly hoping you keep operating on the old assumptions for as long as possible.
The Chief Digital Officer track. That hire only makes sense if the work is big enough to justify the role. A project that one outside operator can finish in a quarter does not need a CDO. So the people most likely to advocate for it inside your organization are not advocating for it.
Your peers. Most of them have not built anything new in the last 18 months. They are running the same playbook they ran in 2022. They have nothing to report.
This is not a conspiracy. It is just a quiet alignment of incentives, all of which point toward you being the last one to find out.
You're not the last one anymore. Now you know.
What you should do this quarter
I'm going to keep this part short, because at this point you can probably write it yourself.
Take the idea you've been sitting on. Find one outside operator who can own the whole thing. Give them 90 days and a budget that, in the old world, would have barely paid for a strategy deck.
Tell them you want a working version of the idea, real customers using it, and hard evidence at the end about whether to scale, kill, or pivot.
That is the move. It is small. It is cheap. It is fast. It produces evidence that you can take to your board with confidence, instead of a deck full of assumptions that everyone in the room secretly knows are guesses.
That is what the new math makes possible.
The thing I want you to walk away with
You did not get to your job by being reckless with capital. The instinct that has kept your side project at "next quarter" for three years is the same instinct that has kept your business profitable. Don't apologize for it.
But the calculator in your head is calibrated to a world that no longer exists. Update the calculator. Re-run the numbers.
There is a real chance that the bet you rejected three times in three years is, in 2026, the obvious move.
Same thesis, different doorway: the number · the line-by-line walkthrough.
If you want help re-running the math on your specific idea, book a call. Thirty minutes. No pitch. Just current numbers applied to a real situation. If a 90-day build fits, we'll say so.