A PM Team Spent 10 Hours a Week on Meeting Notes. They Cut It to 2.
Company profile: 30-person B2B SaaS startup / enterprise workflow automation / 3 PMs, 15 engineers, 4 designers
- Meeting note time: 10 hours/week to 2 hours/week (80% reduction)
- Missed decisions per month: 8 to 0
- New PM onboarding: 3 days to 1 day (67% faster)
This is a 4-week account of a PM team at a 30-person startup adopting Knoi. It includes the stumbles, not just the wins.
Before: A Typical Day for a PM
The Day Was Meetings and Cleanup on Repeat
Morning starts with Slack notifications. Scan client feedback, prep the agenda, then join the 9 AM daily standup. Fifteen minutes of syncing, followed by 20 minutes manually transferring sprint status into Notion.
During the morning planning meeting, the discussion gets heated — you stop taking notes to participate. Afterward, you spend 40 minutes reconstructing what was said from memory. The afternoon client call? You can't screen-share and take notes at the same time. As soon as it ends, you jot down whatever comes to mind. Another 30 minutes.
By the time the sprint review wraps, the line between "confirmed" and "still under discussion" is blurry. By the fourth set of notes, your focus is gone. Two weeks later, you re-read them and can't figure out what half of it means.
Four to five meetings a day. 2 hours of note cleanup. Five days a week: 10 hours. Product planning and user research — the actual PM job — always got pushed back. The joke "Am I a PM or a stenographer?" made the rounds, but nobody laughed.
Alternatives They Tried
Notion templates with pre-built sections for agenda, decisions, and action items still took 30 minutes to fill out, and got skipped entirely on hectic days. Google Docs with real-time collaboration led to three people writing different versions of the same point — creating more confusion, not less. A Slack thread rule for post-meeting summaries lasted two weeks before everyone stopped posting.
The common thread: every approach depended on human willpower. When people are busy, they skip it. When they're tired, they cut corners. Habit-based systems break down.
The Tipping Point — Nobody Remembered a Decision from Two Weeks Ago
It happened during a Friday sprint review. The team had agreed two weeks prior to simplify the payment flow from 2 steps to 1. But engineering had already built the 2-step version.
The Notion doc for that meeting just said "Payment flow discussed." One sprint — roughly 40 hours of engineering work — wasted. The planned notification feature got bumped to the next sprint.
In the retro, the team focused not on blame but on why this keeps happening structurally.
"Someone said, 'If we'd just written better notes, this wouldn't have happened.' But honestly — with four meetings a day, is perfect note-taking even possible? It's a systems problem, not a people problem." — Dohyun Kim, PM Team Lead
The Decision to Adopt
After the sprint review incident, the PM lead researched AI meeting note tools. Finding one that worked well for Korean-language B2B environments was harder than expected.
Alternatives and Their Limits
Otter.ai handled English fine but struggled with Korean recognition. Conversations mixing Korean and English — like "API endpoint refactoring" in an otherwise Korean sentence — dropped in accuracy. 70% of the team's meetings followed that pattern.
Fireflies.ai produced decent transcripts, but they needed heavy editing. The "cleanup time" problem remained. Overseas server storage also raised security concerns.
Clova Note had solid Korean recognition but couldn't distinguish "decisions" from "action items" automatically. PMs still had to read through the full transcript and sort things manually.
The conclusion was clear: transcription alone isn't enough. You need structured summaries with automatic decision and action item classification to actually save time.
Why Knoi
The standout feature was AI summaries built for Korean meetings. It handled Korean-English mixed conversations well and automatically separated content into decisions, discussion points, and action items. Slack notifications, Notion integration, and calendar sync fit into the existing workflow. And the search — being able to type a keyword and pull up "the payment flow discussion from two weeks ago" — sealed the deal.
Getting the CTO on Board
The CTO's first reaction: "Another new tool?"
The PM lead came with numbers. Three PMs spending 10 hours a week on notes means 120 hours a month — roughly $2,500 in opportunity cost. The previous quarter saw 3 rework incidents from missed decisions, burning an estimated 120 hours of engineering time. "A Knoi subscription costs less than hiring another PM." The CTO approved a pilot with one condition: "Use it for a month and prove it with data."
The 4-Week Journey
Week 1: Pilot — One PM, One Meeting
Start small, expand when it works. PM lead Dohyun connected Knoi to the Friday sprint review.
Five minutes after the meeting ended, a summary arrived: 4 decisions and 6 action items, cleanly organized. The usual 40-minute cleanup? It took 5 minutes to add one missing detail.
On Wednesday, a second test: a one-hour client meeting full of mixed technical and business language. The summary correctly separated 3 client feature requests from 2 timeline agreements.
Week 2: Organic Adoption by the Rest of the Team
When Dohyun shared the sprint review summary in Slack, the other two PMs responded immediately: "Can I use this too?" By Tuesday, all three PMs were on board. No mandate — voluntary adoption.
There was friction. In-room meetings had lower recognition accuracy due to microphone placement — solved with an external mic. Client meeting recordings needed a consent process, so the team standardized an opening script: "We'll record for accurate notes and share the summary with you."
Weeks 3–4: Full Rollout and Cross-Team Spread
By week 3, every recurring meeting used Knoi. Note cleanup dropped to under 3 hours a week. PMs started spending afternoons on user interviews and data analysis instead.
The engineering lead asked first: "Those meeting summaries PM shares — can we use it for our internal meetings too?" By mid-week 3, four engineers were on it. By week 4, the design team joined.
Before Knoi, "What did we say in that meeting?" was a daily question. Now a single link answers it. When someone asks for context in Slack, the response takes 30 seconds.
On the last day of week 4, they reported results to the CTO. The numbers were better than expected. The CTO's response was short: "Roll it out company-wide."
"On Wednesday of week 3, a client asked 'Was our request from last time addressed?' I found the exact meeting note in 10 seconds and confirmed the precise ask. The client was surprised. That's when I knew — this isn't just a convenience tool. It changes how you work." — Seoyeon Park, PM
Results After 4 Weeks
Compared against one week of baseline data collected before adoption:
| Metric | Before | After | Improvement |
|---|---|---|---|
| Weekly note cleanup time | 10 hours | 2 hours | 80% reduction |
| Missed decisions (monthly) | 8 | 0 | 100% resolved |
| New PM onboarding time | 3 days | 1 day | 67% faster |
| Time to share meeting notes | avg. 4 hours | avg. 15 min | 94% faster |
| Sprint rework incidents (monthly) | 2–3 | 0 | 100% resolved |
The 8 hours saved per week didn't just free up time. The PM team reinvested it into user interviews and competitive analysis. The quality of the quarterly product roadmap went up noticeably.
Sprint rework dropping to zero mattered to engineering too. Previously, the team averaged 8 rework incidents per quarter, each consuming at least 20 hours of dev time.
Unexpected Side Effects
Team Culture — "People Got More Honest in Meetings"
With notes captured automatically, psychological safety actually went up. The anxiety of "What if I'm remembering wrong?" disappeared, so people voiced disagreements more freely. One engineer noted: "PMs used to stare at their laptops during meetings. Now they make eye contact."
Faster Onboarding for New PMs
A PM who joined in week 4 read through 15 meeting summaries from the past month, in order. Decisions, context, and action items were all structured — making it easy to absorb project context fast.
On their second day, during a sprint review, they asked: "We decided to go with a 1-step payment flow last sprint — how are we handling edge cases?" That level of context used to take at least a week to build.
Client Trust
Sending accurate meeting notes within 15 minutes became a competitive advantage. One client said: "Other vendors send notes a week later. You send them before the meeting is even really over."
Follow-up gaps vanished. Client requests started making it into the next sprint without fail. Monthly client reminders dropped from 5 to zero, and renewal rates improved.
Advice for Other PM Teams
Don't roll it out everywhere at once. Start with the one meeting where missed notes cause the most damage. For us, that was the sprint review. Once the value is clear there, everything else follows.
In the first few days, don't trust the AI summary blindly. Compare it against your own memory for 3–4 meetings. That's enough to build confidence in its accuracy.
To get org-wide buy-in, "it feels easier" won't cut it. Measure your note-writing time for one week before adoption. For us, that single number was the entire CTO pitch. And expect some pushback — "recording feels uncomfortable" or "I prefer the old way." Keep it optional for the first two weeks. Good tools sell themselves through output quality.