🎯
Meeting Performance Playbook
Wins, losses, patterns, and optimization for BSP Monday standups
Built from Apr 6 + Apr 13 standup analysis | Updated after every meeting
📊 Apr 13 Standup Scorecard
✅ WINS (What Worked)
GCLID Field Created LIVE
Created the custom field in ST during the meeting while explaining it. Stephanie saw it happen in real time. Show, don't tell.
💡 Takeaway: Do more live demos during standups. Action + explanation simultaneously.
Emergency Campaign Paused
Showed $1,346 wasted with 0 conversions. Stephanie immediately agreed to pause. Data made the decision obvious.
💡 Takeaway: Always lead with the dollar impact. $1,346 wasted is more powerful than 'low performing campaign'.
Weather Engine Proof
$660 extra spend = 43 calls (2x normal) on Friday. Concrete ROI proof. Kalen's fishing analogy landed.
💡 Takeaway: Tie every system to a dollar outcome. Abstract systems become real when you show the call spike.
Pricebook Access Granted
Asked for access, provided exact click-by-click steps. Stephanie found the setting and granted it during the meeting.
💡 Takeaway: Give Stephanie exact steps. She acts immediately when she knows WHERE to click.
Revenue Numbers Trusted
$70,180/wk cross-validated against QB ($79,742 net). Stephanie didn't question the numbers for the first time.
💡 Takeaway: Cross-validation builds trust. 3 sources agreeing = Stephanie stops questioning.
Format Feedback Captured
Stephanie explicitly said: Problem first, then solution, then data. Clear directive.
💡 Takeaway: She told you how she processes information. Follow it EXACTLY.
❌ LOSSES (What Failed)
Daniel AI ROI Claim Unverified
Presented 334x ROI ($25K from $75) but investigation revealed all 21 Daniel jobs are local DB placeholders with $0 revenue and no ST IDs. The claim was a lie. Stephanie could have caught this.
🛑 Fix: NEVER present an ROI number without verifying the source data. Run the verification BEFORE the meeting, not during.
Pricebook Steps Were Wrong
Told Stephanie to go to Integrations > API Application > User 484-493-1615. That's the API user, not Robert's human account. She couldn't find it because it doesn't exist in that path.
🛑 Fix: VERIFY ENDPOINTS BEFORE BUILDING MICROSTEPS. Hit the actual UI or API first. Don't write steps from documentation.
Solution-First Format
Robert presented in Solution > Problem > Data format. Stephanie explicitly corrected: she needs Problem FIRST to understand context before hearing the fix.
🛑 Fix: Stephanie processes: context (problem) then answer (solution) then proof (data). Reverse the order.
Too Much Technical Detail
Spent time explaining scheduledOn vs Appointments API, div nesting, Triad Architecture. Nobody in the room needed to know this.
🛑 Fix: The standup is for BUSINESS decisions. Technical wins are 'I fixed the schedule page' not 'the ST Jobs API lacks a scheduledOn field'.
Prestige Living Not Discussed
Had the assessment ready but meeting ran long. Discussion item prepared but never surfaced.
🛑 Fix: Put time-sensitive discussion items FIRST. Prestige Living was calling -- needed an answer that day.
No Pre-Meeting Verification
Sacred v2 had stale RAG count (15,356 vs actual 4,425), wrong experiment counts, March 2026 hardcoded period. Found during meeting prep, not before.
🛑 Fix: Run Final Pass (Perplexity) or the output verifier on Sacred v2 the NIGHT BEFORE the standup. Not morning-of.
🧠 Stephanie Communication Patterns
How Stephanie Processes Information
❌ DON'T
Start with the solution (she has no context)
Use technical jargon (scheduledOn, UPSERT, API endpoints)
Present unverified numbers (334x ROI without proof)
Give her homework without exact steps
Talk for more than 90 seconds on any topic
Show her the process (she wants the outcome)
✅ DO
Start with the PROBLEM (she needs context first)
Then the SOLUTION (what you did about it)
Then the DATA (proof it worked)
Give click-by-click microsteps when you need her action
Lead with dollar amounts (not percentages or technical metrics)
Do live demos when possible (she trusts what she sees)
Her exact words (Apr 13): "Give me the problem first, then the solution, then the data. I need context to process complex information."
⚡ Meeting Optimization Protocol
Pre-Meeting Checklist (Sunday Night)
☐ Run nexus_output_verifier.py -- fix any FAIL/WARN
☐ Run Final Pass on Sacred v2 -- fix stale numbers
☐ Pull fresh: Google Ads MTD, Daniel AI calls, Ramp spend, QB P&L
☐ Update Sacred v2 with fresh data + purge Cloudflare
☐ Generate talking script with emojis (save to drafts/)
☐ Verify every ROI claim against actual source data
☐ Prepare discussion items ranked by time-sensitivity
☐ List 3 things that need Stephanie action (with microsteps)
During Meeting Rules
🔴 Problem > Solution > Data format (Stephanie's rule)
🔴 90 seconds MAX per topic
🔴 Lead with dollar impact, not technical detail
🔴 Do live demos when asking for access/permission
🔴 Time-sensitive discussion items FIRST
🔴 End every topic with: "Does anyone have questions on this?"
🔴 Capture Start/Stop/Continue feedback at the end
Post-Meeting Protocol (within 1 hour)
☐ Process transcript (Tactiq/Gemini) into numbered action list
☐ Update Sacred v2 with meeting debrief section
☐ Add Next Monday agenda with carryover items
☐ Update wins/losses in this playbook
☐ Log to session logger
☐ Purge Cloudflare on all updated docs
☐ Save meeting memory to NEXUS
📋 Optimal Meeting Structure (60 min)
0-2 min
Revenue Snapshot
3 numbers: weekly rev, net income, annualized pace. No explanation needed.
2-7 min
This Week's Wins
3-4 wins max. Problem > Solution > Impact for each. Live demo if possible.
7-12 min
Blockers + Asks
What Robert needs from Stephanie/Kalen. Exact steps provided. Get answers NOW.
12-20 min
Discussion Items
Time-sensitive first. Prestige Living, budget decisions, vendor evaluations.
20-30 min
Ads + Marketing
Campaign performance. What to kill/keep/start. Budget reallocation.
30-40 min
Operations
Invoice backlog, call volumes, tech performance, Daniel AI.
40-50 min
Data Cleanup
ST fixes, business units, phantom data, attribution.
50-55 min
Start / Stop / Continue
3 questions. 90 sec each. Stephanie + Kalen fill in.
55-60 min
Next Week Preview
Top 3 priorities. Who owns what. Deadlines.
📈 Historical Meeting Patterns
Apr 6 Standup
120 min (too long). 55 action items (too many). Scattered across topics. Landing pages prioritized over survival guide. Figma approved. Audrey assigned 15 pages. No Start/Stop/Continue.
Lesson: Cap at 60 min. Fewer action items with clearer ownership.
Apr 13 Standup
62 min (better). 25 action items (improved). GCLID + Pricebook done live. Emergency paused. First Start/Stop/Continue attempted. Format feedback received. Daniel ROI exposed as unverified.
Progress: Shorter, more focused, live actions taken. Format still needs work.
🔍 Comprehensive Meeting Analysis: Mar 25 - Apr 13, 2026
15 meetings analyzed | 5 unique meeting types | 11 participants tracked | Built from full Gemini transcripts
📅 Full Meeting Timeline
| # |
Date |
Meeting |
Attendees |
Duration |
Type |
Key Decisions |
| 1 |
Mar 25 |
BSP Tech Pricing Strategy (The Price Book) |
Robert, Kalen |
~45 min |
Strategy |
$600/hr labor target per tech. Flat rate price book based on high material + labor. Pull from ST + Anthony field eval. Xactimate structure chosen. |
| 2 |
Mar 27 |
Multimedia Marketing + Digital Performance |
Robert, Stephanie, Audrey |
~85 min |
Ops |
Audrey overwhelmed - too much data dump. IG = brand/professional, TikTok = fun. Audrey needs specs in one place. 3 posts/week goal. Stephanie: "Talk like a normal person without AI." |
| 3 |
Mar 30 |
Ashton Lead Workflow Discussion |
Robert, Ashton |
~35 min |
Build |
Ashton wants live dashboard: Call Now, Book Now, Schedule Fill lists. Real-time tracking > color-coded dispatch. 3 follow-ups then remove from list. ST integration for status updates. |
| 4 |
Mar 30 |
Monday Standup |
Robert, Stephanie, Kalen, Audrey |
~79 min |
Standup |
KSHB media partnership discussed. Logo debate (chimney removed). Daniel AI is part of Zeus. Saturday calls lost. Snack vendor too expensive - Costco mini fridge. QB integration needed. Kassidy ST framework tabled. |
| 5 |
Mar 30 |
Stephanie + Robert Operations Workflow |
Robert, Stephanie |
~111 min |
Ops |
Quad/Claude doing what ChatGPT couldn't for Stephanie. ST non-managed techs not clicking "done" blocks invoicing. IF-THEN rule for notifications proposed. Kassidy ST training needed. LSA budget increase approved cautiously. Zeus payroll vision discussed. |
| 6 |
Mar 30 |
Kalen + Robert Tech Meeting Planning |
Robert, Kalen |
~35 min |
Data |
Kalen found $27K sewer job was actually $22.4K. Nick's $60K included cancellations. Data integrity issues surfaced. Revenue pulled from wrong endpoint. QB tracing now possible. |
| 7 |
Apr 1 |
Nick + BSP Partnership |
Robert, Kalen, Nick |
~50 min |
Strategy |
Nick (Inspector Nick) partnership. His referrals are warm - customers already know what they need. Other inspectors give junk leads. Free camera inspections when problems exist. Want to bring sewer scope in-house. Indeed for hiring (1 in 100 quality). |
| 8 |
Apr 2 |
Robert + Kalen Callback (Big Picture) |
Robert, Kalen |
~60 min |
Build |
Contact form wiped 3 weeks ago during site crash - nobody noticed. Rebuilt GCLID capture form. ST form can't capture ad attribution. Intelligence layer rebuilt. Explained 5-step validation to Kalen. |
| 9 |
Apr 3 |
Robert + Kalen REVIEW Sewer Camera Blog |
Robert, Kalen |
~45 min |
Build |
Kalen reviewed blog edits. $299 camera price to $199. "Make 199 the most obvious thing on the page." Remove competitor quotes. Fix color coding (green/orange/red offputting). Remove "honesty" overuse. Lock down data/code access soon. |
| 10 |
Apr 4 |
Robert + Stephanie Callback (Big Picture) |
Robert, Stephanie |
~30 min |
Ops |
Robert tried to show data validation system. Stephanie out and about, couldn't look at screen. Explained: 5-step verification, $128K phantom caught, anomaly detection hourly, confidence levels. "Sleeping giant" framing. Low call volume = pattern we can predict + prevent. |
| 11 |
Apr 6 |
BSP Weekly Standup |
Robert, Stephanie, Kalen, Audrey |
~140 min |
Standup |
55 action items. Email campaigns, weather playbook (spammy on Slack). KSHB partnership. LSA tiers. Snack room Costco decision. Landing pages > survival guide. Figma approved. Audrey 15 pages. 228 experiments nearly destroyed admission. Stephanie: "I have no idea what that means, but I'm glad you know." |
| 12 |
Apr 6 |
Audrey Service Page Design Session |
Robert, Audrey |
~15 min |
Build |
Detailed sewer camera inspection page walkthrough. Every asset named and in Drive folder. Hero image with wave. Trust row icons. Blue/yellow underlines. Step icons 1-4. Background hex CFE95. FAQ accordion. Google reviews integration. |
| 13 |
Apr 7 |
Kassidy's Zoom - ST Training |
Robert, Ashton, Kassidy |
~55 min |
Ops |
Kassidy trained on ST booking: book assumed LAST day first (dash-1 holds invoice). Completion date must match last visit. Non-managed techs must click done. Put multi-day jobs on hold. Projects = scope, Jobs = visits. |
| 14 |
Apr 10 |
Service Page Design + Website Platform |
Robert, Stephanie, Kalen, Audrey |
~74 min |
Standup |
Oxygen is the ceiling - 4-6 hrs per page. Unbounce/Instapage for immediate landing pages ($99/mo). Bricks full migration 15-30 days. Figma approved. Stephanie: "Problem first, then solution - I have no idea what I'm looking at." Zeus payroll vision. MIT agentic AI course. Audrey can handle Unbounce solo. |
| 15 |
Apr 13 |
BSP Weekly Standup |
Robert, Stephanie, Kalen, Audrey |
~86 min |
Standup |
Fake review detection business idea. $231K operating costs YTD. CPC 3x baseline. 40% booking rate (was phantom 75%). Ramp COGS 1000 uncategorized txns. Canonical metric registry deployed. GCLID field created live. Emergency campaign paused. Stephanie: "Give me problem first, then solution, then data." |
⏱ Meeting Duration Trends
Duration Analysis Across 15 Meetings
140
Longest (Apr 6 Standup)
15
Shortest (Apr 6 Design)
Positive trend: Standups shortened from 140 min (Apr 6) to 86 min (Apr 13) -- 39% improvement.
Still over target: 60-minute standup goal not yet met. Apr 13 was 86 min (43% over).
Pattern: 1:1 calls with Kalen are consistently efficient (35-60 min). Stephanie 1:1 calls run long when she's mobile.
Danger zone: Full team meetings (all 4 people) consistently exceed 75 min. The more people, the longer it runs.
📋 Action Item Completion: Meeting-to-Meeting Tracking
Completed Between Meetings
✅ GCLID capture form rebuilt (Mar 30 decided, Apr 2 done)
✅ Sewer camera blog reviewed with Kalen (Mar 30 planned, Apr 3 done)
✅ Contact form restored after site crash (Apr 2 done same day)
✅ 5-step data validation layer deployed (Apr 2-4)
✅ Price book structure engineered (Mar 25 decided, delivered)
✅ Sewer camera page assets organized in Drive (Apr 6 Audrey done)
✅ Emergency campaign paused (Apr 13 done in meeting)
✅ GCLID custom field created in ST (Apr 13 done live)
✅ Canonical metric registry deployed (Apr 13)
✅ Unbounce/Instapage decision made (Apr 10, Figma approved)
Carryover Items (Still Pending or Recurring)
❌ Ashton live dashboard (Mar 30 requested, still not built)
❌ Daniel AI warm transfer improvements (recurring since Mar 27)
❌ Landing pages for PPC (discussed Mar 27, Apr 6, Apr 10, Apr 13)
❌ Email survival guide campaign (Apr 6 "launch Tuesday" -- delayed)
❌ Offline conversions pipeline (ongoing blocker)
❌ ST job closing workflow automation (Mar 30 Stephanie requested)
❌ Zeus payroll automation for Stephanie (Apr 10 vision, not built)
❌ Ramp COGS categorization in QB (discovered Apr 13)
❌ Sewer scope camera in-house decision (Apr 1 discussed)
❌ Start/Stop/Continue feedback loop (attempted Apr 13 only)
Completion Rate Analysis
Technical/data fixes: ~80% completion rate. Robert executes these fast because he controls them solo.
Cross-team workflows: ~30% completion rate. Anything requiring Stephanie + Kalen + Audrey coordination stalls.
Landing pages: Discussed in 5 of 15 meetings. Still not live. This is the single biggest carryover item.
Pattern: Items Robert can execute solo get done. Items that need multi-person coordination or external vendors (Unbounce, Kassidy, Nick) lag 2-3 weeks.
🔁 Recurring Topics Heat Map
| Topic |
Meetings |
First Raised |
Status |
Risk |
| Landing pages / service pages |
7 of 15 |
Mar 27 |
IN PROGRESS |
Blocking PPC spend. Every week without pages = wasted ad budget. |
| Data integrity / phantom revenue |
6 of 15 |
Mar 30 |
IMPROVING |
5-step validation deployed. Kalen still catching discrepancies but trust growing. |
| ST workflow / tech job closing |
5 of 15 |
Mar 30 |
PARTIAL |
Kassidy trained Apr 7. Techs still not clicking done consistently. |
| Google Ads / CPC / conversions |
5 of 15 |
Mar 27 |
CRITICAL |
CPC 3x baseline. Spending more, getting less. Negative keywords + landing pages needed. |
| Communication style / overwhelm |
4 of 15 |
Mar 27 |
IMPROVING |
Audrey overwhelmed Mar 27. Stephanie wants Problem > Solution > Data. Progress by Apr 13. |
| Email campaigns / survival guide |
3 of 15 |
Apr 6 |
DELAYED |
Was supposed to launch "Tuesday" (Apr 7). Still not sent. |
| KSHB / media partnership |
3 of 15 |
Mar 30 |
DECIDED |
$5.5K test or $10K. Weather sponsorship free. Launch July. |
🧠 Stephanie Engagement Patterns
When Stephanie Engages Most
💰 Dollar amounts: Revenue numbers, cost savings, spend decisions. She locks in immediately.
🛠 Operational problems: Techs not clicking done, payroll bottleneck, call routing. She gets animated and provides solutions.
📺 Live demos: When Robert creates something in real time (GCLID field, QB fix), she watches and trusts it.
📋 Clear structure: When Robert uses an agenda or numbered items, she can follow along and contribute.
👥 Team decisions: KSHB partnership, Unbounce approval, Audrey workload - she makes fast calls.
When Stephanie Disengages
🚫 Technical jargon: "RAG system," "canonical metric registry," "Jinja templates" -- her eyes glaze. Direct quote: "I have no idea what that means."
🚫 Long explanations without context: She literally said "Give me the problem first." Without the WHY, she can't process the WHAT.
🚫 Mobile calls: Apr 4 she was out and about. Couldn't see screen. Call was less productive.
🚫 AI system descriptions: "228 experiments nearly destroyed" -- she has no framework for why that matters.
🚫 Process over outcome: She wants to know WHAT it does for the business, not HOW it works internally.
Stephanie's Exact Communication Preferences (from transcripts)
Mar 27: "Audrey would like to talk to you like a normal person without AI." / "Too much data dump. It needs to be streamlined."
Apr 4: "Can you give me the context of what this call is about?" (She needs the framing FIRST.)
Apr 6: "I have no idea what that means, Robert, but I'm glad you know." / "If you tell me the point first, then I can follow."
Apr 10: "I'm looking at it and I have no idea what I'm looking at here. Problem first, then solution."
Apr 13: "Give me the problem first, then the solution, then the data. I need context to process complex information."
Evolution: She has given this SAME feedback 5 times across 5 meetings. Each time slightly more explicit. By Apr 13 she spelled it out crystal clear. The fact she had to repeat it 5 times is a pattern Robert must break.
🎭 Robert's Presentation Effectiveness
Meeting-by-Meeting Performance Assessment
| Date |
Led w/ Data? |
Organized? |
Steph Got It? |
Grade |
Notes |
| Mar 25 |
✅ |
✅ |
N/A |
A- |
1:1 with Kalen. Data-driven price book review. Kalen engaged. Clean structure. |
| Mar 27 |
⚠ |
✅ |
❌ |
C+ |
Had an agenda (good), but Audrey felt overwhelmed. Stephanie said "talk like a normal person." |
| Mar 30 (St) |
⚠ |
⚠ |
⚠ |
C |
79 min standup. Too many topics. KSHB, logo, snacks, Zeus, Daniel all in one meeting. Scattered. |
| Mar 30 (S+R) |
✅ |
⚠ |
✅ |
B+ |
Stephanie engaged heavily on ops (tech job closing, payroll). She drove the solutions. Robert listened well. Ran 111 min though. |
| Apr 2 |
✅ |
✅ |
N/A |
B+ |
Good Kalen 1:1. Led with the contact form crisis, explained impact. Kalen asked good questions. |
| Apr 4 |
✅ |
✅ |
⚠ |
B- |
Had a script (good). Stephanie was mobile. She asked for context first. Data validation explanation was too technical for a phone call. |
| Apr 6 (St) |
✅ |
❌ |
❌ |
D+ |
140 min. 55 action items. Stephanie said "I have no idea what that means." Admitted experiment destruction. Too much process, not enough outcome. |
| Apr 10 |
✅ |
✅ |
⚠ |
B |
Clear battle plan. Oxygen ceiling explained well. Unbounce + Bricks decision made. Stephanie repeated "problem first" feedback. |
| Apr 13 |
✅ |
✅ |
⚠ |
B |
Better structure. Live GCLID demo (win). But still 86 min. Stephanie gave explicit format instructions. Did first Start/Stop/Continue. |
Grade trajectory: C+ (Mar 27) → D+ (Apr 6 low point) → B (Apr 13). Recovery happening but slowly.
Best format: 1:1 with Kalen. Data-driven, focused, efficient. Robert is natural here.
Worst format: Full team standup without tight agenda. Spirals into 2+ hours.
🚨 Recurring Mistakes (Pattern Analysis)
1. Technical Jargon Without Translation
Occurrences: Mar 27, Apr 6, Apr 10, Apr 13 (4 meetings). Mentions RAG, canonical registries, Jinja, experiments to non-technical audience. Stephanie explicitly asked for plain English 5 times.
Fix: Before every technical concept, state the BUSINESS IMPACT first. "This means fewer wrong numbers on your reports."
2. Starting With Solution Before Problem
Occurrences: Apr 4, Apr 6, Apr 10, Apr 13 (4 meetings). Jumps into what he built/fixed before explaining what was broken and why it matters. Stephanie repeated "problem first" 5 times across meetings.
Fix: PROBLEM (1 sentence) > IMPACT ($) > SOLUTION (1 sentence) > PROOF (live demo or number).
3. Meeting Time Blowout
Occurrences: Mar 30 (111m), Apr 6 (140m), Apr 13 (86m). Full team standups consistently run 40-80 minutes over the 60-min target. Too many agenda items crammed in.
Fix: Max 8 agenda items per standup. Timer per topic. Park items for async follow-up.
4. Showing Process Instead of Outcome
Occurrences: Apr 6 (experiment failures, timer logs), Apr 13 (metric registry internals). Stephanie does not need to know the engineering. She needs to know "your numbers will be accurate now."
Fix: 1 sentence on what changed. 1 number proving it works. Move on.
5. Admitting Failures Without Positive Frame
Apr 6: Told Stephanie about nearly destroying 228 experiments and losing 3 API keys. This builds anxiety, not trust. She replied "You are really messing up."
Fix: Frame as "We caught X before it became a problem" not "X almost exploded." Lead with the save, not the scare.
6. Overpromising Timelines
Apr 6: "Launch email campaign Tuesday." Apr 10: "Landing pages this week." Both slipped. Stephanie remembers. Each miss erodes credibility.
Fix: Under-promise, over-deliver. Say "by end of week" when you know you can do it by Wednesday.
🤝 Relationship + Trust Evolution
Trust Trajectory: Mar 25 - Apr 13
Phase 1 (Mar 25-30): Establishing Credibility
Robert proving technical depth to Kalen via price book. Kalen engaged and impressed with data sourcing. Audrey felt overwhelmed by volume. Stephanie's first flag: "Talk like a normal person." Trust = fragile.
Phase 2 (Apr 1-4): Building Through Action
Nick partnership meeting showed Robert as connector/facilitator. Contact form crisis handled transparently with Kalen. Stephanie got 5-step validation explanation but still on a phone call while out. Trust = building with Kalen, still shaky with Stephanie.
Phase 3 (Apr 6): Low Point
140-min standup. Too much information. Admitted system failures. Stephanie: "I have no idea what that means." "You are really messing up." 55 action items without clear ownership. Trust = damaged. Robert self-assessed the meeting as a "loss."
Phase 4 (Apr 10-13): Recovery
Apr 10: Clean battle plan. Oxygen limitation explained simply. Decision made (Unbounce). Stephanie engaged on platform choice. Apr 13: Shorter, live demos, first Start/Stop/Continue. Stephanie gave constructive format feedback instead of frustration. Kalen: "Numbers are guilt" (engaged in data review). Trust = recovering. Stephanie is coaching Robert on communication, which means she's investing in the relationship.
Key Signal: Stephanie's tone shifted from frustration (Apr 6: "You are really messing up") to coaching (Apr 13: "Give me problem first, then solution, then data"). This is a positive sign -- she's telling Robert HOW to succeed instead of just expressing disappointment.
🏆 What Works Best (Proven from Transcripts)
Live Demos
GCLID field created during Apr 13 call. QB fix done live. When Stephanie and Kalen SEE it happen, they trust it. No amount of explanation matches 30 seconds of watching it work.
Effectiveness: 10/10
Dollar-First Framing
"We caught $128K in phantom revenue." "$231K in operating costs needs review." "$600/hr per tech target." Leading with money grabs attention instantly from both Stephanie and Kalen.
Effectiveness: 9/10
Problem > Solution > Data
Stephanie's explicit request. When Robert structures his points this way, she follows. When he doesn't, she gets lost. This is the single most important communication fix.
Effectiveness: 9/10
Letting Stephanie Drive Ops
Mar 30 ops call: Stephanie identified the IF-THEN notification rule for non-managed techs. She's strongest when she identifies the operational problem and Robert offers the technical solution.
Effectiveness: 9/10
1:1 With Kalen
Every Kalen 1:1 (Mar 25, Mar 30, Apr 2, Apr 3) was efficient and productive. Kalen engages deeply on data, catches discrepancies, provides field intel. This is Robert's most natural meeting format.
Effectiveness: 9/10
Written Agendas
Meetings where Robert prepared a doc/agenda (Mar 27, Apr 2, Apr 4, Apr 13) were more focused. Apr 6 had no tight agenda = 140 min disaster. Structure prevents sprawl.
Effectiveness: 8/10
👥 Attendee Participation Map
| Person |
Meetings |
Strongest Role |
Best Meeting Format |
Key Quotes |
| Robert |
15/15 |
Technical leader, presenter, builder |
1:1 with Kalen (data deep-dives) |
"Let me cook for a second." / "I think I did decent. Presentation can be dialed in." |
| Stephanie |
9/15 |
Decision maker, ops problem solver, communication coach |
Ops 1:1 with Robert (she drives agenda) |
"Give me problem first, then solution, then data." / "You are really messing up." |
| Kalen |
8/15 |
Data validator, field expert, pricing authority |
1:1 data review with Robert |
"That's not accurate, I sold $22,400." / "Numbers are guilt." |
| Audrey |
7/15 |
Design lead, creative direction, brand guardian |
1:1 design walkthrough (Apr 6 session) |
"I'm having a hard time keeping up." / Every asset named and ready in Drive. |
| Ashton |
3/15 |
Lead management, workflow design, field ops |
1:1 with Robert on workflow |
"A living breathing list where things get taken off automatically." |
| Kassidy |
2/15 |
ST training, booking workflow expert |
Structured training session |
"Book the assumed last day first." / "Projects = scope, Jobs = visits." |
| Nick |
1/15 |
Partnership, referral source, industry insight |
Casual partnership discussion |
"Our clients already know what needs to happen." (Warm referrals.) |
💡 Strategic Recommendations
Meeting Structure Recommendations
1. Cap weekly standup at 60 min with a hard stop. Use timer. Max 8 items.
2. Every agenda item in format: PROBLEM (10 sec) > IMPACT ($) > SOLUTION > NEED (decision/approval/info).
3. Do 1 live demo per standup. Builds trust more than 10 slides.
4. Move data deep-dives to Kalen 1:1s (he loves them, Stephanie zones out).
5. End every standup with Start/Stop/Continue (attempted Apr 13 -- make it permanent).
6. Park technical internals for async Slack updates, not standup time.
7. Track carryover items explicitly. If an item appears in 3+ meetings, escalate it.
Communication Upgrades (for Robert)
For Stephanie: Problem > Solution > Data. Always. No exceptions. Lead with dollars. Zero jargon. Max 90 seconds per topic. If she can't see a screen, keep it verbal-only with 3 key numbers.
For Kalen: Lead with data. Show discrepancies openly. Ask for field validation. He catches things the system misses. Use him as the data trust partner.
For Audrey: One task at a time. All specs in one place (Drive folder per project). No data dumps. Project-by-project. She is detail-oriented but gets overwhelmed by volume.
For Ashton: Show him the dashboard. Make it live and breathing. He thinks in workflows (call now, book now, follow-up). Build what he describes, not what seems cooler.
For all: Stop admitting system failures without framing the save. "We caught a $128K error before it reached your reports" > "228 experiments almost got destroyed."
Next Standup Prep Checklist (based on 15-meeting analysis)
☐ Max 8 agenda items. Each in PROBLEM > IMPACT > SOLUTION > NEED format.
☐ Prepare 1 live demo (something visual Stephanie can watch happen).
☐ Review carryover items: landing pages, email campaign, Ashton dashboard, Daniel AI.
☐ Lead with revenue snapshot: 3 numbers, 10 seconds.
☐ No technical jargon unless Kalen is the audience.
☐ Set 60-minute hard stop. Use phone timer visible to all.
☐ End with Start/Stop/Continue (3 questions, 90 sec each).
☐ Post-meeting: numbered action list with owners and deadlines within 1 hour.
📅 Monday Standup Evolution (4 Meetings Analyzed)
⏱ Duration Trend
📉 53% reduction from worst to best. Target: 50 min.
🏆 Meeting-by-Meeting Scorecard
✅ Clean data, role-specific tasks, clear math
❌ Presentation only, no live discussion, aspirational
💡 Good foundation but untested in live format
❌ 6 min on snacks/logo before business
❌ No structure, no agenda, no revenue numbers
❌ Stephanie arrived 15 min late, missed opening
💡 Need a tight agenda ready BEFORE everyone sits down
❌ 140 minutes (2.3x target)
❌ 55 action items (unrealistic, most carried over)
❌ Scattered across too many topics
✅ Comprehensive coverage, Audrey/Ashton got clear tasks
💡 Volume overwhelmed everyone. Fewer items, tighter time.
✅ 62 min (3% over target, 53% improvement from Apr 6)
✅ 3 things DONE live (GCLID, Pricebook, Emergency paused)
✅ Stephanie most engaged, gave format feedback
❌ Daniel ROI unverified, format still solution-first
💡 Best standup yet. Fix the format and verify every number.
🔄 Carryover Items (Keep Appearing)
3x
🎨 Landing pages (Mar 30, Apr 6, Apr 13) -- STILL NOT DONE. Priority #1 this week.
2x
🧾 Invoice backfill (Apr 6, Apr 13) -- deadline set: Fri Apr 18
2x
🏦 Plaid connection (Apr 6, Apr 13) -- Stephanie action, deadline Fri
2x
🤖 Daniel AI attribution (Apr 6, Apr 13) -- deferred AGAIN until after landing pages
2x
🍫 Snack fridge (Mar 30, Apr 6) -- RESOLVED ✅
🚨 THE #1 PATTERN: Stephanie Has Said This 5 Times
"Give me the problem first, then the solution, then the data. I need context before I can process the fix."
Mar 27 ❌
Apr 4 ❌
Apr 6 ❌
Apr 10 ❌
Apr 13 ❌
5 times. Same feedback. This is the #1 fix for Apr 20.
🎯 Apr 20 Standup Game Plan (Target Grade: A)
🛑 STOP
Leading with solutions
Technical jargon
Unverified ROI claims
Going over 50 min
✅ START
Problem > Solution > Data
Verify numbers night before
Live demos for asks
Timer on every topic (90 sec)
🔁 CONTINUE
Doing things live in meeting
Dollar-first framing
Emoji talking script
Start/Stop/Continue ritual
Comprehensive Analysis | 15 meetings analyzed | Mar 25 - Apr 13, 2026 | Built from full Gemini transcripts