Persona Playbooks
A guide for founders and solo operators on how to organize a growing business intelligence library — build a structured system for competitive
A founder's most valuable competitive advantage is rarely written down anywhere a second person could find it. At seed stage that's fine — the market fits in one person's head, and speed matters more than documentation. It stops being fine the moment a team forms around that founder and starts making decisions the founder alone can no longer make from memory.
That transition happens faster than most founders expect. The competitive set thickens, new segments emerge, pricing shifts, and a regulatory wrinkle nobody budgeted time for shows up. The founder who could once recall every competitor's positioning from memory becomes the bottleneck: the intel lives in their browser bookmarks, the customer discovery notes are scattered across a handful of Notion pages and email threads, and nobody else on the team can act on what only the founder knows.
This guide is for the founder or solo operator who has hit that wall — or wants to build the habit before hitting it. Organized business intelligence isn't overhead for well-funded companies with a research team. It's how a small team makes decisions that look like they came from a company several times its size.
Founders and solo operators need to organize four categories of business intelligence:
1. Competitive intelligence: Who the competitors are, how they're positioned, what they're doing, and what their moves signal about the market's direction.
2. Market intelligence: The size, shape, and dynamics of the market — customer segments, buying behavior, pricing sensitivity, channel dynamics, growth drivers.
3. Customer intelligence: What specific customers say, need, and do — the ground-level evidence for product-market fit decisions.
4. Industry and ecosystem intelligence: The broader context — regulation, technology platforms, talent markets, investor trends, adjacent market developments — that affects the business over a longer horizon.
Each category has different update cadences, different retrieval needs, and different decision contexts. The organizational system needs to handle all four.
Create a primary Collection: "Business Intelligence: [Company Name]"
Sub-Collections:
Competitors:
Market Intelligence:
Customer Intelligence:
Industry and Ecosystem:
Strategic Questions (current focus):
The Strategic Questions sub-Collections are temporary: they exist for the duration of the question. When a question is answered, archive the Collection. This organization ensures that your intelligence library is always oriented toward current decisions rather than just accumulating historical information.
For each significant competitor, maintain a living profile document as the anchor in their sub-Collection. The profile is updated as new information arrives; the individual captures in the sub-Collection are the evidence base.
COMPETITOR: [Name]
Website: [URL]
Profile last updated: [date]
OVERVIEW
What they do: [one sentence]
Target customer: [who they're primarily serving]
Pricing: [model and price points — date this]
Funding/stage: [last known funding, amount, investors]
POSITIONING
Their positioning headline: [from their homepage]
Key value proposition: [what they lead with]
Who they say they're for: [explicit target market]
HOW WE WIN AGAINST THEM
When we beat them: [situations, deal types, customer profiles]
Our strongest differentiation argument:
What customers say when they choose us:
HOW WE LOSE TO THEM
When they beat us: [situations, deal types, customer profiles]
Their strongest argument against us:
What customers say when they choose them:
RECENT MOVES (newest first)
[Date]: [Event — product launch / pricing change / funding / new hire / partnership]
[Date]:
SIGNALS TO WATCH
What I'm monitoring in their trajectory:
Hiring patterns suggesting investment area: [from LinkedIn job postings]
Their apparent roadmap direction (inferred):
Update competitor profiles in intelligence sessions, not reactively. A competitor pricing page that changes doesn't need immediate response — it needs to be captured (Stage 1), processed in an intelligence session, and interpreted in the context of the full competitive picture.
Beyond individual competitor files, maintain a landscape-level document that provides a map of the full competitive environment:
COMPETITIVE LANDSCAPE: [Market Category]
Last updated: [date]
MARKET SEGMENTS WE COMPETE IN
Segment A: [our position / key competitors / dynamics]
Segment B: [our position / key competitors / dynamics]
HOW THE MARKET IS SEGMENTED
[High-level map of how customers/competitors cluster]
WHERE WE WIN
Our strongest segments / deal types / customer profiles:
WHERE WE LOSE
Our weakest areas / where competitors consistently beat us:
MARKET DYNAMICS
Is this market growing or shrinking? [evidence]
How is pricing trending? [evidence]
What platform changes are affecting competition? [evidence]
WHAT I'M WATCHING
Changes that would significantly affect our competitive position:
Emerging players worth monitoring:
The landscape document is the synthesis; the competitor files are the evidence. When you need to explain the competitive landscape to an investor, a new team member, or a potential partner, the landscape document is the starting point.
Customer intelligence — what customers say, need, and do — is the highest-value intelligence for founders, and also the most poorly organized. It arrives across channels (support tickets, sales calls, NPS surveys, community posts, social media mentions, churn surveys) in an unstructured form that's hard to aggregate.
The customer intelligence library provides a consistent home for this information.
For each significant customer capture:
Source: [support ticket / sales call / NPS survey / interview / community post / social]
Date: [when this was said/written]
Customer segment: [which segment this customer belongs to]
Customer stage: [prospect / new customer / established / churned]
What they said (verbatim or close paraphrase):
The underlying need or pain: [your interpretation of what they're actually experiencing]
Product area: [which part of the product or workflow this relates to]
Decision relevance:
Affects: [pricing / product roadmap / positioning / onboarding / support]
Priority: [high / medium / low — based on how common this is and how much it matters]
Action: [what should be done about this / who owns it / by when]
The "customer segment" and "customer stage" fields are critical for weighting intelligence. A churn feedback item from a customer who was a poor fit for the product is different from the same feedback from a customer who was your target ICP and left for a competitor. The first is informative; the second is urgent.
Individual customer captures are data points; patterns are intelligence. The most valuable use of the customer intelligence library is identifying patterns:
Run pattern reviews quarterly: pull all customer intelligence captures from the last quarter and look for repeated themes, recurring pain points, and patterns in where you're winning and losing.
A founder's intelligence library is only valuable to the extent it informs decisions. The most efficient way to organize intelligence for decision-making is to structure it around current strategic questions.
At the start of each quarter, identify 3-5 strategic questions you need to answer:
For each question, create a sub-Collection: "Strategic Q: [Question]". When you encounter intelligence relevant to one of these questions, add it to that sub-Collection.
At the end of the quarter, review the Strategic Q Collections. Each should contain enough organized evidence to answer its question (or to know that you need to gather more specific intelligence to answer it).
The strategic question Collections are temporary by design. They're relevant for a quarter, then archived. The archive is valuable if the question resurfaces; the temporary nature keeps the active library focused on current decisions.
Business intelligence has a shorter shelf life than most other research domains. A competitor pricing capture from 18 months ago may be accurate or may be completely wrong — they've probably changed their pricing at least once. A market sizing report from 2022 may be significantly outdated by 2026.
Undated or stale intelligence that's treated as current is dangerous: it produces confident decisions based on incorrect information.
Maintenance practices:
Date all competitive intelligence explicitly. Every competitor profile, every pricing capture, every positioning update should have a "last verified" date. Any intelligence older than 6 months on dynamic dimensions (pricing, features, positioning) should be reverified or marked "status unknown."
Quarterly competitive review. Once a quarter, review each competitor profile:
Annual market landscape review. Once a year, reassess the full market map:
When intelligence becomes outdated, archive rather than delete. A competitor's 2023 pricing structure that's been superseded by their 2026 pricing is still useful — it shows the direction of change and the scale of adjustment.
Archive structure: maintain an "Archive: [Year]" Collection for each year of significant intelligence. Historical intelligence about how competitors behaved, how the market evolved, and what customers said at different stages is valuable context for future decisions.
The scenario: A solo founder of a B2B project management tool for architecture firms has been operating for 2 years. She has scattered research across Notion, browser bookmarks, and email. She's preparing to raise a seed round and realizes that investors will ask detailed competitive and market questions she can't currently answer quickly.
Library setup (2-week project):
Collections created for 6 significant competitors, with basic profiles built from public information:
Customer intelligence organized from 18 months of customer conversations:
Strategic Q Collections for seed round prep:
Investor meeting use:
Meeting with a seed investor: "Can you walk me through the competitive landscape?"
Founder opens the competitive landscape document (updated 3 weeks prior) on her laptop:
Investor feedback: "Best competitive answer I've seen from a seed-stage company this year. Usually founders know their market or their competitors, not both. You knew both and you had evidence."
A founder's intelligence library is the foundation for confident decisions in a rapidly changing environment. Without organization, the intelligence exists but is inaccessible — scattered across bookmarks, emails, and notebook pages in a form that can't be quickly retrieved or synthesized. An organized library — with competitor files, customer intelligence organized by segment, and current strategic question Collections — supports the kinds of decisions that matter at every stage of a company: which features to build, which segments to target, how to position against competitors, and why the market opportunity is real. The 2-week investment to build the initial structure produces dividends across every strategic conversation the founder will have.
Related reading: Web Clipping for Research Papers.
More WebSnips articles that pair well with this topic.
A guide for educators and course creators on how to organize a growing research library — build a structured teaching resource system for subject matter
A guide for lawyers on how to organize a growing research library — build a structured legal intelligence system for case law developments, regulatory
A guide for marketers on how to organize a growing research library — build a structured marketing intelligence system for competitive ads, campaign
A guide for remote team leads on how to organize a growing research library — build a structured knowledge system for async communication practices
A guide for knowledge workers and consultants on how to organize a growing research library — build a structured system for client intelligence, domain
A guide for PKM and tools enthusiasts on how to organize a growing research library — build a structured web research archive that integrates with your