What's Inside an ICP Intelligence Brief: A Full Walkthrough

Six Sections. One Buyer Archetype Per Brief. By API.

If you've evaluated MeetBri's data offering and wondered what an actual ICP Intelligence Brief looks like — not the marketing description, but the structured payload your model or runtime would consume — this post is the walkthrough.

We license one brief per buyer archetype. An archetype is a specific intersection of role × industry × company stage. CRO at Tech/SaaS at growth stage is one archetype. CFO at Health Systems at enterprise scale is another. CIO at Healthcare Services at health system scale is a third. Each brief is built from the corpus of long-form executive interviews matching that archetype and structured into six sections delivered by API.

Below is a walkthrough of all six, using the CRO at Tech/SaaS archetype as the running example. The data points and language samples in each section are pulled from real interviews. This is what your model or sales training tool receives when you pull this archetype's brief.

Go deeper: The GTM Enrichment partner page walks through deployment options, integration patterns, and how the briefs plug into ICP scoring, message generation, and persona-driven AI features.

Section 1: Persona Portrait

The first section is a written summary of who this buyer is — the narrative version of what the rest of the brief structures.

For the CRO at Tech/SaaS archetype, the portrait describes a revenue-function executive who has consolidated authority across pipeline, retention, and growth. They came up through sales leadership; they think operationally. They are growth-oriented at near-ceiling levels and stakeholder-focused at high levels. They are not technology-fluent in the abstract — they care about technology only when it changes seller behavior or pipeline outcomes. They reach for personal narrative as a credibility currency more often than other C-suite roles.

The portrait is the human-readable handle. It's the section your team uses to align on who the brief describes before any of the structured data gets deployed into models.

Section 2: Behavioral Factor Profile

Every brief includes a seven-dimension behavioral profile, each scored 1–5 on the basis of the underlying interview corpus.

For the CRO at Tech/SaaS archetype:

That profile is the load-bearing structure for any scoring or personalization use case. The CRO at Tech/SaaS is near-ceiling on growth — meaning pitches that lead with scale, expansion, and momentum will land naturally. They are mid-tier on technology — meaning pitches that lead with technical sophistication or AI-architecture vocabulary will land softer than expected for a SaaS-adjacent buyer. They are mid-tier on data — analytical claims are accepted but not led with.

The seven-factor structure lets your model treat archetypes as multi-dimensional vectors rather than as flat personas. Two archetypes with the same growth score can differ meaningfully on stakeholder or operations, and your model can distinguish them.

Section 3: What They Care About

The third section is the priorities-and-concerns layer. It contains five subsections, each surfaced from the corpus:

• Priorities — what the archetype consistently names as the work that matters
• Pain points — what they consistently surface as friction
• Success metrics — what they measure themselves on
• Decision frameworks — how they evaluate whether to act
• Red flags — what makes them disqualify a partner or initiative

For the CRO at Tech/SaaS archetype, sample priorities include:

• Spending time on-site with customers
• Learning the product, industry, and customer deeply
• Creating a better operating environment for the sales contractor workforce

Sample red flag:

• Recognizing performance without tying it to success behaviors

That red flag is a sophisticated objection that almost no synthetic persona produces. It's the CRO challenge to a vendor's outcome claims: how do you know your tool caused the result, rather than the result being attributable to other variables? When your roleplay tool simulates this objection at the right moment, your reps experience the actual CRO conversation. When it doesn't, the simulation lands flatter than the live call.

The structured priorities-and-concerns layer is what lets a message generator produce output that addresses what this buyer actually cares about — not what a generic CRO persona template assumes they care about.

Section 4: Their Language

The language section is where briefs differ most from generic persona templates. Three subsections, each with frequency data:

Power words — the vocabulary this archetype reaches for as emphasis. For CRO at Tech/SaaS, top power words include: successful, scale, critical, amazing, powerful, impact, winning, value, incredible, win, superpowers, growth. Each word comes with a prevalence count so your model can weight which terms are most representative.

Negative words — the vocabulary this archetype uses to describe what doesn't work. For CRO at Tech/SaaS: not working, useless, not repeatable, friction, doesn't work, you're cooked, yesterday's game, wasting my time, was told I was crazy, tug of war. This is the objection vocabulary your AI roleplay tool needs to deploy at realistic frequencies for the simulation to match the live call.

Jargon — the technical and industry-specific terms this archetype uses without explanation. For CRO at Tech/SaaS: CRO, ARR, CRM, AE, ICP, KPIs, SDR, SMB, PLG, GTM, RevOps. This is the working acronym set. A pitch deck that uses any of these terms incorrectly signals immediately to the buyer that the seller doesn't operate in their world.

Each subsection carries the prevalence data with it. Your model knows not just which words this archetype uses, but how often — so the weighting is built in.

Section 5: How They Buy

The buying-process layer covers three subsections:

• Buying triggers — what events or conditions push this archetype toward considering a new vendor
• Evaluation criteria — what factors they actually use when scoring vendors (often different from what they say they use)
• Leadership style — how they make decisions internally and how they expect vendors to engage

For some archetypes, this section is densely populated from the corpus. For others — including the CRO at Tech/SaaS in our current data — the buying-process layer has lower density than the language and priorities sections, reflecting that long-form interviews surface "how I think" content more often than "how I bought my last vendor" content. The brief is transparent about that density: lower-confidence subsections are marked.

When your scoring system or sales training tool needs buying-process data, it sees both what's there and how confident the brief is in each subsection. That transparency is part of the structured product, not a workaround.

Section 6: Tone, Outreach Templates, and Objection Table

The final section is the deployment-ready application layer. Three subsections:

• Tone guidelines — the register and posture that match this archetype's preferred communication style
• Outreach templates — example opening lines, email subjects, and call-introduction phrasing matched to the language and priorities surfaced above
• Objection-handling table — paired objections (in the archetype's actual negative-vocabulary) and recommended seller responses

For the CRO at Tech/SaaS archetype, the objection-handling table includes pairings like:

This is the deployment-ready content. A message generator can produce outreach in the right tone using the templates. An AI roleplay tool can simulate the objections in the actual CRO vocabulary. A scoring system can weight conversations against the priorities and language.

How Briefs Are Delivered

Each brief is structured JSON, served by API, refreshed on monthly cadence as the underlying corpus updates. Your team integrates the brief once; the refresh cycle handles the language drift over time. The ICP Rot post we published earlier this year documented why that refresh cadence matters — buyer vocabulary moves faster than most ICP models account for.

The brief is the product. It's not a report you read once. It's the structured input your AI features consume to make their outputs match the buyer your team actually faces.

Which Archetypes Are Available

We license briefs across the C-suite × major industry × company stage matrix. The most-requested archetypes — CEO, CFO, CRO, CIO, CMO, CISO across Tech/SaaS, AI/SaaS, Health Tech, Cybersecurity, Healthcare Services, Financial Services, Manufacturing — are available now. Adjacent role and industry combinations are available on request, depending on corpus density.

If you want to see the full structured payload for an archetype relevant to your product, the GTM Enrichment partner page is the place to start. The walkthrough above is the surface. The actual structured brief — with all six sections, prevalence data, and deployment-ready templates — is the product behind it.