Buy the $99 tool or build the workflow?

Every week there is a new app that promises to fix one of your problems for a small monthly fee. Sometimes buying it is exactly the right move. Sometimes it is how you end up with five subscriptions that each do part of the job and none that finish it. Here is how I decide, and how I would suggest you decide too.

Off-the-shelf tools are genuinely good, at one job

Let me be clear up front, because it would be easy to read this as "never buy software". That is not my view at all. Off-the-shelf tools are often excellent, and the reason is simple: they do one job, and thousands of businesses use them for that same job, so the maker has had years to make it solid.

Receipt scanning is a good example. Appointment reminders are another. So is email marketing, or a booking calendar, or a password manager. These are well-defined problems that look roughly the same at every firm, and there is a mature product for each. If a tool does the job you need, fits how you work and costs less than the time you would spend building your own version, buy it. Do not build what you can buy for a hundred dollars a month. That is not clever, it is just slower.

The test is fit. Does the tool do the whole job you actually have, or most of it? If it fits, buying is the boring, correct answer.

The gap is in the connections between tools

Here is where buying stops being enough. A tool is good at its own job, inside its own four walls. What no single tool handles well is everything that happens between your tools.

Think about a normal week. A lead fills in a form. Someone has to move that into your practice software. A client sends a document by email, and someone files it and updates a checklist. A deadline approaches, and someone chases the three clients who have not replied. A number does not match, and someone has to notice and decide what to do about it. None of that lives neatly inside one app. It lives in the handoffs: the chasing, the copying, the checking, the exceptions, and all the little rules that are specific to how your firm actually runs.

That gap is where the hours quietly disappear, and it is the part no product page advertises, because no off-the-shelf tool can know your handoffs. They are yours. This is exactly the space where building a workflow earns its keep: stitching the tools you already pay for into a single path, so the work moves between them without a person carrying it by hand each time.

When building is worth it

A custom workflow makes sense in two situations, and they often overlap.

The first is when the pain crosses more than one app. If solving a problem means a human copying data out of one system and into another, or watching two places and reconciling them, you have a connection problem, and connection problems are what a built workflow is for.

The second is when the task needs judgement. Some steps are not just "move this there". They are "read this, work out what it means, and handle it". Sorting messages by what they are asking for, pulling the right figures out of a document, drafting a reply that fits the situation. This is where an AI step fits well, and where I always pair it with a human review before anything goes out. The AI does the reading and the first draft. A person checks it. You get the speed without handing over the parts that carry risk.

Beware the pile of overlapping subscriptions

Now the trap. Because tools are cheap and easy to sign up for, it is very easy to accumulate them. You buy one to solve a problem, it does about sixty percent of the job, so you buy another to cover the gap, and that one overlaps with the first. A year later you are paying for five tools that between them still do not finish the work, and you have a new job nobody wanted: keeping five separate apps in sync.

Overlapping subscriptions feel productive because you are "doing something" about the problem. But paying more each month for more tools is not the same as solving the problem. Often the honest fix is fewer tools joined together properly, not more tools sitting side by side.

The one list that tells you the truth

If you want a practical place to start, do this. Take one process that annoys you and list the manual steps that survive your current tools. Not the steps the software handles, the steps a person still does by hand: the copying, the checking, the chasing, the "then I forward it to Sarah", the "then I remember to update the sheet".

That list is the real project. Every item on it is a handoff your tools do not cover, which is precisely where a built workflow adds value. If the list is short, you are probably well served by the tools you have, and you should leave it there. If the list is long, you have found the thing worth building, and you now know exactly what it needs to do.

Buy the tool when it fits the job. Build the workflow when the job lives in the gaps. And before you sign up for one more subscription, write the list.