How to synthesize customer research interviews as Professional Services Founders
After six client discovery calls in a week, you have six Otter.ai transcripts, three sets of handwritten notes, and a Notion doc someone half-filled in. Synthesizing that into themes — what clients actually want, what objections keep surfacing, what language they use to describe their own problems — takes a senior consultant two to three hours. That person is also on three active engagements. So the synthesis either happens late, happens shallow, or happens in your head on a Friday afternoon before the proposal is due Monday. You miss the pattern that would have sharpened the pitch, and the proposal reads like every other proposal you've sent.
What you'll set up
Apps, data, and prompts
The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.
Meeting Notes transcribes calls live; Starch connects directly to Notion (scheduled-sync provider) to store and retrieve past research; Starch connects directly to Gmail (scheduled-sync provider) so follow-up briefs can be emailed to clients; any recordings stored in Google Drive are reachable through Starch's integration catalog queried live when the synthesis app runs. Presentation Agent (currently in beta — request access to be notified at launch) builds the client-facing deck from the synthesis output.
Step-by-step
See this running on Starch
Connect your tools, describe what you want, and the agent builds it. Closed beta is free.
Meridian Group Proposal — March 2026
| Discovery calls conducted | 6 |
| Hours of transcript (raw) | 9 |
| Themes extracted by Starch | 7 |
| Verbatim quotes surfaced | 22 |
| Synthesis time (actual) | 0.33 |
| Senior consultant hours saved | 2.5 |
You run six stakeholder interviews across Meridian Group's ops and finance teams in the first two weeks of March — 9 hours of recorded conversation. Normally your senior consultant would spend half a day reading transcripts and building a themes doc before you could write the proposal. Instead, you paste all six Otter.ai exports into Starch and type: 'Synthesize these transcripts. Top themes, verbatim quotes per theme, objections that came up more than once, and flag any tension between what ops and finance said about the same topic.' Twenty minutes later you have a structured brief: 7 themes, 22 quotes sorted by theme, and a callout that ops leadership said 'we don't have visibility' in four separate calls while finance said 'the data exists, nobody looks at it.' That tension becomes the opening slide of the proposal. You tell Starch: 'Build a 10-slide findings brief for this engagement. Theme one is the visibility gap — lead with the ops vs. finance contrast and use these two quotes.' The deck is ready to review in under 15 minutes. The proposal goes out Sunday night instead of Monday afternoon. You win the engagement. The findings are already in Notion for the next time a prospect mentions operational visibility.
How you'll know it's working
What this replaces
The other ways teams handle this today, and how the Starch version compares.
One platform — knowledge management, meeting notes, presentation agent all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.
Try it on Starch →Frequently asked questions
My transcripts are in Otter.ai, some are in Zoom, and a few are Word docs from an old-school client who records on a phone. Can Starch handle all of those?
Will the findings actually go into my Notion, or is this just a Starch-internal thing?
Presentation Agent says 'currently in development / request beta access.' When is it actually available?
Is this only useful for the proposal phase, or does it help with ongoing client work?
What if I have confidentiality concerns about storing client interview content?
My team uses HubSpot to track which proposals we sent. Can the synthesis link back to the deal?
Related guides for Professional Services Founders
AP invoice approval is the process of reviewing incoming vendor bills, confirming they match purchase orders or contracts, getting the right sign-off, and releasing payment.
Read guide →A 13-week cash flow forecast is a rolling, week-by-week view of what hits your account and what leaves it — covering roughly one quarter ahead.
Read guide →A strategic account plan is a documented, living view of a specific customer or prospect — their business goals, the stakeholders who matter, the gaps your product fills, the risks to the relationship, and the actions your team is taking.
Read guide →An annual operating budget is a forward-looking plan that maps expected revenue against planned spending for the next 12 months, broken into categories you'll actually track — payroll, software, marketing, COGS, facilities.
Read guide →Synthesize Customer Research Interviews for other operators
The AI stack built for the founder's office.
Read guide →The AI stack built for small marketing teams.
Read guide →The AI stack built for small customer success teams.
Read guide →The AI stack built for small RevOps teams.
Read guide →Ready to run synthesize customer research interviews on Starch?
Request closed-beta access. Everything is free during beta.