Internal tool or another SaaS subscription? How to decide

Every growing team hits this fork: a workflow has outgrown the spreadsheet, and now you’re choosing between another monthly subscription or building something of your own. Both can be right. Here’s how we decide — quickly, without dogma.

Default to buying

Let’s be clear up front: buy first. If a mature product does ~80% of what you need at a sane price, buy it. You get maintenance, security, updates, and someone else’s roadmap for less than the cost of a single developer-week. Custom software is a liability you own forever; only take it on when it earns its keep.

So the real question is: when does buying stop being the obvious answer?

The four questions

1. Is your process the product, or a commodity?

If the workflow is a generic thing every business does — email, accounting, CRM, support inbox — buy it. If the workflow is your edge — the specific way you quote, route, price, or fulfill — off-the-shelf tools will force you to work like everyone else. That’s when a small custom tool pays for itself.

2. How many seats, and at what price?

Per-seat SaaS is cheap at 3 people and brutal at 50. Run the three-year number, not the monthly one. A $40/seat/month tool across 30 people is ~$43,000 over three years — often more than a focused internal tool that does exactly your job and nothing else.

3. How much glue are you paying for in people?

The hidden cost of “we’ll just use three tools” is the human moving data between them. If someone is re-keying or reconciling across apps, you’re already paying for custom software — in salary, monthly, forever. A small integration or internal tool usually costs less than the glue work it removes. (We’ve written about exactly this.)

4. Can you live inside their constraints?

Every SaaS has opinions: its data model, its limits, its export story. If you’re constantly fighting the tool — workarounds, spreadsheets-on-the-side, “we don’t use that field for what it says” — the tool is no longer saving you time. That friction is a signal.

A simple scoring rule

Give one point for each that’s true:

• The workflow is a competitive edge, not a commodity.
• Seat-based pricing is getting expensive at your size.
• A person is paid to move data between tools today.
• You’re actively fighting an existing tool’s constraints.

0–1 points: buy, and don’t look back. 2 points: buy, but automate the glue between tools. 3–4 points: a small, focused internal tool is likely cheaper and better — build it.

If you build, build small

“Custom software” doesn’t mean a platform. The best internal tools do one job the team does daily, with a boring, reliable interface. Start with the single most expensive step (your bottleneck audit will name it), ship that, and stop. You can always add the second thing once the first earns trust.

The goal is never “build vs. buy.” It’s “spend the least to remove the most cost.” Sometimes that’s a subscription. Sometimes it’s two hundred lines of code.

Not sure which side of the line you’re on? Tell us about the workflow and we’ll give you a straight answer — even when the answer is “just keep paying for the SaaS.”