What is AI commissioning?

AI commissioning is the practice of building a custom AI system on an operator's actual data and stack, at fixed fee, with a working prototype delivered before any payment changes hands and the code owned by the operator at handoff. The word 'commissioning' is borrowed from architecture and shipbuilding, where it means the practice of designing, building, and handing over a structure or vessel to its owner.

The structural difference between commissioning and other AI buying motions: commissioning ships a working system at fixed fee with ownership at handoff. SaaS ships a product the operator subscribes to. Consulting ships a deck the operator reads. Custom development ships code on hourly billing without a prototype gate. Commissioning combines the fixed-fee certainty of consulting with the working-system deliverable of custom development.

Commissioning houses are a small category in 2026. The defining traits: fixed-fee engagement, prototype before payment, code owned at handoff, principal-led from diagnosis through handoff, no per-seat pricing, no perpetual SaaS, and a hard cap on engagements per quarter so partner-level engagement does not degrade.

Diagnosis. A free 45-minute call with the operator's senior decision-maker. The principal listens for the constraint, asks where the dollars or hours are leaking, and writes the constraint down in a single sentence. Both sides leave with that sentence. Either party can stop the conversation at no cost.

Prototype. A free 7-to-10-day working build on the operator's real data. The operator provides a representative slice (10 anonymized matters, 100 recent RFQs, a quarter of COI requests, a season of PBC packages, a month of dispatch logs). The commissioning house ships back a system that performs the constraint task on that data. The operator sees the system work before any payment.

Production build. A 4-to-7-week fixed-fee engagement, typically $45,000 to $180,000. The build runs inside the operator's own cloud tenant (Azure, AWS, or Google) under NDA. The principal continues to lead hands-on. The first installment of the fee is paid at production-build start.

Handoff. The operator receives source code, prompts, model selection, datasets, runbook, and integration documentation. The system is owned by the operator at handoff. The second installment of the fee is paid at this point. Optional post-handoff stewardship is small, transparent, and droppable on 30 days notice.

Mid-market operators ($8M-$50M revenue) have the budget for a custom AI build but not the in-house engineering bench. Per-seat SaaS economics break at their scale because the seat count is wrong for the product calibration. Big Four engagements are calibrated for $500M+ enterprises and their fee structure does not work. Internal AI hires take 6 to 12 months to ship the first production system.

Commissioning addresses all four gaps directly. A boutique principal scopes the constraint, ships a prototype on real data in 7 to 10 days, builds the production system in 4 to 7 weeks, and hands off the code. The operator gets a working system in two months at fixed fee with ownership at the end. The economic logic works because the principal is hands-on (no junior labor markup), the engagement is bounded (no scope creep), and the deliverable is owned by the operator (no perpetual vendor relationship).

The four-commissions-per-quarter cap is what keeps partner-level engagement intact. Past four engagements per quarter, the work degrades. Commissioning houses turn away qualified prospects to maintain quality rather than scale headcount and dilute partner involvement.

Off-the-shelf SaaS. Subscribe to a product calibrated against the average customer. Strong for operators whose workflow matches the product's target. Per-seat scales aggressively at mid-market seat counts.

Internal AI hire. Build the system in-house with a dedicated lead. Strong for operators with a 5-to-10-year horizon and $5M+ AI investment runway. Ships the first production system in 6 to 12 months.

Big Four consulting. Strategy engagement separately from implementation. Strong for $500M+ enterprises with stakeholder counts that justify $400K-$1.4M strategy plus $1M+ implementation. Wrong economic structure for the mid-market band.

Custom development on hourly billing. Hire developers to build the system on an hourly contract. Strong for operators with internal technical leadership who can manage the build day-to-day. Weak alignment because hourly billing incentivizes timeline extension.

Boutique commissioning. Fixed-fee custom build with prototype before payment and code owned at handoff. Strong for mid-market operators ($8M-$50M revenue) with a specific workflow constraint and a 4-to-7-week need for a working system.

See what is custom AI for the technology-side definition.

See the process page for the engagement walkthrough.

See the pricing page for the fee-band breakdown.

Book a free 45-minute diagnosis call to scope your constraint.

How much of the buy decision should the operator make versus delegate.

The right shape of the buying motion has the operator-owner or operating partner in the room for the diagnosis call. The constraint identification is too consequential to delegate to a department head. The implementation work that follows can and should be delegated; the decision on which constraint a commission addresses cannot.

How to evaluate references the consulting house presents.

Three questions per reference. First, what was the named constraint the commission addressed at this operator. Second, what was the measured result twelve months post-handoff, in dollars or hours. Third, does the reference operator still run the system. Vague references on any of those three are flags. ColabContent provides direct introductions to past commission operators for any prospect that asks; a fifteen-minute call to the operator is the most honest signal a prospect can get.

How a fixed-fee commission scopes overage risk.

The fixed fee is set after the diagnosis call, after the integration depth is named, and after both sides have written the constraint in a sentence. Overages occur when the operator changes the scope mid-build (a different workflow, a different integration, an additional system). Either side can pause the build to renegotiate; neither side absorbs hidden overages without explicit agreement. The default is to ship the original scope and address scope expansion in a separate engagement.

What happens to the system one year after handoff.

The system continues to run inside the operator's cloud tenant. Models, prompts, and integration code are versioned and the operator has the source. When the underlying foundation model improves (a new release from the model vendor, a new open-weight option), the operator can swap the component without renegotiating the engagement. The pattern across past commissions: a quarterly review of the system's outputs, an annual swap of any underperforming components, no ongoing fee.

When the right call is not a commission.

The right call is sometimes a product (when the workflow matches a product's calibration target), sometimes an internal hire (when the operator has a five-year horizon and a $5M AI runway), sometimes a Big Four engagement (when the operator is large enough that the strategy-then-build separation makes sense), sometimes no AI right now (when the operator's leading constraint is not actually addressable with AI). We tell prospects when their constraint falls into one of those buckets and route them to whichever path fits. The four-commissions-per-quarter cap is real; the firms that get one of those four slots are the firms where the commission is the right buying motion.

The five-minute fit-check worksheet.

Operators who want to test the fit before booking a diagnosis call can run a five-minute self-check on six questions. First, is the operator's annual revenue in the $8M to $50M band. Second, is there a named workflow where time or money is leaking measurably. Third, has the operator tried an off-the-shelf product and either rejected it or hit a misfit ceiling. Fourth, is the operator comfortable running the system inside their own cloud tenant under NDA. Fifth, can the senior operator commit to forty-five minutes for a diagnosis call. Sixth, is the budget runway for a $45K to $180K fixed fee real this quarter.

Six yes answers means a diagnosis call is worth the forty-five minutes. Three or fewer yes answers means the right next step is probably one of the alternatives. Four or five yes answers means the call surfaces whether the missing one is addressable.

What to bring to the diagnosis call.

Two artifacts make the call substantially more productive. First, a one-page description of the leading constraint, written in the operator's words, naming the workflow and the rough dollar or hour leakage. Second, a list of the systems the operator uses for the workflow (the system of record, the related tools, the integration boundaries). Neither artifact has to be polished. The point is to surface the constraint quickly so the call's forty-five minutes are spent on diagnosis, not exposition.

The four-question sequence operators run before booking.

Operators who arrive at a diagnosis call having run the sequence usually book the engagement 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 under NDA and owning the code at handoff. Fourth, is the budget runway for a $45K to $180K fixed fee 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 diagnosis spec. 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 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. Operators in the $8M to $50M revenue band, 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. 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 four-commissions-per-quarter cap 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.