How SaaS Technology Analysts Can Use Claude to Fix the Multi-Source Synthesis Problem That Produces Research Reports Nobody Trusts

You are a senior technology research strategist with 11 years of experience synthesizing market intelligence, product analysis, and competitive data from multiple conflicting sources into coherent research reports for SaaS companies where the quality of the synthesis directly determines whether findings influence product roadmap decisions or get filed and forgotten. Help me write a research report structure so I can improve insight quality and produce reports that clearly show where multiple sources agree, where they conflict, and what the disagreement means for the decision at hand. My situation: - Research topic and business decision it supports: [e.g., "analyzing the competitive landscape for AI-powered customer support tools — output will inform a build vs buy vs partner decision for our support infrastructure in Q3"] - Number and type of sources being synthesized: [e.g., "14 sources — 4 analyst reports, 3 competitor product teardowns, 2 customer interview transcripts, 3 G2 review exports, and 2 internal usage data summaries"] - Primary conflict between sources: [e.g., "analyst reports say AI deflection rates are 65% to 80%, customer interviews suggest 30% to 40% — the gap is unexplained and makes the ROI case impossible to present confidently"] - Audience for the report: [e.g., "VP of Product and CTO — they have 20 minutes to review, want a clear recommendation, and will ask where the numbers came from"] - Current synthesis failure: [e.g., "current report draft presents each source separately with a summary at the end — readers cannot see the pattern across sources or understand why contradictions exist"] - Time constraint: [e.g., "report due in 5 business days — 3 sources still being reviewed, 2 with conflicting data points already identified"] - Previous research this builds on: [e.g., "a market sizing analysis completed last quarter that estimated the addressable opportunity at $2.4B — this report needs to connect to that framing"] Deliver: 1. A research report structure with seven sections — executive summary with the three synthesis findings in order of decision relevance, source map showing how each of the 14 sources contributes to each finding, conflicting data reconciliation section that explains the deflection rate gap with a specific hypothesis, methodology note that establishes why the synthesis is trustworthy despite the source conflicts, main findings with evidence weight ratings, recommendation with confidence level stated explicitly, and appendix structure for source details 2. A source conflict resolution framework — a four-step process for each identified data conflict that classifies the conflict type (methodology difference, sample difference, time period difference, or definition difference), produces a most likely reconciliation hypothesis, and generates the caveat language to use in the report body 3. A synthesis pattern identification method — a structured process for reading across all 14 sources to find the three statements that every source type agrees on, the two statements where analyst reports and customer data diverge, and the one finding that exists only in the primary research and not in secondary sources 4. An evidence weight rating system — a five-tier classification for each data point used in the report, from tier one (multiple independent sources agree) to tier five (single source, unverified), with the disclosure language for each tier embedded in the report body rather than relegated to a footnote 5. An executive summary formula for a conflicted data environment — a three-paragraph structure covering what we know with high confidence and why, what we know with moderate confidence and what would increase it, and the recommendation given the current evidence quality with the decision risk stated explicitly 6. A source map table structure — a format the analyst completes before writing the report that assigns each of the 14 sources to the finding it primarily supports, identifies which findings have only one supporting source, and flags the three most important gaps in the current source set 7. A VP and CTO pre-read brief — a half-page document sent 24 hours before the report review that describes the three findings, the primary data conflict and how it was handled, and the one question the leadership team needs to answer before the recommendation can be finalized 8. A 5-day synthesis production schedule — assigns specific synthesis tasks to each of the five days, with the source conflict resolution framework applied to the deflection rate gap on day two so the finding is resolved before the report structure is written on day three **Write every structural component assuming the analyst is working with genuinely conflicting data and must present that conflict honestly rather than smoothing it over — every framework must help the analyst produce a report that increases decision confidence even when the data is imperfect, because that is the actual research situation.**