How to Write Research Report from A Collection Of Sources
How to write a research report from a collection of sources — a step-by-step guide for academic researchers and PhD candidates who want to convert a
AI Writing & Creator Studio
How to write a research report from competitor research — a step-by-step guide for founders and solo operators who want to convert their competitive
A founder has forty browser tabs open, a spreadsheet row for that pricing change a competitor made in March, and a note somewhere about a review that mentioned a missing feature. All of it is real competitive intelligence. None of it is usable in a board meeting.
A competitive intelligence (CI) report is what converts that scatter into a structured internal document: organized by competitive dimension, with dated observations, comparison tables, and strategic implications the founding team can actually act on. Unlike a public market-analysis post, a CI report can hold specific pricing figures, feature-level comparisons, and review analysis that would be inappropriate to publish.
This guide covers the structure and process for building one from research you've already gathered. WebSnips' research report generator turns the dated observations below into the finished document.
| Section | Purpose |
|---|---|
| Executive Summary | Competitive landscape overview; key competitive dynamics; 3-5 strategic implications |
| Competitor Profiles | One section per competitor: positioning, pricing, features, customer sentiment |
| Comparative Analysis | Side-by-side comparison tables: pricing, features, G2 scores, target segments |
| Customer Sentiment Analysis | Aggregated review patterns (positive, negative, unmet needs) |
| Market Positioning Map | How competitors position against each other and against you |
| Competitive Gaps | Where no competitor serves the market well — your opportunity map |
| Strategic Implications | What this landscape means for your product, pricing, and messaging decisions |
| Methodology | How the research was conducted: sources, dates, selection, limitations |
| Source Log | All observed data with the date observed and source URL |
The source log is what distinguishes a CI report from informal competitive notes: every pricing figure, feature claim, and review quote includes the date observed and where it was found. This supports both accuracy (prices change; old data is misleading) and auditability (team members can verify observations independently).
| X/Twitter market thread | LinkedIn post | CI Report | |
|---|---|---|---|
| Audience | Public | Public | Internal — team, investors |
| Format | Short tweets with links | Single post | Structured report |
| Level of detail | High-level patterns | Single key observation | Comprehensive |
| Pricing specifics | Yes (with dates) | Risk (algorithm + legal) | Yes — detailed |
| Named competitor analysis | Careful | More careful | Yes — specific and detailed |
| Frequency | When useful | When relevant | Quarterly / major market events |
| Distribution | Anyone on platform | LinkedIn connections | Internal team, NDA-protected if sharing |
The CI report can be more specific and more comprehensive precisely because it's not public. Competitive pricing tables, detailed feature comparisons, and verbatim customer review quotes can appear in a CI report in ways that would be inappropriate in a public post.
Pricing data:
Feature data:
Customer sentiment data (from public reviews):
Positioning data:
Strategic observations:
Before structuring the research:
The purpose determines which sections matter most. A CI report for a pricing decision needs detailed pricing tables and customer sentiment on pricing. A CI report for an investor deck needs positioning analysis and market sizing signals.
For each competitive observation, record:
Observation: [What you observed]
Source: [Website / G2 / LinkedIn / Product Hunt / etc.]
URL: [Specific URL]
Date observed: [Date]
Verification status: [Confirmed from source / Inferred / Unverified]
The source log is what converts competitive notes into a CI report. "Competitor X's pricing starts at $49/month" is a note. "Competitor X's pricing starts at $49/month, observed from pricing page at [URL] on [date]" is a CI report observation.
For each competitive dimension (pricing, features, customer sentiment, positioning), create a comparison table. Tables are the core format for CI reports because they make the comparison immediately visible:
Pricing Comparison Table:
| Competitor | Free Tier | Entry Price | Mid Tier | Enterprise | Pricing Model |
|---|---|---|---|---|---|
| [Competitor A] | No | $X/mo | $Y/mo | Custom | Per seat |
| [Competitor B] | Limited | $X/mo | $Y/mo | Custom | Per usage |
| [Your product] | Yes | $X/mo | $Y/mo | Custom | Per seat |
| All prices as of [Month, Year] from pricing pages. Subject to change. |
I'm writing a competitive intelligence report covering [N] competitors in [category].
Report purpose: [What decision this informs]
Research coverage date range: [When observations were made]
Competitors covered: [List]
Executive summary brief: [3-5 most important competitive dynamics I want to highlight]
Competitor 1: [Name]
Positioning (from website, [date]): "[Headline or tagline]"
Target segment (from website/case studies): [Description]
Pricing (observed [date], [URL]): [Tier structure and prices]
Notable features (from website/documentation, [date]): [List]
Customer sentiment (from [platform], [N reviews]):
- Average rating: [X/5]
- Top positive mentions: [Patterns from reviews]
- Top negative mentions / complaints: [Patterns]
- Representative review quote: "[Public review text]" — Source: [Platform, date]
[Repeat for each competitor]
Customer Sentiment Analysis across all competitors:
[Aggregated patterns: what customers praise across the category, what they complain about, what they say is missing]
Market Positioning:
[How competitors position relative to each other]
Competitive gaps I've identified:
[Where no competitor serves the market well]
Strategic implications I want the report to surface:
[What this means for my pricing / features / messaging]
Draft a CI report with:
1. Executive Summary (200-300 words): landscape overview + 3-5 strategic implications
2. Competitor Profiles: one section per competitor with:
- Positioning statement (quoted from their site, with date)
- Pricing table or description (with date and source URL)
- Key features
- Customer sentiment summary
3. Comparative Analysis:
- Pricing comparison table (with observation dates)
- Feature comparison table
- Customer sentiment comparison (rating + key themes)
4. Market Positioning Summary
5. Competitive Gaps
6. Strategic Implications
7. Methodology: how this research was conducted, date range, sources, limitations
8. Source Log: all observations with date + URL
Tone: analytical, neutral, factual. No promotional language about my product.
All pricing and feature observations should note the date observed.
Before distributing the CI report internally:
CI reports based on public, verifiable observations are the legitimate standard. CI reports that contain information obtained improperly or misrepresent competitors create significant legal and reputational risk.
Category: Web research and clipping tools (internal CI report for a founding team)
Competitors profiled: 3 direct competitors
Before (informal competitive notes): "Competitor A is more expensive but has more features. Competitor B targets enterprise. Competitor C has bad reviews. We need to be cheaper and simpler."
No sources, no dates, no specifics, no strategic structure.
After (CI report, Competitor Profile excerpt):
Competitor A — [Category Tool 1]
Positioning (from competitor's homepage, observed June 2024): "[Exact tagline or headline]"
Pricing (observed from pricing page, June 2024, URL: [URL]):
| Tier | Price | Key inclusions |
|---|---|---|
| Starter | $X/user/mo | Feature list from their page |
| Pro | $Y/user/mo | Feature list |
| Team | $Z/user/mo | Feature list |
| Enterprise | Custom | Enterprise features |
Customer Sentiment (G2.com, 247 reviews, 4.2/5 average, accessed June 2024):
Strategic Observation: Competitor A's pricing page was updated in March 2024 to add a lower-tier entry point (previously Pro-only, now Starter at $X/mo). This followed [observable market context]. The new tier includes [features] but excludes [features], which suggests [strategic interpretation].
The CI report section contains specific dated observations, a structured pricing table with the observation date, customer sentiment from a named platform with review count, and a strategic observation that includes the evidence for the interpretation.
I'm writing a competitive intelligence report for [category].
Competitors: [List]
For each competitor:
- Positioning (from site, date): [quote]
- Pricing (from pricing page, date, URL): [tier/price structure]
- Key features: [list from site/docs]
- Customer sentiment: [platform, N reviews, rating, top themes, one representative quote]
My source log: [N observations with dates and URLs]
Strategic implications I want surfaced: [Based on this research]
Draft a CI report:
1. Executive Summary (landscape + 3-5 strategic implications)
2. Competitor Profiles (one per competitor: positioning, pricing, features, sentiment)
3. Comparison Tables (pricing, features, customer ratings)
4. Competitive Gaps
5. Strategic Implications
6. Methodology
7. Source Log
All pricing and feature observations dated.
A competitive intelligence report from your competitor research converts scattered competitive observations into a structured, dated, citable internal document that informs product, pricing, and go-to-market decisions. The key discipline is the source log — recording every observation with the date and URL that enables verification. Start with the 3-5 key strategic questions the report should answer, organize your observations by competitive dimension, build the comparison tables, and draft from there.
See also: Best Web Clipper Extensions.
More WebSnips articles that pair well with this topic.
How to write a research report from a collection of sources — a step-by-step guide for academic researchers and PhD candidates who want to convert a
How to write a research report from your highlights — a step-by-step guide for students and lifelong learners who highlight books and articles and want to
How to write a research report from your knowledge base — a step-by-step guide for remote team leads and ops people who want to synthesize institutional
How to write a research report from your meeting notes — a step-by-step guide for product managers and strategists who want to convert user interview
How to write a research report from your saved research — a step-by-step guide for writers and journalists who want to convert their accumulated research
How to write a research report from your web clippings — a step-by-step guide for knowledge workers and consultants who want to turn their saved web