Your $30K Software Has a $300K Blind Spot
The CEO of a Top 100 firm needed new financial reporting tools for a new audit method. The vendor quote was $200,000 a year. So his team skipped the vendor and built it themselves with AI, Word, and Excel. It worked.
Another founder and CEO needed an audit solutions platform. The vendor quoted him $300,000 a year. He built his own with Claude and Retool for under $30,000.
These stories from Accounting Today sound like serious cost savings. But there’s another cost that doesn’t show up on any invoice.
We got into this on Episode 496 of The Accounting Podcast.
The one-person problem
The part of the story that gets glossed over is that the person vibe-coding the solution is often the only one who knows how it works.
Not "most familiar with it." The only person.
That's the risk of vibe-coded software.
I get the counterargument. My co-host David Leary made it to me on the show. These AI coding tools document themselves shockingly well.
Flip into ask mode, and the tool explains how a feature works, even if you never wrote a single comment. The knowledge isn't trapped in someone's head. It's trapped in the code, and the code can explain itself to anyone who asks.
In theory.
In practice, someone still has to know to ask. Someone still has to notice the thing is broken, know where to look, and trust what the AI tells them about a system they've never opened.
How many firms have built that skill? I’m guessing not many.
We found this out the hard way at Earmark
Our AI course generator runs on a Zapier workflow I built years ago. Seventy-five steps. It worked great until it didn't.
It broke, and nobody else on the team could fix it. Nobody even knew it was broken, because nobody but me was positioned to notice.
That's a no-code tool, not custom software. It still created a single point of failure. Now scale that up to an audit platform that a Top 100 firm depends on every busy season.
Think of it like the financial model nobody wants to touch
You've seen this before. Someone builds an Excel model so complex, with so many interlinked workbooks, that eventually they're the only one who understands it.
Everyone else is scared to click the wrong cell. The model works fine, right up until that person is out sick during crunch time or has left for a different firm entirely.
Vendors sell you something else along with the software: a team that maintains it, documents it, and answers the phone when it breaks. That's the actual product, not just the code.
Vibe-code your own replacement, and you get the code but skip the team. You save the fee but inherit the redundancy problem.
To be fair, buying from a vendor isn't automatically safer. We recently lost data because our podcast streaming platform’s interface was poorly designed, and its support team spent more time deflecting blame than fixing it.
There are vendor risks, too. But there's a company you can point to, a contract, and, in theory, more than one person who understands the product.
So what do you actually do with this?
If you're going to vibe-code a tool your firm depends on, keep in mind the $30,000 isn't the whole cost.
Budget for redundancy from day one. Document it properly, not with AI-generated comments buried in the code, but with a plain-English explanation a second person could follow under pressure.
Better yet, train a backup person to actually understand it, not just to ask the AI what it does.
The tools are now good enough that almost anyone can build something. They aren’t so good that just anyone can maintain what someone else built once that someone is gone.
