What is threading in an AI stack?

Threading is building your own motion into a platform you bought: your prompts, plays, ICP model, evidence, and customer language. The vendor supplies the substrate. The threads are the part a competitor buying the same platform does not have.

When should a revenue team build instead of buy?

Build when the capability is internal and encodes intelligence unique to your business, such as an ICP model or an enablement corpus. Buy anything that is infrastructure, internal or buyer-facing.

Why is buying licenses not a strategy?

Licenses change tooling, not the operating model. Without threading and organizational change, every competitor can buy the same capability the same week.

Framework · Sourcing rule

BUILD, BUY, THREAD

BUILD, BUY, THREAD is a sourcing rule for AI capability, placed on two axes: who uses it, buyer-facing or internal, and what layer it is, infrastructure or intelligence. Infrastructure gets bought. Internal intelligence gets built. Buyer-facing intelligence gets bought as a platform and threaded with your own motion.

Share this framework

Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.

What it is

The old build-versus-buy binary misses the option that matters. Most AI infrastructure vendors will win on capability. Your durable edge is what you thread into their systems.

Threading means building your motion, language, plays, and evidence into a platform you did not build from scratch.

The four quadrants

Buyer-facing infrastructure, buy

CRM, marketing automation, phone, video, storage. Nobody wins by building what everyone else already bought.

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.

Internal infrastructure, buy

Compute, model APIs, vector stores, agent runtimes. Rent the utilities. Buying infrastructure is not a strategy by itself.

Internal intelligence, build

Your ICP model, your enablement corpus, your reply corpus, your reversal ledger, your customer voice model. Only you can build these.

The visuals

Figure

The sourcing grid

Build in the seams. Buy the substrate. Thread the intelligence.

Internal to Buyer-facing

BUY

Everyone has it. CRM, marketing automation, phone, video.

BUY AND THREAD

Buy the platform, thread your prompts, plays, and evidence into it.

BUY

Rent the utilities. Compute, model APIs, vector stores, agent runtimes.

BUILD

Your ICP model, reply corpus, reversal ledger, customer voice model.

InfrastructureIntelligence

Figure

What threading looks like

The platform is the substrate. The threads are the moat.

The platform you bought

Your ICP model

Your language

Your playbooks

Your named-expert corpus

Your reversal ledger

Your customer voice

The platform you bought

Same platform, no threads, no moat.

What you get out of it

Run the audit and every capability in the stack carries a sourcing decision you can defend. You stop arguing build versus buy on capabilities that should be threaded, and the stack becomes strategically coherent.

A stack map where every layer is labeled build, buy, or thread.
Competitive edge concentrated in the two quadrants where your motion actually lives.
A finance story that explains why you bought where you bought and built where you built.

The mistakes it prevents

The old binary: Arguing between an inferior build and a generic buy, when the answer was buy and thread.
Buying AI-native infrastructure: Compute is compute and model APIs are commoditized. A premium wrapper on both is still a wrapper.
Building infrastructure: Every hour spent building a vector store is an hour not spent building intelligence.
Buying intelligence: Generic intelligence means you now run a motion identical to every other buyer of the same tool.
Not threading: The platform gives you most of the capability. The threading gives you the part competitors cannot copy.

How it is used here

Every architecture teardown in the Report labels each layer build, buy, or thread. A reader can audit their own stack the same way in one afternoon.

You need a person to go to an internal use case of an SDR, accountant, HR, whoever, and sit down and understand what's going on and build this infrastructure for each team.
Jonathan Kvarfordt, Adventures in Revenue podcast

The only thing unique then is the people. So the people who are able to amplify themselves with AI, those are the ones they need to double down on.
Jonathan Kvarfordt, Adventures in Revenue podcast

Terms used here are defined in the glossary and explained in plain language in the AI and Revenue Dictionary.

Apply it with a skill

Each skill turns this framework into a job you can finish. Copy the quick prompt for one task, or download the SKILL.md file, a reusable set of instructions for an AI assistant, for repeatable work.

Decide Whether to Build, Buy, or Connect a CapabilityA sourcing call for one AI capability, with the reasoning written down so the next person can challenge it.

All skills and prompts →

Common questions

What is threading in an AI stack?: Threading is building your own motion into a platform you bought: your prompts, plays, ICP model, evidence, and customer language. The vendor supplies the substrate. The threads are the part a competitor buying the same platform does not have.
When should a revenue team build instead of buy?: Build when the capability is internal and encodes intelligence unique to your business, such as an ICP model or an enablement corpus. Buy anything that is infrastructure, internal or buyer-facing.
Why is buying licenses not a strategy?: Licenses change tooling, not the operating model. Without threading and organizational change, every competitor can buy the same capability the same week.

Cite this framework

Kvarfordt, Jonathan. "BUILD, BUY, THREAD." The Revenue AI Report. https://www.therevenueaireport.com/frameworks/build-buy-thread

All frameworks →