Skip to content
Sean Marroquin
Esc
  • HomePage
  • WorkPage
  • AboutPage
  • Start a projectPage
  • How this site is builtPage
  • BlogPage
  • DownloadsPage
  • Client PortalClients
  • PhysicalCount for Limitless POSCase study
  • The Listening RoomCase study
  • CelebrationsCase study
  • Teen Arts AmbassadorsCase study
  • TerraLoopCase study
  • The HollowCase study
  • ListoCase study
  • PasslineCase study
  • DeadBoltCase study
  • DesklingCase study
  • AccuBetsCase study
  • UnwrittenCase study
  • Getting found locally: what actually matters for a small businessPost
  • Getting your point of sale to talk to everything elsePost
  • How to do a physical inventory count without closing the storePost
  • What does custom software cost? What actually drives the pricePost
  • Custom software or off-the-shelf? How to tell which your business needsPost
  • How this site is builtPost
  • Why every client gets a portalPost
  • Switch between light and darkAction
  • Copy my email addressAction
  • PWNTT ArcadePlay
  • Play The Deploy TrailPlay
  • Play Merge ConflictPlay
  • Play Code ReviewPlay
  • Play BacklogPlay
  • Play Standup SurvivorPlay
  • Play Scope CreepPlay

Use the arrow keys to move and Enter to open.

All posts

Custom software or off-the-shelf? How to tell which your business needs

4 min read

I build custom software for a living, and the first thing I tell most people who ask about it is that they might not need it. Off-the-shelf tools are cheaper, ready today, and improved by someone else every month. If one fits, use it.

The trouble is that "fits" is hard to judge from inside a busy week. Here is the test I use with the businesses I talk to.

Start with what you can buy

Booking, invoicing, point of sale, email marketing, scheduling, and a basic website are solved problems. There are good products for each, and most of them cost less a month than an hour of a developer's time. If your business works the way most businesses in your trade do, the software built for that trade will usually serve you well.

Before anything custom, try this:

  1. Write down the job, not the feature. "Customers can book a cleaning and get a reminder" rather than "a booking app". Jobs are easier to match against products.
  2. Trial two or three products against those jobs. Most offer a free trial. Use real data for a week, not the demo.
  3. Check the settings and the integrations page. A surprising amount of "it can't do that" turns out to be a setting, or a connection to another tool you already pay for.

If one of them does the jobs, stop there. You have saved yourself a project.

Signs you have outgrown it

Custom software starts to make sense when the gap between the tool and the business shows up every day. The patterns I see most:

  • The same data is typed in twice. An order goes into the point of sale, then into a spreadsheet, then into the accounting system. Every copy is a chance for a mistake and an hour someone does not get back.
  • The spreadsheet has become the system. It has tabs only one person understands, and the business stops when that person is on holiday.
  • You pay for three tools to do one job, and still fill the gaps by hand.
  • Customers keep asking the same question, like "where is my order?" or "is this done yet?", and the answer lives in someone's inbox.
  • The way you work is the advantage. If your process is why customers pick you, bending it to fit generic software gives that away.

One of these on its own is usually a nuisance, not a project. Two or three together, every week, usually cost more in time and mistakes than building the right thing would.

Custom does not have to mean starting from scratch

The most useful projects are often small. A few that come up again and again:

  • A connection between tools you already have, so an order or a count flows from one system to the next without anyone retyping it.
  • A portal for your customers, where they can see progress, approve a quote, or pay, instead of emailing to ask.
  • An internal tool for one job, like stock counts on a phone, built around the database your point of sale already uses, with nothing to migrate.

Each keeps the off-the-shelf parts that work and replaces only the part that does not. That keeps the cost down and the risk small.

What to ask before you commit

Whoever you hire, these questions protect you:

  • Will I get a written scope and a fixed price before work starts? If the answer is "we will see as we go", expect the invoice to be a surprise.
  • Who owns the code and the data? It should be you.
  • What happens after launch? Hosting, backups, security updates, and small changes all need an owner. Ask what that costs per month.
  • Can I see something working early? A rough version you can click in the first weeks beats a polished demo at the end.
  • What will you not build? A good developer will talk you out of the parts you do not need.

The short version

Buy software when it does the job. Build when the workaround has become the job. And when you are not sure which side of that line you are on, a short conversation with someone who has run a business and built for them is usually enough to tell.

If you would like that conversation, tell me what is slowing you down. I will tell you honestly whether you need me.

Want the next one? Subscribe by RSS.