I’ve been advocating custom software over commodity software for decades. But, I get this question a lot: how do we even start building our own software? Most business owners are immediately overwhelmed at the very thought.
Learned over 35 years: start where it hurts the most. You don’t have to build everything today and you don’t have to automate all your processes tomorrow. Start where the solution pays off the fastest. Where your people suffer the most, where customer complaints cluster, or where your bottlenecks are.
Don’t build everything; build what matters. Build your differentiation. Start with the obstinate problems that compound daily.
Craftsmen Buy Then Build
Craftsmen don’t forge their tools. They buy the best tools, then do their thing.
Same principle applies to software. Not everything needs to be custom. Email? Basic accounting? Off-the-shelf is fine. But that seven-system customer onboarding nightmare that takes hours per client? That’s where custom changes everything.
One drowning client came to us with a complex problem: it took multiple systems just to initiate, track, and expense a single job. We replaced this muddle with clarity; one orchestration layer that made all their systems sing together. At the end the problem disappeared. It wasn’t managed or improved…disappeared.
The 80/20 rule: 20% of your processes drive 80% of your differentiation. Focus there. The rest can wait, or might never need custom treatment at all.
Your Highest-Value Starting Point
Where do real problems hide? Follow the spreadsheets.
Every spreadsheet in your organization is a confession, an admission that your systems can’t handle reality. They’re requirements documents disguised as Excel files. When someone says “we track that in a spreadsheet,” they’re really saying “our software fails us here.”
Map your “sneaker net” processes. Those areas where people manually move data between systems. That’s high-cost disguised as convenience. Someone spending two hours daily on that costs you $30K+ annually in salary alone. Add the errors, delays, and opportunity cost, and that “small” problem might be bleeding six figures yearly.
Your first custom module shouldn’t be your most complex process. It should be your most expensive friction point.
Your first custom module shouldn’t be your most complex process. It should be your most expensive friction point.
Fix the right underlying problem and future-proofing works over any technology changes.
Modernize Incrementally
Phase 1: Relieve Pressure. Start with read-only integrations. Zero risk, immediate value. Build bridges between systems. Create “truth” dashboards showing what’s actually happening. One manufacturer discovered $200K in unbilled services just by connecting their project management and invoicing systems.
Automate the obvious. If someone’s copying and pasting between systems, that’s your target. Not sexy, but pays immediately.
Phase 2: Prove Value. Replace one completely broken workflow. Pick something visible, painful, measurable. Build one competitive advantage customers will notice.
Client example: quote-to-delivery process took eight days. Custom quoting tool brought it to 30 minutes. They won three major contracts in month one purely on response speed. That’s solving the right problem first.
Measure everything: time saved, errors eliminated, satisfaction gained. You’re building credibility for bigger moves.
Phase 3: Accelerate. Now you understand what works in YOUR environment. Your team trusts the process. Move faster, build bigger.
Each success makes the next one easier, cheaper, faster. That’s the compound effect of ownership. Within a year, clients typically have 3-5 custom modules running, teams are happier, and they have capabilities competitors can’t match.
Don’t Overengineer
A frequent mistake? Building for every edge case. You’re not Facebook. You don’t need to plan for a billion users.
“Good architecture isn’t about predicting the future. It’s about making change cheap when the future arrives. Build for next year, not next decade. Simple and working beats complex and perfect.”
We’ve seen companies spend $500K on “future-proof” systems that are obsolete before launch. Meanwhile, we built a client’s core operation for $80K. Five years later, it’s still running their business. Why? Because we plan for evolution.
Start Tomorrow
The best time to invest in infrastructure is 10 years ago.
So, the best time to start is now and the best way to start is to just start. Don’t need a massive budget. Don’t need to become a software company.
Pick one workflow that makes your team crazy. Map it. Fix it. Own it.
That’s how transformation begins—with one craftsman solving one real problem. Your unique business needs unique software, but it doesn’t need to happen all at once.
Start where it hurts. The rest will follow.
Next: “Beyond the Build: Keeping Software Aligned as Your Business Evolves”
How does one eat an elephant? One bite at a time.