Build, buy, or commission.

By Brandon Rodriguez, ColabContent · Updated September 27, 2026

This is lesson 04 of the ColabContent AI-Ready Course, a free seven-lesson primer for mid-market operators considering a custom AI commission. Each lesson takes five to ten minutes and ends with a concrete action. By the end of the seven days the operator has a written scoping document for a potential commission. ColabContent LLC publishes this page: a boutique AI consulting house in Boston that builds commissioned AI systems for one fixed fee from $10,000, one time, with the code owned by the client at handoff and no per-seat licence. The $499 AI-Ready Audit is ordered at colabcontent.com/ai-ready-audit/.

Lesson four of the AI-Ready Course: when to build in-house, when to buy off-the-shelf, and when to commission a custom build, with the failure mode attached to each path — Three paths, each with its honest failure mode.

Day four. Three paths to AI in the growth-stage business. Three decisions, four criteria. The framework we use on every paid engagement.

Lesson4 of 7

Read time~20 minutes

FormatMemo-style

CostFree

The third path.

The conventional choice every operator faces is between build and buy. Build means hire engineers and an AI lead, write the system internally, own the output. Buy means license an off-the-shelf product, configure it for your business, and accept its boundaries.

The third path, commission, is underused because owners don't have a framework for it. Commissioning means hiring a boutique to build a custom system on your data, in your own tenant (an isolated environment in your cloud account), owned by your business at handoff. Different from build (you don't carry the engineering team afterward). Different from buy (the system is yours, configured to your specifics, not the vendor's average).

Build: when it's the right answer.

Build is the right answer when AI capability is going to be a durable differentiator for your business, when you have or can credibly hire the engineering bench, and when the system you need will keep evolving over years.

For a $200M software company (illustrative example, not a client figure), build is often correct. For a $25M services firm (illustrative example), build is usually wrong: the engineering bench is expensive, the AI capability is a means not an end, and the system needs to ship in roughly 8 weeks (estimate) not 8 quarters. Hiring two AI engineers and a head of AI to deliver one workflow improvement is a mismatch of resources to outcome.

Build criteria: Does AI capability appear in your strategy as a moat, not just an enabler? Can you hire and retain at the AI engineer level? Will the system need to evolve materially every year? If yes to all three, build.

Buy: when it's the right answer.

Buy is the right answer when an off-the-shelf product covers roughly 80% or more of your needs (a working estimate, not a measured figure), when your needs are not differentiated from the average customer in the segment, and when configuration is a real lever the vendor exposes.

For meeting transcription, buy. For generic SDR enablement, buy. For most CRM (customer relationship management software) auto-fill, buy. The category leader has solved 80% of the problem for the average customer, and your business probably is the average customer for that workflow. Trying to commission something custom for these workflows is a misallocation.

Buy criteria: Does an off-the-shelf product cover 80%+ of your need? Are your needs essentially the same as the average customer in your segment? Is configuration substantive enough that the vendor's product becomes your business's product? If yes to all three, buy.

Commission: when it's the right answer.

Commission is the right answer when your needs are differentiated (your matter taxonomy, meaning how your firm categorizes and tracks its case files; your part library, your carrier pool, your pricing rules, your business's specific workflow), when off-the-shelf products cover less than roughly 60% of your need (estimate), and when you want to own the system at handoff rather than rent it.

Most of the workflows we listed in Lesson 1 fit this pattern. Custom CPQ AI on the shop's actual part library. Matter-aware retrieval on the operation's specific iManage taxonomy. Submission AI on the agency's actual carrier pool. The vendor product can't capture the specifics; the build option is too heavy; the commission option fits.

Commission criteria: Are your specifics meaningfully different from the average customer? Does off-the-shelf cover less than 60% of your need? Do you want to own the system, not rent it? Will the system be relatively stable once shipped (roughly 5-15% modification per year, not 50%, both estimates)? If yes to all four, commission. Our own fixed-fee terms for a commission are set out on the pricing page. Score your own case against these three paths with the $499 AI-Ready Audit.

Three failure modes.

The three failure modes we see most often, in order of frequency:

Buying when you should commission. The most common failure. Owner sees a polished demo, signs a 12-month contract, the tool covers roughly half the workflow well and half poorly (estimate). Senior staff resent it. The hours-back number doesn't materialize. Year two, the contract gets renewed because nobody wants to admit the mistake.

Building when you should commission. Second most common. Owner hires two AI engineers, an illustrative eight months later there's a half-built internal tool, the engineers are restless because they want to ship to many users, the operation hasn't shipped to even one workflow. The build burns an estimated 18-24 months and never reaches steady state.

Commissioning when you should buy. The least common but most expensive on a per-engagement basis. Custom build for a workflow that an off-the-shelf product covers cleanly. The deliverable works, but the operation is paying boutique fees for what an estimated $400/month SaaS (software delivered over the internet on a subscription) would have done. Avoid by being honest about whether your needs are actually differentiated. Our own view on the ownership question is in how we work.

Tomorrow.

Lesson 5: scoping the first commission. The four elements of a tight scope: outcome, interface, data, guardrails. The difference between an engagement that ships in 6 weeks and one that ships never.

VScoping your first system.Lesson 5. The four elements of a tight commission: outcome, interface, data, guardrails.Day 5~20 min IIIAuditing your operation end-to-end.Lesson 3. The audit you run before any vendor conversation.Day 3~20 min

Where this lesson fits

How the AI-Ready course is structured.

The course runs as seven short lessons, one a day by email, each built around a single decision an owner has to make before commissioning any AI system. The lessons below are in order; each one stands on its own, and the sequence ends with the $499 AI-Ready Audit as the practical next step.

Where lesson 04 fits in the AI-Ready course.

The AI-Ready course is a seven-lesson primer for operators considering whether to commission a custom AI build for their business. The course is free. It is structured as one short lesson per day for seven days, delivered by email. Each lesson can be read in five to ten minutes and ends with a single concrete action the operator can take that day.

The lessons in order: the two questions every operator should answer before any AI buying motion, the build-versus-buy framework, the diagnosis structure, the prototype-before-pay engagement model, the integration boundary, the handoff and ownership posture, and the twelve-month-after-handoff stewardship pattern. This lesson is one of those seven.

How to apply the lesson at your operation this week.

The lesson ends with a concrete action because the course is designed to produce a written artifact, not a feeling. By the end of the seven days the operator has a one-page document that names their leading constraint, names the workflow that addresses it, names the integration boundary, names the buying motion, and names the ownership posture. The document is the operator's to keep regardless of whether the operator commissions a build.

The action this lesson asks for is small. Five to fifteen minutes of work, written down, kept in a single document that the operator returns to as the course progresses. Most operators do the work on a Sunday evening over coffee. By Friday of the second week the document is done.

What the next lesson covers.

Each lesson builds on the previous one. The next lesson takes the artifact the operator built this week and applies the next decision in the sequence. The operator who reads the lessons in order, does the action each one asks for, and lets the artifact accumulate ends the course with a complete written scoping document for a potential commission. The operator who reads the lessons out of order or skips the actions gets less value from the sequence.

Why ColabContent runs the course.

The course exists because most of the operators we end up commissioning for came in already having done some version of this work on their own. The structured course shortens that path. Operators who finish the course and decide their constraint is right for a custom commission order the $499 AI-Ready Audit. Operators who finish the course and decide the right answer is no AI right now, or off-the-shelf, or an internal hire, are better positioned for whichever motion they chose.

The course generates no obligation to commission. Operators who finish the course and choose any of the alternatives are fine; we will refer them to whichever path they decided on if we know who does that path well.

All seven lessons.

The course hub indexes the seven lessons. Each lesson is also available as a standalone read for operators who arrive at it through search or a referral. The hub also explains how the daily email delivery works for operators who would rather have the course paced for them than read it in one sitting.

Buyer worksheet

How to decide whether a commission is the right next step.

Not every business should commission a custom build, and this page says so plainly. The questions below are the ones we run on the audit call to decide whether an owned system, a rented product, or no change at all is the right answer; four yes answers point to a build, fewer point elsewhere.

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 (an isolated environment in their cloud account) under an NDA (a signed non-disclosure agreement), owning the code at handoff. Fourth, is the budget for a custom build from $10,000 (our published price) 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 post-handoff stewardship ($997 a month, cancel on 30 days notice) 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, an estimated $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 roughly $500M-plus revenue (estimate) 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. Start with the $499 AI-Ready Audit to see which of the three applies to your business.

Decide between the three with us.

The audit call ends with a one-page memo telling you which of the three is right for your specific case. A meaningful share of our diagnoses end with us recommending buy or build, not commission.

Related reading: Lesson 05, ColabContent AI-Ready Course.

Start with the $499 audit →

Questions on this lesson

Questions operators ask before committing to a commission.

These are the questions operators raise most often once they have worked through the build, buy, and commission framework above and are weighing whether to book the audit call. Each answer states the cost, the timeline, and what ColabContent asks of the operator in plain terms, so nothing about the commission path is a surprise later.

What does a commission cost, next to buy or build?

Custom commissions start from $10,000, with a working prototype in 7 to 10 days before any build fee is owed. Buy is usually cheaper up front but carries a recurring seat fee instead.

What happens if the commission does not work?

The prototype stage is the check. If it cannot run cleanly on your real data in that window, the engagement stops there and no production fee is owed.

What is expected of us during a commission?

A named internal owner, access to the systems and data involved, and that owner's time to review the prototype before it ships.

Does commissioning a system replace our staff?

Not as a rule. A commission removes assembly work around a judgment a senior person still makes; staffing changes only when the audit call points to one.

How long does a commission take from decision to handoff?

The prototype lands in 7 to 10 days; the full build runs 4 to 6 weeks after that, depending on how many systems the workflow touches.

Who owns the code and prompts once the system ships?

Your business does, at handoff: source code, prompts and documentation transfer to you, no per-seat licence, no fee to keep using it.