01 — Method

The Build vs. Buy Matrix.

Every AI engagement begins with the same question: should this capability be configured from a tool you already pay for, built inside your team, bought from a vendor, or commissioned as a system that does not yet exist? We answer that question with a 2×2 — and because we deliver in all four quadrants, the answer is chosen by fit, not by what we happen to sell.

02 — The matrix
Build vs. Buy — four answers to every AI capability question
Fig. 01 — Build vs. Buy — four answers to every AI capability question

Two axes. Four answers. One framework.

Most firms answer the question with whatever they sell: consultancies recommend advice, vendors recommend software, agencies recommend retainers. We work across all four quadrants, so the recommendation carries no house bias — the quadrant is chosen by the task.

03 — The axes
01
Internal vs. External — A question about where the capability lives once it ships. Internal capabilities are operated by your team and embedded in your stack. External capabilities are operated by a third party and accessed via an interface.
02
Off-the-shelf vs. Custom — A question about specificity. Off-the-shelf capabilities are general-purpose and configured to your context. Custom capabilities are designed to your context from the start.
04 — The quadrants
QUADRANT I
Configure (Internal × Off-the-Shelf) — Use when the capability is well-served by an existing tool, the tool is already in your stack, and the gap is configuration, not capability. Example: lead scoring in HubSpot. Forecast roll-ups in Salesforce.
QUADRANT II
Build (Internal × Custom) — Use when the capability is specific to your motion, no tool serves it well, and the system needs to live inside your data estate. Example: pipeline scoring trained on your win data. Custom enrichment pipeline tied to your firmographics.
QUADRANT III
Buy (External × Off-the-Shelf) — Use when the capability is a commodity, the vendor's version is defensibly better than what you would build, and the per-seat math underwrites the spend. Example: CRM. Calendaring. Conversation intelligence.
QUADRANT IV
Commission (External × Custom) — Use when the capability needs to be custom, but the maintenance burden does not belong inside your team. You commission the build, take ownership of the system, and run it yourself. Example: a deal-review system generated from your transcripts and pipeline state.
05 — Delivery

One studio. All four answers.

The matrix is not a sales device that funnels every capability toward the quadrant we monetize. Each disposition maps to work we do.

01
Configure — We configure the capability inside the tools you already license. No new spend; unlocked capacity you were already paying for.
02
Build — We design and build the system inside your data estate, specified by a Blueprint your team can own and extend from day one.
03
Buy — We run the vendor decision — trade-off matrix, per-seat math, contract terms. We take no referral fees, so the recommendation survives scrutiny.
04
Commission — We design, ship, and transfer the system. Source, weights, prompts, harness, runbook — owned by you on day 91.

Quadrants I and III are typically scoped under the consulting engagement. Quadrants II and IV run through the engineering motion — Blueprint first, then build. The diagnostic decides which quadrant each capability belongs in before either engagement is scoped.

06 — The diagnosis
Most stacks are over-indexed on Quadrant III and under-indexed on Quadrants II and IV.

The diagnostic finds the imbalance. The Blueprint corrects it. The build executes the correction. And when the right answer is a tool you already own, the brief says so — a firm that only recommends what it builds is a vendor with better typography.

07 — Reference

What is the Build vs. Buy Matrix?

The Build vs. Buy Matrix is a decision framework for AI capability investments in a B2B SaaS revenue operation. It maps candidate capabilities onto two axes — Internal vs. External (who operates the system after deployment) and Off-the-Shelf vs. Custom (whether the capability is general-purpose or purpose-built for the company's specific motion) — to produce a written disposition: configure, build, buy, or commission.

The framework is designed to replace anecdotal vendor decisions with a document the CFO can underwrite and the CTO can ratify. FusedLabs delivers against all four dispositions: configuration work and vendor decisions run under its consulting engagement; custom systems — built in the client's estate or commissioned and transferred on day 91 — run under its engineering engagement. Because the studio is not confined to one quadrant, the disposition is selected by best fit for the capability, not by the seller's business model.

08 — Insights

Reading from the studio.

The build-vs-buy decision is upstream of everything else; these notes cover how teams adopt AI and the GTM thinking that determines which systems earn the investment.

No posts yet.
09 — Begin

Where does your stack sit on the matrix?