Here is the math most small business owners do not run.
A 10-person service business. Landscaping, consulting, plumbing, physical therapy, marketing agency. It does not matter. The SaaS stack looks roughly the same:
Project management tool: $50-100/month. Client CRM: $100-200/month. Scheduling and booking: $50-80/month. Invoicing and billing: $30-60/month. Team communication: $80-150/month. Document and proposal generation: $30-60/month.
Total: $340-650/month. That is $4,080-7,800/year.
None of these tools were built for your business. All of them were built for the average business in your category. You adapted your workflow to fit the tool. Not the other way around.
What a custom tool actually consolidates
Be honest: you should not replace all six. Team communication tools like Slack or Teams have network effects and integrations that a custom tool will not replicate easily. Keep those.
Invoicing and billing tools connect to payment processors, handle tax calculations, and manage recurring billing. Unless your billing is simple, keep those too.
But the project management tool, the CRM, and the scheduling tool? Those three are doing variations of the same thing: tracking who needs what, when, and what the current status is. A custom operations tool built for how your specific business works can replace all three.
What the custom tool looks like
A single web application. Your team logs in. They see today's jobs, today's client appointments, and today's tasks. Each client has a profile with their history, preferences, and contact info. Each project has a status, assigned team members, and a timeline.
The scheduling view shows availability and bookings in the same place where the project work lives. No switching between three browser tabs. No copying client names from the CRM into the project tool into the scheduling tool.
The tool was built around your workflow. The fields match what you actually track. The status labels match what your team actually says. "Waiting on parts" instead of "On Hold." "Site visit needed" instead of "Pending Review."
The cost comparison
Building a custom operations tool with Claude Code in a governance sprint: $3,000-7,500 one-time cost depending on complexity.
Ongoing cost: hosting on Railway or Vercel, roughly $20-50/month.
Annual cost: $240-600/year plus the one-time build cost.
Versus: $4,080-7,800/year, every year, for tools that do not fit your workflow.
The custom tool pays for itself in the first year. In year two, you are saving $3,500-7,000 annually. In year three, the cumulative savings exceed $10,000.
What you actually own
When you build a custom tool, you own the code. There is no per-seat pricing. When you hire employee number 11, you do not pay $15 more per month. You add an account.
When your workflow changes, you change the tool. You do not submit a feature request to a vendor and wait six months. You open Claude Code and describe the change. It ships the same day.
When a SaaS tool you depend on gets acquired, changes pricing, or sunsets a feature, you are exposed. When you own the tool, you are not.
The honest caveat
Custom tools require maintenance. Someone on your team needs to understand how to make changes, or you need a relationship with someone who does. This is the trade-off: ownership requires capability. The SaaS subscription trades money for convenience. The custom tool trades convenience for control and savings.
That trade becomes worth it faster than most business owners expect.
See what we build with small businesses — we build these tools with small business owners and teach them to maintain and grow them independently.
Get posts like this in your inbox
No spam. New articles on AI strategy, governance, and building with AI for small business.