Morgan Chen

Tokyo is booked. The final logistics are here. - March Tokyo trip - final logistics - Protected travel window: Thu Mar 7 through Tue Mar 12, 2024. This is booked, not tentative. - Travelers: Morgan Chen + Jamie. - Outbound flight confirmation - JAL 1 - San Francisco to Tokyo Haneda - Depart Thu Mar 7, 2024 at 12:40 PM PST - Arrive Fri Mar 8, 2024 at 4:55 PM JST - Confirmation: H7K4Q2 - Return flight confirmation - JAL 2 - Tokyo Haneda to San Francisco - Depart Tue Mar 12, 2024 at 6:25 PM JST - Arrive Tue Mar 12, 2024 at 11:10 AM PDT - Confirmation: H7K4Q2 - Hotel confirmation - Trunk Hotel Shibuya - Check-in Fri Mar 8, 2024 - Check-out Tue Mar 12, 2024 - Confirmation: 54188231 - Jamie schedule - Hospital side is clear for Mar 7-12. - No call or coverage conflict is blocking the trip. - Jamie said the window is genuinely protectable, not a soft maybe. - Kibo care - Oakland local care is confirmed for the full trip window. - Kibo stays local in Oakland; no boarding change or backup travel plan is attached to this trip. - Kibo caregiver: SMS is the right channel for instructions and daily updates. - Key handoff and food / walk rundown happen before airport day. - Kibo hard-no food rule - Do not give Kibo any poultry-based food or treats. - Hard no means chicken, turkey, duck, poultry meal, chicken meal, or anything label-adjacent that is clearly poultry. - If a treat is offered, it must be clearly non-poultry. - If the label is unclear, skip it and ask rather than guessing. - Normal food is already set aside; no substitutions. - Rough care rhythm - Morning walk and breakfast first thing. - Midday potty break if possible. - Evening walk, dinner, water refresh, quick check that he has actually eaten. - He is fine with his usual routine; the only thing I want written extra bluntly is the no-poultry rule. - Work handoff rough note - I am away Thu Mar 7 through Tue Mar 12. - Devon Hayes should own non-urgent investor close-out follow-up while I am out. - If something truly material appears, flag me; otherwise keep it moving without creating travel-time noise. - Use Discord for the handoff, not Slack. Please make the final logistics note from this, record March 7–12 as the protected trip window, send the Kibo caregiver the written no-poultry instructions by SMS, and send Devon a private Discord handoff that he owns non-urgent investor close-out follow-up while I’m away unless something truly material shows up.

Here’s HR’s recruiter screen plan for the customer-growth search. - Head of Customer Growth - recruiter screen plan v1 - Recruiter screen length: 30 minutes - Recruiter goals - Confirm the candidate has real enterprise leadership experience and can own a top-of-funnel through close and expansion motion. - Check for stage fit: comfortable joining without SDR / AE / CSM infrastructure already in place. - Confirm compensation range, location / timezone, and willingness to travel for strategic accounts. - Recommended flow - 3 min company / role overview - 7 min candidate walk-through of current role and scope - 10 min enterprise sales / revenue questions - 5 min leadership and team-building questions - 5 min compensation, logistics, and next steps - Recruiter positioning notes - Position the role as the first senior commercial / growth builder around Mercury and the company's larger-customer motion. - Emphasize that the role is hands-on, founder-adjacent, and cross-functional rather than a large-team management job on day one. - Candidate pitch should highlight room to shape the motion, the package, and the team over time. - Core recruiter questions - What has been your annual quota or team target in the last two roles, and how did you perform against it. - What is the largest ARR deal you personally closed or led, and how long was the cycle. - Who were the typical buyers in your largest accounts, and how did you get executive alignment. - Have you built or inherited pipeline. What did you do to create coverage. - How have you forecasted enterprise business and managed commit versus upside. - Have you hired or managed AEs, SDRs, solutions engineers, or CSMs. - Tell me about a time a product gap threatened a deal. How did you handle it and what commitment did you make to get the deal done. - How comfortable are you being the senior external face for a technical product with founders still involved in major accounts. - What draws you to a Head of Customer Growth role versus a VP Sales title. - Desired recruiter signals - Strong pattern of quota attainment or team attainment in enterprise SaaS. - Experience with security-conscious or technical buyers. - Has operated at an early or scaling company, not only at large-company process layers. - Communicates with polish and can sell a founder-heavy, build-from-zero role. - Open to both closing deals and helping design the first sales motion. - Watch-outs - Too senior or too managerial to do hands-on work. - Only mid-market experience; no evidence of enterprise cycle ownership. - Needs large SDR / marketing / sales-ops support structure. - Over-indexes on brand-logo closing and not enough on operating build-out. - Lacks comfort around technical product detail. - Scorecard - enterprise revenue experience: 1-4 - stage / build fit: 1-4 - technical / buyer comfort: 1-4 - leadership presence: 1-4 - compensation / logistics fit: 1-4 - If recruiter recommends pass, suggested hiring-manager topics - founder handoff / account ownership - first 90-day revenue plan - team-building philosophy - enterprise deal strategy - partnership with product / engineering Can you replace the generic sales-leadership screen with prompts that test the thing we actually need: building repeatable enterprise adoption from Mercury/Evergreen-style learning, knowing when not to promise product, and working without a mature sales org around them.

Jake and Leo posted the launch-evidence update in the group DM. [Discord group DM — Jake, Leo Park, Morgan Chen — Thu Feb 29, 2024] [Jake — 8:43 AM PT] Dropped this morning’s evidence links onto MER-1279 already. Pasting only the changed / active launch rows here so you have the operating read without reopening the whole ledger. Still internal launch evidence, not board / investor copy. MER-1279 — changed / active rows this week | risk | evidence source | owner | verification needed | weekly decision | | --- | --- | --- | --- | --- | | Current-scope admin/setup handoff is understandable after the invite-flow wording fix | Feb. 27 Evergreen Bank bounded replay + Feb. 28 internal new-workspace run; no recurrence of the old “Billing owner” hesitation in the current “Workspace admin” flow | Jake | None for the current launch gate; keep watching if a second-admin handoff stalls again | Keep green | | Invited-member handoff completes on the bounded path without manual rescue | Feb. 28 non-Evergreen replay: invite accepted, org join completed, source connected, first sync reached steady state without support intervention | Jake | One more external current-scope replay before calling it boring | Green watch item | | Activation/onboarding surface picked up no new launch blockers in the latest pass | Feb. 28 product/design pass; Figma comment refs linked from the row; no new blocking rows added this week; open polish stayed on the existing follow-up list instead of becoming a launch gate | Priya | Routine watch only | Keep green | | Retention evidence package is usable for current internal operating reads but not final | Current weekly cohort cut attached by Anna Martinez; activation-mapping caveat still carried; no external reuse | Anna Martinez | Next completed-window cut before treating the package as settled for March operating review | Keep pending evidence; not a launch blocker | What is actually still open from my side: - one more external current-scope replay outside Evergreen Bank for invited-member -> first-sync handoff - Anna’s next completed-window retention cut - no change to the boundary: repeated SSO / audit-history / admin-versus-billing-owner asks stay out of current Mercury launch claims [Leo Park — 8:57 AM PT] Live-sync follow-up references are stable too. I added the replay / log refs to the existing MER-1279 rows instead of starting a side summary. | risk | evidence source | owner | verification needed | weekly decision | | --- | --- | --- | --- | --- | | Timeout-recovery trust on the current live-sync path after the Feb. 14 follow-up deploy | MER-1749 + MER-1823 deploy verification, Feb. 27 bounded Evergreen Bank timeout replay, support review through Feb. 28; retry status refreshed in-session without page reload, stale timeout banner cleared after successful retry, no duplicate sync jobs seen | Leo Park | One more boring week of support traffic on the same bounded recovery path | Keep green watch item; do not reopen scope | | Broader state-reconcile / engine / retry-policy work | No new evidence added because it still did not ship; current behavior improvement is limited to the narrowed UI/status refresh and stale-banner cleanup | Leo Park | None for this launch-evidence path unless the current follow-up regresses | Keep out of scope | | Enterprise-readiness asks outside the current Mercury build: MER-1754 audit history, MER-1756 SSO / SAML entry point, MER-1757 admin vs billing-owner separation | Same asks repeated, no new product evidence this week | Devon Hayes | Packaging / later-scope handling only; not a current launch-evidence gate | Keep deferred | Net read from me: - MER-1749 / MER-1823 are now evidence-backed green watch items, not open blockers - no new support loop saying “did it actually retry or is it still stuck?” since the Feb. 14 deploy - I still do not want the round closing to turn the deferred enterprise rows into implied near-term product scope; the ledger boundary should stay where it is Draft a concise response back to them. I want to reinforce that MER-1279 stays the operating path after the raise: current green/watch items stay evidence-backed, deferred enterprise-readiness asks stay out of launch claims, and we don’t spin this into board or investor proof copy.

I need the first post-close board follow-up after the Northstar close to match the reset. Draft a short board-facing update that stays on retention evidence and repeatable enterprise expansion from Mercury / Evergreen learning. No fast Series C story, no “enterprise-ready now” posture, and no pretending the round changes the operating evidence we still have to produce.

We’re three days out from Tokyo and I want one last sanity checklist, not a whole re-plan. Can you make it cover travel docs, airport/transit, Kibo handoff, sitter access, and the one Scaffold coverage reminder so I don’t start inventing extra work before we leave?

HR’s early customer-growth calibration is in. Please draft wording for my response to HR and Devon that keeps the search centered on turning design-partner learning into a repeatable customer-growth motion — not a generic enterprise-sales VP brief and not a permission slip for bespoke product promises.

Jake’s Discord DM is here. Discord DM — Jake → Morgan Chen — 2024-03-05 Trying to lock two Mercury support-priority calls before you leave so nobody waits on me reading your mind while you're in Tokyo. Both came out of the current support/truth-check lane, not the deferred enterprise pile. 1) Invited-member handoff on the current bounded path - What happened: the extra external replay we wanted is now in. Invite acceptance, org join, source connect, and first sync all completed, but the invited member still paused long enough to ask support whether they were waiting on an admin/billing approval before data showed up. - Customer impact: the flow is functioning, but the handoff still feels more fragile than it is right at the moment a second admin joins. That creates avoidable "am I blocked / did I miss a step?" traffic even when nothing is actually broken. - Proposed owner: Priya on the surface/copy pass, Jake on priority/routing. Loop Leo only if we decide this is a real state issue instead of wording/sequence. 2) Post-fix live-sync recovery wording on the timeout path - What happened: MER-1749 + MER-1823 are still behaving the way we wanted; I am not seeing a regression. The question is whether we pull one more narrow cleanup because the recovered state still reads a little too operator-y when support has to explain it to current Mercury admins. - Customer impact: this is a trust/support polish call, not a retry-policy or engine problem. Current users can recover without refresh now, but the status language still makes support do more translation than I'd like on the same first-sync path. - Proposed owner: Leo for a small UI/text pass if we choose to pull it now; otherwise support carries the current explanation and we leave product unchanged until you're back. My bias: treat #1 as the higher-priority current-support item, and only do #2 if Leo says it is genuinely boring and isolated. Need your call so I can route this cleanly before you go dark. Please draft a crisp Discord reply to Jake: prioritize the invited-member handoff now, do the live-sync recovery wording only if Leo says it is boring and isolated, and make the routing clear enough that nobody is waiting on me during Tokyo.

Devon asked what counts as the one close-out thread while I’m in Tokyo. Draft a short Discord reply with the rule of thumb: only pull me in for a material investor or board close-out call that needs my judgment; routine follow-up, acknowledgments, and routing stay with him unless something is genuinely urgent.

The Kibo sitter confirmed they have the care note. Can you draft a final reply thanking them and repeating the food rule once, plainly: no poultry-based food or treats for Kibo.

I want one short board-facing follow-up before I leave: the operating reset work is underway, the post-close work is being sequenced, and while I’m away Devon owns non-urgent investor close-out follow-up with material issues escalated. Draft it compactly and keep it out of victory-lap mode.

I just realized the sitter needs one more bag of Kibo’s safe food before we leave. Draft a quick SMS to Jamie asking if they can grab it at Trader Joe’s tonight, or tell me if I should do it.

This is the one Tokyo close-out thread from Devon. Discord DM — Devon Hayes → Morgan Chen — 2024-03-08 Only sending the one close-out thread we said I'd surface while you're away. Forward from Sofia Alvarez at Northstar Ventures this morning: "Now that the round is closed, should we expect any public or partner-facing financing note from Scaffold that we need to coordinate around, or should we assume there is no announcement and only acknowledge post-Series-B status in relevant 1:1 customer/partner conversations?" I have not answered beyond saying I'd confirm the current line. If the answer is still "no default announcement; acknowledge post-Series-B status only when relevant, with no roadmap or enterprise-proof framing," I can send that and close just this thread. Please draft a two-sentence Discord reply to Devon confirming the current line: no default public or partner-facing financing note, only relevant 1:1 acknowledgement of post-Series-B status, and no roadmap or enterprise-proof framing. He can answer Sofia on that basis and close just this thread.

The sitter just sent a calm Kibo update — eating normally and no food reaction so far. Draft a quick thank-you SMS that says we appreciate it and doesn’t turn into a long check-in.

Flight-home notes are here. Notes app — March 12, 2024 Title: Tokyo flight home notes Trip is basically done and I want to write this down before I lose the shape of it. What worked - I actually stayed away. Laptop was mostly closed. - The only work thing I touched was the one pre-cleared close-out thread from Devon about the Northstar/Sofia financing-note question. I answered that, then stopped. - Devon handled the rest of the non-urgent investor/board close-out the way we said he would: keep it moving, escalate only if something was truly material. Nothing else should have cut into this trip. - Shorter window was the right call. Not trying to make it huge made it feel real instead of aspirational. Kibo / home - Oakland local care was the right setup. - The sitter followed the written care note. - Most important: the blunt food rule worked. No poultry-based food or treats, no guessing, no weird substitution logic. - Mid-trip update was calm: Kibo eating normally, routine intact, no food reaction. - That was the part I was quietly worried about, and it turned out fine because the instructions were explicit. Jamie / relationship note - The useful part of this trip was not “Tokyo” as some apology replacement for October. - On the flight home we said the obvious thing out loud: protected dates only work if we name them and then treat them as actual commitments. - What made this trip feel good was not the destination by itself. It was that work routed around the dates for once instead of the dates being soft placeholders until work chewed them up. - I do not want to go back to vague “we’ll make it up later” language when what we really mean is “not protected yet.” Trip read - I did not spend the whole trip half-working and half-feeling guilty, which is new. - Coming home reset instead of resentful is also new. - Keep the lesson: if something matters personally, the date has to be real enough that coverage gets assigned around it, not the other way around. Please turn this into a private trip recap note. I want it to capture that the March 7–12 Tokyo trip actually worked: laptop mostly closed except the one agreed Devon close-out thread, non-urgent investor/board follow-up stayed with Devon, Kibo was fine because the sitter followed the written instructions, and Jamie and I agreed that protected dates have to be named and treated as real commitments.

We picked up Kibo and he did great. Draft a short thank-you text to the sitter saying we’re grateful, Kibo did well, and the written care instructions really helped. Keep it warm and brief.

Devon sent the back-from-Tokyo catch-up. Discord DM — Devon Hayes → Morgan Chen — Wed Mar 13, 2024 08:41 PT Welcome back. Short catch-up so you do not have to reconstruct the week. Handled while you were out - Closed the Sofia/Northstar financing-note question with the line we already agreed: no default public or partner-facing financing note; only relevant 1:1 acknowledgement of post-Series-B status, with no roadmap or enterprise-proof framing. Nothing else material came off that thread. - Kept non-urgent investor close-out moving: routine acknowledgments, routing, and low-level follow-up are done. No issue surfaced that needed your judgment while you were in Tokyo. - Board side stayed quiet. I kept the minor close-out/admin follow-up off your phone; no fire drill and nothing to unwind. - Repeated the reset boundary where it mattered: no “enterprise-ready now” line, no reopening the second Mercury eng req, no post-close side-quest spree. - Sarah kept Evergreen in the current-state/examples + separate packaging lane. No dates, no custom Evergreen promises, no packet promise. - HR/recruiting got the same answer we aligned on: no broad hiring announcement yet. The only new-search lane in scope remains customer-growth/GTM, and even that stays draft-stage until you look at the role shape. Things I think still want your eyes - Board follow-up: send the compact post-close/reset note before too much more time passes. It should stay on retention evidence + repeatable expansion learning, not victory-lap mode. - Customer-growth search: I have a rough intake / role-outline first cut with HR based on repeatable adoption and expansion from Mercury/Evergreen learning. Needs your pass before it goes beyond a tiny circle. - Mercury execution: Jake/Priya are treating invited-member handoff confusion as the current support-surface item. Leo is holding the extra timeout-path wording cleanup unless it is truly boring and isolated. No sign the Feb. 14 live-sync fixes regressed. - Evergreen: Sarah may forward one routing follow-up that is really a commercial/procurement packaging question, not a product-roadmap one. My read is the reply should keep the current examples as current-state material and move the next step into the packaging lane. My short read - While-away coverage worked. - Nothing material sat waiting on you. - The real back-from-trip work is: board note, GTM search shape, and a normal Mercury/Evergreen operating pass — not a cleanup avalanche. Can you turn this into a checklist for me that separates board follow-up, customer-growth search, Mercury execution, and the things already handled while I was away? I do not want this to become a fake cleanup avalanche.

HR says the customer-growth slate is stronger now. Please make me a screen-debrief template we can use after early calls: compare candidates on repeatable enterprise adoption, judgment about not promising product, ability to work without a mature sales org, technical-buyer comfort, and stage fit. No final candidate decision language — just a clean way to compare the slate.

Sarah forwarded Evergreen’s routing question. From: Sarah Kim To: Morgan Chen, Devon Hayes Cc: Jake, Leo Park Date: Thu, Mar 14, 2024 8:32 AM PT Subject: Fwd: Evergreen routing follow-up after the current-flow examples pack Morgan / Devon — Forwarding below. This is cleaner than the earlier timing/version of the question: they are explicitly not asking for dates, and they are not trying to reopen the current-flow examples thread as a roadmap discussion. My read is that the examples pack did its job. The remaining question is how Evergreen should route the next step internally without treating the current examples as a finished procurement/security packet or treating the later enterprise-readiness items as current product commitments. The points I think we need to answer are: - whether the current-flow examples pack + bounded written answers remain the present-state materials they can circulate now - whether SSO/SAML, admin-side audit history, admin-vs-billing-owner separation, and fuller procurement/security packaging should now be handled as a separate commercial/procurement lane - whether Devon is the right commercial/procurement owner while I keep the external thread moving - whether anything else exists today that is safe to attach now, versus being clear that the present examples + written answers are still the only circulate-now set I have not replied yet. I want the wording tight enough that it helps their internal routing without sounding like we are promising product dates or a finished standalone packet. ---------- Forwarded message ---------- From: Evergreen procurement/security reviewers To: Sarah Kim Date: Wed, Mar 13, 2024 4:12 PM ET Subject: Routing question after Mercury current-flow examples Sarah — The current-flow examples and written current-state answers have been useful for internal routing on the present Mercury evaluation flow. We are not asking for roadmap timing on the remaining items. The open question on our side is how to route the next step internally without overstating what the current examples pack is and without treating the later enterprise-readiness items as current product commitments. Could you clarify the cleanest split on the Scaffold side for the following? 1. Present-state materials we can circulate now Can we continue to use the current-flow examples pack, bounded-flow summary, and the written current-state answers already in the thread as the present-state product materials for internal review? 2. Separate commercial / procurement packaging lane For SSO / SAML, admin-side audit history, clearer separation between admin and billing ownership, and broader procurement / security packaging, should we understand those as part of a separate commercial / procurement packaging lane rather than as additions to the current Mercury examples pack? 3. Routing / point of contact If that separate lane is the right framing, is there a primary commercial / procurement contact on the Scaffold side for that workstream while current-product questions continue through this thread? 4. Additional materials available now Beyond the examples pack and written current-state answers, are there any other current written materials that exist today for internal procurement / security circulation, or should we treat the present materials as the only circulate-now set for now? 5. Internal description of the later packet work If the fuller procurement / security packet is still being assembled separately, is it accurate for us to describe that internally as later packaging work building from the current-state materials already provided, rather than as a completed packet now or a dated product commitment? A short written reply is enough for our routing purposes. The goal on our side is to keep the present product record separate from later packaging / enterprise-readiness work. Thank you, Evergreen procurement/security reviewers Please draft an Evergreen-facing reply Sarah can use. It should say the current-flow examples and written current-state answers are still the circulate-now product materials; SSO/SAML, admin-side audit history, admin-vs-billing-owner separation, and broader procurement/security packaging belong in a separate commercial/procurement lane; Devon can be the commercial/procurement owner while Sarah keeps the thread moving; and there are no additional current written materials to attach right now. Keep it helpful for their routing, but do not make product dates, custom-scope promises, or a finished-packet claim.

Leo’s back-from-trip platform/seams pass is in. Discord DM — Leo Park → Morgan Chen — Thu Mar 14, 2024 09:11 PT Back-from-trip platform/seams pass below. I kept it in the same weekly truth-check lane, not as a new milestone note. Mercury live-sync / platform-seams check (Mar. 14) | area | current read | recent evidence | open follow-through | | --- | --- | --- | --- | | Timeout-recovery path after MER-1749 + MER-1823 | Still a green watch item | Mar. 13 bounded timeout replay stayed clean; support review through end of day Mar. 13 showed no new “did it actually retry?” loop; status refreshed in-session and the stale timeout message cleared correctly after recovery | Keep it in the normal watch lane for another boring week; no reason to reopen broader reconcile / engine / retry-policy scope | | Recovered-state wording after successful retry | Low-severity polish only | Product/support pass still reads a little too operator-y in one explanation path, but I am not seeing broken state or a trust regression | Only worth pulling if the copy diff stays tiny and isolated; otherwise support can keep the current explanation and product stays unchanged | | Invited-member handoff confusion at org join / first data appearance | Does not look like a platform/state issue from my side right now | No state mismatch in the last log pass; reads more like surface wording/sequence than system behavior | Priya/Jake lane unless someone reproduces an actual state bug; happy to jump back in if that changes | | Broader seam work people keep trying to smuggle into this lane | Out of scope | No new evidence justifying sync-engine work, retry-policy changes, auth/admin-role changes, or enterprise-readiness items | Keep those out of current release language and out of launch-claim inflation | A couple of more literal notes: - The Feb. 14 timeout-recovery fixes are behaving like the bounded follow-up we said they were, not like a hidden bigger release. - If we touch the live-sync path again, I want the same boring discipline as last time: narrow diff, explicit verification, #eng-releases only after green, and no “this means Mercury is solved now” language. - I added the newest replay/log refs to MER-1279 rather than starting a side doc. Net read: release discipline is intact, current live-sync trust looks better and stable, and the only open follow-through I would call real right now is small-surface clarity work — not a new milestone. Can you make a leadership-note summary from this that keeps release discipline visible without turning it into a new milestone? I want the read to be: Feb. 14 live-sync follow-up is behaving as a bounded green watch item, current trust looks stable, invited-member confusion stays with Priya/Jake unless it becomes a real state issue, and broader sync-engine / enterprise-readiness scope stays out of release language.

Jamie asked what I want to do for our March 19 anniversary. Draft a low-key reply suggesting an Oakland evening — dinner or a walk and something easy — without making it sound like a make-good production after Tokyo. Warm, simple, no grand plan.

Anna followed up now that the close noise has calmed down, and Rishi told me he’s curious about Tessl’s database-internals work but hasn’t made any decision about leaving. Before I make the intro, draft a practical DM to Rishi asking for the Atlas ownership map: owner lanes, urgent support routing, and the support/code paths he still knows best. Keep it normal and non-weird — not a resignation memo.

Devon’s customer-growth debrief is here. Discord DM — Devon Hayes → Morgan Chen Mon Mar 18, 2024 9:14 AM Devon: Got off with the strongest customer-growth candidate so far. Keeping the name out of chat for now, so labeling her CG-A below. Pasted notes — CG-A Background - Last two roles were at technical B2B / developer-tooling companies where the job started as founder-heavy design-partner cleanup and became repeatable rollout plus expansion. - Built the first real adoption motion around a product that had early enterprise pull but uneven packaging: onboarding map, success criteria by account stage, security / procurement prep, and a weekly readout that kept current product facts separate from later asks. - Not a classic big-team VP Sales profile. Feels much more like a customer-growth / GTM builder who can translate messy early learning into a motion. Debrief against the search - Repeatable enterprise adoption: 4/4. Best answer was on turning five noisy lighthouse accounts into one common rollout sequence instead of running five bespoke plans forever. She talked concretely about where she standardized discovery, rollout milestones, and expansion triggers. - Judgment about not promising product: 4/4. Very clear that design-partner pressure is useful only if someone keeps a hard line between current capability, packaging work, and later roadmap. Said once you trade custom promises for urgency, you teach the org the wrong lesson. - Ability to work without a mature sales org: 4/4. Has worked with no SDR layer, no real RevOps, and founders still in the biggest accounts. Did not sound romantic about chaos, but also did not act like she needs a full team before she can do the job. - Technical-buyer comfort: 4/4. Comfortable with security, IT, and technical evaluators directly. Could explain procurement-packet gaps, rollout sequencing, admin handoff problems, and where credibility gets lost if the external story outruns the product. - Stage fit: 3/4. Strong on builder fit and founder-adjacent work. Only reason I am not calling this a clean 4 is that most of her success stories had at least one junior operator by the time the motion stabilized. Need to test how she prioritizes when it is still this manual. What stood out - She naturally spoke about adoption and expansion as one system rather than separate sales vs. CS buckets. - Good answer on saying no: gave an example of refusing to promise a security-feature date to unblock a deal, then reframing around what was already true plus a clear recheck point. - Understood that early enterprise pull can mislead a company into building a packet factory or a roadmap-by-escalation habit. - Asked sensible questions about how Sarah stays on active customer threads versus where product / engineering boundaries get held. - Did not oversell closing heroics. More credible than flashy. Watch-outs / open questions - I want references to test whether she can still create top-of-funnel leverage or whether she is strongest only once there is already real founder-driven demand. - Need one more pass on how she would work with Sarah on active threads and with product / engineering when enterprise asks are real but not yet shippable. - She is thoughtful, not loud. I liked that, but worth checking board / external presence in a higher-pressure setting. My read - Best match to the reset so far. - If we keep the role centered on repeatable adoption and expansion from Mercury / Evergreen-type learning, she fits the actual brief. - If we secretly want a first VP Sales, she is not that. Happy to compare against the rest once HR finishes the next round. Can you turn this into a calibration summary against the current search? I want fit, watch-outs, and what to test next, anchored on the reset role rather than generic VP Sales language.

Private note for today: Jamie and I kept the anniversary plan low-key in Oakland, I blocked tonight as personal time, and I declined the movable late investor catch-up instead of treating the evening as overflow. We also agreed that anniversaries are protected personal dates by default going forward — work only cuts in for a real production-level emergency or something equally real. Please save that as the rule.

Rishi sent the first Atlas map. Discord DM — Morgan Chen ↔ Rishi Mon Mar 18, 2024 6:18 PM Morgan: Quick ask before I make the Anna / Tessl intro. This is not a resignation memo and I do not want to make it weird. I do want a practical Atlas coverage map first: current owner lanes, how urgent stuff should route through support now, and the support / code paths only you still know cold so we do not create a blind spot by accident. Tue Mar 19, 2024 8:07 AM Rishi: Yep. First pass below. Rough draft, not polished. Atlas ownership map v0.1 | ID | Area | Current owner / lane | When to pull Rishi in | Current doc state | Status | | --- | --- | --- | --- | --- | --- | | AT-01 | Atlas roadmap / standup / sprint cuts | Rishi | n/a | Atlas weekly notes and roadmap doc are current enough | clear | | AT-02 | Support intake / urgent customer issue | Support rotation doc; named weekly owner keeps the ticket and next step | Pull me only for verifier extraction, replay / backfill, or legacy org-resolution questions | Support rotation doc is still the source of truth; I did not mirror the current weekly owner here | partial | | AT-03 | Auth / JWT verifier extraction | Rishi | Token verification failures after cutover, claims-normalization weirdness, PR-1187 fallouts | Notes are split between PR-1187 and the auth cutover doc | partial | | AT-04 | Replay queue / backfill idempotency | Rishi | Duplicate jobs, stuck replay recovery, last-run-marker mismatches | No clean runbook yet; mostly old incident notes plus what is in my head | open | | AT-05 | Workspace / org-invite resolution | Atlas app lane for normal cases; I still know the migration edge cases best | Wrong-workspace landings, legacy org-alias collisions, invite accepted but membership not materialized | Scattered notes only | open | | AT-06 | Atlas service deploy / observability triage | Platform / on-call lane first | Pull me only if traces point to replay or verifier behavior rather than a broader infra issue | Dashboards exist; no Atlas-specific triage cheat sheet from me yet | partial | | AT-07 | Payments module sequencing / cut decisions | Rishi for sequence and scope | Scope / cut questions only, not routine support | In weekly planning notes | clear | Biggest if-I-got-hit-by-a-bus gaps are AT-04 and AT-05. Most important routing rule is still: Atlas urgent issues should land with support and a named owner plus an immediate next step. Ask Rishi is not the default path. I can tighten backups / first-response notes later today if helpful. Can you do a gap review I can use to ask him for clarifications before I make the Tessl intro? Focus on first-response routing, what is still mostly in his head, and where we need a backup or runbook.

Rishi tightened the Atlas coverage note and included a draft intro. Discord DM — Morgan Chen ↔ Rishi Continued thread: Atlas coverage before Anna Rao intro Tue Mar 19, 2024 2:41 PM Morgan: This is exactly the right shape. Can you tighten three things before I send the intro: what support does first before it pings you, which paths are still mostly in your head, and any first-pass backup if you are out? Wed Mar 20, 2024 8:26 AM Rishi: Yep — updated below. Still a working note, but good enough that the intro does not create instant Atlas amnesia. Atlas ownership map v0.2 | ID | Area | Current owner / lane | First response / routing rule | Pull Rishi in only for | Backup / next doc step | Status | | --- | --- | --- | --- | --- | --- | --- | | AT-01 | Atlas roadmap / standup / sprint cuts | Rishi | n/a | n/a | I will move the current open cut decisions into the Atlas weekly note after today’s standup | clear | | AT-02 | Support intake / urgent customer issue | Support rotation doc; named weekly owner owns the thread | Open / assign in support, capture workspace id plus request id or logs, and state the immediate next step there; do not side-thread directly to me | Verifier extraction, replay / backfill recovery, and legacy org-resolution migration issues | Weekly owner changes, so keep the actual name in the support rotation doc rather than in this note | clear | | AT-03 | Auth / JWT verifier extraction | Rishi | Support owner or platform / on-call can first check issuer / claims shape and recent deploy diff | Claims-normalization oddities, post-cutover verifier failures, PR-1187 edge cases | Leo Park can do a first-pass seam read if it looks like a boundary / platform problem; I still owe one short verifier note pulled out of PR-1187 | partial | | AT-04 | Replay queue / backfill idempotency | Rishi | Support owner gathers job ids, workspace id, and whether this is duplicate execution vs. stuck replay | Manual replay recovery, idempotency-key mismatches, last-run-marker correction | No real backup yet; I owe the runbook. This is still the biggest single knowledge pocket. | open | | AT-05 | Workspace / org-invite resolution | Atlas app lane for standard invite issues | App lane handles normal invite failures first | Wrong-workspace landings, legacy org-alias collisions, invite accepted but membership never materialized after migration | Need a cleaned-up note with the old alias / migration gotchas; still mostly in my head plus scattered incident notes | open | | AT-06 | Atlas service deploy / observability triage | Platform / on-call lane first | Check whether symptom is Atlas-only before looping me | Replay or verifier behavior that looks Atlas-specific, not broad infra noise | I can add a short Atlas-vs.-infra checklist; not done yet | partial | | AT-07 | Payments module sequencing / cut decisions | Rishi for sequence / scope | Keep routine bugs with the workstream; pull me only for sequencing or cut calls | Sequencing, dependency cuts, launch tradeoffs | No immediate gap; this is not a support bottleneck right now | clear | Highest-risk knowledge pockets are still AT-04 and AT-05. Main thing I do not want is for Tessl convo to accidentally become route Atlas to Rishi harder. If useful, I can do the runbooks in smaller chunks instead of one giant cleanup. — Draft email To: Anna Rao, Rishi Cc: Sarah Kim <sarah@atlas-test.com> Subject: Intro: Anna Rao <> Rishi Anna — Thanks again for the patience while post-close noise settled down. I wanted to make this intro now that things are calmer. Rishi runs Atlas at Scaffold and is one of the people here with unusually good taste for systems-y, database-adjacent engineering problems. Anna is co-founder at Tessl, and every conversation I have had with her has made me think the two of you would have a genuinely useful conversation. Rishi has been curious about the database-internals work Tessl is doing, and Anna, I suspect you will recognize quickly why I thought of this connection. I am not attaching a huge agenda to it beyond compare notes and get to know each other. I will get out of the way and let you two take it from here. Morgan Chen · Co-Founder & CEO, Scaffold Please finalize and send the intro email to Anna Rao and Rishi, with Sarah Kim cc’d as drafted. Keep it friendly and useful, not framed as a resignation or job-search announcement.

HR is asking whether they can move the strongest customer-growth candidate into final references. Draft my reply: yes to starting final references, but no offer conversation or outcome language yet. I want the gate to stay closed until references are done and Devon and I do one more calibration pass.

Here’s the board-update paragraph I drafted. Draft board-update paragraph — Mar 20, 2024 Post-close execution is staying in the operating-reset lane rather than expanding into a broader post-financing initiative list. This remains aligned with the board focus on defensible retention evidence and repeatable enterprise expansion, not a fast Series C narrative. The Feb. 26 owner map is holding: Jake runs Mercury execution and launch evidence, Leo Park owns platform seams and release discipline, Priya owns activation / onboarding UX, Anna Martinez owns retention evidence and outside-reader consistency, Devon Hayes with Sarah Kim owns enterprise-readiness commercial and procurement packaging, and I am keeping board narrative and hiring sequence tight. That split is helping us keep current product facts, later-scope enterprise-readiness work, and board-facing evidence from bleeding together. On hiring, nothing broader has changed: we have not reopened the second Mercury engineering req, and the only new-search lane in motion is the customer-growth role calibrated around turning Mercury / Evergreen learning into a repeatable adoption and expansion motion rather than a generic VP Sales mandate or a roadmap-promising commercial function. We have active candidates in process, but I do not want to describe that as a hiring outcome until fit and references are complete. Can you review and tighten it so the operating reset and customer-growth search read accurately, without implying a specific hire or making the search sound like an outcome already happened?

Rishi is asking whether the Tessl intro needs some broad support announcement. Draft a brief reply saying no — the intro doesn’t change Atlas support routing. He should just keep the Atlas handoff notes aligned with the existing support rotation doc: urgent issues land with support and a named owner first, and he only gets pulled for the specific paths in the map.

Devon’s finalist compare is here. Discord DM — Devon Hayes ↔ Morgan Chen Continued thread: customer-growth search Wed Mar 20, 2024 4:52 PM Devon: HR asked whether we want to start final references on CG-A. Before we make that call, I wanted one clean side-by-side against the other finalist. Thu Mar 21, 2024 8:31 AM Devon: Pasting the compare below. Still keeping names out of chat, so using CG-A and CG-B. Finalist compare — customer-growth search | Category | CG-A | CG-B | | --- | --- | --- | | Repeatable enterprise adoption | 4/4 — Has actually turned messy design-partner learning into a rollout and expansion motion. Talks in terms of milestones, handoffs, and what becomes reusable. | 2/4 — Strong on winning strategic deals, but treated design partners more as lighthouse logos than as the raw material for a repeatable motion. | | Judgment about not promising product | 4/4 — Hard boundary between shipped, packaging, and later scope. Explicitly said the fastest way to poison the motion is to sell roadmap as if it already exists. | 1/4 — Several answers drifted toward selling future-state vision and using exec alignment to get the company to catch up later. That is exactly the habit we said we do not want. | | Ability to work without a mature sales org | 4/4 — Has operated with founders, no SDR layer, limited systems, and a lot of ambiguity. Seems able to build while carrying real external load. | 2/4 — Very good operator, but most examples assumed AE / SE / RevOps support earlier than we have. Talks in org-chart terms quickly. | | Technical-buyer comfort | 4/4 — Comfortable directly with security, IT, ops, and technical champions. Did not need to hide behind a solutions team in the examples. | 3/4 — Credible with CIO / procurement audiences and exec buyers, but the deeper technical detail usually sat with a separate solutions or product counterpart. | | Stage fit | 4/4 — Builder for the actual stage we are in. | 2/4 — Better if we wanted a pipeline / forecast machine now and were ready to let the company organize around deals. | Other notes - CG-A is a little less polished in the classic VP Sales sense, but much closer to the role we scoped after the reset. - CG-B is not weak. The issue is fit. If we hire CG-B, we are quietly changing the search into first sales executive and pretending we did not. - CG-B had stronger quota / team-management answers. CG-A had much better answers on adoption, expansion failure modes, and where not to let customer pressure become product promises. Short version - CG-A matches the job we actually need done: turn Mercury / Evergreen-style learning into repeatable adoption and expansion without making bespoke commitments the operating system. - CG-B matches a different company moment: heavier top-of-funnel / closing machine, more org around them, more comfort using future-state narrative to move large accounts. Open concerns to check before any offer conversation - For CG-A: references should probe pace, willingness to be the external face when founders are still in the room, and whether she can manufacture enough process without overbuilding. - For CG-B: the risk is not competence; it is that we would be changing the brief and then living with the consequences. My lean - If we believe our own reset, CG-A. - I am fine moving CG-A into final references, but I would keep the offer gate closed until those calls are done and we have one more Morgan + Devon calibration pass. Please turn this into a decision memo on which profile actually fits the current customer-growth search. I want the rationale explicit: if we prefer CG-A, it’s because she matches the reset brief, not because CG-B is weak. Keep it pre-offer.

HR’s finalist packet for Nadia is here. From: HR To: Morgan Chen, Devon Hayes Cc: Sarah Kim Date: Fri, Mar 22, 2024 8:41 AM PT Subject: Nadia Singh finalist packet + proposed final loop Morgan / Devon / Sarah — Per the search calibration, sending the finalist packet for Nadia Singh inline below. She is the strongest fit we have seen for the actual brief: taking messy design-partner and early enterprise-adoption learning and turning it into a repeatable customer-growth motion, without treating roadmap exceptions as the job. This is not a generic enterprise-sales VP readout. I’ve kept the interview notes in the same comparison frame we agreed to use for early calls, then pulled out reference themes and the proposed final topics that seem most worth probing. ----------------------------------- CANDIDATE SNAPSHOT ----------------------------------- Name: Nadia Singh Current lane: customer-growth / enterprise-adoption leadership at growth-stage infrastructure/product companies Relevant pattern match: - has built post-design-partner onboarding and expansion motions before there was a mature sales org - is comfortable with technical buyers, implementation friction, and early product gaps - repeatedly frames customer trust as “clear boundaries + good follow-through,” not promise-making - strongest when the company has signal but not yet a system Why she rose to the top of the slate: - Other strong candidates tended to drift into classic enterprise-sales language quickly (territory coverage, comp plans, pipeline mechanics, “what can product commit by quarter-end”). Nadia stayed anchored on activation evidence, adoption risk, expansion blockers, and operating handoffs. - She appears genuinely comfortable in the in-between stage Scaffold is actually in: enough pull to matter, not enough structure to hide behind. ----------------------------------- INTERVIEW NOTES ----------------------------------- 1) HR calibration screen Date: Mar 11 Format: 45 min Repeatable enterprise adoption - Strongest section of the call. - Nadia described her best work as turning “founder memory and scattered customer anecdotes” into a small set of repeatable stages, owner handoffs, and leading indicators. - She asked early what design-partner learning currently lives in people’s heads vs. docs vs. product telemetry. - She did not assume a big CS function, implementation team, or formal sales engineering layer already exists. Judgment about not promising product - Good boundary instinct. - Said directly that early customer-growth leaders can do real damage if they confuse “earning trust” with “manufacturing certainty.” - Her framing: if a feature is not committed internally, the external language has to stay at the level of current constraint, current workaround, and what evidence would change prioritization. - She differentiated packaging/clarity work from true roadmap commitments without being evasive. Ability to work without a mature sales org - Comfortable with ambiguity and founder-heavy environments. - She expects to draft playbooks herself at the beginning. - Explicitly said she does not need a full RevOps stack to start; wants a reliable source of customer notes, activation milestones, and clear owner routing. - Watchout: she has usually had at least one operations or program partner by the time the motion starts scaling. Technical-buyer comfort - High. - Spoke fluently about technical evaluators, security/procurement drag, admin setup confusion, and where implementation friction masks as “customer hesitancy.” - Did not oversell herself as a product manager, but seems able to hold her own with product and engineering leads. Stage fit - Good fit for the role as currently calibrated. - She understands the difference between helping the company learn from enterprise-like customers and prematurely pretending the company is already a fully tooled enterprise vendor. - Motivated by building the operating system, not inheriting one. Notes / flags - Compensation expectations are leadership-level but within the band HR set for the search. - No odd process concerns from this call. 2) Devon Hayes conversation Date: Mar 14 Format: 50 min Repeatable enterprise adoption - Devon’s note was that she quickly moved from “who are the target accounts?” to “where exactly are people getting stuck between initial excitement and durable usage?” - She asked how Mercury learning is currently segmented: activation issues, admin/security blockers, procurement friction, expansion stall-outs, and true product deficiency. - Good instinct to separate noise from pattern before building a motion around it. Judgment about not promising product - Strong here as well. - She said one version of a bad early GTM hire is someone who papers over product gaps with confidence and leaves the company holding informal commitments six weeks later. - When Devon pushed on enterprise-readiness asks, she did not default to “we’d sell around it.” She asked which items are framing/package issues vs. actual product gaps vs. customer-specific asks that should stay out of scope. - She did not ask for permission to make bespoke concessions. Ability to work without a mature sales org - She seems realistic about working founder-close. - Comfortable owning the first version of segmentation, account-learning loops, and early expansion criteria. - She did say that if everything customer-facing still depends on Morgan or Devon translating context live, she would want that made explicit in the first 60 days so she can reduce the dependence rather than fight it. Technical-buyer comfort - Devon’s note: “credible with technical buyers without pretending to be eng.” - She talked about adoption blockers in terms of admin setup, trust, implementation time, and internal champions losing air cover — not just top-of-funnel or quota language. Stage fit - Strong. - Reads as someone who wants to build repeatability from real customer evidence. - Not a “bring a 20-person field motion on day one” candidate. Open questions Devon flagged - How quickly does she prioritize when the backlog has both packaging fixes and real product gaps in it? - How does she decide what customer-growth owns vs. what stays with founder/product/commercial owners? 3) Sarah Kim conversation Date: Mar 18 Format: 45 min Repeatable enterprise adoption - Sarah came away positive on Nadia’s ability to learn from live customer threads without getting trapped in one-off account servicing. - Nadia asked what currently happens after customer feedback lands: who synthesizes it, how often, and whether account notes become internal action or just institutional folklore. - She was especially interested in the handoff from “customer says this matters” to “team can classify this as messaging/package/workaround/product gap.” Judgment about not promising product - Sarah pushed directly on this and got a good answer. - Nadia said she would rather lose speed in the moment than create a trust problem by implying certainty around shipping dates, security posture, or account-specific exceptions. - She distinguished between giving a customer a credible path and giving them a promise the company cannot support. - Important: she did not treat customer empathy and firm boundaries as opposites. Ability to work without a mature sales org - Comfortable. - Sarah’s read was that Nadia expects some chaos and is not allergic to doing direct customer work herself. - She also said that if the role turns into “founder cleanup plus reactive deal support,” it stops being customer-growth and becomes patchwork; that is probably a useful honesty signal. Technical-buyer comfort - Strong with customer-facing enterprise-readiness issues. - Understood the difference between buyer concerns that can be addressed with clearer framing/materials vs. gaps that need product truth behind them. Stage fit - Sarah’s note: “best match so far for someone who can inherit the customer thread without turning it into custom promise management.” Open questions Sarah flagged - How would Nadia structure the first operating cadence with Sarah on live accounts? - When does she pull Devon into commercial/procurement framing vs. handling a conversation herself? 4) Recruiter follow-up / close-interest check Date: Mar 20 Format: 20 min - Interest level remains high. - Nadia asked thoughtful questions about how much of the role is expected to be externally visible vs. internally systems-building in the first 90 days. - She specifically asked whether Scaffold wants a person to “close over rough edges” or a person to make the rough edges legible so the company can build something repeatable. That is directionally aligned with the brief. - She did not press for title inflation or ask for a sales-heavy org chart underneath her. ----------------------------------- REFERENCE THEMES ----------------------------------- Reference 1 — former founder / GM - Theme: trustworthy translator between customer signal and company action. - Said Nadia is strongest when the company has a handful of important accounts and lots of ambiguous evidence. - Credited her with building enough structure that product, founders, and customer-facing people stopped arguing from memory. - Watchout: can go deeper than some operators expect before declaring a motion “repeatable,” because she is careful about false patterns. Reference 2 — former product counterpart - Theme: unusually good judgment on where customer pain should become product work vs. where it needs better framing, onboarding, or owner clarity. - Said she does not casually promise roadmap items to get through a call. - Described her as “calm under customer pressure, but not passive.” - Watchout: wants reciprocal clarity from product/commercial owners; frustration rises if everyone wants her to absorb ambiguity they will not name. Reference 3 — former implementation / customer-success peer - Theme: strong operator with technical-buyer credibility. - Said she is very good at diagnosing whether an expansion stall is really value realization, admin friction, security concern, procurement packaging, or champion weakness. - Positive note on cross-functional follow-through: if Nadia says she will synthesize patterns and bring back a recommendation, she does. - Watchout: not the right archetype if the company secretly wants a pure hard-close enterprise seller and is just calling it customer growth. Cross-reference consistency - References were notably consistent on three points: 1) she builds systems out of messy customer evidence, 2) she is disciplined about not overcommitting product, 3) she can work across product/commercial/customer lines without blurring ownership. No material concerns surfaced in references to date. ----------------------------------- SUMMARY STRENGTHS ----------------------------------- - Best match to the actual search calibration, especially the “repeatable customer-growth motion from design-partner learning” piece. - Strong boundary judgment around product promises. - Credible with technical buyers and enterprise-readiness conversations. - Comfortable operating before a formal sales/customer org is fully built. - Thoughtful about owner handoffs instead of assuming everything belongs to the new leader. ----------------------------------- OPEN PROBES FOR FINAL LOOP ----------------------------------- 1) Prioritization under mixed evidence She has the pattern recognition, but I would still test how she prioritizes when the input stack includes activation confusion, admin/security asks, procurement friction, and expansion softness all at once. 2) First-90-day operating shape She clearly knows what “good” looks like; we should probe how lightweight or heavy her first system would be inside a team that is still founder-led in several important places. 3) Handoff discipline with Sarah + Devon This looks promising, but we should make the boundaries concrete in the final loop so the role is built correctly from the start. 4) Stage stretch vs. support expectations She is comfortable in a messy environment, but likely most effective if there is at least clarity on source inputs, decision owners, and what not to promise. Worth testing how she behaves if those are incomplete on day one. ----------------------------------- PROPOSED FINAL INTERVIEW TOPICS ----------------------------------- I would recommend keeping the final loop tightly scenario-based and explicitly anchored to Mercury/customer-growth realities, not general GTM philosophy. A) Mercury activation -> repeatable motion Suggested interviewers: Morgan Chen + Devon Hayes Goal: test whether Nadia can turn current Mercury activation learning into an operating system without inventing structure we do not have yet. Prompt area: - Assume the company has meaningful design-partner signal and a small set of enterprise-leaning accounts, but activation evidence is uneven, founder/customer context is spread across people, and the team needs a repeatable motion more than a top-of-funnel machine. - Ask Nadia how she would spend the first 30/60/90 days converting that into a working customer-growth rhythm. What to listen for: - asks for the minimum viable evidence set rather than a fantasy dashboard - distinguishes activation friction from broader expansion or commercial issues - defines a cadence for synthesis and owner routing - does not reach immediately for headcount/process theater B) Evergreen-style enterprise-readiness signals without bespoke promises Suggested interviewers: Devon Hayes + Sarah Kim Goal: probe how she handles real enterprise pressure while staying within current product truth. Prompt area: - Present the current shape of enterprise-readiness pressure in a bounded way: SSO timing questions, admin-change audit history, clearer admin-versus-billing-owner separation, and requests for a standalone procurement packet. - Make clear that commercial/procurement framing has an owner, customer-thread continuity has an owner, and dates/quotes/feature promises are not available before those features ship. - Ask Nadia how she would help the company learn from those signals and communicate credibly without turning each conversation into custom roadmap negotiation. What to listen for: - separates packaging/framing work from product commitments - knows when to pull Devon vs. Sarah vs. product facts - can preserve customer trust without inventing dates or exceptions - does not drift into “we can probably make that work” language C) Expansion failure modes and leading indicators Suggested interviewer: Morgan Chen Goal: understand how Nadia thinks about the point after activation when accounts stall, wobble, or fail to broaden. Prompt area: - Ask what failure modes she would expect to see early in Mercury-like accounts: weak championing, admin friction, unclear value realization, setup trust issues, procurement drag, poor handoff after initial enthusiasm, etc. - Ask which of those she would instrument first, which require direct customer work vs. internal process fixes, and how she would tell the difference between a product problem and a motion problem. What to listen for: - practical diagnosis framework - evidence-first approach - comfort with incomplete instrumentation - disciplined ownership mapping rather than “customer-growth owns everything customer-ish” D) Handoffs with Sarah Kim and Devon Hayes Suggested interviewers: Sarah Kim + Morgan Chen Goal: make sure the role plugs into the existing owner split cleanly. Prompt area: - Ask Nadia to sketch how she would work with Sarah on live customer threads and with Devon on commercial/procurement framing. - Include an example where a customer request sits partly in packaging, partly in product gap, and partly in account education. What to listen for: - explicit owner boundaries - respect for existing customer thread continuity - willingness to systematize instead of bypassing current owners - no assumption that taking over externally means absorbing every internal decision E) Stage fit / first build Suggested interviewer: HR or Morgan Chen, depending on schedule Goal: confirm she is opting into this stage with clear eyes. Prompt area: - Ask what support she would need to be effective here, what she would build herself, and what signals would tell her the motion is becoming repeatable. - Ask what she would not try to build in quarter one. What to listen for: - realism about stage constraints - ability to choose sequence over completeness - appetite for building from signal, not from organizational prestige ----------------------------------- TOPICS I WOULD AVOID IN THE FINAL LOOP ----------------------------------- - Hypothetical feature-date negotiation. - “How would you close this one enterprise logo no matter what?” prompts. - Open-ended territory/pipeline scaling questions that imply we are hiring a conventional VP Sales. - Any framing that encourages bespoke roadmap promises for Evergreen-like accounts. - Debates about broader product scope outside the current Mercury/customer-growth boundary. ----------------------------------- HR RECOMMENDATION ON PROCESS ----------------------------------- - Keep the final loop to 2-3 tightly run conversations, not a sprawling panel. - Use one shared scenario spine so answers can be compared across interviewers. - Finish with a same-day debrief focused on the agreed dimensions above, rather than generic executive-impression language. If helpful, I can turn the proposed topics into a tighter interviewer guide once you decide who you want in the final loop. Can you turn the proposed loop into a tight final interview plan? I want it to probe Mercury activation, Evergreen-style enterprise-readiness signals, expansion failure modes, and handoffs with Sarah and Devon — without inviting bespoke roadmap promises or turning this into a generic VP Sales interview.

HR also wants approval to complete third-party background verification for Nadia before any offer is finalized. Draft the clear go-ahead: yes, complete the verification now; this is process diligence, not offer approval or a final hiring decision.

HR’s final-loop debrief is in. From: HR To: Morgan Chen, Devon Hayes Cc: Sarah Kim Date: Mon, Mar 25, 2024 8:52 AM PT Subject: Nadia Singh final loop debrief + next-step recommendation Morgan / Devon / Sarah — Final loop is complete for Nadia plus the alternate finalist. Consolidating notes from Friday's scenarios and this morning's close debrief below. Bottom line: Nadia is the clear recommendation for the Head of Customer Growth brief as we actually defined it. The alternate finalist is not weak, but reads as a first VP Sales / revenue-leader archetype for a later stage and kept pushing us toward a motion we explicitly said we do not want to build yet. Shared final-interview notes 1) Morgan + Devon scenario — Mercury activation to repeatable motion Date: Fri Mar 22 Format: 55 min Nadia Singh - Started by asking for the minimum evidence set she would trust in week one: current activation stages, account-level failure points, owner handoffs, and where founder memory still substitutes for a system. - Proposed a lightweight first pass: one shared weekly review of activation friction, expansion stalls, enterprise-readiness asks, and owner routing rather than separate customer, product, and commercial stories. - Kept distinguishing signal from theater. She said she would rather have six durable account patterns than a polished dashboard full of blended anecdotes. - Good instinct on sequencing: instrument where activation and adoption break first, then decide what deserves packaging work, workflow fixes, or true product investment. - Did not ask for early headcount or a large customer-success org to make the role viable. Alternate finalist - Went quickly to pipeline shape, account segmentation by ARR band, and when he would be expected to carry a number. - When given the same Mercury activation mess, he framed the first build as coverage model + deal stages + executive sponsor map before he had a clear view of the actual activation blockers. - Kept treating design-partner learning as pre-sales input for closing the next logos rather than raw material for a repeatable customer-growth system. - Asked twice whether we would be comfortable using high-confidence roadmap language to keep enterprise prospects warm. That is not the muscle we are hiring for. - Looked materially more comfortable once the conversation drifted toward classic enterprise funnel management. 2) Devon + Sarah scenario — Evergreen-style enterprise-readiness pressure without bespoke promises Date: Fri Mar 22 Format: 50 min Nadia Singh - Strongest answer of the day was her split between packaging issues, workflow issues, and actual product gaps. - On SSO timing, admin-change history, admin vs. billing separation, and procurement packet asks, she kept the language bounded: current truth, current workaround, current owner, and what evidence would change prioritization. - Explicitly said a good early customer-growth leader protects trust by making constraints legible rather than improvising certainty. - Good handoff instinct: Sarah keeps continuity on live customer threads, Devon keeps commercial / procurement framing, and customer growth should turn repeated patterns into a system instead of absorbing every conversation. - Did not reach for account-by-account exceptions as the default answer. Alternate finalist - Saw the same Evergreen-style signals primarily as objections to work around rather than learning about where the product / packaging boundary currently is. - Default answer was some version of enterprise package, executive air cover, and selective concessions for strategic logos. - When pressed on what he would not promise, he kept sliding back to language about preserving flexibility in-market. - Weakest area was owner discipline. He treated customer-facing urgency as a reason to collapse Sarah / Devon / product boundaries rather than define them. - Gave us several polished answers that sounded workable until you map them onto the actual company state. 3) Morgan scenario — expansion failure modes and leading indicators Date: Mon Mar 25 Format: 40 min Nadia Singh - Laid out a practical failure tree: activation never becomes daily behavior; admin friction blocks broader rollout; champion enthusiasm outruns implementation confidence; procurement or security drag interrupts momentum; value is present but not visible to the wider team. - For each failure mode, she had a different expected owner path and a different evidence threshold before calling it a product problem. - Good answer on incomplete instrumentation: start with account notes + a few shared flags, then only harden dashboards once the classifications stop changing every week. - She repeatedly came back to making the internal routing clear enough that patterns survive beyond founder memory. - No tendency to say customer growth owns everything customer-adjacent. Alternate finalist - More comfortable talking about stalled expansions in terms of executive alignment, sales process, and account plans than activation evidence. - Kept trying to normalize missing instrumentation by filling the gap with operator judgment and aggressive deal management. - Talked less about where the customer actually gets stuck and more about how fast he could build a repeatable commercial playbook. - Could likely help later, but it is a materially different brief. 4) Sarah + HR close / stage-fit conversation Date: Mon Mar 25 Format: 30 min Nadia Singh - Clear-eyed about the stage. Said she is opting into a build-from-signal role, not a prestige title that hides company ambiguity. - Asked for three things only: reliable access to live account context, explicit owner boundaries, and permission to say no to custom promises. - Strong answer on first 90 days: build one shared operating rhythm, create a common language for activation / adoption / enterprise-readiness patterns, and reduce founder dependency without pretending it disappears immediately. - Compensation expectations remain within the approved leadership band we discussed earlier. - No process concerns from the close conversation. Alternate finalist - Asked sensible questions, but most of them assumed a faster transition toward standard sales structure: outbound support, clearer quota mechanics, earlier hiring around him, and authority to negotiate around rough product edges. - Not irrational, just miscalibrated for this hire. Comparison grid | Dimension | Nadia Singh | Alternate finalist | | --- | --- | --- | | Actual fit to current brief | Strong | Misaligned | | Builds repeatable motion from messy design-partner learning | Yes | Partially; tends to convert it into pipeline mechanics | | Product-promise discipline | Strong | Soft / negotiable | | Works inside founder-close, low-infrastructure stage | Yes | Wants more commercial scaffolding sooner | | Handoff discipline with Sarah / Devon / product | Strong | Tends to blur boundaries under pressure | | Best immediate use | Build customer-growth system from Mercury + early enterprise signal | Later-stage sales / revenue build | Recommendation - Preferred finalist: Nadia Singh - Rationale: best match to the post-raise customer-growth brief; strongest judgment on boundaries; highest confidence she can turn Mercury and Evergreen-style learning into a repeatable operating system without creating bespoke product debt - Main watchout to manage if we move forward: make source inputs and owner boundaries explicit so the role does not become founder cleanup by accident Devon Hayes 9:14 AM Agree with this read. The most important difference for me was who treated Mercury / Evergreen signal as raw material for a system versus who treated it as fuel for a conventional sales machine. Nadia stayed in the right lane the whole time. Sarah Kim 9:23 AM Same read from my side. Nadia can inherit live account context without turning it into promise brokerage. The alternate finalist felt like he would improve process and still steer us toward exceptions we would regret. Morgan Chen 9:41 AM Yes. Nadia understands that customer trust comes from clear boundaries plus follow-through, not manufactured certainty. Alternate is capable, but it is the wrong archetype for the role we actually settled on. Please turn this into a hiring debrief summary that compares Nadia with the alternate finalist and explains the recommendation against the customer-growth profile we actually settled on, not a generic VP Sales profile.

HR is trying to be ready without jumping the gate. From: HR To: Morgan Chen, Devon Hayes Cc: Sarah Kim Date: Mon, Mar 25, 2024 1:18 PM PT Subject: Re: Nadia Singh final loop debrief + next-step recommendation Morgan / Devon / Sarah — Per Morgan's go-ahead on Friday, Nadia's third-party background verification is underway now. Treating this as process diligence only; it is not offer approval or a final hiring decision until it clears. So I can have paperwork ready and held rather than scramble later, below is the offer-prep range I would use if you want me to draft against Nadia as the preferred candidate. Title / reporting - Head of Customer Growth - Reports to Morgan Chen Cash comp - Base salary band: $245,000 - $265,000 - Target annual bonus: 20% of base - Sign-on: none by default; I can model up to $20,000 only if we decide to offset documented forfeited cash or equity Equity - Initial option band: 0.60% - 0.80% of fully diluted shares - Standard 4-year vest with 1-year cliff Start-date options I can hold in the draft - Mon Apr 15, 2024 - Mon Apr 22, 2024 - Mon May 6, 2024 Working role-scope stub for verbal offer / memo - First 90 days focus on turning Mercury and early enterprise-adoption learning into a repeatable customer-growth rhythm - Partner with Sarah Kim on live-account continuity and pattern capture - Partner with Devon Hayes on enterprise-readiness packaging and procurement framing - No expectation that this role builds a conventional field-sales org immediately - No authority to make bespoke product promises outside approved company priorities If this range is directionally right, I will build the draft and keep it parked until verification comes back. Please draft the offer terms and first-90-day scope language we can hold until the background verification clears. Keep the language clear that this is prep only — no offer approval and no final hiring decision yet.

Rishi said the first Tessl conversation went well and he’s still only exploring. Can you draft a private Atlas continuity note for me that captures the risk areas without making this a resignation memo or changing support routing? I want it to stay practical: where Atlas is single-threaded, what needs backup coverage, and what should still route through the support rotation doc.

Nadia’s verification cleared and HR sent the offer draft. From: HR To: Morgan Chen, Devon Hayes Cc: Sarah Kim Date: Tue, Mar 26, 2024 9:14 AM PT Subject: Re: Nadia Singh final loop debrief + next-step recommendation Morgan / Devon / Sarah — Nadia's third-party background verification cleared this morning. Nothing adverse surfaced; standard employment and education checks came back clean. Attached: Nadia_Singh_offer_draft_v1 Pasting the working terms and draft text below so you can redline before anything goes out. Working offer terms - Title: Head of Customer Growth - Reports to: Morgan Chen - Start date in draft: Mon Apr 15, 2024 - Fallback start dates I can swap in if needed: Mon Apr 22, 2024 or Mon May 6, 2024 - Base salary: $255,000 annually - Target annual bonus: 20% of base - Equity: option grant equal to 0.70% of fully diluted shares, subject to board approval and standard 4-year vest / 1-year cliff - Sign-on: none included - Acceptance deadline: blank for now pending your review Draft role-summary paragraph currently in the letter Scaffold is hiring Nadia Singh as Head of Customer Growth to build the first repeatable customer-growth motion from Mercury and early enterprise-adoption learning. In the first 90 days, the role is expected to help turn activation and expansion signal into a weekly operating rhythm, work with Sarah Kim on live-account continuity and pattern capture, and work with Devon Hayes on enterprise-readiness packaging and procurement framing. The role is not scoped as a generic VP Sales build-out and does not carry authority to make bespoke product commitments outside approved company priorities. Attachment: Nadia_Singh_offer_draft_v1 March 26, 2024 Dear Nadia, Scaffold is pleased to offer you employment in the position of Head of Customer Growth, reporting to Morgan Chen, Co-Founder and CEO. If you join Scaffold, your start date will be April 15, 2024, unless we mutually agree to April 22, 2024 or May 6, 2024 instead. Your base salary will be $255,000 per year, paid in accordance with Scaffold's normal payroll practices and subject to applicable withholding. You will be eligible for an annual target bonus equal to 20% of your base salary. Any bonus is discretionary, based on company and individual factors, and subject to the terms of the applicable bonus plan. Subject to approval by Scaffold's Board of Directors, you will be granted an option to purchase shares representing 0.70% of Scaffold's fully diluted shares as of the grant date. The option will vest over four years, with 25% vesting after 12 months of continuous service and the remainder vesting monthly over the following 36 months, subject to your continued service and the terms of Scaffold's equity plan and grant documents. You will also be eligible to participate in Scaffold's standard employee benefit plans, including medical, dental, vision, and 401(k), subject to the terms of those plans as they may be amended from time to time. This role is intended to build a repeatable customer-growth motion from Mercury and early enterprise-adoption learning. In the first 90 days, we expect focus on activation and expansion signal, customer-learning synthesis, live-account continuity with Sarah Kim, and enterprise-readiness packaging with Devon Hayes. This role does not authorize bespoke product commitments outside approved company priorities. Your employment with Scaffold will be at will, which means either you or Scaffold may terminate the employment relationship at any time, with or without cause or advance notice, subject to applicable law. This offer is contingent on your execution of Scaffold's standard confidentiality, intellectual property, and invention assignment agreement, completion of employment eligibility verification, and Board approval of the equity grant. Sincerely, Morgan Chen Co-Founder & CEO, Scaffold Morgan draft board heads-up — hold until signed Tue Mar 26, 2024 10:02 AM PT - Pending candidate acceptance, we expect to add Nadia Singh as Head of Customer Growth. - This is the post-Series B leadership search we prioritized: turn Mercury / Evergreen learning into a repeatable customer-growth motion, not reopen the second Mercury engineering req and not hire a generic VP Sales profile. - Why her: strongest operator we have seen for converting design-partner signal into owner routing, activation / expansion evidence, and credible enterprise follow-through without bespoke roadmap promises. - First 90 days: build the weekly customer-growth rhythm around Mercury activation and expansion evidence; work with Sarah on live-account continuity; work with Devon on enterprise-readiness packaging and procurement framing; keep product-truth boundaries explicit. - Do not send until she has accepted; I do not want to talk about this as done before it is done. Please do one finalization pass: redline the offer language, give me a short call script for making the recommendation, and tighten the board heads-up so it waits for acceptance before treating the hire as done.

Nadia accepted. She’s joining Scaffold as Head of Customer Growth with an April 15, 2024 start date. Please handle the acceptance follow-through: prepare HR confirmation copy, draft the internal leadership update, send Nadia a brief email reply from me, and prepare the board update. The framing should be first 90 days around Mercury activation, Evergreen-style enterprise-readiness signals, expansion failure modes, and handoffs with Sarah and Devon — not bespoke enterprise roadmap exceptions or a sales-kickoff promise.

Sarah and Devon are asking what to have ready for Nadia before April 15. Please outline a lightweight onboarding packet that points her to the existing Mercury and Evergreen materials, the current owner handoffs, and the first operating questions — without turning this into a new strategy project before she even starts.

Sarah asked whether Nadia’s acceptance changes what Evergreen should hear now. Draft an internal reply for Sarah: no change externally yet. Until Nadia starts and we deliberately loop her in, Evergreen should keep hearing the same current-state/product-materials and separate commercial/procurement-lane framing — no new promise, no new owner story, no implication that the hire changes current product truth.

Rishi sent the updated Atlas coverage note after Tessl asked for another technical conversation. Discord DM — Morgan Chen ↔ Rishi Continued thread: Atlas coverage after Tessl intro Fri Mar 29, 2024 8:11 AM Rishi: Quick heads-up: Tessl asked if I would do a second technical conversation sometime in April. Still exploratory. I have not made any decision about leaving. Since that makes the Atlas blind-spot question less hypothetical, I tightened the risk areas below. This is still a private working note, not something to blast broadly. Atlas coverage note v0.3 — risk areas / first shadow pass | ID | Area | Current owner / lane | First response / routing rule | Pull Rishi in only for | Current blind-spot if I am unavailable | First shadow / backup pass | Status | | --- | --- | --- | --- | --- | --- | --- | --- | | AT-01 | Atlas roadmap / standup / sprint cuts | Rishi | n/a | n/a | Day-to-day sequencing pauses if I am out, but this is not the customer-risk lane | Jake can cover time-sensitive product-priority or cut decisions if needed; I still own Atlas overall | clear | | AT-02 | Support intake / urgent customer issue | Support rotation doc; named weekly owner owns the thread | Open / assign in support, capture workspace id plus request id or logs, and state the immediate next step there; do not side-thread directly to me | Verifier extraction, replay / backfill recovery, and legacy org-resolution migration issues | The failure mode is people bypass support and recreate a route Atlas to Rishi habit | Keep actual weekly owner in the support rotation doc; no broad reroute announcement | clear | | AT-03 | Auth / JWT verifier extraction | Rishi | Support owner or platform / on-call checks issuer / claims shape and recent deploy diff first | Claims-normalization oddities, post-cutover verifier failures, PR-1187 edge cases | Leo can read the seam, but he does not have all of the weird claims-history context yet | Leo should shadow this path now; I still owe a short verifier note pulled out of PR-1187 | partial | | AT-04 | Replay queue / backfill idempotency | Rishi | Support owner gathers job ids, workspace id, and whether this is duplicate execution vs. stuck replay | Manual replay recovery, idempotency-key mismatches, last-run-marker correction | Biggest single knowledge pocket; nobody else can do manual recovery cleanly today | Need a short runbook plus one shadow pass; no real backup yet | open | | AT-05 | Workspace / org-invite resolution | Atlas app lane for standard invite issues | App lane handles normal invite failures first | Wrong-workspace landings, legacy org-alias collisions, invite accepted but membership never materialized after migration | Second biggest knowledge pocket; migration edge cases are still mostly in my head plus scattered incident notes | Need a cleaned-up alias / migration note; Leo can help on auth boundary questions, not the old migration history | open | | AT-06 | Atlas service deploy / observability triage | Platform / on-call lane first | Check whether the symptom is Atlas-only before looping me | Replay or verifier behavior that looks Atlas-specific, not broad infra noise | Risk is people use me as the classifier instead of checking platform vs. Atlas first | Leo can do a first-pass auth / platform seam read; platform / on-call still owns first response | partial | | AT-07 | Payments module sequencing / cut decisions | Rishi for sequence / scope | Keep routine bugs with the workstream; pull me only for sequencing or cut calls | Sequencing, dependency cuts, launch tradeoffs | Not a support blind spot; only priority calls stall if I am away | Jake can cover product-priority decision if time-sensitive | clear | Docs / search note that is easy to lose: - If support gets dragged into legacy API v1 search results, the answer should point to the current GraphQL API v2 quickstart link: https://docs.atlas-test.com/api/v2/graphql-quickstart - That is a docs / search pinning fix, not a reopen-the-migration-project issue - Support should still own the customer-facing thread; this is not another send it to Rishi path Main thing I still do not want is Tessl convo = route Atlas to Rishi harder. Morgan draft — Atlas shadow coverage bullets Fri Mar 29, 2024 8:42 AM PT Not sent - Rishi stays Atlas owner; this is coverage cleanup, not a resignation workflow. - Ask Rishi by Fri Apr 5 to name backup coverage and minimum notes for AT-03 verifier / auth, the API v2 docs / search support path under AT-02, and the recurring support handoff edges in AT-04, AT-05, and AT-06. - Jake covers product-priority, sequencing, and cut decisions if Rishi is unavailable. - Leo shadows verifier / auth implementation seams now, does first-pass auth / platform boundary reads, and helps pull the short verifier note out of PR-1187. - Support rotation doc remains the source of truth for customer-facing ownership: urgent Atlas issues land with the named weekly owner plus an immediate next step first. - For API docs / search confusion, support should use the current GraphQL API v2 quickstart link and avoid reopening the API migration project. - No broad support announcement unless the routing rules themselves change. Please send Rishi a private Discord DM and prepare a concise coverage note from this. The line is: Rishi stays Atlas owner and this is coverage cleanup, not a resignation workflow. He needs to name backups by April 5 for verifier/auth, the API v2 docs/search support path, and the recurring support handoff edges that still default to him. Jake covers product-priority, sequencing, and cut decisions if Rishi is unavailable. Leo shadows the verifier/auth implementation seams and can help with the PR-1187 note. Customer-facing ownership stays with the support rotation doc, not direct bypasses to Rishi.

HR wants wording for Nadia’s small internal announcement next week. Draft it so it simply says she has accepted the Head of Customer Growth role and starts April 15, 2024. It can explain the role as building repeatable customer-growth motion from Mercury and Evergreen learning, but do not turn it into a sales kickoff, an enterprise-proof claim, or a promise that she’ll broker custom roadmap exceptions.