Twenty years ago a sixty inch flat screen cost about as much as a decent used car. Today you roll a cart past one at Walmart, stacked in cardboard six feet high, for a few hundred dollars. Nobody had to sit you down and explain that change. The price sat on a shelf, you walked past the shelf a few times a year, and your sense of what a TV costs stayed current without you ever thinking about it.
Custom software has gone through the same kind of collapse, more than once. The difference is that there has never been a shelf. Nothing in the normal run of an owner’s week shows the going rate for a build, so whatever number got into your head, however it got there, just sits and ages.
A computer shop in Amsterdam, 1984. Hardware got shelves and price tags. Custom software never did. Sjakkelien Vollebregt / Anefo, Nationaal Archief, CC0.
Where the number in your head came from
When custom software comes up in conversation, the number most owners are carrying is a big one, and it’s usually honest. It just has a date on it. For most of the 2000s and 2010s, a real web application built properly started around fifty thousand dollars and climbed fast from there. It took a team: developers, a designer, somebody to run the servers, the security, the backups. If you priced a build in that era, or watched a friend get quoted, or heard a horror story secondhand, you learned the true price of that decade, and the lesson stuck: custom is for companies with an IT department. The longer version of how this price has swung across seventy years is a story of its own, and I wrote it up here.
So when the spreadsheet starts hurting, most owners never even ask. Another thirty-dollar subscription is an answerable question, and a build feels like a number with too many digits, so it never comes up again.
If that’s you, your math was never bad. Prices moved, and a price change doesn’t send out a memo. Everyone is carrying an old number about something.
What changed
The expensive part of a build has always been skilled hours. A working application in the 2010s took hundreds of them, spread across several specialists. What AI changed is how far one experienced developer’s hour goes. Across the industry, project costs have come down by roughly a third to a half, and they have fallen hardest exactly where a small business shops: the focused, well-understood build measured in weeks, not quarters. The rest of the old cost pile shrank on its own. The machine your app runs on is the browser already in everyone’s pocket, and hosting for a small team costs less per month than the office coffee.
What a build runs today
Before the numbers, picture the thing itself. One system for the whole company: the office works from a clean desktop view, each person sees exactly what their role needs and nothing they shouldn’t, and everyone in the field carries a mobile app where the day’s jobs, checklists, and updates live. It moves the way your business already moves, because it was built around how your business moves, and a dedicated developer keeps it healthy and grows it as you grow. Now guess what that costs. Whatever number just formed, the real one probably sits under it. The price tag has moved from Gucci’s side of the street to Walmart’s, and the TV already taught you that a Walmart price can sit on a very good product.
Here are the real numbers, from my own order book and from watching the market. Most of what people hire me for is small, which surprises them. A single automation that takes one manual handoff off somebody’s plate runs hundreds of dollars, sometimes less. A focused tool that runs one part of the business, a quote builder, a digital intake flow, a scheduling board, a dashboard that pulls the numbers into one place, runs a few thousand. And a complete operating system, the app your whole team logs into every day, built around how the business actually works: the ones I’ve built have landed in the low tens of thousands, all in. My own company runs on one of those, and I opened its books so you can see the math from the inside. And if you’d rather browse these sizes like a store aisle, real examples included, I built the shelf.
Now put that against the other column. A twenty-person company paying ordinary rates rents thirty-six to seventy-two thousand dollars of software a year, every year, at $150 to $300 per person per month. Hold the columns side by side and the shape of it changes: the full owned system costs about a year of the rent, and the mid-size tool costs about a month of it. An owned build also tends to earn its keep by year two or three, faster when it retires a stack of per-seat subscriptions on its way in.
If the year-of-rent math sounds too good, run it on a house. Say your mortgage company called with an offer like this: professional builders will put up a brand new house for you, designed around how your family actually lives, for about what you pay in rent or mortgage in one year. The builders stay on call after you move in, keeping the plumbing tight, the wiring safe, and the utility bills down. When you want another room in a few years, or the layout changed, the same crew comes back, and they know every stud in the place. And the build takes a month or two instead of a year. Nobody hangs up on that call. That is close to the actual offer on the table for the system your business runs on. It only sounds unbelievable because the cost of building fell while the cost of renting kept climbing.
When renting is still the right answer
None of this is a case against subscriptions. Accounting is a solved problem and the rented tools are genuinely good at it. Payroll, the same. When an off-the-shelf tool fits a commodity job, renting it is the right answer, and if your current stack works and nothing hurts, the right move is probably to change nothing. There’s no deadline here and nothing to fall behind on.
And owning has a real carrying cost I’d rather tell you about than have you discover: software needs upkeep the way any working asset does. Things break, needs shift, a report starts looking wrong. A modest care plan belongs in the math from day one, and any quote that leaves it out is a quote for half the thing.
Finding your number
The fix for an old number is ordinary: ask somebody current. It also helps to know what your current stack really costs, and there’s a five-minute worksheet for that. Describe the job you’d want done, ask what it runs, and you’ll have a 2026 number instead of a 2015 one, whatever you decide to do with it. That’s a conversation I’m happy to have straight. Book a call, tell me how the work flows, and I’ll tell you what I’d build and what it would cost, or tell you plainly that you don’t need a build yet. And if you want to see the top of the menu in real life first, read the story of a fence and deck company that replaced six rented tools with one app it owns.
There is a shelf after all. You just have to ask somebody to walk you past it.