When a Connecticut Business Actually Needs Custom Software

Every few weeks someone asks whether they should have software built for their business. Most of the time the honest answer is no, not yet. Off-the-shelf tools are cheap, they are maintained by someone else, and they cover the common cases well. Building something custom means owning it forever.

But there is a point where the math flips, and it is usually later than software salespeople say and earlier than most owners realize. Here is how to tell where you are.

The three signals

1. A person is the integration. You have two systems that both hold the truth, and somebody spends part of every week copying data from one into the other. The estimating tool does not talk to the accounting software, so an office manager retypes the numbers. That person is not doing data entry. They are being paid to be an API.

The cost is not just their hours. It is the errors that come from retyping, and the fact that nobody can answer a simple question without opening three tabs.

2. Your best process is the one no product models. Every industry has standard workflows, and there is software for all of them. If your business runs on a standard workflow, buy the standard product. But some businesses have one process that is genuinely theirs, and it is usually the profitable one. When you are bending a general-purpose tool badly to fit the thing you actually do well, you are paying a tax on your own advantage.

3. The subscriptions passed the build cost. Add up every per-seat license you pay monthly, including the ones you forgot about. Multiply by three years. Compare that to a fixed build. Sometimes the tool still wins, because it ships updates and you do not maintain it. Sometimes it does not, and nobody ever ran the numbers.

When the answer is still no

If you are under five people, buy the tool. If a product exists that does eighty percent of what you need, buy the tool and live with the twenty. If your process changes every quarter because the business is still finding its shape, buy the tool, because custom software freezes decisions and you are not ready to freeze anything.

And if the reason you want something built is that the current tool is annoying rather than expensive, that is not a business case. Annoying is survivable.

What to ask before anyone starts

Whether you hire us or someone else, these are the questions that decide whether the project goes well:

• What happens if you disappear? Ask who holds the code, where it lives, and whether you can hand it to another developer tomorrow. If the answer is vague, stop.
• What does year two cost? Software is not a purchase, it is an obligation. Hosting, updates, and the occasional broken integration are real line items. Anyone who tells you the number is zero is hiding it in a subscription.
• What is the smallest version worth building? The correct first version handles one workflow completely rather than every workflow partially. It should be in real use within weeks, not quarters.
• Who owns the data, and can you export it? You should be able to leave with everything, in a format another system can read, without asking permission.

These overlap with the questions worth asking any developer before you hire them, and for good reason: the failure modes are the same.

The middle path most people miss

There is a lot of ground between "buy a subscription" and "build a platform." Often the right answer is a small tool that sits beside the software you already pay for and does the one thing it cannot: a form that writes into two systems at once, a report that assembles itself, a scheduler that respects the actual rules of your trade.

That kind of work is measured in weeks, and it removes the person who was acting as the integration. It is usually the cheapest useful thing anyone can build for you.

We do this for businesses around Danbury and Fairfield County, and what that work looks like is here. If you want to talk through whether your situation is a buy or a build, tell us what the workaround looks like and we will tell you honestly which one it is. If it turns out you mostly need a website that works, that is a different and much cheaper conversation.