How it works

How it works

Done for you in 2–3 weeks, with about one day of your team's time spread across the project.

What working together looks like

1

Book & prep

After you book, I send you a short intake survey (5–10 min) and a link to schedule your expert interview(s).

2

Share what you already have

I set up a folder for any existing documentation you want incorporated: call transcripts, demo videos, webinars, RFP responses, user guides, messaging docs. A handful of strong examples beats a big folder of everything, and if you don't have much, that's fine. The interview is built to fill the gaps.

3

Customize the interview guide

I review your survey and materials, then build a custom interview guide to capture what your documents don't: the workflows, edge cases, competitive nuance, and buyer reality only your expert knows.

4

Interview your experts

60–90 minutes with your expert (sometimes two). This is the most critical part, the step generic tools and DIY templates skip, and it's why the output sounds like someone who actually knows your product.

5

Draft & review

I build all 5 deliverables, sourcing every claim back to where it came from. Anything that conflicts or I can't confirm gets consolidated and flagged for your review. Drafts delivered 5 days after the interview.

6

Finalize & deliver

After your review, I reconcile your feedback and deliver your final kit in two formats: markdown files ready for any AI tool and formatted docs for the humans on your team. Plus an Activation Guide and a Maintenance Guide to help you get started.

In under 3 weeks, you'll have everything you need to build and maintain an intelligence layer your whole GTM team works from, not a file that gets opened once.

"With our busy schedules, it can be hard to get product experts in a room for these in-depth conversations. The structured interview pulled far more out of that time than we'd get on a normal call. You dig deeper and capture the anecdotes and angles that wouldn't normally make it into documentation."
Emily MalesEmily Males
Sr. Digital Marketing Specialist

What I'll need from you

Most of this project runs on my desk, not yours. Here's everything I'll ask of your team, and how long each piece takes:

Step Your time
Intake survey 5–10 minutes
Scheduling the interview and sharing materials However long it takes to forward a scheduling link and drop files in a folder
Expert interview 60–90 minutes, no prep needed
Draft review Usually under an hour, because drafts arrive consolidated and color-coded

Your expert gives one focused interview instead of being the permanent review step for every piece of content your team ships.

How I protect what you share

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.

That protection carries into how the kit gets used too. 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.

Questions I hear a lot

More answers on the FAQ page.

Who should the product expert be?

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).

What existing materials should we share as inputs?

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.

Will it be accurate and technical enough for our product?

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.

Take a look before you book.

See a sample kit Schedule a discovery call

No pressure. The sample shows you exactly what you'd get.