Guide

Build, buy, integrate or automate: a decision framework

15 min read

By . Published . Last updated . Reviewed by Mavrin Labs on . How this guide was researched and checked.

A card reading "Build, buy, integrate or automate: a decision framework" beside the Mavrin Labs logo
The card that shows when this guide is shared or linked.

A systems decision framework is a short method for choosing how to fix work that stalls between tools. Four paths are open: build something, buy something, integrate what you already have, or automate the repeat work. Choose by naming the outcome you want, finding the one step holding it up, and taking the least complex path that moves it.

The framework is written for owners running several tools whose work still stalls between them. The guide covers choosing among the four paths. Picking a product, comparing suppliers and agreeing the investment come after that choice, and are left out here.

What is a systems decision framework?

A systems decision framework is a short, written method for choosing how to fix work that stalls between tools, by naming the outcome you want, finding the step that holds it up and taking the least complex of four paths: build, buy, integrate or automate. Its output is one page.

It is not a product comparison. It decides which kind of fix fits before anyone compares products, and it ends in the decision record described later in this guide.

It is also wider than the usual build vs buy software question, because connecting or automating what a business already runs is often the smaller change.

Name the outcome and itsownerA sentence with a measureattachedFind the first constraintFollow real items and note wherethey waitTake the least complex pathBuild, buy, integrate orautomateWrite the decision recordOutcome, constraint, path,options ruled outReview on the set dateAfter the review, look for the nextconstraint
The framework as a flow: from an owned outcome to the step holding it up, the least complex path that moves it, a written record and a review. Constraints move, so the review starts the next round.

Why it matters: firms already run on several tools

Most firms already lean on software, which is why the choice of path matters. In the Census Bureau's report on its 2023 annual business survey, most businesses described cloud-based technology (59.0%) and specialized software (58.9%) as very important to their processes or methods (Census Bureau report on technology use, checked Saturday, October 10, 2026).

AI is now arriving on top of those tools. The Census Bureau's business trends and outlook survey put AI use at between 17 and 20 percent of U.S. businesses from mid-December 2025 to early May 2026 (the Census Bureau's story on AI use by firm size, checked Monday, November 16, 2026).

Each new tool is another place for work to stall unless someone decides how it joins the rest.

Why does adding tools stop helping?

Adding tools stops helping once the work stalls between them rather than inside any one. The business has a tool for customer records, one for scheduling, one for invoicing and one for messaging, and the work still waits. Somebody retypes the same details into a second system, or assembles a report by hand from three exports.

Here is an illustration, which describes no real client. An enquiry arrives on a website and lands in an inbox. Somebody reads it, copies the details into the customer system, then messages a colleague to say it needs quoting.

The colleague looks up a figure in the accounting tool and replies. Two days later somebody asks whether the customer was ever answered, and nobody can say without searching three places.

Nothing in that story is a missing tool. The tools are all present. What is missing is agreement about which system owns the record and what happens next.

When the complaint is retyping, waiting and uncertainty about whose job it is, the problem is rarely the absence of another tool.

What are the four ways to fix a systems problem?

Four paths are available, and naming them precisely stops the conversation from drifting. Building means commissioning software shaped around your work. Buying means adopting an existing product. Integrating means joining what you already run so information moves, and automating means having software carry out the repeat steps.

Build
Commission software shaped around your steps and definitions. You decide what it does next, and you carry the upkeep.
Buy
Adopt an existing product and configure it. Fastest to start, and the supplier decides what changes.
Integrate
Join the systems you already run so each piece of information is entered once and travels. Fixes most retyping.
Automate
Have software carry out the repeat steps a person now does by hand, with people approving what matters.
TheslowstepBuildHow you work is partof your offerBuyThe work is commonand not where youcompeteIntegrateThe same informationis entered twiceAutomateA task repeats weeklyalong known steps
Four paths that can relieve the first constraint, the slow step, each with the sign that points towards it. Take the least complex one that moves the outcome.

The rule for choosing is to take the least complex path that plausibly moves the outcome you named. Complexity here means how much has to change, how many people have to learn something, and how much you will have to maintain.

Mavrin Labs works across all four paths, which is why a first conversation sometimes ends with a recommendation to change nothing yet. The services page sets out what each path involves.

Integrating most often means joining the CRM (customer relationship management system), the program that holds client and prospect records, to the accounting and scheduling tools. Mavrin Labs does that through systems integration, where it acts as a CRM integration consultant, and an online store's version of the same join is set out under ecommerce order automation for online sellers.

Why start with the outcome and its owner?

Starting with an outcome somebody owns gives the decision something to be measured against. Write the outcome as a sentence a person could be held to: the hours a task takes each week, the share of enquiries answered on the day they arrive, or the number of records that need correcting. Then name who owns it.

An unowned outcome produces a project nobody can stop. Everything sounds worth doing, scope grows, and the review at the end has nothing to compare against.

An owned outcome with a measure attached does the opposite. The outcome rules options out, and it gives you a date on which you will know. The measurable results method sets out how a target and a review date are agreed before work starts.

Published standards show the shape of a sentence somebody can be held to.

One criterion in version 2.2 of the W3C accessibility guidelines states a plain floor: a pointer target must measure 24 by 24 CSS pixels or more (W3C accessibility guidelines, version 2.2, checked Thursday, October 15, 2026). Write your outcome that clearly and anybody can check it.

Where is the first constraint?

The first constraint is the one step that sets the pace of everything around it. Find it by following several real items from arrival to finish and noting where each one waited longest, or where mistakes entered. That step, and not the one that annoys you most, is where the change belongs.

Work upstream of a constraint only arrives at the queue faster. Work downstream of it has nothing new to do. Projects aimed at the wrong step therefore produce a tidier process and no change a customer would notice, which is the most expensive kind of success.

Constraints move. Once the first one is relieved, the pace is set somewhere else, which is the reason to take one path at a time and measure after each.

  • Where the idea comes from

    The idea is not new. Treating one step as the limit on a whole flow is the core of what became known as the theory of constraints, which reached a wide audience through a 1984 business novel, The goal: excellence in manufacturing (the library record of the 1984 edition, checked Wednesday, November 18, 2026).

    That book told the idea as the story of a manufacturing plant (an encyclopedia entry on the theory of constraints, checked Wednesday, November 18, 2026). In an office the slow step is more often a handoff between tools, which is why this framework looks between systems first.

  • What the constraint view means for buying

    The constraint view also corrects the buying view. A tool can be the easiest path to buy and still be the wrong one. If it relieves no constraint, the work moves at the same pace, and the business has taken on a subscription, a round of training and one more place for records to drift.

    So judge each path first by whether it moves the slow step, and only then by how easily it can be bought, built or switched on.

    The constraint is often the clerical handoff, and that work is not a rounding error. For May 2025 the Bureau of Labor Statistics put employment in office and administrative support occupations at 17,753,430, against 155,495,730 jobs in all occupations (occupational employment and wage estimates, May 2025, checked Thursday, October 15, 2026).

What evidence settles a build or buy software decision?

Each path has evidence that points towards it and evidence that points away, and reading both is what keeps the choice checkable. The table below sets out the signs for building, buying, integrating and automating. Where your situation shows signs in both columns for one path, look closer at the constraint before choosing that path.

What evidence settles a build or buy software decision?
Path Points towards it Points away from it
Build how you work is part of your offer; staff keep a parallel record; the rules change often your process is ordinary; nobody will own the upkeep
Buy the work is common and not where you compete; you need something running soon the tool's assumptions clash with yours; your records would be stranded
Integrate the same information is entered twice; work waits between systems the systems offer no interface for other software; nobody owns the join
Automate a task repeats weekly along known steps; a baseline can be measured every case needs judgment; the task runs a few times a year

One piece of evidence usually points at integrating, because software arrives in waves.

In the Census Bureau's report on its 2023 annual business survey, 68.0% of the businesses using AI had taken it up in 2021 or 2022, while cloud-based technology was most often taken up in the years from 2016 to 2020 (40.0%) (Census Bureau technology adoption timing, checked Thursday, October 15, 2026).

Each wave leaves a tool behind it and joins none of them up, so a firm that has been buying for a decade is holding an integration problem rather than a shortage of tools.

If the evidence points nowhere yet, the six-question project finder asks where the week goes and names the kind of project to look at first.

How do you write the decision record?

A decision record is a one-page note, written before work starts, that names the outcome, the first constraint, the chosen path, the options ruled out and the review date, so the project can be held to its reasons later. Keep it short enough that people will read it.

  • The outcome, as a sentence somebody owns, with its measure attached.
  • The first constraint, and how you identified it.
  • The path you chose, in the words build, buy, integrate or automate.
  • The options you ruled out, each with the reason.
  • The assumptions you rely on, so a wrong one shows later.
  • Today's baseline, and the date you will review the result.

Keep the record where the next person will find it. The value is not in the writing but in having something specific to argue with when somebody proposes adding scope.

What are the common mistakes when choosing a path?

Four mistakes are common when choosing a path. They are starting from a shortlist of tools, fixing the step that annoys you rather than the one that limits the work, running all four paths at once, and leaving the result without an owner. Each has a correction, set out below with the reason it works.

Starting from a shortlist
A list of tools contains no decision. Start from the outcome and the constraint, and the list shortens itself.
Fixing the step that annoys you
The irritating step and the limiting step are usually different. Follow real work through the process to find the limiting one.
Running all four paths at once
Simultaneous changes cannot be measured or credited. Sequence them, and review after each.
Leaving the result unowned
An outcome without an owner has no one to stop it growing. Name the owner before the work, not at the review.

Sources behind this guide

Five public references bear on the four paths, and each is worth opening before you commit. The employment estimates from the Bureau of Labor Statistics, cited above, are the fifth.

For building, the secure software development framework published by NIST sets out practices a buyer may require, and version 1.1 is defined in its publication SP 800-218 (NIST secure software development framework, checked Thursday, October 8, 2026).

For connecting, an API (an application programming interface, the published way one system asks another to read or write information) is where two systems meet, and the OWASP project on API security names the failure modes that appear there. Its current list of ten risks is the 2023 edition (OWASP list of API security risks, checked Thursday, October 8, 2026).

For automating with an AI step, the AI risk management framework from NIST, released on January 26, 2023, offers a structure for deciding what to watch once a system is live (NIST AI risk management framework, checked Thursday, October 8, 2026).

For anything a customer touches, the web content accessibility guidelines (WCAG) apply: the international guidelines for making web pages usable by people with disabilities, written in version 2.2 as testable statements rather than advice (W3C accessibility guidelines, WCAG 2.2, checked Thursday, October 8, 2026).

Each claim and its source

The table below pairs each claim the guide makes from outside evidence with that evidence and its publisher.

Each claim and its source
Claim Evidence Source
Most businesses already depend on software Most businesses described cloud-based technology (59.0%) and specialized software (58.9%) as very important to their processes or methods (2023 survey report, checked Saturday, October 10, 2026) Census Bureau
A buyer can require secure building practices The framework sets out practices a buyer may require of whoever builds the software NIST secure software development framework
The join between systems is where API risks appear The project keeps a public list of the most serious API security risks OWASP list of API security risks
Accessibility can be tested, not just aimed at The guidelines are written as testable statements for anything a customer touches WCAG accessibility guidelines
Software arrives in waves, which is why tools accumulate Most AI adoption happened in a recent two-year window, while cloud adoption peaked years earlier Census Bureau technology adoption timing
An outcome can be written as a floor somebody can check A published criterion states a minimum pointer target rather than an aspiration the published accessibility guidelines on target size
Clerical handoffs are a large part of employment Office and administrative support occupations are about one job in nine nationally occupational employment and wage estimates
AI is arriving on top of existing tools A minority of businesses reported using AI in the survey's recent periods Census Bureau story on AI use by firm size

Key takeaways

  • Four paths fix a systems problem: build, buy, integrate or automate.
  • Start from an outcome somebody owns, with a measure attached.
  • Find the first constraint by following real work, not by annoyance.
  • Take the least complex path that plausibly moves the outcome.
  • Write a one-page decision record before work starts.

Each path has a guide that goes deeper. For building, read custom software or an off-the-shelf tool. For connecting, read the systems integration checklist, and for automating, read the AI automation readiness guide.

A decision reached this way puts hours back into the week of the people doing the work, instead of adding another system for them to learn.

Frequently asked questions

Why start from an outcome rather than from the tools?

Starting from an outcome gives you something to decide against. A tool shortlist has no answer in it, because every option on the list can be defended in the abstract. An outcome somebody owns, with a measure attached, rules options out quickly: anything that cannot plausibly move that measure is off the list, however impressive it is.

What counts as the first constraint?

The first constraint is the step that sets the pace of the whole flow, the one where work waits longest or where errors enter. Follow several real items through the process and note where each one sat still. Fixing anything upstream of it only delivers work to the queue faster. Fixing anything downstream changes nothing a customer would notice.

Can I choose more than one path?

Most real answers combine two paths, and that is fine as long as they are sequenced. A typical pattern is to buy a tool for the ordinary part, connect it to what you already run, and automate the repeat work the connection makes possible. What goes wrong is doing all three at once, because nothing can then be measured.

What is a decision record and why write one?

A decision record is a short written note of what you chose, what you were trying to achieve, what you considered and why you ruled the others out. Writing one takes under an hour and earns its place twice: it keeps the project on course when somebody adds scope, and later it shows whether the reasoning was sound.

How often should the decision be revisited?

Revisit the decision on the review date you set when you made it, and otherwise only when a stated assumption changes. A date chosen in advance keeps the project from drifting and keeps you from reopening a settled question whenever somebody mentions a new tool. A wrong assumption is a real reason to reopen it.

What if the answer is to change nothing?

Changing nothing is sometimes the right answer, and a framework that cannot reach it is a sales process. If the constraint is a habit, an unclear responsibility or a step nobody needs, then fixing the manual version is quicker than any software. Write that conclusion down as a decision too, so the question stays settled until something real changes.

The Mavrin Labs mark

Who writes these guides

Client work at Mavrin Labs is delivered by a team in mixed roles, led by our founder. AI tools help with research and drafting, and a person at Mavrin Labs checks each fact against its named source before a guide is published.

Enquiry form

Start with one workflow

Tell Mavrin Labs what is stuck and which systems it touches. A person at the firm reads every enquiry and replies by email.

Start a conversation

Fields marked with an asterisk are the ones a reply needs.

So a reply can address you properly.

The address the reply goes to.

Optional. Give one only if you would rather talk than write; the reply goes by email either way.

Optional, and useful when it says what the work has to fit around.

The result you want, and when you would want it working. Two or three sentences are plenty.

The task as it actually happens, roughly how often it runs, and which systems it touches. Two links at most, please.

Optional.

What you send goes to the Mavrin Labs inbox and is used to answer you, and a phone number, if you give one, is used for the same thing and nothing else.

A person reads it and replies by email.

If the form does not send, write to info@mavrinlabs.com instead; it reaches the same inbox.

Which hours would you take back first?

Name the one workflow that eats the most of your week. Mavrin Labs reads it, and the reply comes from the people who would build the fix.

Start a conversation