Morgan Chen

Use this: - Friday is Nadia’s last day. - Acknowledge that she sharpened enterprise conversation prep, account-source discipline, and scripts for cleaner account questions. - Say the Head of Customer Growth role is not the right fit for Scaffold’s next phase. - Say we’re not opening an immediate replacement search. - Route customer-growth pattern work to Sarah for account-thread hygiene, Anna for evidence quality and Compass caveats, Devon for commercial/procurement context where needed, and me for board/customer narrative. - Product requests and roadmap asks still go through standard product-owner routes.

Keep it respectful, short, and operational. No restructuring, performance, blame, Compass GTM proof, behavior-change proof, or replacement-search loop.

Closeout is complete. Nadia’s final day is today.

HR paperwork and access closeout are ready for end-of-day execution. Devon and I did the last wording check with Nadia. Send the team note today, create a private closeout record, and update the customer-growth staffing plan so HR doesn’t treat this as a backfill trigger.

Final inputs: - This is role-fit / next-phase, not blame. - Nadia improved enterprise conversation prep and account-source discipline in places, and handed scripts to Sarah plus behavior-read context and evidence caveats to Anna. - No immediate Head of Customer Growth replacement search. - RevOps, CS, SDR, field-sales, and the second Mercury engineering req stay closed through the rest of Q2. - After the exit, Sarah owns account-thread hygiene, live-account continuity, and customer-thread notes; Anna owns evidence quality, definitions, caveats, and behavior-read context; Devon owns commercial/procurement context where needed; I own board/customer narrative. - Evergreen stays Sarah’s live customer thread and Devon’s commercial/procurement lane. Nadia’s prior involvement doesn’t change product facts or authorize roadmap promises. - Compass stays narrow internal action-prompt work, not a customer-facing launch, GTM proof, behavior-change proof, H1 hiring trigger, or immediate hiring trigger.

Draft the Friday wrap.

Inputs: - Team: Nadia transition closed today; customer-growth pattern work now routes through Sarah for account-thread hygiene, Anna for evidence quality, Devon for commercial/procurement context where needed, and me for board/customer narrative. Compass stays internal prompts only. Mercury sequencing stays protected. - Customers: Evergreen is a steady annual-account current-state proof point and customer-thread continuity stays with Sarah. Acme’s API v2 export-timeout stays a bounded Atlas/support product-priority item, not Compass proof. - Investors/board: Q2 board cycle starts next week. Story is restraint, retention/renewal evidence, and reliable Mercury/Atlas execution — not a Series C narrative. - Legal/ops: no new decision needed beyond the already-handled HR closeout.

Bullets under team, customers, investors/board, and legal/ops. No intro or outro. Keep each bullet short and don’t rehash private personnel detail beyond the already-announced transition.

Friday evening. Place the usual Lemongrass green curry order.

Quick Kibo update to record: we kept the protected Saturday morning block, did the early short flat Lake Merritt-side walk, and he was stable after. Started a little stiff, loosened up, ate normally afterward, and no vomiting or new gait issue. Just record it — no follow-up needed.

Looking at Monday board-cycle prep. Give me a compact pass.

Scratch notes: - Q2 board cycle starts Monday. - Evergreen is a real annual Growth account win and enterprise-readiness evidence source, but not repeatable customer-growth proof by itself. - Compass got cut down to internal action prompts. No customer-facing launch, GTM proof, board dashboard, behavior-change proof, or hiring trigger. - Nadia is out; work now routes to Sarah for account-thread hygiene, Anna for evidence quality, Devon for commercial/procurement context where needed, and me for board/customer narrative. - Atlas and Mercury should read steadier under the current owner split: Jake for Mercury sequencing, Leo for platform seams and Atlas technical reads, support/customer owner path intact. - No Series C narrative or investor-coffee loop from this cycle.

Bullets only: opening line, evidence order, where to say no, and what still needs live discussion Monday. Don’t write it like the board cycle is already closed.

Devon flagged the board deck — a few phrases are still too strong. Update the slides directly before the first review block.

Comments + edits: - Evergreen slide should say real annual-account win and current-state enterprise evidence, not repeatable customer-growth proof by itself. - Compass slide should say the customer-facing plan got cut down to retained internal action prompts, not customer workflow or GTM proof. - Owner-routing slide should show Sarah for customer-thread/account hygiene, Anna for evidence quality, Devon for commercial/procurement context, me for board/customer narrative, Jake for Mercury sequencing, Leo for platform seams and Atlas first technical reads, and support rotation as the customer-facing Atlas entry point. - Do not open Series C narrative, hiring trigger, or bespoke-roadmap language.

Update the Q2 board prep deck with that wording.

Sofia just sent this: Evergreen is starting to look like the kind of account later-stage investors will ask about, and she asked whether I want to begin a few quiet coffees after the board cycle so the next financing story doesn’t get built too late.

She framed it as a question, not a demand.

Reply: fair question, but I want to answer it inside the Q2 operating review. Don’t start a Series C narrative or a broad investor-coffee loop this week. Keep the board story on retention, renewal evidence, narrowed Compass learning, and reliable Mercury/Atlas execution.

Devon just offered to take an overnight pass on board cleanup if I need him.

I don’t want him defaulting into that again. Send him a private DM: thanks, no overnight cleanup pass needed.

Route nonurgent cleanup by owner this week instead — Jake for Mercury sequencing, Leo for Atlas/platform seams, Anna for evidence quality, Sarah for customer-thread/account hygiene, Devon only for commercial/procurement context where it’s actually needed, and I’ll hold board/customer narrative.

Overnight board-prep inputs landed from Anna, Sarah, Jake, and Leo. Useful, but scattered, and I want one working evidence grid before the next board review block so the operating story stays restrained.

Make a Board-folder doc titled "Q2 board evidence grid — June 24 working pass." Same boundaries as Monday: Evergreen is real evidence, Compass gets cut down, Atlas/Mercury are steadier, and nothing drifts into Series C, bespoke roadmap, or a hiring implication.

Source notes: - Anna: Evergreen usage and renewal evidence are cleanest where Sarah's account thread is clean; Compass prompt evidence still shows owner noticing/account prep, not customer behavior change; board-facing retention should stay on sturdier renewal/cohort evidence, not weekly cuts. - Sarah: Evergreen is steady as an annual Growth account; customer-thread continuity is clean; no new advanced-admin or procurement/security promises should be implied; Acme remains bounded to its own support/product route. - Jake: Mercury sequencing is holding; do not let Compass become a Mercury sequencing change or a dashboard ask. - Leo: Atlas interim split is holding for normal/medium issues; support owns customer entry, Leo owns first technical read, Jake owns priority/sequencing; Acme large-export follow-up remains bounded. - My scratch: make the evidence order visible; say no to Series C, bespoke roadmap, and staffing-trigger language.

Sofia sent a short list of likely board questions. I want live-answer bullets only — not an email, not a deck edit.

Her questions: 1) What evidence would make Evergreen repeatable instead of just a strong one-account proof point? 2) Should Compass stay alive if it's only internal prompt work? 3) If later-stage investors ask about Evergreen and Mercury, when would I start shaping the next financing story?

Keep the answers inside operating evidence. No investor coffees, no Series C narrative work.

Jamie and I picked this week's offline blocks before board cleanup crowds them out.

Put protected holds on Thursday June 26 from 6:30–8:30 p.m. PT and Saturday June 28 from 8:00–10:00 a.m. PT. Same actual-incident/customer-impacting-emergency exception, and add the Saturday note for a short flat Lake Merritt-side Kibo walk if he's comfortable.

Midweek board block is later this morning. I want a tight facilitation script I can keep in front of me — bullets only.

Scratch notes: - Open with: Q2 was a cleanup quarter and the useful thing is what held after we cut the noisy pieces. - Evidence order: Evergreen, Mercury/Atlas owner split, Compass cutdown, then Q3 operating asks. - Expected pushback: Evergreen looks promising, but repeatability isn't proved; Compass may be too small to keep, but the retained prompt work can still improve owner follow-up; no Series C loop yet. - Closing boundary: Q3 should rebuild evidence quietly around retention, renewal, and reliable execution.

Midweek board block just ended. Capture the notes without softening the caveats, and update the Q2 board prep deck slide on Q3 evidence tests.

Notes right after the block: - Sofia: the operating story is clearer than Monday; Evergreen is real, but don't call it repeatable until Q3 renewal/expansion evidence holds outside the single clean thread. - Compass: okay to keep as internal prompt learning if it stays narrow and has a behavior-evidence test. - Financing: no objection to holding off investor coffees for now, but be ready to say what evidence would change that. - Devon: gave the commercial/procurement context when needed, but looked wiped; offered to take cleanup tonight. - Me: don't let Devon become the default cleanup engine.

Devon just offered another overnight board-cleanup pass.

He said he could take the Evergreen/Compass connective tissue and the commercial slide tonight if I want.

Send him a private Discord DM declining it. Thank him, but route cleanup by owner instead — Jake for Mercury, Leo for Atlas seams, Anna for evidence, Sarah for account threads, Devon only for true commercial/procurement context, and I’ll hold board/customer narrative.

Closing slide still reads too much like a launchpad for the next financing story. Fix it before Thursday's final prep block.

Draft line I want gone: "Evergreen gives us the enterprise proof to reopen the next financing narrative from a stronger position."

Replacement direction: Evergreen gives us a real annual-account proof point; Q3 rebuilds retention, renewal, and execution evidence quietly before any broader investor story. Compass is cut down, not relaunched. Mercury/Atlas are reliable owner-routed execution, not a new platform narrative.