Decision guide

Build or buy: how to decide in one meeting.

Few decisions cost more than choosing the wrong software route. Five questions, asked in one meeting, usually settle whether to buy a product, connect tools you have or build.

Bring the person who will use the tool and the person who pays for it.

Published
1 November 2026
Time needed
One meeting
You need
The user and the budget holder
Written by
The Tractionora team

The five questions

  1. What does the tool have to do on day one, in two sentences?
  2. Does a product already do most of it?
  3. Could two tools you already use be connected instead?
  4. Is this process part of how we win customers?
  5. What does the current workaround cost us each month?

Reading the answers

If a product does most of it, buy it and adapt your process a little. If connecting two tools solves it, do that. If the process is your advantage, or the workaround cost keeps growing and nothing fits, a build deserves a scoping sprint.

Start small

Even when you build, start with the smallest version that is useful and add features later. A first version in weeks teaches you more than a perfect plan, and you can stop if it does not work. Insist that you own the code, the data and the accounts.

Scope it before you commit.

Custom Software Development starts with a scoping sprint from $3,500 and a build from $15,000. You own the code, the data and the accounts.