# AI GTM Workflows and Prompts for B2B Revenue Teams

Build one persistent AI workspace with the business context, real artifacts, and standing instructions your revenue team uses every week.

Use worked prompts for founders, CROs, and RevOps across board updates, forecasts, pipeline reviews, coaching, territories, and process documentation.

For AI planning, maturity, and governance, start with the GTM AI Charter™ on the AI strategy page.

## Why your AI output reads like it was written for nobody

Most leaders try AI by pasting in a one-off request: "write me a board update" or "build me a forecast model." The output reads like it was written for any company at any stage, because the model has zero context about your business, your numbers, or how you actually operate.

The fix is persistent context. Tools like Claude, ChatGPT, and Gemini all let you create a dedicated project: a saved workspace that holds your context and reads it before every response. Once that exists, every answer starts from understanding instead of guessing.

This is the same context a GTM Gap® diagnosis produces: an accurate, current picture of the business. The fastest way to make AI genuinely useful is to feed it the artifacts you already have.

## Five steps to set it up

- Create a dedicated project, not a one-off chat. A project persists context across every conversation you have inside it.
- Load your business context once: ICP, positioning, current metrics, how you actually sell.
- Upload your real artifacts: decks, playbooks, call notes, the last board update, your actual comp plan.
- Set the standing brief: a short paragraph on tone, format, and what "good" looks like.
- Run the worked prompts, then edit like an editor. Treat every output as a first draft from a sharp analyst.

## Three roles, three playbooks

Founder / CEO: turning a messy board update into something crisp, pressure-testing a fundraising narrative, sizing a new market, prepping for a hard leadership conversation.

Revenue Leader / CRO: diagnosing why a forecast keeps missing, prepping sharper pipeline reviews, building a rep coaching plan from call data, redesigning a comp plan.

RevOps: documenting a process that only lives in one person’s head, auditing the tech stack for what’s actually used, building a territory model, writing the SOP nobody had time for.

## Who this is for

Built for B2B leadership teams already running, or trying to run, a real go-to-market motion, not for teams still searching for product-market fit. AI amplifies whatever system already exists, and pre-PMF, there is no system yet to amplify.

## Frequently asked questions

### Do I need Claude specifically, or does this work with ChatGPT or Gemini?

The mechanism, not the brand. Claude Projects, custom GPTs, and Gemini Gems all do the same job: they hold persistent context across conversations instead of forgetting it the moment you close the tab. Use whichever tool your team already has a paid seat for.

### How much of my real data should I actually paste in?

More than most leaders are comfortable with at first. Vague inputs produce vague outputs. Real call notes, real forecast numbers, real deck drafts: that specificity is what separates a genuinely useful answer from a generic one. Keep client-identifying details out where it's not needed; the pattern matters more than the name.

### What if we don't have clean playbooks or documentation yet?

Then start with what's true, not what's polished. A messy paragraph describing how you actually route leads today is more useful context than a beautifully formatted playbook nobody follows. You can ask the tool to help you clean it up as a first step.

### Do I need a paid plan?

For real project/context features, yes, since the free tiers of most tools cap context window and project count in ways that make this workflow impractical past a handful of uses a week. It's a small line item next to what it replaces in hours.

### How is this different from what I'm already doing?

Most people use AI as a search bar with better grammar: one-off questions, no memory, no context. This is the difference between hiring a smart contractor with zero briefing and one who's read your last three board decks. Same tool, completely different output.

### What happens when the output is wrong?

It will be, sometimes. Treat every output the way you'd treat a draft from a capable but junior analyst: fast and useful, never shipped untouched. The judgment stays with you. That's not a limitation of the tool; it's the correct way to use it.