Practical guide / Build or buy: choosing business software

Build, buy, or fix the process first?

A new tool can be the right answer, but only after you can name the work it must support. Use this sequence to compare an existing product, a connection between tools, and a focused custom build.

When to use this

Start with the decision in front of you.

Use this when spreadsheets and manual work are causing friction, or when several software options promise to solve the same problem.

Decision steps

A practical sequence.

  1. 01

    Describe one real workflow

    Follow a request from arrival to completion. Record who touches it, what information changes hands, and the exceptions that force people outside the normal path. A vague need for 'one system' is not enough to evaluate software.

  2. 02

    Check the tools you already have

    Ask whether an existing product can handle the workflow with configuration and training. Include permissions, reporting, and what happens when the process does not fit its default model.

  3. 03

    Price the whole operating decision

    Compare setup, licenses, data migration, support, staff time, and the cost of workarounds. A custom build also needs hosting, security ownership, and a plan for future changes.

  4. 04

    Choose the smallest reversible test

    Trial one workflow with representative records and users. If it works, expand deliberately. If the critical exception still requires a spreadsheet, decide whether integration or a narrow custom tool is justified.

Illustrative scenario, not a client case study

See the decision in context.

An estimator records requests in a form, prepares quotes in a spreadsheet, and waits for owner approval by email.

Decision to test. The team could first test whether its current system supports draft quotes and approvals. If it does not, a focused approval tool may be more useful than replacing the whole CRM.

First action. Map the fields, approval rules, and source of truth before requesting a software proposal.

Take to your team

Questions worth answering.

  1. 01Which exception breaks the current process most often?
  2. 02What can the current tools already do with better configuration?
  3. 03Who will maintain the workflow after launch?

Bring us the workflow.

On a founder call, we’ll map one problem and discuss what a useful first step could be.