TJ Slade
Web designer · Kansas City
Here is a business I meet about once a month. Leads come in through a form tool. Somebody copies them into a CRM. Jobs get scheduled in a second app that does not talk to the CRM. Invoices go out from a third. A spreadsheet ties it all together, and one person on the team is the only one who knows how. The monthly bill is somewhere north of four hundred dollars, and the actual process is copy and paste. I'm TJ Slade, I do custom development for small businesses, and a surprising amount of that work is replacing a stack like that with one small tool built to do exactly the job.
This post is about when that is the right call, when it is not, and what it honestly costs. Because the answer is not always build it. Sometimes the answer is that you are using the software wrong, and I would rather tell you that for free than bill you for something you did not need.
The subscription stack, and why it grows
Nobody plans a stack of six tools. It happens one reasonable decision at a time. You needed a form, so you signed up for a form tool. You needed to track leads, so you added a CRM. Scheduling came next, then invoicing, then a Zapier account to glue the pieces together, then a spreadsheet for the reporting none of them do. Each one was the right choice on the day you made it.
The cost shows up in three places, and only one of them is the credit card statement. The second is the time somebody spends moving data between tools by hand, usually the owner or the one person who understands the whole system. The third is the errors: the lead that never got called back because the copy step got skipped, the invoice that went out with last month's price. Those are the expensive ones, and they never show up on a bill.
What a custom internal tool actually is
The phrase sounds bigger than it usually is. An internal tool is a small web app that only your team uses, built around the way your business actually works instead of the way a software company guessed most businesses work. It has a login, a database, and a handful of screens that do the specific things you need. Nothing else.
Some examples of tools I have built or scoped for small businesses, to make it concrete:
- A quote builder for a gym that sells equipment too heavy for normal shipping. The customer picks sizes, the tool works out freight from the real carrier, and the owner gets an order instead of a phone call and a spreadsheet.
- A booking page tied straight to a Google Calendar, replacing a scheduling subscription that did the same job for forty dollars a month and looked like somebody else's product.
- A job tracker for a service company: intake form, status board, automatic text to the customer when the job moves, and a weekly report to the owner. It replaced a CRM, a texting tool, and the spreadsheet.
- A client portal where a customer can see where their project stands, what is due from them, and every document in one place. That one runs my own business, and it is the page my clients open most.
None of those is a big piece of software. Each one is a few screens that do one workflow properly, which is the whole point.
When building beats subscribing
A custom tool is the right answer when most of these are true:
- The process is specific to your business and no off-the-shelf tool matches it without workarounds.
- Somebody spends real hours every week moving data between tools by hand.
- You are paying for three or more subscriptions to run one workflow.
- The workarounds cause mistakes that cost money or customers.
- You are paying per user or per contact, and the bill climbs every time the business grows.
- The process is stable. You have run it the same way for a year and it works, it is just slow.
That last one matters more than people expect. Custom software is for a process you understand. If you are still figuring out how you want to run things, keep using the flexible tools until you know.
When you should keep the subscription
I turn down about as many of these projects as I take, and here is why:
- The software works and you just have not set it up properly. Most CRMs and scheduling tools do far more than their users ever turn on. An afternoon of configuration beats a build every time.
- The job is accounting, payroll, or anything with legal or tax rules behind it. Let the software company carry that liability. You do not want a custom invoicing tool when the sales tax rules change.
- You need it to do many different things for many different people. Off-the-shelf software is good at breadth. Custom tools are good at depth.
- The process changes every month. Custom software is fast to use and slow to change. Flexible tools are the opposite.
- The total subscription cost is under a hundred dollars a month and nobody is losing time to it. Leave it alone.
The honest test is this: if I set up the software you already pay for, properly, would the problem go away? If yes, that is what I will tell you to do.
What it costs, and when it pays back
A small internal tool, meaning a login, a database, and a handful of screens for one workflow, usually lands between a few thousand and the low five figures, depending on how many systems it has to connect to. Connecting to a payment processor, a calendar, or a texting service each adds work. A tool that replaces three or four subscriptions and a spreadsheet is typically in the middle of that range. I put the numbers I can put in public on the pricing page, and a real quote comes after a conversation about your process, not before.
The payback math is simple, and I will do it with you before anything gets built. Add up the subscriptions the tool replaces. Add the hours somebody spends on the manual steps, at what their time is worth. Add a rough number for the mistakes. If that total does not pay for the build inside about two years, do not build it. Most of the projects I take pay back in under one.
Two costs people forget. Custom tools need hosting, which for something this size is usually a small monthly number, not a server bill. And they need someone to fix them when a connected service changes its API, which happens a couple of times a year. I host and maintain what I build, and that is a line item, not a surprise. It is the same idea as website maintenance, applied to a tool.
How the build actually goes
The first step is not code. It is me watching you do the process, ideally on a screen share, while you narrate. Every workaround you have stopped noticing is a requirement. Then I write it up in plain English, one page, and you tell me what I got wrong. That page is what gets built, and it is what the price is based on.
The build itself is small screens, shipped one at a time. You use the first one while I build the second. That catches the things nobody thought to mention, because you only notice them when you are using the real thing with real data. A tool for one workflow is usually a few weeks, start to finish, including the part where your team tries to break it.
At the end you own it. The code, the database, the hosting account. That matters for the same reasons owning your website matters: if you and I part ways, the tool keeps running and any developer can pick it up.
If you are wondering whether this is you
Write down every tool you pay for, what it costs, and the one thing you actually use it for. Then write down every step somebody does by hand between those tools. If the second list is longer than the first, send me both. I will tell you which subscriptions to set up properly, which to cancel, and whether there is a tool worth building. That conversation is free, and about half the time it ends with no build at all.