Do I need a custom app or will off-the-shelf software work?

Short answer: start with off-the-shelf software if a product already does most of what you need. It's faster to set up and someone else maintains it. Custom software is worth it when the workarounds cost you real time every week, when your process is part of what makes your business better, or when your tools don't talk to each other. Often the best answer is in between: a small custom piece that connects or extends the tools you already have.

I build custom web apps, mobile apps, and industrial software, and the first thing I do on most calls is check whether an existing product would solve the problem. Sometimes it would, and the honest answer is to go buy it. Here's the framework I use to decide, so you can work through it yourself before you talk to anyone.

Start with off-the-shelf

Off-the-shelf software has real advantages. You can usually start the same day, it's been tested by thousands of other businesses, and the vendor handles hosting, security, and updates. For standard jobs like accounting, email, scheduling, and payroll, it's almost always the right call. There's no reason to build your own accounting system.

A useful rule of thumb: if a product handles most of what you need and the missing pieces are minor, adapt your process to the tool. It's cheaper than adapting a tool to your process.

Signs off-the-shelf no longer fits

Things change as a business grows. These are the signs I hear most often from owners who have outgrown their tools:

• Spreadsheets hold everything together. Data gets copied from one tool into a spreadsheet, then into another tool, by hand, every week.
• The workaround is the process. Your team has a list of tricks for making the software do something it wasn't built for, and new hires need to learn them all.
• You pay for a lot you don't use. You're on an expensive plan for one feature, or paying per user for people who only need to see one screen.
• Your tools don't talk to each other. Customer details live in three places, and none of them agree.
• Your process is your advantage. The way you quote, schedule, or track work is part of why customers choose you, and generic software flattens it.
• You can't get your data out. Reports you need aren't available, or exporting your own data is difficult.

One or two of these might be livable. If several sound familiar, it's worth adding up how many hours a week the workarounds cost. That number is often the clearest argument for or against building something.

The in-between options

Custom doesn't have to mean replacing everything. Before building a full app, consider these:

Configure what you have

Many tools are more flexible than they look. Custom fields, automations, and templates can close a surprising number of gaps. Check what your current plan supports before you assume it can't be done.

Connect your tools

If the real problem is copying data between systems, an integration may solve it. Many products offer an API, which is a way for software to talk to other software. Automation services can link common tools without code, and a small custom integration can handle the cases they can't.

Build a small piece on top

Sometimes the right answer is a focused custom tool that does one job, like a quoting calculator, a customer portal, or a dashboard that pulls data from your existing systems, while everything else stays off-the-shelf.

Comparing the costs honestly

The price tag alone is misleading in both directions. Compare these instead:

The real risks of custom software, and how to manage them

Custom software isn't risk-free, and anyone who says otherwise is selling something. The main risks, and how to handle them:

• Scope creep. Projects grow as new ideas come up, and so do costs. Start with a focused first version that solves the most painful problem, use it, then decide what comes next.
• Depending on one developer. Make sure you own the code repository, hosting, and domain from day one, and ask for documentation. That way, anyone qualified can take over.
• Maintenance. Software needs updates and occasional fixes. Budget for it, the same way you'd budget for a subscription.
• Building the wrong thing. Involve the people who will use the tool every day, and test early versions with them instead of waiting for a big reveal.

What a focused first version looks like

The safest way to build custom software is to start small on purpose. A focused first version solves one painful problem well, for the people who feel it most, and leaves the nice-to-haves for later. In practice, that usually means:

• One main job, such as creating quotes, tracking jobs, or showing customers their order status
• The few screens needed to do that job, designed for the device people will actually use, whether that's a phone in a truck or a desktop in the office
• Sign-in and permissions, so the right people see the right data
• A way to get data in and out, through imports, exports, or a connection to the tools you already use
• Backups and basic monitoring from day one

Once the first version is in daily use, the next steps become obvious, because you're deciding based on real experience instead of guesses. Some owners find the first version is all they needed. Others add features over time in small, predictable phases. Either way, you never bet the whole budget on a plan that hasn't met real users yet.

Questions to ask before you decide

1. What exact problem am I solving, and how many hours a week does it cost today?
2. Have I checked whether an existing product, or my current one, already solves it?
3. Would connecting my existing tools solve most of the problem?
4. What is the smallest version that would make a real difference?
5. Who will own the code, the data, and the accounts?
6. What will it cost to maintain each year?

How I approach these projects

When someone asks me about custom software, we start with a short conversation about the problem, not the features. If an existing product fits, I'll point you to it. If custom makes sense, I give a fixed quote for a focused first version, you own the code and accounts, and we build from there based on what you learn using it.

You can read more about web apps and custom software, mobile apps, and industrial software, or tell me about your project and I'll give you an honest take on whether to build or buy.