Skip to content
AspirecoStart
All answers

Custom software

Custom software or off-the-shelf: how do you decide?

The short answer

Buy by default, and build only the part no vendor sells. Custom starts to make sense when your price is a calculation, when your business runs on a noun no product has a table for, when per-seat cost outgrows the work, or when the integrations have become the system.

Updated

Start from buy

Payroll, card processing, email delivery, tax filing, telephony and hosting are the same problem for everyone, and someone else's roadmap is doing work you would otherwise have to fund. A useful test: if you can describe what you need without a noun specific to your trade, buy it. Even custom work sits on bought parts — Stripe takes the card, Postgres holds the rows — and only the middle that nobody sells gets built.

Four signals that flip it

  • Your price is a calculation. On Shopflooring, a room size resolves to boxes, square footage and a priced estimate, with waste applied before the box rollup. No general platform has a field for that.
  • A noun no vendor supports. A "job" sits between CRM and accounting, and neither category wants to own it. Contractor OS exists because of that gap.
  • Per-seat cost at your headcount. Subscription cost scales with people; build cost scales with scope.
  • The integrations are the system. Every connector is a promise to keep up with somebody else's API.

You rarely have to decide all at once

Replace one piece at a time: leave the incumbent running, build the piece with the sharpest edge beside it, and move its work across. Atelier is that shape — it embeds with one iframe tag, and the storefront stays where it is.

The long version, with the questions to put to your own business, is in the full guide.

Asked next

What if we decide we need custom software and we're wrong?

Then buy instead: being wrong about a subscription costs a cancellation. A good first question is what somebody in your business corrects by hand every week. The answer is usually a spreadsheet, and fairly often the honest conclusion is that you are early and should buy something for now.

What does owning custom software cost to maintain?

More than people plan for, so plan for it. Asisly, our own voice receptionist, carries seventy versioned migrations, six hundred and forty-three backend tests and thirteen scheduled jobs on a quarter-hour cadence — that is what ownership looks like written out. The return is that the assets most expensive to rebuild stay on infrastructure you own.