The short answer
Buy an app first. Build something custom only when buying has stopped working.
Most small businesses can run on software that already exists. Invoices, scheduling, email, taking payments: thousands of businesses do those the same way, and someone has already built a good tool for them. Paying for custom software to do what an app does for a few dollars a month is a bad deal.
But some businesses hit a wall. They type the same thing into two systems. Their schedule lives on a whiteboard. They cannot say which jobs made money last month without losing a weekend to a spreadsheet. If that sounds like you, an app you can buy may be the wrong shape for how you work, and a program built just for your business can be the better answer.
The rest of this page helps you tell which one you are, before you spend anything.
Signs an app you can buy is enough
Buying is probably right if:
- Your work looks like everyone else's in your trade. You send quotes, schedule visits, send invoices, get paid. That is the most common kind of work, and the most common kind of app.
- You can name an app other owners in your trade already use and like. If three people you trust use the same one, start there.
- Your real problem is that things are disorganized, not that the tool cannot do it. Software will not fix a process nobody has agreed on. If every job gets handled a different way, a new program will just record the mess more neatly.
- You are still working out how you want to run things. Early on, a cheap app you can drop later is worth more than a program built around habits you might change.
Signs you have outgrown it
Custom starts to make sense when you see these, especially more than one at once:
- You type the same information in more than once. An order goes into one system, then again into your accounting. A customer's address lives in three places, and they never match.
- Your schedule lives on a whiteboard, in text messages, or in someone's head. If the person who knows where the crew is going gets sick, the business stops.
- You cannot tell which jobs made money. Revenue is easy to see. Profit per job takes a weekend and a spreadsheet, so you stop checking.
- You pay for features you never use and work around the ones you need. The app has forty buttons and the one you want is not there.
- You have bent your business to fit the software. "We can't do it that way, the app won't let us" is a sign the tool is in charge.
- One spreadsheet is the whole business. It works, until it gets too big, or one person leaves, or it breaks, and nobody knows how it works.
Try this before you pay for anything custom
A few cheap steps will tell you more than any sales call:
- Write the problem in one sentence, and what it costs you. "Re-typing orders takes about six hours a week." If you cannot say what it costs, you are not ready to pay to fix it.
- Ask two other owners in your line of work what they use. Ask what they hate about it, too.
- Try an app with your real jobs, not the demo data. Most offer a free trial. A demo always works. Your messy Tuesday is the real test.
- Keep a list of every workaround you invent. A short list is normal and fine. If the workarounds have become half the job, that is your answer.
- Check that you can get your data out. Before you commit to any app, find the "export" button. If there isn't one, the app owns your business history, not you.
What "custom" actually means
It does not have to mean a huge project. Sometimes it is one small tool that does one job: a single screen that replaces the whiteboard, or a small program that moves orders from one system into another so nobody types them twice.
It means a program made for how you already work, instead of making you work the way a program does. The slow, annoying parts stop eating your day because someone built around them.
The best custom projects start small and solve one real problem, then grow only if they need to. A big system built all at once, before anyone has used it, is how projects go over budget and sit unused.
The costs people forget, on both sides
An app you buy:
- You pay every month, for every person who uses it, for as long as you use it. Over a few years that adds up to real money.
- Switching later is painful. Your data, your habits and your staff's training are all inside it.
- The company can raise the price, change the features, or shut down. You get a notice, not a vote.
Something built for you:
- Someone has to keep it running: updates, hosting, backups, fixing what breaks. Ask who does that, and what it costs, before you start.
- Most of the early work is not typing code. It is working out how your business really runs, and that takes your time.
- You depend on whoever built it, unless you own the code and know how to get it back.
Neither choice is free. The question is which cost you would rather carry.
Questions to ask any developer, including me
Whoever you talk to, ask these. A good answer is short and clear:
- Who owns the code and the data? The answer should be you.
- Where does it run, and whose name is the hosting account in? It should be yours, so it can never be held hostage.
- What happens if we stop working together? Can another person pick it up?
- Can I see a small first version before the whole thing is built? Early and rough beats late and perfect.
- How will we know it is working? Ask for a number that should change: hours saved, errors dropped, jobs tracked.
- What happens when something breaks on a Friday evening?
If the answers are vague, that is your answer.
A middle road: buy the base, build the gap
You do not have to choose one or the other. Often the best answer is to keep the apps that already work (your accounting, your payments) and build only the missing piece between them.
For example, if an order has to be typed into your shop system and again into your invoices, a small program can pass it along so it is only typed once. You keep the tools you know and fix only the part that hurt.
When I would tell you not to build
I would tell you to buy, or to wait, if:
- An app already does most of what you need, and the rest is a small workaround you can live with.
- The real problem is that you have not decided how you want to do things yet.
- You have only a handful of jobs a week, and the pain is mostly that nothing is written down.
- You are hoping software will fix something that is really about people or habits.
If buying is the right answer, I will say so, even when it means no work for me. A client who bought the right app is better for my business than one with a program they did not need.
What to do next
Start with the cheap test above: write down the problem and what it costs you. If you are still stuck, or an app you tried does not fit, tell me what is not working. I will tell you plainly whether it is a buy, a build, or a small fix to the way you do things. Use the button below to start that conversation.