Software Should Adjust to the Business. Not the Other Way Around.
This is a principle I have held for more than 25 years of software work: the business defines the tool. The tool does not define the business. When a company adopts software that forces it to change how it operates — how it handles customers, how employees do their jobs, how data moves through the organization — that is a red flag, not a feature.
Sometimes those changes are minor and worth the tradeoff. Sometimes they are significant and nobody fully accounts for the cost until after the contract is signed, the migration is done, and the complaints start coming in. The decision about which software to use deserves more rigor than most businesses give it — and that starts with bringing in someone who has seen this play out enough times to know what questions to ask.
Three Options — and SaaS Changed the Math on All of Them
For most of software history the decision was binary: buy something off the shelf or build something custom. Off the shelf was faster and cheaper upfront. Custom was more expensive but fit the business exactly. SaaS added a third lane — subscription-based software delivered over the internet — and it changed the equation in ways that are still being sorted out.
SaaS lowered the barrier to entry dramatically. Tools that used to require significant upfront investment are now accessible to small businesses for a monthly fee. That is genuinely good. But it also made it easier to adopt software quickly without fully evaluating whether it fits — because the commitment feels lower when it is month-to-month. The commitment is actually higher than it looks, because data migration, training, and process change are expensive no matter what the contract says.
- Off the shelf — fast to deploy, lower upfront cost, limited flexibility
- Custom — fits the business precisely, higher upfront investment, owned long term
- SaaS — low barrier to entry, ongoing cost, vendor-dependent, often more flexible than traditional off the shelf
The Real Cost Is Not the Software — It Is What Changes Around It
When a business adopts software that does not quite fit, the cost shows up in predictable places that are rarely accounted for in the original evaluation. Employees adapt their workflows to work around the software’s limitations. Processes get modified to match what the system expects rather than what the business actually needs. Customer-facing interactions change — sometimes visibly — because the software handles things differently than the previous system did.
These are not hypothetical risks. They are what happens in the majority of software implementations that are evaluated and selected without adequate expertise involved. The software works. The business adjusts. And six months later someone is asking why the team is spending so much time on manual workarounds or why customers are complaining about something that used to be seamless.
- Employee time spent working around limitations rather than doing their actual job
- Process changes that introduce friction where none existed before
- Customer experience degradation that is hard to trace back to the software decision
- Data migration problems that surface weeks or months after go-live
- Integration failures between the new software and existing systems
Bring In an Expert Before You Commit — Not After
The most valuable time to bring in outside expertise is before the software decision is made — not during implementation, and certainly not after something has gone wrong. An experienced consultant who has worked across multiple platforms, industries, and software types can evaluate options in ways that an internal team typically cannot, simply because they have seen more of what can go wrong.
That expertise does not have to mean a lengthy engagement. Often the most valuable work is a focused evaluation — looking at what the business actually does, where the current system is failing, what the real requirements are, and whether the software being considered actually meets them. That conversation, done well before a vendor is selected, saves more time and money than almost any other investment in the process.
The cost of getting it wrong is almost always higher than the cost of getting expert input before you commit. That is true whether the decision is a $50/month SaaS subscription or a $500,000 enterprise platform.
Frugal First — But Frugal Does Not Mean Cheap
My default position has always been to look for the simplest, most cost-effective solution that actually fits the need. Open source where it makes sense. Off the shelf where it fits well. SaaS where the flexibility and ongoing development justify the subscription cost. Custom only where nothing else reliably closes the gap — but when custom is the answer, it is usually clearly the answer.
Frugal does not mean accepting software that does not fit. It means not overspending on complexity you do not need, not paying for features that will never be used, and not committing to a platform because it is the biggest name in the category. The right software for a 12-person professional services firm is almost never the same software that is right for a 500-person manufacturing operation — even if both are being sold the same product.
SaaS Creates Flexibility — and New Risks Worth Understanding
SaaS has genuinely changed what is possible for smaller businesses. The ability to access well-built, continuously improved software on a subscription basis — without the overhead of hosting, maintenance, and version management — is a real advantage. It has also made software development companies more flexible in how they deliver solutions, including hybrid approaches that combine SaaS platforms with custom layers built on top of them.
But SaaS introduces risks that off-the-shelf and custom software do not carry in the same way. Your data lives on someone else’s infrastructure. Pricing can change. Features can be deprecated. The vendor can be acquired. The platform can pivot in a direction that no longer fits your business. None of these are reasons to avoid SaaS — they are reasons to evaluate it carefully and make sure the fit is real before the dependency grows.
- Understand where your data lives and what happens to it if you leave
- Evaluate the vendor’s stability and track record, not just the product
- Know what the exit process looks like before you need it
- Consider whether a custom integration layer reduces your dependency on any single platform
Signs You Need Outside Input Before Making a Software Decision
Not every software decision needs outside help. Replacing a tool with a clear equivalent, adding a simple SaaS subscription for a single-purpose need, or upgrading a platform you already know well — these are often straightforward. But if several of the following are true, it is worth a conversation before you commit.
- The software will touch multiple departments or significantly change how employees work
- You are evaluating options and are not sure how to compare them against your actual requirements
- The vendor is telling you that your current process needs to change to fit their system
- You are migrating data from an existing system and are not sure what that involves
- The decision involves a multi-year commitment or significant upfront cost
- A previous software implementation did not go as planned and you want a different outcome this time
Talk Through the Decision Before You Make It
Whether you are evaluating platforms, considering a custom build, or trying to figure out why your current software is not working the way it should — a focused conversation is usually the best place to start.
Contact Me