Skip to content
Product · Playbook

Findings tied to your notes, with the sample size said out loud.

A synthesis of interview or survey notes into findings, support counts, and recommended actions, using only what the notes contain.

IncludedNative Claude Skill + plain .md for ChatGPT, Gemini & every LLM
100 Playbooks in the catalogDelivered as Claude Skill + plain .mdReviewed Oct 22, 2026Instruction-only · verifiable

Synthesis drifts into storytelling. A vivid quote becomes a trend, five conversations become 'users want,' and the recommendation was settled before the first interview. The team then acts on a story.

Research Synthesis records the sample first, extracts observations by participant, and groups them into findings with a count such as 5 of 6 and a verbatim quote. Thin findings are labeled as leads, contradictions stay visible, and every recommendation traces back to specific notes.

What you get

What it produces.

  • →A sample statement saying who the research can and cannot speak for
  • →Findings with participant counts, IDs, and a verbatim quote
  • →A list of contradictions and gaps in the notes
  • →Recommended actions sized to how strong each finding is
Who it's for
  • ✦Product managers and designers after a round of interviews
  • ✦Founders with a pile of customer call notes
  • ✦Teams reading open-ended survey responses
What's included
  • →research-synthesis.zip: a native Claude Skill. Upload to Settings → Skills in Claude, or unzip to ~/.claude/skills/
  • →research-synthesis-skill.md: plain markdown. Works in ChatGPT Custom GPTs, Gemini, Claude Projects, agent system prompts, anywhere
  • →A README inside the zip with install steps for Claude, ChatGPT, and Gemini
Delivery
Emailed within 60 seconds of payment
Compatibility
Claude, ChatGPT, Gemini, any LLM
License
One-time purchase, yours to keep
Sample output

What it does with a real question.

The brief

I ran 11 customer interviews between March 4 and March 22 with ops managers at mid-size logistics firms, and my notes are pasted below. The goal was to understand why trial users drop off before connecting their first warehouse system. Please pull out the main findings with supporting quotes and recommend next steps for our product team.

Start with what the notes cannot tell you. Your notes didn't come through in the message, only the description of them, so I can't cite a single quote or participant count without inventing it. That limit matters more than usual here, because it shows the main risk in this kind of work: a tidy story about drop-off that nobody actually said.

What I can say is how I would treat what you have. Eleven interviews with ops managers at mid-size logistics firms is a reasonable base for spotting patterns inside that one group, but it says nothing about smaller firms, other roles, or trial users who never agreed to talk. The people who will sit through an interview about a stalled trial are rarely the ones who vanished fastest, so expect the most disengaged users to be underrepresented.

For each candidate reason for drop-off, such as needing IT approval, missing documentation, or an unsupported warehouse system, I would count how many of the eleven raised it unprompted, attach one verbatim line, and label it widespread, common, or a lead. Anything from two or three people gets a small test, not a roadmap slot. Only something that showed up for most of the eleven earns a real product commitment.

Next move: paste the notes with participant IDs, and I will produce the counted findings, the contradictions, and actions ranked by how well each is supported.

The full Playbook runs the whole procedure and writes the complete deliverable, not this excerpt.

Written by claude-sonnet-5-5 with this Playbook loaded, 2026-10-11. Checked automatically for length and for copied framework text.

One-time purchase
$12.99
Yours to keep
No subscription · free updates within v1.x

Works as a Claude Skill (.zip) and as a plain .md for ChatGPT, Gemini & every LLM
Delivered to your email within 60 seconds · Secured by Stripe
Price includes UK VAT where applicable

Questions

Before you buy.

How is this different from just asking Claude directly?

Asked cold, Claude writes confident themes and can generalize from a few conversations or add a plausible insight the notes never said. This keeps every finding tied to the notes, counts the support, flags small samples, and deletes any statement it cannot trace.

How is this different from a Tool?

Playbooks are systematically produced to a fixed template and priced accordingly ($12.99). Tools are hand-built, one at a time, and go deeper ($39 to $199). A Playbook gives you a reliable method for routine work; a Tool is for when the judgment matters more than the format.

Will this work with ChatGPT, Gemini, and other LLMs?

Yes. You get a native Claude Skill (.zip) that auto-invokes in Claude, plus a plain .md you can paste into a ChatGPT Custom GPT, a Gemini system prompt, or any LLM. The procedure travels with the file.

Can I share this with my team?

It's licensed for your own personal and professional use. The output it produces is yours to circulate. To put the Playbook itself in the hands of a whole team, email hello@authority.md about team licensing.

What if it doesn't work for me?

If the file hasn't been delivered, or arrives defective or empty, we refund in full: see our refund policy.

More Product Playbooks

Other Playbooks.