Custom software is the most flexible option and the most expensive to own. Buying is fast but fits only where your process matches the product. Configuring what you already pay for is often enough and is usually skipped. These four steps compare the three on the same need, so the decision rests on fit and total cost rather than on a demo.

Step 1 — Define the need, not the solution

Goal: Describe what has to happen without naming a tool.

  1. Write the job in one sentence: who does what, with which information, to get which result.
  2. List the must-haves and separate them from preferences.
  3. Note the systems it must connect to and the data it will hold.
  4. Name the owner who will decide and live with the result.

You finish with: A one-page need statement with must-haves and an owner.

Step 2 — Try configuring what you have

Goal: Check whether current tools already cover the need.

  1. List the tools you already pay for that touch this work.
  2. Test the must-haves against their settings, automations and AI features.
  3. Record which must-haves are met, partly met or missing.
  4. Stop here if the gaps are small enough to live with.

You finish with: A fit table for your current tools.

Step 3 — Compare buy and build on total cost

Goal: Weigh the remaining options on fit, time and ownership.

  1. Shortlist two or three products and test them on your own examples.
  2. Estimate the build: first version, hosting, and ongoing maintenance and support.
  3. Include migration, training and integration costs for every option.
  4. Check data ownership, exit terms and who can change the system later.

You finish with: A side-by-side comparison of fit, time to use and total cost.

Step 4 — Decide and de-risk

Goal: Commit to one path with a way to check it early.

  1. Choose the option that meets the must-haves at the lowest total cost of ownership.
  2. If building, fund a fixed-scope first version rather than the full wish list.
  3. If buying, run a time-boxed trial on real work before signing a long contract.
  4. Write down what would make you revisit the decision.

You finish with: A recorded decision with a first milestone and a review point.

Common pitfalls

  • Building because the demo of a product missed one preference.
  • Comparing a product’s price with a build’s first-version cost only.
  • Skipping the tools you already pay for.
  • Signing a long contract or a full build before testing on real work.

More guides like this

Related answers

Read as Markdown Build the missing piece