Twenty minutes. That’s how long John Munsell of Bizzuka says an AI-built prospect brief took, for work he estimates would have kept four people busy for about two weeks.
That’s a showcase from r/PromptEngineering, pulled from an interview on the Better Business Better Life podcast. Munsell was heading to Houston to meet several higher ed institutions. He skipped the usual scramble through LinkedIn and news alerts. His team ran a set of AI skills they had built, and it returned a brief for the higher education sector.
Treat the numbers as his estimate, not a benchmark. Nobody ran a controlled test. Even if the real gap is a tenth of that, it’s still a big shift in prep time. Two days of research for a trip becomes a couple of hours, and that changes how many meetings a small team can walk into well prepared.
What the brief actually contained
The interesting part isn’t the speed. It’s what the brief covered:
- Buying signals. New hires, promotions, and who just took charge of key areas, matched to what his company actually sells. A new VP of digital learning, for example, is a very different conversation starter than a generic “how are things going.”
- New state regulations. Rules the schools now have to comply with, including deadlines that could create urgency on their side.
- Insurance requirements tied to AI adoption. Things the schools might not know about yet.
The last two are the edge. When you walk in knowing what just changed and what the school is on the hook for, you’re not just prepared. Sometimes you’re the one telling them something new. That flips the dynamic from a sales pitch to a useful briefing, and people remember who told them something they didn’t already know.
3 practical applications
🎯 Pre-meeting briefs for any sector. Swap higher ed for healthcare, logistics, or local government. The structure holds: who changed roles, what rules changed, what that means for what you sell. A rep covering hospitals might track new compliance mandates, while one covering city governments might track budget cycles and procurement rules.
🎯 Team-wide standard for account prep. Every rep works from the same brief format instead of their own version. Quality stops depending on who had time that morning. New hires also ramp faster, because they can read ten finished briefs and see exactly what “good” looks like.
🎯 Compliance-angle outreach. Use the regulation and requirement findings as the opening line of a cold email. It’s specific, and it’s useful to the reader. Something like “Your state just changed its rules on X, and here’s what that means for your Q1 plans” earns a reply far more often than a generic intro.
Tips and pitfalls
The post’s own advice is the best part: write down what a good account brief looks like on your team today, then build a repeatable process around it. Define the standard first, automate second. If you automate a vague process, you just get vague output faster.
A commenter on the thread backed this up, saying the last paragraph is the piece they’d copy. They also noted that trust breaks fastest when a buying signal in the brief turns out to be wrong. That’s the pitfall to plan for. One bad claim said out loud in a meeting can undo the credibility the other nine correct ones built.
A few ways to guard against it:
- Ask the AI to cite a source for every signal and regulation, and open the links before the meeting.
- Mark each item as confirmed or unverified in the brief itself.
- Spot-check one claim per brief. If it fails, don’t use the rest without checking.
- Never state a regulation to a client as fact until you’ve read the primary text.
- Check dates. A promotion announced eight months ago is history, not a signal.
Pros: huge time savings, consistent standard across reps, and you walk in with something fresh to teach.
Cons: it only works if your definition of “good brief” is clear, and unverified AI claims can cost you credibility fast.
Your move
This week, write down the five things your best rep always knows before a big meeting. That list is your brief template. Turn it into a prompt, run it on your next prospect, and time it against your old method. Then compare the two briefs side by side and note what the AI missed, so the second version of your prompt closes that gap.
The full interview is on YouTube if you want to see how teams learn to build these tools: https://www.youtube.com/watch?v=LsAWMe6S1Vc
Frequently Asked Questions
Q: How do you keep an AI prospect brief from sending reps out with a stale or wrong signal?
Give every signal a date and a source link. One team found that a ‘just promoted’ note from two years ago, or a regulation that was proposed but never passed, broke trust faster than anything else. With dates and links attached, a rep can check the sources in a couple of minutes instead of redoing the research.
Q: What belongs in a background section instead of the signals list?
A common rule is to move anything older than about 90 days into a separate background section. Those items still tell you something about the school’s history and priorities, but they shouldn’t count as a reason to reach out. Keeping them apart stops an old fact from looking like fresh news.
Q: Can the 20-minute brief stay 20 minutes once you add verification?
Yes, if the checking is built into the format. When every claim already has a date and a link, verifying it becomes a quick scan rather than a second round of research. The brief stays fast because the rep never has to hunt for the proof.
How to use AI to build prospect briefs in 20 minutes
by u/Admirable_Phrase9454 in PromptEngineering