Keith Erik Wilson
When PMs ask me what an AI PM day actually looks like, generic descriptions (“AI PMs work with engineers and customers”) never satisfy them. What I’ve found helps is a real hour-by-hour schedule. So I’ve put together exactly that: a representative Tuesday in the life of an AI PM at a Series B SaaS company, with the meetings, the model work, the rituals, and the trade-offs that fill her day.
A Day in the Life of an AI Product Manager (Real Schedule)
After the day, I cover how the rhythm changes by company stage, by seniority, and by team structure, so you can compare your own day to the patterns I see most often and spot where you’re under- or over-investing.
The Setup: Meet Sara
Sara is an AI PM at a 200-person SaaS company in their Series B stage. She owns a customer-facing AI assistant feature shipped 6 months ago, currently used by ~12,000 active customers weekly. Her team is 1 ML engineer (full-time), 2 software engineers (full-time), 1 designer (50%), and a part-time data analyst.
She has 3 years of total PM experience, 18 months of which has been on AI products. She works hybrid - 3 days in the office in San Francisco, 2 days remote. She reports to the Head of Product who reports to the CEO.
She’s not exceptional - she’s representative. Many AI PMs at Series B companies have similar shapes.
7:30 - 9:00: Inbox, Async, and Daily Data
- Quick scan of email and Slack (15 minutes).
- AI-generated daily metrics summary (5 minutes). Her team built a small internal tool that summarises overnight metrics movement, model usage, and any flagged outputs.
- Read the AI cluster of last 24 hours of customer feedback (10 minutes). Themes: confusion about how to phrase queries, occasional concerns about accuracy on edge cases.
- Spot-check one sample of the assistant’s outputs from last night (10 minutes). She picks 5 random conversations and reads them end-to-end.
- Write the morning Slack update for the team (10 minutes). Three lines: yesterday’s headline, today’s focus, anything blocked.
The morning rhythm catches issues early. Twice in the past quarter, this routine surfaced quality regressions hours before customer support reported them.
9:00 - 10:30: Discovery and Research
Today’s slot: 2 customer interviews, 30 minutes each. Otter is recording. Tomorrow’s discovery synthesis will use these.
Sara aims for 4-6 customer interviews per week. Some weeks she does fewer when launches dominate; some weeks she does more during discovery cycles.
Between the calls, 15 minutes to review yesterday’s interview transcripts and tag key quotes. She uses a simple Notion template: pain, current workaround, what they wish existed, willingness to pay signal.
She tagged “complex multi-turn queries” as a recurring pain that’s missing from current product. Will surface in tomorrow’s synthesis.
10:30 - 12:00: Cross-Functional Meetings
- 30 minutes with the ML engineer reviewing eval results from the latest prompt iteration. Today’s eval shows 91% accuracy on the regression suite, up from 87% last week, but a regression on one specific category (multi-step reasoning). They discuss whether to ship or iterate.
- 30 minutes with engineering on a feature spec. They identify a latency problem in the proposed design - server-side calls would add 2 seconds. They explore client-side caching as alternative.
- 30 minutes with the designer reviewing the trust UX for a new AI behaviour. The new behaviour is generating SQL queries on customer data. Designer pushes back on the confidence-display approach. They sketch alternatives.
Sara’s calendar limits cross-functional meetings to mornings, with rare exceptions. The afternoon is protected for deep work.
12:00 - 13:00: Lunch and Decompression
Walk + protein meal. No screens. Mental reset. Sara found that lunchtime screens led to afternoon energy crashes; the discipline of stepping away made afternoons more productive.
13:00 - 15:00: Deep Work
Today’s deep work: drafting the PRD for next quarter’s expansion of the AI assistant. AI generates a structured first draft from her one-page brief. She edits, adds judgement, and removes filler.
Her PRD process: - Write a one-page brief by hand (problem, who, why now, success criteria). - Use Claude to expand into structured PRD format. - Edit heavily, removing AI filler and adding specific judgements. - Add an explicit “what we’re not doing” section. - Add eval criteria and trust mitigations.
Output: a 1,500-word PRD ready for review. Total time: 90 minutes (vs 4-5 hours pre-AI).
15:00 - 16:30: Eval and Quality Reviews
- Run the latest eval set against the new prompt version (15 minutes setup, the eval itself runs unattended).
- Review failure cases (30 minutes). 11 failures across 200 cases. She categorises: 5 are real regressions, 4 are eval-set issues, 2 are ambiguous.
- Prioritise the next prompt iteration with the ML engineer (15 minute Slack thread). They agree to fix the 5 real regressions before merge.
- Review one customer escalation flagged by support (15 minutes). The customer hit a known edge case. Sara writes a follow-up that explains the limitation and the timeline for fix.
Quality work happens daily. It is the difference between an AI feature that gets retired and one that stays in production.
16:30 - 18:00: Stakeholder Updates and Strategic Work
- AI generates first draft of weekly stakeholder update.
- Sara edits for tone and accuracy. She adds two specific judgements about prioritisation that AI didn’t have context for.
- Sends update at 17:00.
- 30 minutes of strategic reading or industry research. Today: a competitor’s earnings call transcript and a recent academic paper on agent reliability.
- Plans tomorrow’s priorities (15 minutes). Three primary items, two secondary.
End of day at 18:00. Slack is on do-not-disturb until next morning.
After 18:00: The Optional Hours
Sara doesn’t typically work after 18:00 on Tuesdays. Mondays and Thursdays she occasionally adds 60-90 minutes of evening work for cross-time-zone discovery interviews (with European customers) or strategic memo drafting.
She protects evenings strictly. Burned-out PMs ship worse work; the AI work in particular requires careful judgement that fatigue degrades.
Weekly Rhythm Beyond Tuesday
- Monday: weekly planning, executive product sync, customer success sync.
- Wednesday: discovery synthesis (2 hours), prompt iteration cycles, design crit.
- Thursday: more discovery interviews, recruiting calls (1-2 candidates), strategy time.
- Friday: retrospective, weekly metrics review, stakeholder updates, no-meeting block.
Discovery is weekly, not crammed. AI tools save 2-3 hours per day across the workflow.
Monthly Rhythm: What Doesn’t Happen Daily
- Quarterly OKR planning (2 days every quarter).
- Pricing and packaging review (monthly).
- Trust and safety audit (monthly with security team).
- AI ethics review (quarterly with legal).
- Cross-product coordination (every 2 weeks).
- All-hands prep (monthly).
These activities are critical but compressed. Sara batches them rather than spreading them through the week.
The Patterns That Hold
- Mornings: data, async, decisions.
- Midday: meetings.
- Afternoons: deep work and quality.
- Late afternoon: stakeholder communication.
- Discovery is weekly, not crammed.
- AI tools save 2-3 hours per day across the workflow.
The pattern is intentional. Cross-functional meetings in the morning maximizes engineering’s afternoon focus too. Deep work in afternoons leverages Sara’s natural energy curve.
How the Day Differs by Company Stage
Pre-seed/seed AI startups: more chaos, more wearing of multiple hats. Sara’s day at a 5-person seed company would include sales calls, hiring, customer onboarding, plus AI PM work.
Series A: similar to Series B but with less established processes. Discovery often less consistent.
Series B-C (Sara’s stage): rhythm matures. Specialization emerges. Discovery becomes weekly habit.
Late stage / Pre-IPO: more meetings. More cross-product coordination. Less hands-on prompt work.
Big Tech (FAANG): heavily process-driven. Many more meetings. Eval and quality often handled by specialized teams.
AI-first companies (OpenAI, Anthropic): technical depth higher. More time in technical reviews. Eval is universally rigorous.
How the Day Differs by Seniority
Associate AI PM: more execution, less strategy. More of the day is implementing decisions made by senior PM.
AI PM (Sara’s level): roughly the day described above.
Senior AI PM: less daily quality work, more cross-team coordination. More writing of strategy memos.
Group AI PM: 50%+ in 1:1s with PMs. Much more meetings. Less hands-on AI work.
Director / VP: meetings, hiring, strategy. Hands-on AI work mostly via close lieutenants.
The Tools Sara Uses
- Linear: tickets and roadmap.
- Notion: PRDs, discovery notes, knowledge base.
- Slack: async communication.
- Otter.ai: interview recording and transcription.
- Claude: drafting, editing, synthesis.
- ChatGPT: occasional brainstorming, image generation.
- Cursor: light code review (read-mostly).
- Looker / Mixpanel: metrics dashboards.
- Braintrust: eval framework.
- Figma: design reviews.
Stack varies by company. Sara’s stack is representative for a Series B SaaS in 2026.
What She Tries Not to Do
- Reactive Slack response. She batches Slack to twice an hour.
- Optional meetings. She declines or sends a representative.
- Vanity metrics review. She tracks 4-5 metrics seriously.
- Multitasking during interviews. She’s fully present.
- Skipping discovery. Even busy weeks include 2 interviews minimum.
- Working past 18:00 routinely. Burnout costs more than it saves.
With 25+ years of experience in Agile transformation, enterprise delivery, and coaching, Keith brings extensive real-world expertise to Agile leadership. Holding 16+ global certifications, including PMP, CSM, and SAFe, he is an Advanced SAFe Practice Consultant specializing in AI-enabled Agile practices, portfolio management, and Scrum Master development. Known for his high-energy, practical approach, Keith brings years of transformation experience across leading organizations
Questions people ask
Published