A build vs buy software decision checklist should answer one question before you sign anything: does a finished product fit how your business already works, or is the way you work the thing that needs building? Buy when a finished product fits your process with small changes. Build when your process is the advantage you sell, or when no product fits. Buy ready-made software with source code when you want a working base you can change. If you are still stuck, a software consulting review can test the options before you commit.
1Is it better to build or buy software?
The decision usually starts with a problem you can see. An order is typed into two systems. A manager rebuilds the month-end report in a spreadsheet that only she understands. Staff quietly work around a tool because it gets in the way. Each of these costs time and creates errors.
Price matters, but it is the wrong place to start. Ask where the work should live. If a finished product already runs your common tasks well, renting it is usually the quicker route. If your way of working is what wins customers, software that forces you into someone else's shape can cost more than any licence fee.
Three answers cover most cases:
- Buy a finished product when it covers most of your process.
- Build custom software when your process is the edge, or when no product fits.
- Buy with source code when you want a starting point you can change, keep in-house or hand to another developer.
2When is buying off-the-shelf software the right answer?
Buying makes sense when the product already does the job and the job is common. Look for these signs:
| Sign | What it looks like in practice |
|---|---|
| Your process is standard | Your steps match how most businesses in your sector handle the same task, such as invoicing or leave requests. |
| The vendor's plans cover your needs | The features you need are in the current product or on the published roadmap, not only promised in a sales call. |
| Staff can work with it after light set-up | You change settings, not the way people work. |
| Your data can leave | You can export records in a usable format, and you have tested that export. |
| Connections are few and standard | It links to your other tools through ordinary connections you can check before buying. |
Test the tool with your own records, not the demo data. A demo shows the best case. Your exceptions, such as split orders or credit notes, show whether it fits.
Buying also means accepting the vendor's price rises, release dates and decisions to retire features. List those risks before you sign. To see the finished products Treevoxa runs itself, start with all products.
What hidden costs come with buying off-the-shelf software?
The licence fee is rarely the whole cost. Watch for these:
- Per-user charges that grow with every hire.
- Set-up and configuration work.
- Integration work to connect the product to your other systems.
- Data migration, including cleaning old records.
- Staff training.
- Time spent on workarounds, old spreadsheets and double entry. This is often the largest hidden cost.
- The cost of leaving the vendor later, including export work and a new migration.
3When should you build custom software instead?
Custom development fits when the software has to match the business. Signs include:
- Your workflow is the edge you sell. If a competitor could run the same steps on the same tool, you would look like them.
- Staff keep changing the process to suit the tool, and you have stopped noticing.
- You must connect several existing systems, and the connections carry most of the value.
- You need to own the code and accounts, so no vendor can change the price, features or terms without your agreement.
For many owners, custom software development is the right route once the process is the edge. When Treevoxa builds custom software, you own the code and accounts. That matters most when the software becomes a core asset for years. If you are weighing a subscription against a build, custom software vs SaaS: how to choose sets out the trade-off.
Can a business with no IT department own custom software?
Yes, but ownership is not the same as running it. You need one named person who makes product decisions, and a written agreement on hosting, support and who holds the accounts from day one. Ownership on paper means little without those.
How long does custom software take to build?
Nobody can give an honest date without a written spec, because the timeline depends on scope. Treevoxa agrees written scope, a fixed price and the launch date before work starts. Be wary of any partner who names a date before reading what you need.
4What is buying with source code?
Ready-made business systems are sold with full source code. You start from a working product rather than a blank page. You can change it, keep it in-house or hand it to another developer. It sits between renting a hosted product and commissioning a build from scratch.
Browse ready-made software with source code to see what is available. Before you buy, check four things:
- Code delivered. Does the package include full source code, and is the database structure documented?
- Licence terms. Who can use, change, host or resell the code? Read the licence as a contract.
- Who can change it. Can your team or a developer you choose make changes, and does that affect support?
- What support covers. Bug fixes, security updates, hosting and training. Write each one down with response times.
A hosted subscription you cannot inspect is a different arrangement. Ask which one you are being offered.
5The build vs buy software decision checklist
Have the owner and one operations lead answer these ten questions in writing. Each answer should be a sentence giving the reason. A bare tick tells you nothing when you revisit the decision in a year.
| Question | Points to buy | Points to build |
|---|---|---|
| 1. Does a finished product cover most of the process? | Yes, most steps work with settings alone. | No, core steps need changing or extra tools. |
| 2. Do staff change the process to fit the tool? | No, the tool fits how people already work. | Yes, people have built workarounds. |
| 3. Must it connect to other systems? | Only a few, through standard links. | Yes, several systems must share live data. |
| 4. Will the data need to leave with you? | Yes, and the export has been tested. | Yes, and you need control of the data from the start. |
| 5. Is the process a competitive edge? | No, competitors run the same steps. | Yes, the way you work wins customers. |
| 6. Who supports it after launch? | The vendor, under a contract you have read. | A named partner or internal person, agreed in writing. |
| 7. How fast must it be live? | A ready product can be switched on sooner, once set-up is done. | There is time to write a spec and agree a launch date. |
| 8. Is the budget fixed or open? | A fixed monthly budget can absorb the subscription, but per-user charges and price rises still need checking. | A fixed-price build fits a set scope, with a plan for later changes. |
| 9. Who will own the product day to day? | The vendor's team, plus a named admin in your business. | A named person in your business owns decisions and the backlog. |
| 10. Would a vendor exit hurt you? | No, you could move to another tool without stopping work. | Yes, losing the vendor would stop operations. |
How to read your score
Count the answers on each side. As a rule of thumb for this checklist, seven or more answers on one side point that way. If neither side reaches seven, the answers are split. A split means you write the spec or run a short pilot before you decide.
The seven-answer threshold is a suggestion, not an industry standard, and it has not been tested against your business. Use it to start the conversation.
Some answers matter more than their count. A business whose process is its edge may find question 5 decisive, whatever the other nine say. If so, write that down and explain why.
Here is a hypothetical example. Imagine a freight company where dispatch rules are its edge and staff have built spreadsheet workarounds, while its accounts work is standard. The dispatch answers point to building and the accounts answers point to buying, so the answers split. The company writes a spec for dispatch and runs a pilot on last quarter's orders before it chooses. Your answers will differ.
Treat the checklist as a conversation tool, not a verdict. Its real value is in the places where the owner and the operations lead disagree. It cannot tell you whether a tool will fit your business, or whether a build will finish on time.
6How do you compare five-year costs?
First-year prices flatter both sides. Subscriptions look modest at the start and keep charging. Custom builds look expensive at the start and then carry upkeep. A five-year view puts both on the same line. It is long enough for recurring costs to matter and short enough to forecast with some confidence.
Use this formula, filled in with your own quotes:
Five-year cost = one-off costs + recurring costs over five years + changes over five years + internal staff time + exit cost
Fill in the table with written quotes or real estimates. Leave a cell blank until you have one.
| Cost line | Buy side | Build side |
|---|---|---|
| One-off costs: set-up, scoping, build or configuration, migration, training | ______ | ______ |
| Recurring costs over five years: annual recurring cost × 5, entered once | ______ | ______ |
| Changes and integration over five years | ______ | ______ |
| Internal staff time over five years: hours × hourly cost | ______ | ______ |
| Exit cost if you leave later | ______ | ______ |
| Five-year total: add the five rows above | ______ | ______ |
Work out the annual recurring cost in a scratch note, multiply it by five, and enter only the five-year figure. Do not add the annual figure as a separate line, or you will count it twice.
Use the software development cost calculator for a rough first view, and replace its estimates with real quotes as soon as you have them. For how build work is usually priced, see software development rates. For a fuller picture of build costs, read custom software development cost in 2026.
Get every quote in one currency, USD or CAD, and say whether taxes are included. If a vendor quotes in another currency, record the rate and the date you used. Exchange rates move, and your five-year total moves with them. Ask your accountant how sales tax applies to a subscription or a build in your case.
The buy side
Count these lines:
- Subscriptions or licences, including per-user charges that grow with every hire.
- Set-up and configuration.
- Integration work to connect the product to your other systems.
- Data migration, including cleaning old records.
- Staff training.
- Time spent changing how the team works. This is often the largest hidden cost. Staff build workarounds, keep old spreadsheets alive and enter data twice.
- The cost of leaving the vendor later, including export work and a new migration.
The build side
Count these lines:
- Scoping and the written spec.
- The build cost at a fixed price.
- Hosting and any third-party services the system needs.
- Support after launch.
- Later changes, which will come.
- The time your own staff spend on testing and making decisions.
Fill both columns, then compare the totals and the less visible lines. A lower total does not settle the decision if the cheaper side depends on a vendor you may need to leave.
7What should a written software specification include?
A spec turns the decision into something a team can quote and build. Without one, quotes will not compare, and you will pay for the gaps. Include these sections:
- Goals. Three or four outcomes that matter, in plain terms.
- Users and roles. Who uses the system, and what each role can see and do.
- The process, step by step. How the work is done now, and how you want it done.
- Data and reports. What is stored, which reports you need and how often you need them.
- Integrations. Each system involved, what data moves and in which direction.
- Security and privacy. Who can access what, and which sensitive data the system handles. Privacy rules in Canada's private sector and in some US states may apply to customer and employee data. Confirm which ones apply to you with an adviser before you write this section.
- Acceptance tests. How you will know each feature works before you pay for it.
- Budget range and launch date. State the currency, USD or CAD.
- Support. Hours, response times, and who handles changes after launch.
Treevoxa agrees written scope, fixed price and launch date before work starts, so the spec becomes the core of the agreement. If you are scoping an ERP, ERP software development covers that work in more detail.
8What should you ask before signing a contract?
Use these two short checklists.
For a software vendor:
- How is data exported, in what format, and how quickly?
- Who owns the code, the data and the accounts?
- What happens to our data if the vendor shuts down or is sold? Who holds it, in what format do we receive it, and how long do we have to move it?
- How are price rises capped, and how much notice do we get?
- What support hours and response times are included?
- How is security handled, and what can the vendor show us in writing?
For a build partner:
- Is the scope written, and is the price fixed?
- Is the launch date written into the agreement?
- Who owns the code, and who holds the hosting, domains and third-party accounts?
- How are changes requested and priced after launch?
- Which overlap hours will the team work with us? Treevoxa is a remote team and agrees overlap hours with the client.
- Who answers our calls after launch, and how fast?
Ask how you would leave before you ask anything else. If a vendor or partner cannot explain the exit, treat that as an answer in itself.
9What if the answer is still unclear?
Wait, or run a short pilot. Waiting is a real option. If the process is about to change, buying or building now may lock in the wrong shape.
A pilot tests fit with real records. Decide in advance what evidence would change your mind:
- a real quote against a written spec, not a rough estimate;
- a test with your own data, including the awkward exceptions;
- a count of the workarounds staff use during the test;
- a tested export from the vendor, not a promised one;
- the operations lead's view on whether the process should change first.
A pilot shows fit. It does not guarantee results, and it does not fix a timeline. Write the evidence down, then decide.
10Summary: the build vs buy software decision checklist
Use the build vs buy software decision checklist in this order:
- Describe the problem in one plain paragraph.
- Answer the ten questions in writing, one sentence each.
- Read the result with the seven-answer rule of thumb. If the answers split, write the spec or run a pilot.
- Fill the five-year table with your own quotes, in one currency.
- Work through the contract checklist for the option that leads.
- Send the written spec to two or three vendors or partners, and compare their answers against it.
Keep your written answers. Revisit them when the process changes, a vendor raises prices or the spec moves. A build vs buy software decision is only as good as the reasons behind it, so keep those reasons with the decision.