Industry Playbooks
Research workflows for consultants are the structured processes for conducting primary and secondary research efficiently — from rapid industry orientation to deep client-specific analysis — while managing tight project timelines and multiple parallel workstreams.
A strategy consultant is staffed on a new project Monday. Client kickoff is Thursday. She needs to understand a market she's never worked in — competitive dynamics, key players, regulatory environment, growth drivers — in three days.
This is the standard consulting research challenge: tight timelines, unfamiliar territory, enormous information volume, and a need for findings that are both accurate and defensible. The consultant who approaches this with a research workflow for consultants — a structured process for orientation, deep dive, synthesis, and organization — will produce better work faster than one who searches randomly.
Speed: Consulting timelines don't accommodate weeks-long literature reviews. Research must produce usable findings in days, not weeks.
Defensibility: Findings that go into client decks and recommendations need traceable sourcing — "our analysis shows" must be grounded in citable data. A statistic without a source is unusable in professional consulting work.
Structured synthesis: Finding information is only half the job. Converting information into structured insight — "the market has three distinct segments with materially different economics" — is the intellectual value-add.
Portfolio management: Consultants typically work on multiple workstreams simultaneously. A research workflow must handle parallel research tracks without confusion.
Before searching, write the specific question you need to answer. Not "understand the healthcare payments market" — but "identify the 5-7 largest payers in the commercial insurance market and their approximate market share."
Specific questions:
For each project, create a research question log before starting. Major question → sub-questions → specific data points needed.
The first 30-60 minutes on any new topic should produce a working mental model, not a definitive analysis. Use synthesis sources:
Analyst reports and market research:
Trade press:
Company IR materials:
Wikipedia as starting point (not source): Wikipedia industry articles often contain useful structural information and links to primary sources. Use for orientation; don't cite.
Goal: After rapid orientation, you should be able to sketch the market structure, name the major players, and identify the key dynamics. You don't have all the data yet; you have the framework.
With the market structure in mind, prioritize which specific questions need deep research:
For competitive analysis: Primary sources — each competitor's website, IR materials, press releases, job postings (which reveal strategic priorities), LinkedIn (team composition, growth areas).
For market sizing: Published reports with methodologies you can evaluate, government statistics (US Census, BLS, industry regulatory filings), trade association data.
For customer insight: Qualitative primary research (client interviews, expert calls) and published VOC research, survey data, or product review sites.
For regulatory context: Government agency websites (FDA, FTC, SEC, relevant state agencies), Federal Register for recent rulemaking, law firm client alerts on regulatory developments.
Assign each deep-dive question a researcher (on a team) or a time block (solo). Cap each at a defined time before moving to synthesis.
Secondary research tells you what is publicly known. Primary research tells you what isn't:
Expert network calls (GLG, Guidepoint, AlphaSights): 30-60 minute calls with former executives or practitioners in the relevant space. For each call:
Client stakeholder interviews: For client-facing projects, structured internal interviews to understand current state, pain points, and organizational context.
Synthesis call debriefs: After each expert call, write a 3-5 bullet synthesis: what you learned that wasn't in secondary research, what you believe vs. what remains uncertain.
The difference between a research summary (what you found) and a consulting deliverable (what it means) is synthesis.
After completing research, the synthesis question is: "Given everything I've learned, what is the single most important thing to understand about this question?"
A synthesis approach:
Synthesis should produce a 3-5 bullet "so what" that can be read in 60 seconds and drives action or decision.
After project close (or at project milestones), organize research for future use:
The research that will inform your next project is often the research from this one. Organized for retrieval, it compounds; filed by client name, it disappears.
A consultant, Marcus, is staffed on a market entry project for a B2B software company entering the logistics sector.
Day 1 — Orientation: Marcus spends 3 hours on rapid orientation:
After 3 hours, Marcus can sketch the market structure: 5 major incumbents, 12 notable challengers, enterprise vs. mid-market segments with different buying dynamics, an emerging AI-native subsegment.
Day 2 — Deep dive: Marcus assigns three specific research questions to the morning:
Each question gets a 90-minute block. He uses IDC market share data for (1), web clips of competitor customer case studies and G2 reviews for (2), and FTC/state AG enforcement actions + law firm client alerts clipped via WebSnips for (3).
Day 3 — Expert calls + synthesis: Two 45-minute expert network calls with former logistics technology executives. Marcus takes structured notes. After each call, he writes a 5-bullet synthesis.
Synthesis brief (end of Day 3): "The logistics software market has consolidating dynamics at the top with 3 players controlling ~60% share. Mid-market is fragmented and price-sensitive. The emerging AI-native players are winning new logos but struggling with enterprise compliance requirements. The client's best entry point is mid-market customers with multi-carrier complexity problems — where incumbents are weakest and the AI-native players haven't focused."
This is the synthesis that goes into the deck.
| Tool | Use | Notes |
|---|---|---|
| Google (Advanced Search) | Starting point for any topic | Use site:, date filters, filetype:pdf for targeted results |
| IBISWorld / Statista | Market sizing and overview | Subscription required; worth it for frequent industry work |
| Seeking Alpha / Koyfin | Company and competitive research | Free and paid tiers; strong on public company data |
| PitchBook / Crunchbase | Private company and VC research | Deal data, funding rounds, investor intelligence |
| AlphaSights / GLG / Guidepoint | Expert network calls | Project-based billing; essential for primary research |
| Notion / Obsidian | Research organization | Build the long-term knowledge base |
| WebSnips | Web-published research capture | Clip regulatory updates, trade press, company announcements |
| Zotero | Citation management | Keep sourcing organized for defensible deliverables |
WebSnips for consulting research: Regulatory agency websites, government databases, company newsrooms, and trade press are major consulting research sources — but they're web-published, not database-indexed. WebSnips clips specific sections (a specific regulatory announcement, a competitor press release, an industry association statistic) with source URL and date. For a project where you're clipping 20-30 web sources, having them organized in a project collection — searchable and citable — is materially more useful than a folder of browser bookmarks.
Mistake 1: Searching without a question. "Research the healthcare payments market" produces an infinite information set with no clear stopping point. "Identify the three largest commercial payers and their approximate commercial market share" is a question you can answer. Write the question before searching.
Mistake 2: Compiling without synthesizing. A 40-slide deck of research findings is not analysis. Clients pay for "what this means for us," not "here's what we found." Every research block must end with a synthesis brief: the 3-5 bullets that answer "so what?"
Mistake 3: Not capturing sources at point of research. Finding a great IBISWorld statistic and not noting the source, page number, and date means spending 20 minutes re-finding it when you need to cite it in the deck. Capture citation at the same moment you capture the content.
Mistake 4: Separating research from synthesis. Synthesis isn't a step you do at the end — it's a running hypothesis you test against research findings. Maintain a "current hypothesis" document that you update as each piece of research comes in.
A research workflow for consultants converts unfamiliar territory into structured, defensible insight in compressed timelines. The difference between a consultant who produces excellent research and one who produces good data is largely the presence of a workflow: question-first orientation, structured deep dive, systematic primary research, and synthesis discipline. That workflow, consistently applied, produces deliverables that are faster to build, better sourced, and more persuasive — and research that, organized by topic rather than by client, becomes the expertise that differentiates a consultant over a career.
More WebSnips articles that pair well with this topic.
AI knowledge work for consultants is transforming research, analysis, document synthesis, and proposal creation — with tools that compress timelines from days to hours while introducing new verification and confidentiality obligations.
Knowledge management for consultants is the practice of capturing client intelligence, research findings, and project learnings in organized, searchable systems — turning each engagement into a compounding asset rather than a closed folder.
A note-taking system for consultants must handle four distinct contexts — client meetings, research synthesis, project management, and cross-engagement knowledge building — with fast capture, confidential separation, and topic-organized retrieval.