Decide Whether to Build, Buy, or Connect a Capability

Revenue Operations, GTM Engineering, Executive and Founder, Revenue Finance.

• A team wants to build something a vendor already sells.
• You are being sold a tool that mostly moves data between systems you own.
• The same capability is being sourced twice by different teams.

• The capability you need, described as a job, not a product
• What your current systems already do toward that job
• Engineering time you can realistically get, in weeks
• Whether the capability touches your buyer or only your team

Best for one task. Copy it, add your information, and run it in your AI assistant.

You are a go-to-market architect. Using the details I paste below, make a three-way sourcing call for the capability: build it, buy it, or connect existing systems. For each option state the cost, the time to first value, the maintenance burden, and the failure mode. Weigh whether the capability is buyer-facing or internal. Recommend one option, name the second-best, and write the condition that should make me switch. Do not assume engineering capacity I did not give you.

Details:
[paste]

Best for repeatable work. The file includes the process, required inputs, decision rules, quality checks, and output format.

---
name: decide-build-buy-or-connect
description: A sourcing call for one AI capability, with the reasoning written down so the next person can challenge it.
license: MIT
metadata:
  author: The Revenue AI Report
  version: 1.0.0
  last-reviewed: 2026-09-04
  source: https://www.therevenueaireport.com/skills/decide-build-buy-or-connect
---

# Decide Whether to Build, Buy, or Connect a Capability

A sourcing call for one AI capability, with the reasoning written down so the next person can challenge it.

## When to use this skill

- A team wants to build something a vendor already sells.
- You are being sold a tool that mostly moves data between systems you own.
- The same capability is being sourced twice by different teams.

## Inputs to collect

- The capability you need, described as a job, not a product
- What your current systems already do toward that job
- Engineering time you can realistically get, in weeks
- Whether the capability touches your buyer or only your team

## Process

1. Collect the inputs above. Thin input produces a confident, wrong answer.
2. Buyer-facing infrastructure, buy: CRM, marketing automation, phone, video, storage. Nobody wins by building what everyone else already bought.
3. Buyer-facing intelligence, buy and thread: Where most AI-native leverage now lives. The vendor supplies the substrate. You supply the language, the plays, and the evidence.
4. Internal infrastructure, buy: Compute, model APIs, vector stores, agent runtimes. Rent the utilities. Buying infrastructure is not a strategy by itself.
5. Internal intelligence, build: Your ICP model, your enablement corpus, your reply corpus, your reversal ledger, your customer voice model. Only you can build these.
6. Write the verdict and the next action with an owner and a date.
7. Have one person who did the work review the output before you share it.

## Decision rules

- Infrastructure that everybody needs and nobody sees is usually bought.
- Build only where the capability is the difference between you and a competitor.
- Connecting existing systems is the default when the data already exists in them.
- Do not build against engineering time you have not been promised in writing.

## Output requirements

- Three options costed on money, time, maintenance, and failure mode.
- One recommendation with the second-best option named.
- The condition that would flip the decision.

## Quality checks

- Maintenance is costed, not assumed to be zero.
- The recommendation matches the engineering capacity you actually have.
- The flip condition is observable.

## Limitations

- Pricing you did not supply is unknown and must not be estimated.
- The call ages. Re-run it when a platform ships overlapping functionality.

## Example input

Capability: enrich and route inbound leads within two minutes. Current systems hold firmographics and routing rules. Engineering: four weeks, unconfirmed.

## Example output

Recommendation: connect existing systems, because both data sets already sit in tools you own and the routing rules are configuration, not code. Second best: buy. Flip condition: routing logic that needs per-account judgment more than twice a week.

## Review checklist

- Did engineering confirm the time estimate in writing?
- Is maintenance owned by a named team?
- Is the flip condition on someone's review calendar?

## Works with

- Playbook: Score your ICP on stack density (L4) (revops, L4) https://www.therevenueaireport.com/playbooks/score-icp-on-stack-density-l4
- Playbook: Put an answer layer on the warehouse you already paid for (L4) (revops, L4) https://www.therevenueaireport.com/playbooks/answer-layer-on-warehouse-l4
- Playbook: The agent control plane (L4) (revops, L4) https://www.therevenueaireport.com/playbooks/agent-control-plane-l4
- Tool: Mode (Data & Analytics) https://www.therevenueaireport.com/tools/mode
- Tool: Vector (Sales & Revenue Intelligence) https://www.therevenueaireport.com/tools/vector
- Tool: Rows.com (AI Agents & Workflow) https://www.therevenueaireport.com/tools/rows-com
- Tool: Unbabel (AI Agents & Workflow) https://www.therevenueaireport.com/tools/unbabel
- Tool: Writer AI Agents (AI Agents & Workflow) https://www.therevenueaireport.com/tools/writer-ai-agents

## Rules of conduct

- Write for a Director, VP, or operator. Short sentences. Explain uncommon terms.
- Separate facts from assumptions. Never hide uncertainty.
- Do not invent numbers, benchmarks, quotes, or customer names.
- Do not send messages, change CRM records, or publish anything unless the user explicitly asks.
- Flag when a decision needs human review.

## Evidence

This skill is grounded in The Revenue AI Report research:
- https://www.therevenueaireport.com/research/what-works
- https://www.therevenueaireport.com/research/spend-vs-attribution
- Related analysis: https://www.therevenueaireport.com/blog/headless-gtm-stack

- Applies the framework: https://www.therevenueaireport.com/frameworks/build-buy-thread


Source and updates: https://www.therevenueaireport.com/skills/decide-build-buy-or-connect

1. 1.Collect the inputs above. Thin input produces a confident, wrong answer.
2. 2.Buyer-facing infrastructure, buy: CRM, marketing automation, phone, video, storage. Nobody wins by building what everyone else already bought.
3. 3.Buyer-facing intelligence, buy and thread: Where most AI-native leverage now lives. The vendor supplies the substrate. You supply the language, the plays, and the evidence.
4. 4.Internal infrastructure, buy: Compute, model APIs, vector stores, agent runtimes. Rent the utilities. Buying infrastructure is not a strategy by itself.
5. 5.Internal intelligence, build: Your ICP model, your enablement corpus, your reply corpus, your reversal ledger, your customer voice model. Only you can build these.
6. 6.Write the verdict and the next action with an owner and a date.
7. 7.Have one person who did the work review the output before you share it.

• Infrastructure that everybody needs and nobody sees is usually bought.
• Build only where the capability is the difference between you and a competitor.
• Connecting existing systems is the default when the data already exists in them.
• Do not build against engineering time you have not been promised in writing.

• Three options costed on money, time, maintenance, and failure mode.
• One recommendation with the second-best option named.
• The condition that would flip the decision.

Capability: enrich and route inbound leads within two minutes. Current systems hold firmographics and routing rules. Engineering: four weeks, unconfirmed.

Recommendation: connect existing systems, because both data sets already sit in tools you own and the routing rules are configuration, not code. Second best: buy. Flip condition: routing logic that needs per-account judgment more than twice a week.

• Did engineering confirm the time estimate in writing?
• Is maintenance owned by a named team?
• Is the flip condition on someone's review calendar?

What does the Decide Whether to Build, Buy, or Connect a Capability skill do?

A sourcing call for one AI capability, with the reasoning written down so the next person can challenge it.

Who is the Decide Whether to Build, Buy, or Connect a Capability skill for?

Revenue Operations, GTM Engineering, Executive and Founder, Revenue Finance. It sits at the advanced level and takes about an hour.

What do I need before I start?

Collect these first: The capability you need, described as a job, not a product; What your current systems already do toward that job; Engineering time you can realistically get, in weeks; Whether the capability touches your buyer or only your team.

What is the difference between the quick prompt and the SKILL.md file?

The quick prompt is for one task. Copy it, add your information, run it. The SKILL.md file is for repeatable work: it carries the process, required inputs, decision rules, quality checks, and output format so an AI assistant runs the same way every time.

What should I check before trusting the output?

Did engineering confirm the time estimate in writing? Is maintenance owned by a named team? Is the flip condition on someone's review calendar?

Is it free to use?

Yes. Every skill on The Revenue AI Report is free and published under the MIT license. Attribution is welcome, not required.

• Pricing you did not supply is unknown and must not be estimated.
• The call ages. Re-run it when a platform ships overlapping functionality.

Run the skill, then roll it out with a playbook. Vendor links are supporting context, not a recommendation.

• Playbook: Score your ICP on stack density (L4) (revops, L4 L4 Orchestrated)
• Playbook: Put an answer layer on the warehouse you already paid for (L4) (revops, L4 L4 Orchestrated)
• Playbook: The agent control plane (L4) (revops, L4 L4 Orchestrated)
• Tool: Mode (Data & Analytics)
• Tool: Vector (Sales & Revenue Intelligence)
• Tool: Rows.com (AI Agents & Workflow)
• Tool: Unbabel (AI Agents & Workflow)
• Tool: Writer AI Agents (AI Agents & Workflow)

• Research: what works
• Research: spend vs attribution
• Related analysis
• The BUILD, BUY, THREAD framework, explained