Turn every founder call and user interview into clustered pain themes, updated ICP docs, and roadmap signals — in one session

ZeroTwo reads your call transcripts, interview notes, and support conversations, clusters repeated pains and desired outcomes by persona, and produces an updated ICP document, JTBD summary, and messaging hypothesis — saved in a Project so every team member inherits the same customer understanding, not their own interpretation of scattered notes.

Start your discovery workspace

Discovery Session — B2B SaaS (Series A)

Customer Discovery Analysis

Transcripts analyzed14 calls — founders, sales, support

Pain themes extracted7 clusters — ranked by frequency

Top pain: manual reportingMentioned in 11 of 14 calls

ICP updated3 personas — signals added from calls

Roadmap signal flagged'Export to PDF' mentioned 9x — not on roadmap

ZeroTwo

The strongest signal across all 14 calls: customers don't hate the product — they hate the manual step between your output and their stakeholder report. 'I have to copy this into a slide deck every Monday' came up 9 times across different accounts and personas. This is not a feature request — it's a workflow gap that's creating weekly frustration for your power users. It should be on the roadmap before the next QBR feature.

Pain Clusters — 14 Calls

Manual reporting workflow11/14 calls — highest frequency

Onboarding time investment7/14 calls — especially enterprise

Missing integrations (Salesforce)6/14 calls — mid-market segment

Export quality complaints5/14 calls — power users only

Pricing confusion (usage vs. seats)4/14 calls — early deal blockers

ICP Update — 3 Personas

Persona 1: RevOps ManagerPain: manual reporting — budget owner

Persona 2: Startup FounderPain: time to insight — moves fast

Persona 3: Enterprise AnalystPain: integration gaps — longer sales cycle

New signal: reporting workflowAdded to all 3 personas

New objection added'Does it connect to Salesforce?' — added to sales playbook

Jobs-to-Be-Done Summary

Core job: see pipeline health without manual workPrimary functional job

Social job: look like they have the data at exec meetingsPresentation-readiness

Emotional job: stop dreading Monday morning reportingAnxiety reduction

Switching trigger: current tool requires too many stepsFrom support conversations

Gain creator: automated stakeholder-ready exportHighest-value outcome named

Roadmap Signals from Calls

'PDF export' mentioned9/14 calls — not on current roadmap

'Salesforce sync' requested6/14 calls — on backlog only

'Slack digest' mentioned4/14 calls — new signal

'Team sharing' asked about3/14 calls — current workaround: CSV

Priority recommendationPDF export before next enterprise push

Customer discovery tools built for SaaS startups

Every call compounds — pain themes get clearer with every session

ZeroTwo saves each discovery session in a Project so the 14th call adds to the pattern from the 1st — instead of starting fresh each time. Themes sharpen, personas update, and the roadmap signal gets stronger with every conversation.

From transcript to ICP doc in one session

ZeroTwo reads call transcripts, clusters repeated pains and desired outcomes by persona, and produces an updated ICP document, JTBD summary, and messaging hypothesis — turning a pile of notes into a structured customer knowledge base.

Roadmap signals that surface before the sprint meeting

ZeroTwo flags the things customers mention repeatedly that aren't on the roadmap — so the team knows about the 'copy to slide deck every Monday' friction before it becomes a churn reason, not after.

How to run customer discovery with ZeroTwo

Step 1

Upload transcripts and notes

Share call transcripts, interview notes, support ticket summaries, and any written customer feedback. ZeroTwo reads all formats — raw notes, structured docs, PDFs, or pasted text — and starts identifying patterns across sources.

Step 2

Cluster pain themes and desired outcomes

ZeroTwo groups repeated pains, desired outcomes, objections, and customer language into named clusters — ranked by frequency across the call set. Each cluster includes representative quotes, the personas where it appears, and the implied job-to-be-done.

Step 3

Update ICP, personas, and messaging

ZeroTwo produces the updated ICP document with new signals added by persona, a JTBD summary for each persona's core and secondary jobs, and updated messaging hypotheses that use the customer's own language — not internal product language.

Step 4

Surface roadmap signals for the product team

ZeroTwo identifies the gaps between what customers repeatedly ask for and what's on the current roadmap — and flags the ones with the highest frequency and strongest sentiment signal for product discussion.

Step 1

Upload transcripts and notes

More ways to use ZeroTwo for ICP refinement and user research

Cluster pain themes from call transcripts

Read these call transcripts and cluster the repeated pain themes by frequency — name each cluster, rank by how many calls it appeared in, and include a representative quote for each.

Update ICP document from discovery calls

Update the ICP document based on these discovery call insights — add new pain signals by persona, new objections to the sales playbook, new desired outcomes, and any shifts in who the buyer actually is.

Write JTBD summary from interviews

Write a Jobs-to-Be-Done summary from these user interviews — functional job, social job, emotional job, switching trigger, and gain creators — for each primary persona identified.

Flag roadmap signals from customer calls

Identify the product features, workflows, or integrations mentioned repeatedly in these calls that are not on the current roadmap — rank by frequency and sentiment strength, and flag the top 3 for product discussion.

Extract customer language for messaging

Extract the exact words and phrases customers use to describe their pain, their desired outcome, and their current workaround — formatted as a messaging swipe file for homepage copy, sales emails, and onboarding.

Write user interview question guide

Write a user interview question guide for a SaaS startup — 8 questions that uncover functional jobs, emotional context, switching triggers, and the decision process — without leading the customer toward a specific answer.

Summarize discovery call themes by persona

From these 14 call notes, separate the themes by persona — what pains appear for RevOps managers vs. startup founders vs. enterprise analysts — and identify which pains are shared vs. unique to each segment.

Write discovery call summary memo

Write a discovery call summary memo for the product and marketing team — top pain clusters with frequency, ICP updates, JTBD observations, messaging implications, and top 3 roadmap signals.

Extract objections for sales playbook

Extract all objections mentioned across these sales and discovery calls — categorize by persona and stage, and write a response framework for each objection for the sales playbook.

Build customer feedback loop SOP

Write a customer feedback loop SOP for a small SaaS startup — how often to run discovery calls, how to tag and store insights, how to update ICP, and how to share signals with product and marketing.