Persona Playbooks
A guide for founders and solo operators on how to turn their intelligence library into finished business outputs — investor decks, product strategy
A founder's limiting resource is rarely more research. Most founders who have spent a year capturing competitor moves, customer signals, and market data already know more about their market than their investor deck, board memo, or sales battlecard currently shows. The bottleneck sits between what they know and what they've actually written down for someone else to use.
That gap matters because founders are constantly asked to prove things: investors want evidence the market is real, boards want evidence the quarter's decisions were sound, sales reps want evidence to counter a specific competitor in a specific deal. Each of those asks is really a request for a document, and the document is only as good as the founder's ability to pull the right slice of accumulated intelligence and turn it into something someone else can read in five minutes.
Writing that document also does something for the founder directly — it's usually the moment gaps in the underlying research become visible. A board memo that won't quite come together is often telling you that a piece of customer evidence you assumed you had doesn't actually exist yet.
This guide is about the mechanics of that translation — turning an intelligence library into the investor materials, strategy documents, and battlecards a founder actually has to produce.
Founders produce six types of documents that draw heavily from their intelligence library:
1. Investor materials: Pitch decks, executive summaries, data rooms. These require market research, competitive intelligence, and customer data organized into a narrative about why the market is real, why the timing is right, and why your team has the right to win.
2. Strategy documents: Annual plans, quarterly strategic memos, product strategy documents. These synthesize what you've learned about the market, customers, and competitors into direction for the business.
3. Product briefs and PRDs: Product specification documents that draw on customer research and competitive intelligence to justify what to build, for whom, and why.
4. Competitive battlecards: One-page references for sales conversations, summarizing how to win against each competitor. Dense with competitive intelligence; designed for retrieval during live conversations.
5. Board memos: Regular communications to the board summarizing what's happening, what you've learned, what you're deciding. These draw on customer intelligence, market signals, and operational data.
6. Customer-facing content: Thought leadership articles, case studies, customer newsletters. These draw on market knowledge and industry intelligence to produce content that builds trust and authority.
Before pulling from your intelligence library, answer two questions:
The answers define what to include and what to leave out. A competitive battlecard for a sales rep needs different depth and format than a competitive landscape section of an investor deck, even though both draw from the same competitive intelligence library.
Filter your library to the intelligence that serves this specific document:
customer-signal tags for the relevant segment + customer interview capturesThe goal is not to include everything — it's to identify the 20% of your intelligence that does 80% of the work for this specific document. Most intelligence documents fail because they include too much: every piece of intelligence gathered rather than the most important pieces synthesized into an argument.
Before writing the document, build a synthesis note: what does the totality of this intelligence tell you?
For a competitive section of an investor deck:
SYNTHESIS: COMPETITIVE LANDSCAPE (for investor deck)
WHAT THE INTELLIGENCE SHOWS
1. The market has 8 players, but competition effectively clusters into 2 categories: [describe]
2. Our strongest direct competitors (A and B) are positioned for [X], which leaves [Y] underserved
3. Our win rate against A and B is [N]%; we win primarily when [conditions]
4. The most important differentiator in competitive deals is [specific feature/characteristic] — documented in [N] win/loss captures
THE INVESTMENT THESIS IMPLICATION
This competitive landscape supports the claim that [our opportunity] because:
- The current competitors are not solving [specific gap]
- We are specifically built for [gap] — our wins confirm this
- No well-funded player is currently pursuing this position
WHAT INTELLIGENCE IS STILL MISSING
- Win rate data against Competitor C (only 2 deals; need more)
- Current pricing of Competitor B (last verified 4 months ago — should re-verify)
The synthesis note is the intellectual work. The document is the synthesis note in presentation form.
When writing the document, work from the synthesis note and from the specific captures you've identified as supporting each claim. Do not try to include everything in your library.
This produces documents that are:
The raw intelligence library is the evidence base. The synthesis note is the argument. The document is the communication.
Investors see hundreds of competitive slides. The ones that persuade are specific:
From your intelligence library:
A battlecard should be one page, scannable in 2 minutes, and immediately useful in a live competitive conversation.
Structure:
BATTLECARD: vs. [Competitor Name]
WHO THEY TARGET
[Their stated ICP in one sentence]
HOW THEY POSITION
"[Their actual marketing headline or key message]"
WHEN THEY BEAT US
[Situations where we lose to them — honest, not defensive]
WHEN WE BEAT THEM
[Situations where we win — specific conditions]
OUR STRONGEST ARGUMENTS AGAINST THEM
1. [Specific technical or feature argument]
2. [Specific business value argument]
3. [Specific proof point — customer or data]
THEIR LIKELY ATTACKS ON US
- "[What they typically say about us]" → Our response: [specific]
- "[Their second typical attack]" → Our response: [specific]
KEY PROOF POINTS
- [Customer X switched from them for [reason]]
- [We won against them in [deal type] [N] times last quarter]
- [Independent comparison: [source] ranked us higher on [dimension]]
PRICING COMPARISON
[Their pricing as of: DATE] vs. [Our pricing]
Key pricing differences: [specific]
The battlecard is produced from the competitor sub-Collection. Pull the competitor profile, the relevant win/loss captures, and customer intelligence captures that reference this competitor. Write the battlecard from those sources.
Update battlecards quarterly or whenever significant competitive intelligence arrives (pricing change, new feature launch, positioning shift).
A product brief built from your customer intelligence library is more credible and more useful than one built from product team intuition:
Problem statement section: Pull customer intelligence captures where the problem is described in customers' own words. Quote 2-3 specific customers (anonymized if appropriate). The problem statement should cite evidence, not assert.
Customer segment section: Pull your ICP definition work. Which segment experiences this problem most acutely? What do they look like?
Success criteria section: Pull customer intelligence on what "good" looks like for them. What would they consider success for this feature or product?
Competitive context section: Pull relevant competitor captures. Who is currently solving this problem partially, and why isn't it sufficient?
A product brief that cites "from 23 customer conversations and 8 support ticket patterns" is more persuasive internally than one that asserts "customers need X." The intelligence library is what makes the evidence claim credible.
WebSnips' Creator Studio can accelerate the drafting of business documents from your intelligence library. Appropriate uses:
Not appropriate: asking Creator Studio to generate intelligence it doesn't have, or to produce claims that aren't supported by your captures.
The Creator Studio workflow for business documents:
Every business document drawn from your intelligence library requires a verification pass before sharing:
The verification pass is especially important for investor materials, where inaccurate claims are a reputational and legal risk.
The scenario: A B2B SaaS founder is preparing a Series A investor deck. The competitive section is the most common area for vague, generic slides. She wants to produce a competitive section with specific evidence.
Intelligence available:
Synthesis note built (30 minutes):
From the win/loss captures:
From competitor files:
Synthesis: "The market is dominated by simple, horizontal tools positioned for accessibility. The complexity required for architecture/engineering workflows is underserved. Our 91% win rate in enterprise deals with specification versioning requirements confirms this is the deciding criterion."
Competitive slide produced (20 minutes of writing from synthesis):
Slide 1: Market map showing 2×2 of "simple/accessible" vs "complex/workflow-specific" on one axis and "horizontal" vs "vertical" on the other. 4 competitors plotted in "simple/horizontal" quadrant. Our product in "complex/vertical" quadrant. Empty quadrant: "complex/horizontal" — why we're not there.
Slide 2: Win rate by scenario. "91% win rate when specification versioning is required (26 deals). 72% overall win rate. Primary loss scenario: SMB price sensitivity vs. Competitor B."
Slide 3: 2 customer quotes (anonymized) on why they chose us over Competitor A. One direct quote about specification versioning.
Investor feedback on the section: "This is exactly what I want to see in a competitive slide — you have actual data, not assertions."
The founder who has spent a year systematically gathering competitive intelligence, customer signals, and market research has built genuine knowledge advantage. That advantage produces business returns only when it's translated into documents others can act on: investor decks with specific evidence, battlecards sales reps can use in live deals, product briefs that reflect what customers actually need. The workflow — define the document's purpose, identify the relevant intelligence, synthesize before writing, write from the synthesis — converts an intelligence library into business output that demonstrates the depth of the founder's market knowledge. The intelligence gathering was the investment; the document production is the return.
See also: Web Clipping for Research Papers.
More WebSnips articles that pair well with this topic.
A guide for educators and course creators on how to turn saved research into finished output — build better lesson plans, course modules, assessments, and
A guide for lawyers on how to turn saved research into finished output — write better client memos, regulatory analyses, briefs, due diligence summaries
A guide for remote team leads on how to turn saved research into finished output — write better team protocols, onboarding documents, async communication
A guide for PKM and tools enthusiasts on how to turn a saved research library into finished output — overcome the perpetual preparation trap, write from
A guide for marketers on how to turn a saved marketing intelligence library into finished output — write better campaign briefs, creative strategy
A guide for knowledge workers and consultants on how to turn a saved intelligence library into finished deliverables — produce better strategy memos