The key points
- Buying is the sensible default for common needs.
- Build when the thing you track does not fit a product's model.
- License costs across a growing team can tip the balance.
- Permissions and audit logging may be the deciding requirement.
When is buying clearly the right answer?
When your need is common: accounting, standard email marketing, general project tracking. The products are mature, support is included and adapting your process to one is usually quicker and cheaper than building. We say so on a first call about custom software rather than take on a project that does not need to exist.
When does building start to make sense?
Three situations strengthen the case. The thing you manage is not what the product assumes, such as school fee cycles and admissions, bookings or installations, so its vocabulary never quite fits. It is the same mismatch that makes teams ask whether they need a custom CRM. Per-seat pricing across a growing team costs more over time than owning the system. And your records need role-based access and an audit trail that a general product reserves for expensive tiers. For schools, what school management software costs to build or subscribe to sets out both routes.
What about replacing spreadsheets?
Spreadsheets are often the real incumbent. If your business runs on a set of linked sheets that people edit by hand, a purpose-built internal platform that migrates them and enforces the rules can remove errors without forcing your process into someone else's model. Count what keeping the manual approach would cost over another year, then set it against what custom software costs to build and run.
Buy compared with build
| Aspect | Buy a product | Build custom |
|---|---|---|
| Fit | Good for common needs | Good for unusual workflows |
| Cost shape | Per-seat or tiered fees | Build effort, then ownership |
| Control | Within the vendor's roadmap | Yours to change |
| Permissions and audit | Often a higher plan | Designed to your rules |
| Data migration | Import into their model | Shaped around your records |
Build-or-buy test
- Is there a product that fits at least most of my process?
- Is the record I manage something a product models well?
- What will licenses cost as the team grows?
- Do I need role-based access and audit history?
- What would manual work cost me over another year?
Sources
Rules and guidance this answer relies on. Policies change, so check the current version before acting on it.