GuidesHow to2 min
How to choose custom vs off-the-shelf
A decision test: buy when the job is common, build when the workaround is the company, sequence a migration so you are not betting the week.
This is not a personality test. It is whether a product that already exists can run your Tuesday without a hero. If it can, buy it. If the workaround has become the company — exports, retyping, a sheet nobody trusts — custom is cheaper than another year of seats plus overtime.
SINLE Innovation Agency will tell you to buy when the job is common. We take the 20% that is actually the business and leave you the keys. We will not rebuild email so a slide can say “platform.” Pilot is a small site. Invent is a core workflow you own. If leaving the vendor kills the process, you rented a department. We will not sell you that.
Most companies need a mix. The sequence below is how you decide which 20% is worth a statement of work.
How the mix usually lands
Buy the common 80%: email, payroll, a calendar. Build the 20% that is the company: the queue, the lock, the status a customer should see. A staged move beats a rewrite. Monday still has to run on the package while the painful job moves into software you own.
If leaving the vendor kills the week, you rented a department. That is the line. Taste is not a reason to build. A hero in a spreadsheet is.
The sequence
Do these in order. Skip a line and you are back to a workshop.
- 01
Write the job the package would have to survive
If a normal tool already does 80% and the rest is taste, buy the tool.
- 02
Count the unofficial steps
Exports, retyping, a hero in a sheet. Three or more is a smell that the package is the workaround.
- 03
Price five years
Seats, overage, the integrator, the day the vendor kills the feature you need.
- 04
Ask who owns the workflow
If leaving the vendor kills the process, you rented a department.
- 05
Build only the 20% that is the business
Do not rebuild email. Extract the painful job into software you own.
- 06
Keep the package where it fits
A staged migration beats a big-bang rewrite. Monday still has to run.
Keep these
- Off-the-shelf wins on common jobs. Custom wins when the hack is the company.
- A spreadsheet is a prototype you forgot to replace — it is not a third option forever.
Do this before you spend
- 01Write the job a package would have to survive on Tuesday.
- 02Count unofficial steps: exports, retyping, a sheet. Three or more is a smell.
- 03Decide which 20% is worth a statement of work. Leave the rest bought.
Send the 20%. We will tell you to buy, to build, or that the job is not ready.
Questions
- Should we build custom software or buy off-the-shelf?
- Buy when the job is standard. Build when packages force workarounds that cost more than a scope, or you must own the workflow. Most companies need a mix.
Next how-to
- How to replace a spreadsheet with software you ownMap the real columns, agree who confirms a row, propose-then-confirm, then the sheet becomes an export — not the company.
- How to budget for custom softwarePrice the job, not a platform. Site vs workflow vs product, five-year cost, and what a $750 Spark is actually for.
- How to scope an MVPMinimum means one core workflow in a real user’s hands. It does not mean half of everything. A 90-day shape you can actually calendar.
Next
Bring the workaround. We will say buy or build.
Spark is $750. A written note: keep the package, or scope the slice you should own. You keep the note.