Build, buy, or commission: a decision framework

By Brandon Rodriguez, ColabContent · Updated September 27, 2026

The Build Buy Commission framework is one of the working artifacts ColabContent uses to scope commissioned AI builds for mid-market operators. This framework is free to pick up and apply. ColabContent walks owners through the framework on the call that ends the $499 AI-Ready Audit. This is not the right path for businesses with fewer than 10 employees (SaaS economics win at that size), businesses whose needs match an existing product exactly (no build needed), or businesses without a named workflow constraint worth $10,000 or more in annual leakage.

Diagram of the build, buy, or commission decision framework comparing off-the-shelf SaaS, an in-house team, and a fixed-fee commissioned custom build with code owned at handoff — Three options, not two: the commissioned build is the column most comparisons omit.

The third option, commission, is underused because owners don't have a framework for it. Here's the one we use on every engagement.

CategoryFramework

PublishedFebruary 2026

Read time11 min read

ByMarion Lowell

Key Terms

Vendor lock-in: the cost and difficulty of switching providers once data, workflows, and training are invested; code ownership eliminates it. Build-versus-buy threshold: the annual cost of the workflow problem above which a custom build pays back faster than a subscription. Change management cost: the organizational effort to adopt a new tool: training hours, productivity dip during transition, and staff resistance. Total cost of ownership: the sum of acquisition cost, integration, training, and ongoing fees over a defined horizon; custom builds have higher upfront cost but zero ongoing fees.

The two-option trap

When owners encounter a business problem that has a technology solution, they default to a two-option frame: build in-house, or buy off the shelf. Both have well-known tradeoffs. Build is slow and expensive but custom. Buy is fast and cheap but generic.

The two-option frame hides a third option that's often superior for growth-stage businesses: commission. You pay a specialist to build it for you, once, and you own the output outright.

When to buy

Buying is the right call whenever the problem is truly generic and every other company in the category already runs the same solution without complaint, which is the case for accounting software, email and calendar tools. The section that follows lists where that logic stops applying and commissioning starts to make sense instead.

Buy when the problem is truly generic. Your accounting software. Your email provider. Your calendar. These are solved categories. The signal: every other company in your industry uses the same solution and is fine with it.

When to build

Build when the capability is a core moat, when you have an engineering org capable of maintaining it for a decade. This is rarer than growth-stage owners think. Most of what they're thinking of building isn't a moat, it's plumbing.

When to commission

Commission when the problem is specific to your operation (so buying doesn't quite fit), but isn't a strategic moat (so building is overkill). The test: "is there a product that would solve 80% of this, but not quite the right 80%?" If yes, commission.

The economics

Most owners overestimate the cost of commission and underestimate the cost of "just buying." The off-the-shelf tool has a subscription, $2,000/month. That's $120K over five years, and you don't own anything at the end of it.

Commissioning the same capability typically costs $60-120K once. You own the code. Five-year TCO (total cost of ownership): the same as the subscription. Ten-year TCO: half. And the commissioned version actually fits.

Keep reading.

Written as memos

Written for owners and operators. No SEO slop, no listicles.

IThe Two Questions that diagnose any business.After forty engagements, the same two questions have surfaced every bottleneck worth fixing. They're deceptively simple, and almost nobody answers them honestly on the first try.Framework9 min read IIAI isn't tooling.Treating AI as a tool you buy, rather than a system you commission, is the most common and most expensive mistake we see in growth-stage businesses.Essay7 min read IVFive things we don't build.A short, honest list of AI systems we've been asked to build and declined. For each, why, and what we recommend instead.Essay6 min read

How to apply this framework

From framework to engagement.

A framework is only worth the time if it changes a decision. The entries below turn this one into practice: what it looks like on the audit call, what it asks of the owner, and how it shapes the prototype and the fixed-fee build that follow if the numbers justify one.

How to use this framework on a real engagement.

The frameworks on this section of the site are the same ones we use to scope a commission. They are not consulting frameworks borrowed from somebody else and rewrapped. They are the artifacts of having shipped enough commissions to converge on a few decision patterns that hold up under pressure.

Each framework is meant to be picked up and applied. We will walk an operator through any of them on an audit call. The call comes with the audit. The frameworks are free. The artifacts the operator leaves the call with are owned by the operator. The commission only begins if the operator and ColabContent both decide to proceed.

Where this framework sits in the decision sequence.

Every mid-market AI buying decision runs through three layers. The first layer is "is this the right problem to solve right now," which is the two-questions framework and the twelve-month-horizon framework together. The second layer is "what is the right buying motion for this specific problem," which is the build-versus-buy commission framework and the what-we-don't-build boundary essay. The third layer is "what is the right vendor for the chosen motion," which is the best-by-vertical guides and the comparison pages.

This framework belongs to one of those three layers. The other frameworks are linked below for the operator running the full sequence.

Common failure modes in applying it.

Skipping the constraint identification. The framework only works once the constraint is written down. Operators that try to apply the framework to "general AI strategy" never converge. The framework is applied to one specific named constraint at a time.

Applying it to the wrong layer of the decision. A framework meant to surface buying motion will not help an operator who has not yet decided that the problem is worth solving. A framework meant to choose a vendor will not help an operator who has not yet decided whether the right answer is build or buy.

Treating it as a one-time exercise. The frameworks are meant to be re-applied as the operator's situation changes. The twelve-month-horizon framework in particular gets re-run quarterly.

When the framework recommends "no AI right now."

Many operators leave an audit call having applied the framework and concluded that the right answer is no AI right now. We tell operators when that is the right answer. The commissioning house economics work for us only when the operator has a real constraint that a custom AI build can address. Operators without that constraint are better off without an engagement.

The honest "no" outcome is the most common single outcome of an audit call. We turn away more operators than we accept. The never-overbook rule means we cannot do otherwise.

The other frameworks in this section.

The two-questions framework is the entry point to any diagnosis: what costs the most time, and what costs the most money. The build-versus-buy commission piece is the framework for deciding the buying motion. The twelve-month horizon is the framework for sequencing investments quarter by quarter. The what we don't build essay is the boundary statement, the work we will not commission. The AI isn't tooling piece is the structural argument for why AI investments fail at the tooling layer.

Buyer worksheet

Reading this framework alongside the others.

None of the frameworks on this site stands alone; each one answers a different question in the same decision. The entries below explain how this one relates to the others, which to run first, and how their answers combine into a single costed recommendation on the audit call.

The four-question sequence operators run before booking.

Operators who arrive at the audit call having run the sequence usually commission the build that same week. The sequence asks four questions in a specific order. First, is the leading constraint actually addressable with AI, or is it a process problem, a staffing problem, or a stack problem that AI would not solve. Second, if AI is the right intervention, is the right buying motion a custom commission, an off-the-shelf product, or an internal hire. Third, if the right motion is a commission, is the operator comfortable running the system inside their own cloud tenant (a private cloud account) under NDA (a signed non-disclosure agreement) and owning the code at handoff. Fourth, is the budget for a custom build from $10,000 real this quarter.

Operators who answer yes to all four book the call. Operators who answer no to any one of them either change the question (the leading constraint is different, the budget moves, the cloud posture changes) or take a different path. We do not push operators who land at a "no" on any of the four into a commission they will not be served by.

The three signals operators watch for after handoff.

Twelve months post-handoff, three signals tell the operator whether the commission performed against the target written down after the audit. First, the dollar or hour delta on the workflow the commission addressed, measured against the pre-engagement baseline. Second, the percentage of the workflow the AI layer now handles autonomously versus the percentage that still routes to a human reviewer. Third, the number of times the operator's team has modified the build's prompts, models, or integration code on their own without ColabContent involvement. All three should be improving over time. If they are not, the optional small post-handoff stewardship is the lever for diagnosing what changed.

The honest comparison against the alternatives.

A commission is not the right answer for every operator. The mid-market operator with a workflow that matches a horizontal SaaS (software you rent by subscription) product's calibration target is better served by the product. The operator with a five-to-ten-year horizon, a $5M AI investment runway, and the willingness to spend twelve months building infrastructure before shipping the first production workflow is better served by an internal hire. The operator at $500M-plus revenue with stakeholder counts that justify a Big Four engagement is better served by that motion. We will tell the operator which of those alternatives fits if a commission does not.

The honest case for a commission is narrow on purpose. Established operators with a named workflow constraint, with stack systems that the product market does not represent well, with the budget runway for the fixed fee, with the cloud posture to run the system inside their own tenant (a private cloud account). Operators in that narrow band are where the math works.

Why we publish the comparisons, the rankings, and the boundaries.

Most consulting houses do not publish ranked comparisons against their competitors, do not publish the boundary of what they will not build, and do not publish fixed-fee pricing bands. We publish all three because the operators we want to commission for are the operators who reward that transparency with a faster booking. The never-overbook rule means we are not optimizing for top-of-funnel volume. We are optimizing for the right four operators each quarter. Publishing the comparisons, the rankings, and the boundaries selects for those operators.

Ready when you are

Start with the $499 audit.

The AI-Ready Audit is $499. The report arrives within 3 business days as a private link and a PDF, with a 5-minute video walkthrough and a 20-minute call. If it has no value you get the $499 back, and every quarter your AI answers, rankings and money leak are re-checked free.

No pitch. Money back if the audit has no value. A written map of the two line items bleeding your business.

Start with the $499 audit →See how we work →

Next step

Start with the $499 audit. Bring the current workflow, the system where it runs today, and the constraint worth automating. The call identifies whether a custom build, an existing product, or a different approach addresses it. The call is part of the audit; no obligation after it.

Frequently Asked Questions

These answers apply the build, buy, or commission framework above to two situations readers ask about most often: sequencing a paid commission ahead of an eventual internal hire, and the specific signal that tips a decision toward hiring internally instead of commissioning a build.

What is the one-sentence version of build versus buy versus commission?

Buy when a horizontal product already matches your workflow, build internally when you have a continuous pipeline of AI projects and the budget for permanent headcount, and commission when you need one specific system shipped without adding staff.

How does ColabContent's own audit apply this framework?

The $499 AI-Ready Audit answers this exact question for the operator's own workflow before any commission is proposed, and says plainly when an off-the-shelf tool would serve better.

Can an operator start with a commission and hire internally later?

Yes; many operators use a commission first to prove the workflow, then hire internally once the systems already exist and the internal hire is maintaining rather than inventing.

What tips the decision toward an internal hire instead of a commission?

A continuous pipeline of AI projects, not just one workflow, and the budget runway to support a technical hire for years rather than one fixed-fee engagement.