Test 098

We got through the reset. Notes are here. - leadership reset - notes from Feb 26 - attendees: Morgan Chen, Devon Hayes, Jake, Leo Park, Priya, Anna Martinez. Sarah Kim joined the opening handoff and enterprise-packaging section. - internal line agreed: more room, same discipline. Defensible story, not a bigger story. - No one is to use the close as permission to describe Mercury as enterprise-ready now or to reopen every deferred initiative. - owner map - Jake keeps Mercury execution and the weekly launch-evidence path. MER-1279 remains the internal operating ledger for launch-relevant evidence, with links back to source evidence rather than summary theater. - Leo Park owns platform seams, release discipline, and the cases where sync trust / system behavior crosses from cleanup into architecture or system-risk work. - Priya owns activation / onboarding UX, admin / setup clarity, and failure-state legibility. Settled design decisions stay settled unless new evidence says otherwise. - Anna Martinez owns retention evidence, cohort-definition discipline, and the board-consistent outside-reader package. - Devon Hayes owns enterprise-readiness commercial framing and procurement packaging, working with Sarah Kim on the customer / external coordination thread. - Morgan Chen owns board follow-through, sequencing, dates / promises / not-yet lines, and the hiring sequence. - enterprise-readiness sequence - Keep the next-phase list bounded to SSO timing, admin-change audit history, clearer admin-versus-billing-owner separation, and a standalone procurement packet. - Devon Hayes + Sarah Kim package current-state commercial / procurement material using shipped or current product facts only. - Jake + Leo Park provide current product facts and seam-risk input; they are not to backdoor roadmap promises into customer material. - No Evergreen-specific commitments, no feature dates, and no enterprise add-on quoting before the relevant work ships. - Evergreen Bank remains a useful stress case for the current path, not a reason to convert wave-1 learning into bespoke-build behavior. - board / investor follow-through - First post-close board framing stays on defensible retention evidence and repeatable enterprise expansion learned through Mercury / Evergreen, not a rush to spin a Series C story. - MER-1279 and Leo Park's risk readout stay internal operating evidence, not board or investor proof claims. - Anna Martinez + Morgan Chen will keep the board pack tight: retention truth, expansion truth, bounded enterprise-readiness next steps. - hiring sequence - Decision: do not reopen the second Mercury engineering req. - If Mercury engineering hiring reopens later, use the existing evidence rule: senior for repeated platform / architecture seam failures needing independent ownership; implementation-heavy mid-level for hardening / throughput constraints; no req if the current split can close the remaining work. - Decision: first new search to scope is a customer-growth / GTM leader, not an immediate Mercury engineering search. - Role intent: build a repeatable customer-growth motion out of Mercury / Evergreen-like pull without turning accounts into bespoke commitments or product-roadmap negotiating sessions. - Devon Hayes + HR to draft the first role description. Morgan Chen reviews before anything goes wider than the small reset group. - near-term cadence - Short weekly Mercury truth check stays focused on support edges, live-sync trust, admin friction, and what is materially changing in product. - Enterprise-readiness review stays a separate lane from current Mercury release work so it does not contaminate every release note. - Close-thread handoff is explicit: Sarah Kim keeps the customer coordination lane, but owners take back their operating lanes now. Please turn this into an internal leadership recap. It should record the actual operating decisions: Jake on Mercury execution and MER-1279, Leo on platform seams/release discipline, Priya on activation/onboarding UX, Anna on retention evidence, Devon + Sarah on enterprise-readiness commercial packaging, and me holding board/hiring sequence. Also make the hiring outcome unambiguous: no second Mercury engineering req reopened, first new search to scope is customer-growth/GTM.

We got through the reset. Notes are here. - leadership reset - notes from Feb 26 - attendees: Morgan Chen, Devon Hayes, Jake, Leo Park, Priya, Anna Martinez. Sarah Kim joined the opening handoff and enterprise-packaging section. - internal line agreed: more room, same discipline. Defensible story, not a bigger story. - No one is to use the close as permission to describe Mercury as enterprise-ready now or to reopen every deferred initiative. - owner map - Jake keeps Mercury execution and the weekly launch-evidence path. MER-1279 remains the internal operating ledger for launch-relevant evidence, with links back to source evidence rather than summary theater. - Leo Park owns platform seams, release discipline, and the cases where sync trust / system behavior crosses from cleanup into architecture or system-risk work. - Priya owns activation / onboarding UX, admin / setup clarity, and failure-state legibility. Settled design decisions stay settled unless new evidence says otherwise. - Anna Martinez owns retention evidence, cohort-definition discipline, and the board-consistent outside-reader package. - Devon Hayes owns enterprise-readiness commercial framing and procurement packaging, working with Sarah Kim on the customer / external coordination thread. - Morgan Chen owns board follow-through, sequencing, dates / promises / not-yet lines, and the hiring sequence. - enterprise-readiness sequence - Keep the next-phase list bounded to SSO timing, admin-change audit history, clearer admin-versus-billing-owner separation, and a standalone procurement packet. - Devon Hayes + Sarah Kim package current-state commercial / procurement material using shipped or current product facts only. - Jake + Leo Park provide current product facts and seam-risk input; they are not to backdoor roadmap promises into customer material. - No Evergreen-specific commitments, no feature dates, and no enterprise add-on quoting before the relevant work ships. - Evergreen Bank remains a useful stress case for the current path, not a reason to convert wave-1 learning into bespoke-build behavior. - board / investor follow-through - First post-close board framing stays on defensible retention evidence and repeatable enterprise expansion learned through Mercury / Evergreen, not a rush to spin a Series C story. - MER-1279 and Leo Park's risk readout stay internal operating evidence, not board or investor proof claims. - Anna Martinez + Morgan Chen will keep the board pack tight: retention truth, expansion truth, bounded enterprise-readiness next steps. - hiring sequence - Decision: do not reopen the second Mercury engineering req. - If Mercury engineering hiring reopens later, use the existing evidence rule: senior for repeated platform / architecture seam failures needing independent ownership; implementation-heavy mid-level for hardening / throughput constraints; no req if the current split can close the remaining work. - Decision: first new search to scope is a customer-growth / GTM leader, not an immediate Mercury engineering search. - Role intent: build a repeatable customer-growth motion out of Mercury / Evergreen-like pull without turning accounts into bespoke commitments or product-roadmap negotiating sessions. - Devon Hayes + HR to draft the first role description. Morgan Chen reviews before anything goes wider than the small reset group. - near-term cadence - Short weekly Mercury truth check stays focused on support edges, live-sync trust, admin friction, and what is materially changing in product. - Enterprise-readiness review stays a separate lane from current Mercury release work so it does not contaminate every release note. - Close-thread handoff is explicit: Sarah Kim keeps the customer coordination lane, but owners take back their operating lanes now. Please turn this into an internal leadership recap. It should record the actual operating decisions: Jake on Mercury execution and MER-1279, Leo on platform seams/release discipline, Priya on activation/onboarding UX, Anna on retention evidence, Devon + Sarah on enterprise-readiness commercial packaging, and me holding board/hiring sequence. Also make the hiring outcome unambiguous: no second Mercury engineering req reopened, first new search to scope is customer-growth/GTM.