AI meeting summary templates, built in

Overview
The team reviewed Q2 roadmap priorities and aligned on the order of the next three launches.

Discussion
• Onboarding revamp is in QA; ship date holding for the 14th.
• Pricing experiment results came in mixed — the new mid-tier moved trial→paid but hurt ARPU.
• Mobile push notification permissions are the biggest activation drag right now.

Decisions
• Ship onboarding revamp on the 14th as planned.
• Pause the pricing experiment and revert to control.
• Prioritize push permission UX as the next mobile work.

Open questions
• Should we revisit pricing again after the onboarding launch settles?

Action items
• Maya — finalize Q2 OKRs draft and share by Friday.
• Ben — schedule a follow-up with the security review team next week.
• Priya — pull pricing-experiment numbers segmented by signup source.
• Whole team — review the onboarding revamp PR before Tuesday.

Decisions
• Holding the launch on the 14th.
• Reverting the pricing experiment.

Discussion notes
• Push notification permission grant rate is currently ~30% — discussed copy and timing.

Summary
Q2 launch sequencing is locked. Onboarding ships first, pricing experiment is reverting after a mixed result, and mobile activation is the next focus.

What changed
• Pricing test paused — moved trial→paid but reduced ARPU.
• Onboarding revamp on track for the 14th.

What's next
• Push notification permission UX as the next mobile workstream.
• Re-evaluate pricing after the onboarding launch settles.

Risks
• Push permission grant rate is the largest single drag on activation today.

Buyer context
Acme Co., ~180 employees, distributed across 3 time zones. Currently using a mix of Otter and manual notes.

Pain points raised
• Reps forget to start recording on customer calls.
• Notes don't get into Salesforce reliably.
• Sales managers can't sample-listen across the team.

Objections
• Security review process takes 4–6 weeks; needs SOC 2 documentation up front.
• Concerned about EU data residency for European reps.

Champion / decision process
Champion: VP Sales (Jamie). Decision committee includes Head of Security and CFO. Budget approval is quarterly.

Next steps
• Send SOC 2 report under NDA.
• Schedule security review call for next week.
• Trial 5 reps for 30 days.

Topic
Introduction to monetary policy transmission.

Key concepts
• Policy rate vs market rate.
• Channels of transmission: interest rate, exchange rate, asset prices, expectations.
• Lags in transmission and why they matter for forecasting.

Definitions
• Policy rate: the central bank's target overnight rate.
• Transmission lag: the time between a policy change and its full effect in the economy.

Examples
• 2008 — coordinated rate cuts across central banks.
• 2022 — rapid rate-rising cycle and uneven sector response.

Questions to revisit
• How do central banks signal forward guidance without committing?
• Why is the housing channel the most rate-sensitive?

Background
Subject is a senior PM at a Series B SaaS, ~6 years experience. Interview focused on how they evaluate meeting tools for their team.

Key quotes
• "The tool I pick has to work whether I'm in the office or at a coffee shop with a customer."
• "If it can't get into the CRM cleanly, I'm not buying it."
• "I don't care about the bot showing up — I care about who reads the notes after."

Themes
• Mobility matters more than they expected when they started looking.
• CRM integration is the dealbreaker, not the headline feature.
• Downstream distribution of notes is more important than capture quality.

Follow-ups
• How do they define 'cleanly into the CRM'?
• Who actually reads the notes — and how often?

A custom template is just a saved instruction. For example:

"Summarize the call as 1) what they said they want, 2) what they actually need (based on the conversation, not their stated request), 3) the next step I should take, 4) anything that contradicted what they said earlier."

Wave applies that structure to every future recording you tag with this template.