Questions you might have

A done-for-you AI source of truth for complex B2B. I interview your product expert, capture the knowledge that's only in their head, and package it into product and buyer context your team and AI tools can use.

Seven documents — five core (Product Brief, Approved Claims Guardrail, Buyer Persona Profile, Stakeholder Messaging Guide, Use-Case Message Map) plus Activation and Maintenance guides. Each ships two ways: a readable doc for people and AI-ready markdown for tools.

AI Context Kit™ costs $3,500 per product, paid before the project starts. Additional products are 10% off each; each needs its own expert interview, because the knowledge base has to be product-specific. That price covers all seven deliverables, in both human-readable and AI-ready formats.

An AI Context Kit™ engagement runs 2–3 weeks end to end. First drafts arrive 5 business days after the interview and materials are in hand. Most of the remaining time is scheduling: booking the interview, then your review cycles.

About one day total, spread across the project, and most of that is the interview and review. Here's what you can expect:

• →Up front, you'll need to complete an intake survey (5–10 minutes), schedule the expert interview(s), and gather any existing materials to share.
• →The expert interviews are typically 60–90 minutes. No prep needed.
• →Five business days after the interview, I share the drafts for your team to review. Everything is consolidated and color-coded, so most reviews take under an hour. I've intentionally built this step to be as painless as possible.

Yes. The AI Context Kit™ sample kit contains all five core deliverables built for a fictional B2B company, so you can judge the depth and format before buying. Get the sample kit here.

Someone who knows how the product actually works in real customer environments and how buyers actually decide. Usually a product manager, solutions engineer, senior sales engineer, or technical founder. Sometimes one expert interview is enough, other times it's two. Either way, I'm after candid, technical depth (not a polished demo).

Point me to the high-signal materials you already have that are accurate, current, and supplement what your experts will share. For product context, that's things like implementation or user guides, datasheets, RFP responses, demo recordings. For buyer context it might be existing personas, messaging docs, and a few of your best sales call transcripts.

Focus on quality over volume here; a handful of strong examples is better than a big folder of everything. And if you don't have much, that's fine too. The interview is built to fill the gaps.

Yes, and the interview is exactly how I get there. I go deep on how your product actually works: the workflows, the edge cases, the details that never made it into your docs, and where it wins against the alternatives your buyers are weighing. Everything is built from what your expert says and the materials you share, with every claim sourced back. Anything that conflicts or I can't confirm gets flagged for you to review and approve.

Still skeptical? Read the sample kit and judge the depth for yourself.

I treat everything you share with me as confidential, and I'm glad to work under your NDA. You can share materials however you prefer, through your own folder or a private Google Drive folder I set up, and I use them only to build your kit. And if you'd like your source materials deleted when the project wraps, just say so.

You review every deliverable before we finalize, so you control what makes it into the final versions. And every kit includes a claims guardrail document you review that tells AI what's safe to say, what can be said with a caveat, and claims that can never be made. Once the kit is in use, that's how we keep confidential information out of the outputs your team creates with it.

Have specific requirements? Schedule a discovery call and we can talk them through.

All of them. Everything ships as structured markdown you can load as project context into Claude, ChatGPT, Gemini, Copilot, or any other LLM or AI marketing tool. Every kit comes with an Activation Guide for setup and use. Most teams start by creating a Claude Project or custom GPT with the kit files, either uploaded directly or connected through a shared GitHub repository, and see the difference on the first prompt.

No. I run the interview, decide what matters and what to leave out, and build the deliverables using judgment you can't automate. AI helps me move faster, but every claim is sourced from what you share, and every draft is reviewed twice, by me and by you. You're paying for the method and the judgment, not raw AI output.

AI only knows what it's been trained on, so prompts can't compensate for missing product knowledge. If the AI doesn't know how the product works or what claims are safe, better phrasing gives you a polished version of the same shallow output.

You absolutely can, but most lean marketing teams I talk with don't have the time or resources to do it well. Internal documentation projects without an outside owner, a deadline, and a structure tend to become just another good intention. AI Context Kit™ turns it into a fixed-scope project with a finished output this month. And the structured interview surfaces knowledge your team might not think to write down.

The hard part is extraction: getting the knowledge out of your expert's head and structured for the first time. Once the foundation exists, keeping it current is lighter, routine work. Assign an owner, fold updates into your release rhythm, and keep a changelog so everyone knows what's current. Every kit ships with a Maintenance Guide that covers exactly this: what to update, when to update it, and how to keep the source of truth from drifting.

Your first product is $3,500, and each additional product is 10% off. Each product needs its own expert interview, because the knowledge base has to be specific to that product to be useful. I'd start with one, your most complex or most neglected, and add more when you're ready.