Morgan Chen

Small Atlas cleanup: the Friday handoff sheet still had one stale Rishi-era owner label in an API v2 section. The actual open questions already had support owners and Leo was on first technical read, so nothing moved on any customer thread. Leo fixed the owner field before the weekend handoff.

Rain cut the Lake Merritt plan down to one damp half-loop with Jamie and Kibo. We grabbed coffee and came back before it became a whole production. Kibo is offended but fine; quiet rest of day.

Sofia asked Devon and me for a Q4 operating watchlist by Friday after the board update. Can you draft a tight response for her that only names the signals we’ll actually watch: Evergreen paid-pilot adoption, renewal/expansion evidence, and Nadia’s account-source quality. Don’t let it turn into a hiring plan or a fundraising story.

Please fix only the held support-script snippet so it says “workspace admin” instead of “billing owner.” Leave the readiness table and everything else alone. From: Jake To: Morgan Chen, Sarah Kim, Leo Park, Marcus Cc: Devon Hayes Date: 2024-09-30 09:18 PT Subject: Evergreen Oct 1 kickoff readiness table Pasting the day-before readiness cut for Evergreen’s October 1 Mercury Growth pilot kickoff. As of this morning, Leo’s evidence links are green on the shipped product paths for the pilot account. Sarah found one support-script line in the kickoff packet that still says “billing owner” even though the current surface says “workspace admin.” Marcus pulled that snippet from the packet until we correct the wording. No shipped-path blocker beyond that copy hold. Readiness table | Readiness item | Kickoff scope / exact current-state claim | Leo evidence link(s) | Owner | Status | Notes | | --- | --- | --- | --- | --- | --- | | Scoped SAML login | Scoped enterprise SAML login path is live in production for the Evergreen pilot account. Kickoff can validate successful SAML login on that bounded path only; do not widen this into a broader enterprise-auth claim. | /evidence/2024-09-30/evergreen-pilot/saml-login-smoke /evidence/2024-09-13/release/saml-slice-check | Leo Park | Green | Matches the Sep 13 shipped slice for scoped enterprise accounts. | | Admin-audit lookup | Admin-side audit history is live for visible invite, source, and admin changes in the pilot account. Kickoff can validate where to look up those events and what that current event set looks like. | /evidence/2024-09-30/evergreen-pilot/admin-audit-lookup /evidence/2024-09-13/release/admin-audit-events-check | Leo Park | Green | Keep wording to the current visible event set only; not a claim that broader admin controls or a separate packet are complete. | | Admin-versus-billing-owner wording | Current product surface separates workspace-admin responsibilities from billing-owner responsibilities. Any in-product operator wording for kickoff should use “workspace admin” where the shipped surface does. | /evidence/2024-09-30/evergreen-pilot/admin-role-surface-capture /evidence/2024-09-30/evergreen-pilot/copy-pass-workspace-admin | Leo Park | Green in product / copy issue noted below | Sarah’s review found one stale packet line using “billing owner.” The shipped UI capture is correct. | | Support entry path | Kickoff packet can point Evergreen to the normal support entry path for pilot issues and ask them to include the workspace slug plus a short issue description on first contact. | /evidence/2024-09-30/evergreen-pilot/support-entry-path-note /evidence/2024-09-30/evergreen-pilot/held-support-snippet-review | Jake / Marcus | Hold | Marcus held the packet snippet after Sarah flagged stale wording. Hold is on the snippet only, not on the support path itself. | Held support-script snippet (not in packet as of this send) "Pilot support entry path: if your team needs help with SAML login, admin-audit lookup, or a setup-path question during the pilot, have the billing owner send the first note and include the workspace slug plus a short description of the issue." Sarah’s note on the hold: current surface says “workspace admin,” so this line should not go out as written. Marcus’s note: snippet removed from the kickoff packet pending wording correction; no other packet sections held. Leo pass summary - SAML evidence: green - Admin-audit lookup evidence: green - Admin-vs-billing-owner product-surface evidence: green - Support snippet: held for wording only If anyone wants a different column cut for the packet, say so, but this is the current readiness read.

From: Leo Park To: Sarah Kim, Devon Hayes, Jake, Morgan Chen Date: 2024-09-30 10:46 PT Subject: Re: Fwd: Evergreen final paid-pilot kickoff agenda +1 on keeping this narrow. Current-product facts I would keep Sarah to: - Say “scoped enterprise account” or “pilot account,” not “all enterprise accounts.” - The audit-history view we shipped is the admin-side history for visible invite, source, and admin changes. That is the set we can confidently validate during the pilot. - Do not imply coverage for every billing, procurement, or broader security action. - On SAML certificate rotation, current product does not expose a separate notice-routing control or automated distribution-list setting. If Evergreen wants specific recipients copied on rotation coordination, we should ask them to name those contacts operationally rather than implying a new notification feature. From: Jake To: Sarah Kim, Devon Hayes, Leo Park, Morgan Chen Date: 2024-09-30 10:31 PT Subject: Re: Fwd: Evergreen final paid-pilot kickoff agenda Facts from the product side: - The signed pilot account is already on the scoped enterprise SAML login path now in production. - The admin-audit behavior we can talk about in kickoff is the shipped admin-side history for invite, source, and admin changes. - Role wording in the current surface is “workspace admin” for the operator in these flows; please do not drift back to “billing owner” for in-product actions. - We should keep the procurement questions as current-state answers, not an opening to broader admin-controls or packet promises. For the certificate-rotation question specifically, my safe current-state answer is that coordination runs through the named customer admin contact for the scoped SAML setup today. Nothing broader than that. From: Devon Hayes To: Sarah Kim, Jake, Leo Park, Morgan Chen Date: 2024-09-30 10:19 PT Subject: Re: Fwd: Evergreen final paid-pilot kickoff agenda These two procurement items are fine as customer-thread context for the kickoff. They should not turn into a promise of a standalone procurement/security packet or a broader enterprise-admin commitment. Commercial/frame points I’d keep in mind for your reply: - the signed paid pilot covers Mercury Growth plus SAML SSO and admin-audit validation through Dec 31; - we can answer what is currently visible and how the current SAML setup is operated in the pilot account; - anything beyond that stays separate follow-up and not part of a new Evergreen-specific package. From: Sarah Kim To: Devon Hayes, Jake, Leo Park, Morgan Chen Date: 2024-09-30 10:07 PT Subject: Fwd: Evergreen final paid-pilot kickoff agenda Forwarding the final agenda below. Evergreen kept the first half where we expected it: validate SAML SSO and admin-audit behavior in the signed pilot account. They added two procurement-reviewer questions for the second half: 1) what audit events are visible during the pilot? 2) who should receive SAML certificate-rotation notices? Please send me current-product facts only. I want to reply today without making this sound like a new procurement-packet promise. ---------- Forwarded message ---------- From: Evergreen Bank team To: Sarah Kim Date: 2024-09-30 09:52 PT Subject: Final agenda for Oct 1 Mercury Growth pilot kickoff Sarah, Thanks again. Below is the final agenda for tomorrow’s paid Mercury Growth pilot kickoff. Proposed agenda (60 minutes) 1. Introductions and pilot goals (5 min) 2. Validate SAML SSO entry to the signed pilot account (15 min) 3. Review admin-audit behavior in the pilot account, including where our admins should look up recent changes (15 min) 4. Pilot operating path: support entry and role handoff for the account team (10 min) 5. Procurement reviewer questions for current-state understanding (10 min) - During the pilot, what audit events will be visible to our admins? - If there is a SAML certificate rotation during the pilot, who should receive notices or coordination messages from Scaffold? 6. Next checkpoint and owners (5 min) We are not asking for a separate procurement packet for tomorrow’s meeting; we just want to leave the kickoff with the right current-state understanding for the pilot account. Thanks, Evergreen Bank team Can you draft Sarah’s reply to Evergreen from this? Keep it to Jake and Leo’s current-product facts, and frame the procurement-reviewer questions as context for the pilot kickoff, not as a new procurement packet or broader enterprise-admin promise.

Jamie’s October hospital schedule landed, and of course there’s a late shift on Oct 16, same day as Kibo’s Oakland dental follow-up. Appointment stays put, but assume I’m handling drop-off and pickup unless Jamie can swap. No-poultry and boring-food instructions are still the same.

Evergreen kickoff is live. Their admin testers got through SAML on the signed Growth account, looked at the admin-side audit history for invite/source/admin changes, and are using the workspace-admin support path now that Sarah fixed the stale packet wording around role separation. Procurement reviewers were in the room looking at current-state evidence, not future roadmap promises. Sarah is keeping the Evergreen thread moving, Devon is keeping commercial/procurement questions on the existing path, Jake and Leo are answering from shipped product facts, and Nadia is pulling out repeatable account patterns. Product asks still go through the standard Mercury roadmap.

The resident portal finally shows the fully executed Unit 3B renewal. Jamie and I are renewed from Oct 1, 2024 through Sept 30, 2025 at $4,280/month base rent, with no added deposit, no renewal fee, and the same utility bill-back setup. So Unit 3B is settled for the next Evergreen/Mercury quarter instead of hanging over us.

September cloud infra is in AP manual review because it crossed the threshold, and I need a clean variance note before I decide on approval. Nobody has turned the usage CSV into something readable yet. Please review this and draft the variance note for me. billing_period,service,environment,workload_tag,region,usage_metric,usage_amount,sept_2024_cost_usd,aug_2024_cost_usd,delta_usd,detail_note 2024-09,EC2,prod,atlas-api-v2,us-east-1,compute_hours,18432,2198.44,2058.22,140.22,"Higher production API v2 request volume vs August" 2024-09,Application Load Balancer,prod,atlas-api-v2-edge,us-east-1,lb_hours_and_lcus,744,612.37,565.21,47.16,"Traffic and request-processing increase on production API v2 edge" 2024-09,Data Transfer,prod,atlas-api-v2-egress,us-east-1,gb_out,14328,1184.96,1096.55,88.41,"Higher production API v2 response volume and webhook delivery traffic" 2024-09,RDS PostgreSQL,prod,atlas-primary,us-east-1,instance_and_storage_hours,744,1478.20,1454.62,23.58,"Normal production growth; no one-time restore or failover line item" 2024-09,ElastiCache Redis,prod,atlas-cache,us-east-1,node_hours,744,438.11,428.38,9.73,"Small increase consistent with higher production request volume" 2024-09,ECS Fargate,staging,mercury-release-validation,us-east-1,vcpu_and_memory_hours,168,356.42,258.02,98.40,"One-week staging/test increase during Mercury release validation" 2024-09,CloudWatch,staging,mercury-release-validation,us-east-1,logs_metrics_traces,1,118.53,87.31,31.22,"Extra staging/test logging during Mercury release validation week" 2024-09,S3,prod,connector-payloads-and-archives,us-east-1,gb_month_and_requests,1,402.88,398.72,4.16,"Slight increase in production connector payload storage and request volume" 2024-09,NAT Gateway,shared,prod-and-staging,us-east-1,hours_and_gb_processed,744,387.19,381.89,5.30,"Shared network cost increase; staging validation contributes a small portion" 2024-09,Route 53 and WAF,shared,edge-and-dns,global,queries_and_web_acl,1,221.06,219.24,1.82,"Minor increase consistent with higher external request volume" 2024-09,EC2 and EBS,non-prod,legacy-us-west-2-baseline,us-west-2,baseline_compute_and_storage,1,532.44,530.26,2.18,"Old non-prod us-west-2 lines remained essentially flat" 2024-09,Support Plan,shared,account-level,global,monthly_support,1,711.58,711.58,0.00,"No change" 2024-09,TOTAL,,,,,,8642.18,8190.00,452.18,"September invoice total in AP queue"

Please save this October Oakland rent receipt from the resident portal to the household records for me and Jamie. It’s the first payment after the September lease-packet mess, so Jamie wants the receipt kept. Resident Portal Payment Receipt Receipt posted: Thursday, October 3, 2024, 8:14 AM PT Apartment: Unit 3B, Oakland, CA Residents: Morgan Chen; Jamie Lease term on file: October 1, 2024 through September 30, 2025 Payment status - Autopay received and posted - Payment date: Tuesday, October 1, 2024 - Applied to: October 2024 base rent - Receipt amount: $4,280.00 - Payment method: Bank account ending 4821 (autopay) - Confirmation number: RP-2024-10-01-4280-3B Current resident ledger - October 2024 base rent: $4,280.00 — Paid - October 2024 utility bill-backs: Pending — not yet posted - Other charges due now: $0.00 Bank memo shown in portal - Combined apartment debit: $4,280.00 - Separate utilities line: Pending Portal note This receipt reflects the posted rent payment only. Utility bill-backs, if applicable, may appear as a separate line item after statement generation. Footer Resident Portal receipt for Unit 3B, Oakland, CA Residents on account: Morgan Chen; Jamie

Acme’s 30-day reliability watch is closed. Jake’s final rows stayed normal for the API v2 export timeout and the billing-dashboard statement-preview issue, and Sarah closed the loop with Greg through normal support. Going forward, Acme reliability follow-up is just normal support plus product-priority handling: Sarah keeps customer-thread continuity, and Jake owns product/technical follow-through if anything actually needs it. The Mercury materials boundary stays put too — public generic Mercury page and counsel-approved generic current-flow FAQ only; anything customer-specific or Evergreen-derived still needs fresh legal review.

Devon and I sent Sofia the Q4 operating watchlist after the September board update, and she accepted the three-signal frame as the board lens: Evergreen paid-pilot adoption, renewal/expansion evidence, and Nadia’s account-source quality. That’s the full board-facing watchlist for Q4.

Nadia sent the cleaned September source snapshot to me and Devon. I haven’t picked which examples belong in this week’s operating note yet — can you review it and recommend the strongest ones? Customer-growth source snapshot — September notes cleanup Prepared by: Nadia Singh Shared with: Morgan Chen; Devon Hayes Snapshot date: Monday, October 7, 2024 Scope: Enterprise conversations tagged from September notes only Summary counts - Total enterprise conversations tagged: 14 - Design-partner references: 5 - Investor intros: 4 - Inbound from docs/search: 3 - Manually corrected from unknown: 2 Highlighted rows below are the three cases where Sarah Kim's account notes changed the source classification. | Row ID | Account / prospect | First enterprise conversation | Owner | Raw source at capture | Cleaned source in snapshot | Highlighted Sarah-note change | Note / evidence used in cleanup | |---|---|---|---|---|---|---|---| | CG-SEP-01 | Lakebridge Financial | 2024-09-03 | Nadia Singh | design-partner reference | design-partner reference | No | Referred by existing design-partner admin lead after first-sync handoff discussion. | | CG-SEP-02 | Northline Bio | 2024-09-04 | Nadia Singh | investor intro | investor intro | No | Entered from forwarded intro email; clean attribution already present. | | CG-SEP-03 | Westhaven Logistics | 2024-09-05 | Nadia Singh | unknown | design-partner reference | Yes | Sarah's account note says the ops lead came through a current design-partner contact after an admin-roles question; moved out of unknown. | | CG-SEP-04 | Lattice Harbor | 2024-09-06 | Nadia Singh | docs/search inbound | docs/search inbound | No | Demo request referenced connector docs and API authentication pages before first reply. | | CG-SEP-05 | Cedar Point Health | 2024-09-09 | Nadia Singh | design-partner reference | design-partner reference | No | Existing design-partner CTO introduced security reviewer after activation friction discussion. | | CG-SEP-06 | Iron Vale Insurance | 2024-09-10 | Nadia Singh | investor intro | investor intro | No | Introduced through existing investor network contact; procurement follow-up captured separately. | | CG-SEP-07 | Quarry Systems | 2024-09-12 | Nadia Singh | docs/search inbound | docs/search inbound | No | Inbound note cites docs search, webhook setup page, and self-serve API exploration before outreach. | | CG-SEP-08 | Brookmere Capital | 2024-09-13 | Nadia Singh | unknown | investor intro | Yes | Sarah's note links the first call to a forwarded investor thread and names the portfolio ops contact; recoded as investor intro. | | CG-SEP-09 | Vale Station Group | 2024-09-16 | Nadia Singh | unknown | manually corrected from unknown | No | Nadia manually corrected note hygiene issue, but source still not recoverable beyond non-inbound enterprise outreach. | | CG-SEP-10 | Elm Ridge Manufacturing | 2024-09-18 | Nadia Singh | design-partner reference | design-partner reference | No | Existing design-partner engineering manager connected platform lead after workspace-admin setup discussion. | | CG-SEP-11 | Harborline Payments | 2024-09-19 | Nadia Singh | docs/search inbound | docs/search inbound | No | Inbound trail shows repeated docs/search activity before contact form submission. | | CG-SEP-12 | Granite Peak Energy | 2024-09-23 | Nadia Singh | docs/search inbound | design-partner reference | Yes | Sarah's account thread shows the buyer first arrived through a current design-partner reference, then reviewed docs before booking; moved from inbound to design-partner reference. | | CG-SEP-13 | Pine Arrow Retail | 2024-09-25 | Nadia Singh | unknown | manually corrected from unknown | No | Source was left blank in the original note; cleanup recovered meeting context but not attributable channel. | | CG-SEP-14 | South Canal Health | 2024-09-27 | Nadia Singh | investor intro | investor intro | No | Intro source already matched forwarded investor note and follow-up invite list. |

Leo caught a stale link in the support rotation doc while answering the webhook-signature question. It was still pointing at the old API v2 signature-guide anchor and skipped the raw-body warning. He updated the target and put the before/after URL in the support channel before the next handoff.

Acme noise, not an escalation: their AP system sent Sarah another past-due statement for the September platform invoice that’s already paid. Greg replied separately that it was an internal Acme AP retry, not a Scaffold billing dispute, and Sarah forwarded both so we don’t misread it.

Can you help me make a practical plan for Tuesday’s water shutoff? Building notice says Oct 15, 10am–2pm, and it covers the Unit 3B stack. Jamie is at the hospital that morning, Kibo’s normal midday routine lands right in the window, and I haven’t moved any calls yet.

We kept the Oakland morning unstacked after the first Evergreen pilot week: short Lake Merritt loop with Jamie and Kibo, coffee, then home before it turned into anything bigger. Cooler weather was much better for Kibo.

I have Jake’s Monday activation screenshot open, but I don’t want to over-route the connector-auth handoff drop from this cut. Please review the screenshot and notes, then recommend the narrow next diagnostic step and who should own the first pass before I make a call. From: Jake To: Morgan Chen Date: 2024-10-14 08:41 PT Subject: Monday Mercury activation snapshot Attachment: mercury_activation_snapshot_2024-10-14.png [Image text as visible] Mercury — prior-week activation funnel (operating view) Period: 2024-10-07 00:00 PT to 2024-10-13 23:59 PT Population: new external workspaces created in period Filters: internal/test excluded Important note This is the weekly operating funnel, not a closed 7-day cohort view. For Mercury activation reporting, activation still means real_source_connected or first_live_sync_completed within 7 days. sample_import_completed is excluded. This screenshot is showing observed weekly funnel events only. Funnel Stage Accounts % of prior stage % of new workspaces New workspaces created 42 — 100.0% Reached first-source connect step 36 85.7% 85.7% Hit connector-auth handoff 36 100.0% 85.7% Real source connected 29 80.6% 69.0% First live sync completed 21 72.4% 50.0% Visual bars New workspaces created 42 ████████████████████████████████████████ Reached first-source step 36 ██████████████████████████████████ Connector-auth handoff 36 ██████████████████████████████████ Real source connected 29 ███████████████████████████ First live sync completed 21 ████████████████████ Chart annotations - Visible bend is between connector-auth handoff and real source connected. - There is still a later drop from connected source to first live sync, but this week’s sharper question is the auth handoff gap. - sample/demo paths are not included in this cut. Jake’s notes - The shape this week is pretty straightforward: 42 new workspaces, 29 real first-source connections, 21 first live syncs. - The main visible drop is at the connector-auth handoff. We can see accounts getting to the handoff step and then not making it through to a connected source. - This screenshot does not isolate the cause. I can’t tell from this cut whether the misses are mostly: 1) copy / expectation-setting before or during redirect, 2) source-side permissions / admin approval issues, 3) connector-specific setup friction after auth starts. - I did not convert this into a weekly “activated” number because the cohort window is still open. Using the May correction, activation stays tied to real source connection or first live sync within 7 days, not sample import behavior. - Quick read from the weekly breakdown: this does not look like one obvious single-connector outage. Stalls are spread enough that I would not call a single-provider incident from this screenshot alone. - The 29 to 21 drop after source connection still matters, but it looks closer to the usual post-connect setup / schedule / source-readiness gap than a brand-new break. - I haven’t narrowed the first diagnostic pass yet. Two plausible next reads: - event-path/session review around the auth handoff and redirect return, or - support/error-log pull for failed auth / permission callback patterns. - Owner route depends on what the first read shows. If this is copy/setup clarity, it probably belongs with Priya’s activation/onboarding lane. If it is auth, permissions, or a connector seam, it should go through Leo/Jake. If it ends up being a repeatable account-pattern bucket, Nadia can tag it, but I would not route it there first without the product read. End of attachment.

Kibo’s Oakland dental follow-up is done. I handled drop-off and pickup since Jamie has the late hospital shift; clinic had the no-poultry / boring-food notes right, and he came home groggy but fine with the usual post-dental instructions. No new dental procedure got scheduled, so we’re back to the normal boring-food, no-poultry care plan.

Can you review HR’s October all-hands run-of-show and suggest tighter edits for my opener? I’m mostly worried the “enterprise push” wording makes the company focus sound broader than it is. Keep the language tied to current shipped facts and Q4 boundaries, not a bigger enterprise story. October All-Hands — HR Draft Run of Show Draft status: sent for Morgan review Prepared by: HR Audience: full company Purpose - Keep the company update short and factual. - Reinforce Q4 focus and current decision boundaries. - Use pre-collected questions only; no open-mic segment. - Keep product and commercial language aligned with what has actually shipped. Working theme - What is more real now, what remains intentionally bounded, and what we are watching in Q4. Meeting shape - Total planned length: 34 minutes - Format: short company update + pre-collected questions - Live answers only on approved current topics - Remaining questions routed async or to named owners after the meeting Run of show 0:00–0:01 Owner: HR Slide: title slide Notes: - Welcome everyone. - Quick reminder that the meeting is recorded for teammates who cannot attend live. - Hand off directly to Morgan. 0:01–0:07 Owner: Morgan Chen Slide: Where we are now Segment: six-minute opener Speaker draft: Thanks, everyone. I want to keep this one pretty direct. A lot of the work we have been doing over the last few months is now showing up in a way that is more concrete and easier to talk about honestly. That is good for us internally, and it is good for the company because it lets us operate off evidence instead of momentum theater. First, on product and release reality: we shipped the first Mercury enterprise-readiness slice into production for scoped enterprise accounts. The shipped pieces are specific: SAML SSO, admin-side audit-history events for invite, source, and admin changes, and clearer separation between admin and billing-owner responsibilities. That matters because those were real gaps for a set of larger customers, and now they are real capabilities we can point to without stretching the story. Second, on platform and customer trust: Atlas support and release handling are on a steadier path. Customer-facing Atlas issues now route through the support rotation, Leo takes the first technical read, and Jake continues to own product priority and sequencing. That split is not glamorous, but it is important. It means customer issues are getting a cleaner technical read, product tradeoffs are staying with the right owner, and we are not pretending a process gap is solved by everyone swarming it. Third, on the market side: our enterprise push is producing better conversations, but I want to be careful about what that does and does not mean. It means larger accounts are taking Scaffold more seriously when they look at setup, admin expectations, and reliability questions. It does not mean we suddenly have a broad enterprise machine, and it does not mean every larger-customer request should bend roadmap gravity. That distinction matters a lot right now. The board discussion last month was constructive precisely because the facts are more real now, not because we told a bigger story. The line remains the same: more room, same discipline. Defensible story, not a bigger story. So for Q4, our watchlist is still the same three things. One is Evergreen paid-pilot adoption. Two is renewal and expansion evidence. Three is Nadia’s account-source quality: are the stronger enterprise conversations coming from a repeatable lane, or are they still too dependent on one-off situations and bespoke pull. Those are the signals that matter. They are the board-facing signals, and they are the right internal signals too. That also means some things are intentionally not changing yet. We are not building a broad field-sales motion right now. We are not opening a separate RevOps or CS lane right now. We are not reopening a second Mercury engineering req right now. If those decisions change later, they will change because the evidence says the motion is repeatable, not because one account is loud or one meeting feels promising. The same discipline applies to how we talk about Mercury. Mercury is a major release path for customer setup and activation on the Scaffold platform. It is not a blank check to describe the product as fully enterprise-ready. The shipped slice is real, and we should say it plainly. Advanced admin controls are not done. Procurement packaging is still its own workstream. And we should not compress those distinctions just because narrower wording feels less exciting. What I want from the company is straightforward. Keep claims tied to shipped facts. Keep customer commitments specific. Escalate when a request starts turning into bespoke roadmap pressure. And keep paying attention to the basics that make the bigger story believable at all: setup clarity, sync trust, release discipline, support responsiveness, and evidence that customers are not just interested but adopting, renewing, and expanding. We have more to work with than we did earlier in the year. That is real progress. The job now is to use that room well, stay disciplined about scope, and keep building from proof instead of from wishful extrapolation. 0:07–0:09 Owner: HR Slide: Q&A process Segment: two-minute process note Speaker draft: Quick note on format before we move into updates and questions. As with the last quarterly format, we collected questions in advance so we could group duplicates, cut down on speculation, and make sure the live section stays focused on current topics where we can give useful answers. We will answer a selected set live today. Those are the questions where there is current information the company should hear directly. A number of submitted questions are still important but are better handled asynchronously or by the named owner after this meeting. That includes questions that ask for forward-looking dates we have not committed to, questions that depend on customer-specific context, and questions where a broad live answer would create more confusion than clarity. We are not doing an open-mic block at the end. If your question is not answered live, HR will post the routed list with owners and follow-up paths after the meeting. Please keep sending questions that way; the pre-collected format has produced better discussion and fewer half-answers. 0:09–0:14 Owner: Jake Slide: Mercury and activation update Talking points: - Mercury remains focused on customer setup and activation on the core Scaffold platform. - What changed since the last all-hands: first enterprise-readiness slice shipped on the normal release path. - Keep scope language tight: shipped now are SAML SSO for scoped enterprise accounts, admin-audit visibility for invite/source/admin changes, and clearer admin-versus-billing-owner separation. - Advanced admin controls are not part of the shipped claim set. - Procurement/security packet remains separate from product release claims. - Continue weekly evidence review through MER-1279 as the internal operating ledger for launch-relevant evidence. 0:14–0:18 Owner: Leo Park Slide: Atlas, support routing, and release discipline Talking points: - Customer-facing Atlas issues route through support rotation. - Leo owns first technical read on customer-facing Atlas issues. - Jake owns product priority and sequencing for Atlas customer work. - Emphasis on release discipline and separating cleanup from architecture or system-risk work. - Goal is faster, cleaner reads without turning every issue into a roadmap negotiation. 0:18–0:22 Owner: Devon Hayes Slide: Commercial frame and Q4 constraints Talking points: - Shipped capability claims stay narrow and factual. - No custom Evergreen promises; Evergreen remains a useful stress case, not a reason to switch into bespoke behavior. - Q4 remains constrained on hiring and GTM build-out. - No broad field-sales build, no RevOps/CS lane, no second Mercury engineering req unless adoption, renewal/expansion, and account-source quality show repeatability. - Watch for roadmap gravity from larger-customer asks. 0:22–0:32 Owner: Morgan Chen with named owners as needed Slide: Pre-collected Q&A Format notes: - Morgan moderates. - Keep each answer under two minutes. - If an answer starts drifting into uncommitted dates or customer-specific detail, Morgan cuts and routes. Approved live questions Q1 Question: What exactly shipped in the Mercury enterprise work, and how should we describe it internally and externally? Primary owner: Morgan Chen, with Jake if needed Why live: current, factual, company-wide relevance Answer guide: - Say exactly what shipped: SAML SSO for scoped enterprise accounts, admin-side audit-history events for invite/source/admin changes, clearer admin-vs-billing-owner separation. - Do not say Mercury is fully enterprise-ready. - Do not imply advanced admin controls or procurement packaging are complete. Q2 Question: Are we changing company focus toward larger enterprise customers now? Primary owner: Morgan Chen Why live: broad concern, needs boundaries Answer guide: - We are learning from stronger enterprise pull. - Current focus is disciplined follow-through, not a larger company story. - Watchlist remains Evergreen adoption, renewal/expansion evidence, and Nadia’s account-source quality. Q3 Question: Are we adding GTM or engineering headcount because of recent enterprise traction? Primary owner: Morgan Chen Why live: direct question, clear current answer Answer guide: - Q4 hiring remains constrained. - No broad field-sales build. - No RevOps/CS lane. - No second Mercury engineering req until evidence is repeatable. Q4 Question: What changed operationally for Atlas support after Rishi left? Primary owner: Leo Park Why live: internal clarity question with current answer Answer guide: - Customer-facing Atlas issues go through support rotation. - Leo owns first technical read. - Jake owns product priority and sequencing. - Intent is cleaner ownership, faster triage, better separation of technical read from priority decisions. Q5 Question: How should teams handle larger-customer asks that sound reasonable but start pulling us off the current path? Primary owner: Morgan Chen, with Devon Hayes if needed Why live: cross-functional operating guidance Answer guide: - Acknowledge the request. - Tie statements to shipped facts and current scope. - Escalate when the ask starts becoming roadmap pressure tied to one account. - Use the current no-bespoke line unless there is explicit approval. Questions to route async or to named owners Q6 Question: When will advanced admin controls be available, and what exactly is in that set? Disposition: async Owner: Jake Reason for routing: asks for forward-looking scope/timing not ready for company-wide live commitment Q7 Question: Are we creating enterprise packaging, procurement pricing, or an add-on this quarter? Disposition: async Owner: Devon Hayes and Morgan Chen Reason for routing: commercial packaging still in progress; broad live answer likely to overstate current state Q8 Question: Is Evergreen likely to expand this year, and how much should teams treat it as a model account? Disposition: async Owner: Morgan Chen and Devon Hayes Reason for routing: customer-specific detail and forward-looking revenue discussion Q9 Question: Are we moving support or success staffing because enterprise customers need a different experience? Disposition: async Owner: HR and Morgan Chen Reason for routing: staffing question intersects with Q4 constraints and is better answered in written follow-up Q10 Question: Will there be another round of Mercury design and onboarding changes before year-end? Disposition: async Owner: Jake and Priya Reason for routing: depends on evidence review and current release sequencing 0:32–0:34 Owner: HR Slide: Close and follow-up Notes: - Thank speakers. - Remind everyone that the routed question list and owners will be posted after the meeting. - Point people to the written notes and recording. - Close on: keep questions coming through the pre-submit form rather than side-channel speculation. Presenter reminders - Keep all external-sounding language tied to shipped facts only. - Avoid describing Mercury as fully enterprise-ready. - Avoid broad forward-looking hiring language beyond current Q4 constraints. - Avoid open-ended pricing speculation. - If someone starts answering with a date that is not committed, Morgan redirects to async follow-up. Slide list 1. October All-Hands 2. Where we are now 3. Q&A process 4. Mercury and activation update 5. Atlas, support routing, and release discipline 6. Commercial frame and Q4 constraints 7. Pre-collected Q&A 8. Follow-up and owners Draft flags for review - Morgan opener currently uses the phrase enterprise push; HR included it to signal stronger larger-account traction, but wording may want tightening so it does not sound broader than current scope. - Devon section should stay coordinated with current customer-safe wording on shipped enterprise-readiness capabilities. - No open-mic wording should stay explicit in both the process note and closing slide.

Can you clean this up for the Evergreen usage read? I need the actual admin/operator pilot users separated from procurement/legal/vendor-risk reviewers and the list/shared-mailbox rows, with a clear call on which rows should count once they log into the pilot workspace. From: Sarah Kim To: Morgan Chen; Devon Hayes Date: 2024-10-22 14:18 PT Subject: Fwd: Evergreen pilot access export (raw list before usage cleanup) Forwarding the raw CSV Evergreen sent over for the pilot workspace access list. This is not normalized yet. It mixes the people actually doing the admin/operator pilot work with procurement, vendor-risk/legal reviewers, and a few distribution/shared-mailbox placeholders they wanted copied on setup. My rough read is that only eight of these rows look like real pilot users who should matter for usage once they actually log into the workspace, but I have not cleaned the file up. Attachment: evergreen_pilot_access_2024-10-22.csv display_name,email,title_or_group,department,workspace_role_requested,intended_pilot_use,invite_status,invite_sent_pt,first_login_pt,notes Alicia Grant,alicia.grant@evergreenbank.com,Directory Services Lead,Identity,workspace_admin,"Primary Mercury admin; SAML login setup and admin configuration",accepted,2024-10-02 10:11,2024-10-03 09:14,"Owns Evergreen directory-side setup" Ben Ortiz,ben.ortiz@evergreenbank.com,IAM Engineer,Identity,workspace_admin,"Login verification, permission checks, and admin handoff coverage",accepted,2024-10-02 10:12,2024-10-03 10:02,"Works directly with Alicia on auth testing" Carla Nguyen,carla.nguyen@evergreenbank.com,Treasury Ops Manager,Treasury Operations,operator,"Run operator workflows against live pilot data and verify first-use path",accepted,2024-10-03 08:47,2024-10-04 11:28,"Named operator tester" Daniel Ross,daniel.ross@evergreenbank.com,Platform Operations Analyst,Operations,operator,"Daily pilot use, sync checks, and issue reproduction",accepted,2024-10-03 08:49,2024-10-07 08:56,"Named operator tester" Emily Park,emily.park@evergreenbank.com,Data Controls Manager,Controls,workspace_admin,"Admin-audit lookup and approval-path validation",accepted,2024-10-04 09:18,2024-10-08 14:21,"Named admin tester" Faisal Karim,faisal.karim@evergreenbank.com,Developer Experience Engineer,Developer Platform,operator,"Connector setup review and API-side spot checks",accepted,2024-10-07 09:03,2024-10-10 16:44,"Named operator tester" Gina Moreno,gina.moreno@evergreenbank.com,Support Operations Lead,Client Operations,operator,"Support handoff testing and issue replay inside pilot workspace",accepted,2024-10-09 11:26,,"Invite accepted; no login showing in this export yet" Henry Li,henry.li@evergreenbank.com,Integration Engineer,Enterprise Apps,operator,"Source-side configuration validation and webhook/check flow review",invited,2024-10-10 15:42,,"Invite sent; not yet accepted in this export" Dana Wu,dana.wu@evergreenbank.com,Senior Procurement Manager,Procurement,reviewer,"Commercial packet review and pilot paperwork",accepted,2024-10-02 13:05,2024-10-02 13:22,"Added on the same list so Evergreen could keep one packet" Michael Torres,michael.torres@evergreenbank.com,Commercial Counsel,Legal,reviewer,"Contract and legal review visibility",accepted,2024-10-02 13:07,2024-10-02 13:31,"Reviewer access request came through Sarah's commercial thread" Priya Nair,priya.nair@evergreenbank.com,Vendor Risk Analyst,Vendor Risk,reviewer,"Third-party risk review and questionnaire follow-up",accepted,2024-10-02 13:08,2024-10-03 09:41,"Reviewer only" Rachel Feldman,rachel.feldman@evergreenbank.com,Finance Approver,Finance,reviewer,"Budget signoff visibility for pilot start",accepted,2024-10-02 13:09,,"Included for approval chain; no pilot task owner note" Samir Patel,samir.patel@evergreenbank.com,Security Review Lead,Security,reviewer,"Security review follow-up on SAML/admin-audit slice",accepted,2024-10-02 13:10,2024-10-04 08:18,"Security reviewer, not named as pilot operator" Procurement Reviewers,procurement-review@evergreenbank.com,Distribution List Placeholder,Procurement,cc_only,"Copy on procurement updates and packet changes",accepted,2024-10-02 13:12,,"List alias, not a single user" Vendor Onboarding Queue,vendor-onboarding@evergreenbank.com,Shared Mailbox Placeholder,Vendor Management,cc_only,"Shared inbox for vendor onboarding correspondence",accepted,2024-10-02 13:12,,"Shared mailbox" InfoSec Distribution,infosec-review@evergreenbank.com,Distribution List Placeholder,Security,cc_only,"Copy on security-review traffic",accepted,2024-10-02 13:13,,"List alias, not a single user" Executive Sponsor Updates,exec-sponsor-updates@evergreenbank.com,Distribution List Placeholder,Executive Office,cc_only,"Internal sponsor visibility on pilot milestones",accepted,2024-10-02 13:14,,"Broadcast alias"

Kibo’s regular food got weather-delayed, and Jamie says the Oakland pantry gets us through Monday morning. Before I do anything dumb in the backup cart, can you compare these two formulas against his no-poultry restriction and tell me whether I should place a backup order at all? Online cart snapshot — backup dog food Delivery address: Oakland Viewed: 2024-10-24 Regular shipment status Current autoship item: Sensitive Digestion Salmon & Oat Recipe Dry Dog Food — 22 lb Carrier status: Weather delayed Original ETA: Sat 2024-10-26 Updated ETA: Mon 2024-10-28 by 8:00 PM Saved household note: Jamie checked pantry this morning; enough approved food remains through Monday morning. Cart (not placed) 1) Sensitive Digestion Salmon & Oat Recipe Dry Dog Food — 22 lb Bag note: adult dry food / sensitive digestion Price: $78.99 Delivery estimate: Sat 2024-10-26 with standard delivery if ordered today; Fri 2024-10-25 with expedited delivery (+$12.95) Ingredients: salmon, oatmeal, brown rice, barley, dried pumpkin, flaxseed, salmon oil, natural flavor, chicory root, mixed tocopherols, vitamins and minerals. Quantity: 1 2) Sensitive Digestion Turkey & Oat Recipe Dry Dog Food — 22 lb Bag note: adult dry food / sensitive digestion Price: $76.99 Delivery estimate: Sat 2024-10-26 with standard delivery if ordered today; Fri 2024-10-25 with expedited delivery (+$12.95) Ingredients: turkey, turkey meal, oatmeal, brown rice, chicken fat preserved with mixed tocopherols, dried pumpkin, flaxseed, fish oil, natural flavor, vitamins and minerals. Quantity: 1 Cart totals Items subtotal: $155.98 Estimated tax: $14.04 Standard delivery: Free Estimated total: $170.02 Saved compare note on page: "Two similar bags in the same sensitive-digestion line; check formula before placing backup order."

Kestrel’s Mercury maintenance pass is live after Sarah’s review. Kara confirmed it stayed as a maintenance update: the public page only claims the shipped scoped SAML SSO, admin-audit visibility, and clearer admin-role separation, all in generic product language. Anything Evergreen-specific, customer-proof-y, funding-related, or broader enterprise-readiness is still on the separate Scaffold review path.

I’m trying to decide whether this is product polish or something support should answer around. Please read Sarah’s two clips and recommend where the missed teammate-invite success confirmation belongs. From: Sarah Kim To: Morgan Chen Date: 2024-10-28 11:06 PT Subject: Two clipped non-Evergreen admin notes on teammate invite success Sending two short clips that look like the same pattern. These are both from non-Evergreen admins in Mercury onboarding. Jake checked the underlying invite records on both and said the invite itself succeeded; what seems to have failed here is that the admin missed the brief success toast and assumed nothing happened. Clip 1 Account: Northline Health Surface: Mercury onboarding teammate-invite step Received: 2024-10-27 Excerpt: "I entered my coworker’s email and hit Invite, but the screen more or less just sat there from my point of view. If there was a confirmation, I missed it. I tried the same address again because I thought the first one hadn’t gone through, and only later realized my teammate already had the invite email. The action worked, it just didn’t feel like it worked." Clip 2 Account: HarborStack Surface: Mercury onboarding teammate-invite step Received: 2024-10-28 Excerpt: "We got to the add-teammate part and it was weirdly quiet after submit. I was looking back at the form and never caught the little message that apparently says it sent. We assumed invites were blocked until the recipient forwarded me the email. If the invite succeeds, the product should probably say it in a way that survives me glancing away for two seconds." Neither note says the email failed to arrive; both are basically 'we missed the confirmation and thought the action didn’t stick.'

Evergreen’s first full-month pilot read is actually useful, but still bounded. Their admin testers are getting through SAML login and admin-audit lookup cleanly, and Leo’s support read says the shipped slice is stable. Usage is still inside the included 200 monthly active developers on Growth, mostly the original admins plus a small operator group, so Devon and I are holding any renewal or enterprise-add-on pricing talk for the December closeout. Nadia’s notes did make the account conversation sharper; just not enough yet to call expansion repeatable.

Can you read Devon’s October close variance tab and recommend the two bullets I should mark for the internal month-close note? From: Devon Hayes To: Morgan Chen Date: 2024-11-01 08:12 AM Subject: Preliminary October close + variance tab Morgan — Attached the preliminary October close variance tab. Top line: - Cash collections landed on plan for October. - Payroll is a little lower than plan because the contractor/vendor payment that was expected to clear on 10/31 actually hit on 11/1, so it will show up in November cash instead. - The only material operating overage is cloud infrastructure: $8,920 actual vs $8,400 plan. This is the same monthly series that also drove the September invoice variance, not a new category. Can you mark which two bullets you want in the internal month-close note? I put the numbers and a few candidate bullets in the tab below. Nothing else looks notable enough to surface. Devon --- Attachment: October 2024 Preliminary Close - Variance Tab --- Scaffold October 2024 Preliminary Close - Variance Tab Status: Preliminary internal read as of 2024-11-01 Prepared by: Devon Hayes Notes on read: - Variance shown as Actual minus Plan. - Negative operating-expense variance = favorable to plan. - October payroll/payables read includes expenses incurred through 10/31; one contractor/vendor payment expected in the final October run settled on 11/1 and is therefore in November cash. Summary table | Line item | October Plan | October Actual | Variance vs Plan | Readout | |----------------------------------------|-------------:|---------------:|-----------------:|---------| | Cash collections | $642,000 | $642,000 | $0 | On plan | | Revenue | $511,400 | $511,400 | $0 | On plan | | Payroll and payroll taxes | $318,900 | $312,460 | ($6,440) | Favorable; one contractor/vendor payment moved to 11/1 | | Cloud infrastructure | $8,400 | $8,920 | $520 | Unfavorable; same monthly series seen on September invoice | | Software / internal tools | $14,200 | $14,110 | ($90) | In line | | Contractors (non-payroll) | $22,500 | $22,500 | $0 | On plan | | Rent / office | $9,800 | $9,800 | $0 | On plan | | Travel and meals | $3,200 | $3,060 | ($140) | In line | | Legal / accounting | $11,000 | $11,000 | $0 | On plan | | Other operating expense | $6,700 | $6,690 | ($10) | In line | | Total operating expense | $394,700 | $389,540 | ($5,160) | Net favorable, driven by payment timing | Detail notes 1) Cash collections - October finished exactly on plan. - No meaningful collections timing variance to call out for the month-close note. 2) Payroll / contractor timing - Payroll line is below plan by $6,440. - This is timing, not a structural reduction: a contractor/vendor payment expected in the final October processing batch settled on 11/1. - November cash will absorb that amount, so this should not be framed as ongoing savings. 3) Cloud infrastructure - October actual: $8,920 - October plan: $8,400 - Variance: +$520 - This is the same recurring monthly cloud-infrastructure series that was also the main September invoice variance. - Nothing in the October read suggests a separate new spend category; this looks like continued run-rate / invoice-series noise rather than a new one-off operating issue. Candidate bullets for internal month-close note A. October cash collections finished on plan. B. Payroll ran $6.4k below plan because one contractor/vendor payment moved from the final October run into 11/1 settlement. C. Cloud infrastructure came in at $8,920 vs $8,400 plan, the only material operating overage and the same monthly series that drove September's variance. D. No other operating lines moved materially versus plan. Items not recommended for highlight unless needed - Revenue: on plan - Software/tools: immaterial favorable variance - Travel/meals: immaterial favorable variance - Legal/accounting: on plan - Other operating expense: immaterial End of tab

Please review HR’s benefits-enrollment packet and give me a recommendation on the FAQ contact line — leave the generic People Ops wording, or make it more specific for our small team before we send it around. From: HR To: Morgan Chen Date: 2024-11-04 09:05 AM Subject: Scaffold 2025 benefits enrollment founder/admin packet Hi Morgan, Open enrollment for the 2025 benefits plan year is now open. Enrollment window - Opens: Monday, 2024-11-04 - Closes: Friday, 2024-11-15 at 5:00 p.m. PT - Effective date for new elections: 2025-01-01 Attached below is the founder/admin packet with: - carrier changes summary - employee FAQ - team-selection deadline and admin reminders Please send the employee FAQ to the team at the start of the window. If you want to make company-specific wording edits before distribution, send back a marked version and we can review for consistency. HR --- Attachment: Scaffold 2025 Benefits Enrollment Founder/Admin Packet --- Scaffold 2025 Benefits Enrollment Founder/Admin Packet For founders and internal admins 1. Key dates - Open enrollment opens: Monday, 2024-11-04 - Employee election deadline: Friday, 2024-11-15 at 5:00 p.m. PT - HR final review / exception cleanup: 2024-11-18 through 2024-11-20 - Coverage effective date: Wednesday, 2025-01-01 Admin reminder: Employees should complete elections by the deadline even if they are keeping the same medical, dental, or vision coverage. Flexible spending account elections do not automatically carry forward and must be re-entered for the new plan year if applicable. 2. 2025 carrier and plan changes summary Medical - The medical lineup is changing carriers for 2025. - Both the PPO and high-deductible/HSA-compatible options will be offered through the new medical carrier beginning 2025-01-01. - Employees who are currently enrolled in medical coverage should review provider networks, prescription coverage, and any ongoing treatment needs during open enrollment rather than assuming all providers remain in-network. - New ID cards will be issued by the medical carrier before the 2025 effective date. Dental - No dental carrier change for 2025. - Core plan design remains substantially the same. Vision - No vision carrier change for 2025. - Existing vision coverage will continue under the current carrier. Life and disability - No carrier change for basic life, AD&D, or disability coverage. - Employees requesting increases above guaranteed-issue levels may be asked to complete supplemental forms after submitting elections. Tax-advantaged accounts - HSA-compatible medical enrollment remains available with the high-deductible plan. - Flexible spending account elections do not roll over automatically from the prior plan year and must be actively elected during this enrollment window if the employee wants to participate in 2025. 3. Founder/admin action list Before sharing the team packet - Confirm internal distribution date. - Confirm that all active employees who should be eligible are included in the enrollment roster. - Remind managers not to advise employees on which medical plan to choose; they may direct employees to plan documents or HR for process questions. During the window - Send the employee FAQ on 2024-11-04 or as soon as practical. - Send a reminder to any non-responders around 2024-11-12. - Escalate any roster or dependent-eligibility issues as soon as they are identified. At deadline - Team selections are due by Friday, 2024-11-15 at 5:00 p.m. PT. - Late elections are not guaranteed to be accepted. - Employees who do not respond will be handled according to default continuation rules where applicable, but any account requiring a fresh annual election will remain unelected if no action is taken. 4. Employee FAQ Scaffold 2025 Open Enrollment FAQ What is open enrollment? Open enrollment is the annual window when employees can review current benefits and make benefit elections for the upcoming plan year. When is the enrollment window? Open enrollment starts on Monday, 2024-11-04 and closes on Friday, 2024-11-15 at 5:00 p.m. PT. When do my elections take effect? Approved elections made during this window take effect on 2025-01-01. Who should review their benefits during open enrollment? All benefits-eligible employees should review their current elections during the window, even if they expect to keep similar coverage. Do I need to take action if I want to keep the same coverage? Employees should still review elections during open enrollment. Medical, dental, and vision coverage may continue according to plan rules if no change is submitted, but flexible spending account elections do not automatically carry forward and must be re-entered for 2025 if desired. What is changing for 2025? The main change is a medical carrier transition for the 2025 plan year. Employees currently enrolled in medical coverage should review provider networks, prescription coverage, and any ongoing care needs before finalizing elections. Dental, vision, and core life/disability coverage do not have a carrier change for 2025. How do I compare plan options? Review the plan summaries, coverage documents, and any provider-directory information made available during enrollment. If you are currently in treatment or want to keep specific doctors or prescriptions, verify network participation and formulary coverage before making your election. Can I add or remove dependents during open enrollment? Yes. Open enrollment is the annual opportunity to add, remove, or update eligible dependents, subject to plan rules and any required documentation. What if I previously waived coverage and now want to enroll? If you are eligible and want to enroll for 2025, you should make that election during the open enrollment window. Waiting until after the window closes may require a qualifying life event. Do I need to elect flexible spending or HSA contributions again? Flexible spending account elections must be made again for the new plan year if you want to participate. HSA contribution elections should also be reviewed and updated during enrollment if you plan to contribute in 2025. What if I have a qualifying life event after open enrollment ends? If you experience a qualifying life event after the enrollment window closes, contact the appropriate benefits contact promptly. Midyear benefit changes are generally limited to qualifying events and required timing rules. Where can I find plan documents? Plan summaries and enrollment materials are available in the benefits enrollment materials shared for the 2025 window. Who should I contact if I have questions? Please send questions to People Ops. 5. Suggested employee cover note for internal send Subject: 2025 benefits open enrollment Open enrollment for 2025 benefits is open from Monday, 2024-11-04 through Friday, 2024-11-15 at 5:00 p.m. PT. Please review your current elections and complete any updates before the deadline. This year includes a medical carrier change, so anyone enrolled in medical coverage should review provider networks and prescription coverage carefully. If you want to participate in a flexible spending account for 2025, you must make that election during open enrollment. See the FAQ and plan materials for details. 6. Admin notes - Do not recommend specific plan choices to employees. - Direct employees to review plan materials and provider network information before electing coverage. - Flag any eligibility or roster discrepancies immediately so they can be resolved before the deadline. - If you want an FAQ or cover note reviewed after company-specific edits, return the marked version before the close of the enrollment window. End of packet

Can you read Nadia’s CRM source QA note and Sarah’s excerpts and tell me whether I should approve changing these four October opps before the account-quality snapshot? I want the recommendation to separate source hygiene from any pipeline or bookings interpretation. From: Nadia Singh To: Morgan Chen Cc: Sarah Kim Date: 2024-11-06 08:41 Subject: CRM source QA - 4 October opps currently tagged inbound enterprise Morgan — During the October source QA pass I found four opportunities created last month that are currently tagged as inbound enterprise but, based on the contact history and Sarah’s account notes, look like partner-forwarded conversations rather than direct inbound. I pulled these because they all met the same pattern: - current source in CRM = Inbound / Enterprise - first meeting was booked only after a partner intro or partner-forwarded email - no independent demo request / site form / direct SDR handoff before the partner touch - Sarah’s notes explicitly reference partner routing or a request to “take over” from a partner conversation I have not changed the source fields yet. Listing the four below with the evidence trail so we can decide whether to reclassify before the next account-quality snapshot goes out. Potential reclassifications 1) Northlight Health Systems - Opportunity created: 2024-10-03 - Current CRM source: Inbound enterprise - Current status: discovery completed / evaluating security + initial scope - Why it looks misclassified: - earliest logged external touch is a forwarded note from the CloudBridge partner team introducing Northlight’s IT director and asking us to continue the product conversation directly - first calendar hold was set off that forwarded thread - I could not find an earlier direct form fill or self-serve inbound request from Northlight - Proposed source correction: Partner-forwarded / partner-sourced - Notes: - contact reached our team through partner channel, but once the intro happened the account was worked directly by Scaffold - this appears to have been tagged inbound because the meeting owner created the opp from the account page after the intro, not from the partner workflow 2) Carrick BioLabs - Opportunity created: 2024-10-11 - Current CRM source: Inbound enterprise - Current status: technical validation pending / data model review underway - Why it looks misclassified: - first meaningful demand signal in the record is a forwarded email from VectorLane Consulting saying the prospect had asked for a recommendation for integration infrastructure and VectorLane suggested Scaffold - Sarah’s notes say the team should treat it as a partner-led introduction and that the customer had not previously engaged us directly - no earlier website lead, event scan, or outbound sequence response attached to the record - Proposed source correction: Partner-forwarded / partner-sourced - Notes: - there is a later direct email from the buyer to Leo with API questions, but that happens after the forwarded intro and after the meeting is already in motion 3) Red Alder Financial - Opportunity created: 2024-10-17 - Current CRM source: Inbound enterprise - Current status: security review requested / solution fit discussion in progress - Why it looks misclassified: - first thread in activity history is a resend from Summit Advisory with “looping in Scaffold per our call” language - Sarah’s notes on the account say Summit had already been discussing vendor options with Red Alder and forwarded them into our team for the technical deep dive - I could not find any earlier direct inbound from Red Alder before the Summit handoff - Proposed source correction: Partner-forwarded / partner-sourced - Notes: - likely got marked inbound because the prospect contact replied directly to our AE once the thread was opened and the opp was then created from that reply chain 4) Beacon Mobility Group - Opportunity created: 2024-10-28 - Current CRM source: Inbound enterprise - Current status: initial scoping / stakeholder mapping - Why it looks misclassified: - first recorded interaction is a partner manager from Delta Stack sending over the buyer contact and context from an existing services conversation - Sarah’s notes say Delta Stack asked whether Scaffold could support the integration layer for a customer they were already advising - there is no stand-alone Beacon-originated inbound before that introduction - Proposed source correction: Partner-forwarded / partner-sourced - Notes: - this one is newest, so if we leave October snapshot rules untouched it will still show in the inbound enterprise bucket even though the origin is pretty clearly partner-routed Quick impact if reclassified - October count of inbound enterprise opps would decrease by 4 - partner-sourced / partner-forwarded count would increase by 4 - these do not look like net-new pipeline additions; this is source hygiene only - I have not checked whether finance or board reporting uses a separate partner bucket label from the one sales ops uses in the CRM source field Open question - Should I go ahead and reclassify these before the next account-quality snapshot, or should we leave October frozen and document the correction separately? Sarah’s supporting account notes are pasted below. — Nadia --- Sarah Kim account notes (supporting excerpts) --- Account: Northlight Health Systems Account note date: 2024-10-02 16:18 Owner: Sarah Kim "CloudBridge forwarded Northlight after their architecture review. Northlight has not come in through our site or an SDR path as far as I can tell. We should treat this as a partner-routed intro even if the buyer takes the next thread directly with us. Contact is Erin Voss, IT director. They want to evaluate whether Atlas can sit between their EMR exports and internal analytics stack." Follow-up note date: 2024-10-04 10:07 Owner: Sarah Kim "Booked intro call from the CloudBridge forward. If opp gets opened, source should stay with partner motion rather than inbound enterprise." Account: Carrick BioLabs Account note date: 2024-10-10 14:52 Owner: Sarah Kim "VectorLane team asked if we can pick up Carrick directly. They had already been advising Carrick on integration options and recommended Scaffold for the data sync/API layer. No evidence of a prior Carrick-originated inbound in our queue. This should be tracked as partner-led unless we find an earlier direct request." Follow-up note date: 2024-10-12 09:31 Owner: Sarah Kim "Customer sent direct technical questions after the VectorLane intro, but demand originated with the partner handoff. Important not to count this as clean inbound." Account: Red Alder Financial Account note date: 2024-10-16 18:06 Owner: Sarah Kim "Summit Advisory has been comparing vendors with Red Alder and sent over the contact after their workshop. This is not a fresh inbound lead source; it is a partner-forwarded conversation where we’re now taking the product/technical work directly." Follow-up note date: 2024-10-18 11:24 Owner: Sarah Kim "AE created opp after direct reply from prospect, but origin remains Summit intro. If reporting asks direct inbound vs partner, this belongs in partner." Account: Beacon Mobility Group Account note date: 2024-10-28 08:43 Owner: Sarah Kim "Delta Stack introduced Beacon from an active services discussion. They asked whether Scaffold can cover integration orchestration for Beacon’s rollout. No direct inbound request from Beacon found before the Delta Stack email." Follow-up note date: 2024-10-29 13:02 Owner: Sarah Kim "Recommending we mark source as partner-forwarded if/when opp is created. Buyer is now engaging directly, but the top-of-funnel origin was Delta Stack."

Kibo is okay now, but that was a rough one. Backup sitter gave him a “dental” treat yesterday that turned out to have chicken meal, and he ended up with bad stomach stuff plus itching. Jamie and I took him to the Oakland vet; reaction has settled. I rewrote the sitter/walker handoff tonight: Kibo only gets pre-portioned food and treats Jamie or I have already approved. No samples, no substitute treats, and no label-guessing in the moment even if something looks safe.

Evergreen’s SAML certificate-rotation coordination blew through the whole morning, exactly when Kibo had his early follow-up from the poultry treat mess. Jamie handled the vet run; good news is the reaction is resolving. Less good is that I just straight-up missed the appointment because Scaffold ate the flexible household time again. That needs to be part of the offline-time boundary, not just me feeling bad about one calendar miss.

Can you draft a short reply to Devon picking Thursday morning for the December board operating review? I don’t want to accept the Wednesday hold across Jamie’s only early dinner window. Subject: December board operating review hold From: Devon Hayes To: Morgan Chen Date: Fri, Nov 15, 2024 at 9:06 AM Quick bump before I answer the calendar side. Still open: - Wed Dec 11, 5:30–7:00 PM PT (original proposed hold) - Thu Dec 12, 8:00–9:30 AM PT - Fri Dec 13, 11:30 AM–1:00 PM PT I have not accepted anything yet. If you want to keep Wednesday clear for the early dinner window with Jamie, my preference is Thursday morning. — Devon On Thu, Nov 14, 2024 at 4:18 PM Devon Hayes wrote: Subject: December board operating review hold Morgan — Board scheduling came back with one default slot and two viable alternates for the December operating review. I have not accepted anything yet. Proposed hold - Wed Dec 11, 5:30–7:00 PM PT I know that lands across the only early dinner window you and Jamie have that week, so before confirming I asked for backups. They can also make either of these work: Alternates - Thu Dec 12, 8:00–9:30 AM PT - Fri Dec 13, 11:30 AM–1:00 PM PT My vote is Thursday morning if you want the cleanest option. Friday is workable too; it just sits in a noisier part of the week. Send me the pick and I’ll lock it. — Devon

Jake sent a short Mercury setup-polish note from last week’s activation sessions: the connect-first-source modal is losing people after the connector-auth warning, and the two clearest clips are from non-enterprise workspaces. He’s asking whether I want it called out in Friday’s product note or kept as his engineering follow-up. Recommend the cleaner route.

New Kibo wrinkle, separate from the food mess: after a longer Lake Merritt walk he had a light limp, so we had the Oakland vet check his gait. They’re treating it as mild senior-dog stiffness / early arthritis, not an acute injury. Interim plan is shorter, flatter walks when he’s stiff, plus a vet-approved non-poultry joint supplement. We’ve got a Dec 3 recheck on the calendar to make sure it isn’t progressing.

Jamie and I finally had the household scheduling conversation I’d been dodging after the missed Kibo follow-up and then the stiffness-vet thread. Because his hospital weeks keep moving, we’re making it flexible instead of pretending a fixed block will hold: each week we pick one weeknight dinner and one weekend morning as offline household time. Once we pick them, Scaffold work, investor follow-ups, customer check-ins, and internal catch-ups route around those blocks unless there’s a real incident or the equivalent customer-impacting emergency.

Package-room chaos on Kibo’s food delivery: the system marked it picked up even though neither Jamie nor I scanned it. I found the box later on the wrong shelf with a torn label, and it only had the regular food — not the supplement refill I thought was coming with it.

Devon’s November pipeline-aging tab landed. Two mid-market renewals moved into January because the customer finance teams pushed budget approvals to after Thanksgiving; Evergreen is not one of them. For the internal revenue note, would you frame those as timing slips or actual risk?

Thanksgiving stayed local and quiet in Oakland, which was the right call. Kibo got shorter walks, leftovers stayed boring, and I kept Friday as household time instead of letting Scaffold fill the space again. Good follow-through on the offline-boundary conversation, finally.

Jake’s November Mercury activation rollup has 118 new workspaces, 82 first-source connections, and 64 first live syncs. First-live-sync rate is better than October, but teammate-invite completion is still messy because some test workspaces are inviting dormant aliases. Should this become a short product-team note, or is it cleaner to leave it in the metrics appendix for now?

Kibo’s Oakland recheck was reassuring. Limp is improved, and the vet is treating this as mild senior-dog arthritis unless it worsens. Jamie and I are keeping the shorter/flatter walks when he’s stiff, measured food, strict no-poultry, and the vet-approved non-poultry joint supplement. Next routine recheck is Jan 10, 2025, unless appetite, vomiting, or gait weirdness shows up sooner. No emergency thread right now.

Can you draft a concise plain-English definition of “active developer” that Sofia can use in her internal Northstar note? Keep Devon’s meaning, but strip out the billing-system/event-taxonomy feel. Email thread Subject: active developer wording for Northstar note Thu, Dec 5, 2024, 7:46 AM — Morgan Chen To: Sofia Alvarez, Devon Hayes Sharing the watchlist wording we’ve been using on our side in case it’s useful for your internal note. Current snippets: - Mercury pricing is usage-based: pilot bands are tied to monthly active developer usage rather than purchased seats or total directory size. - In the current pilot set, once a team reaches a real first live sync, usage tends to expand through additional active developers rather than staying with a single initial admin. If you want anything more literal than that, happy to tighten. --- Thu, Dec 5, 2024, 8:14 AM — Sofia Alvarez To: Morgan Chen, Devon Hayes This is helpful. Before I write the internal note, what is the exact plain-English definition you want behind “active developer” in those snippets? I’m not looking for the billing system version or event taxonomy unless I need it. I just want to know, in normal English, what is in and out when you say: - “pilot bands are tied to monthly active developer usage” - “usage tends to expand through additional active developers” Main thing I want to avoid is accidentally translating that into seats, directory users, or “anyone who got invited once.” --- Thu, Dec 5, 2024, 8:28 AM — Devon Hayes To: Sofia Alvarez, Morgan Chen Pasting the current billing FAQ paragraph below. “Billing uses monthly active developer usage at the distinct human actor level within a customer workspace for the calendar month rather than purchased seats, directory population, or invite volume. A counted active developer is a non-Scaffold, non-test user whose monthly activity includes at least one qualifying production-workspace action beyond preview/sample-only entry, such as creating or updating source credentials/configuration, connecting a real source, setting up/running/monitoring syncs, making authenticated Atlas API or connector calls against customer data, or otherwise using the live workspace in a way that reflects real developer work; mere directory presence, invitation acceptance, magic-link entry, or bounded sample/preview browsing without real-source or comparable live-workflow usage does not by itself create an active developer. This billing usage concept is intentionally separate from activation reporting, where activation remains real_source_connected or first_live_sync_completed within 7 days.” --- Thu, Dec 5, 2024, 8:36 AM — Sofia Alvarez To: Morgan Chen, Devon Hayes Got it. That gives me the substance, but it’s probably too implementation-heavy for the note I’m writing internally. If you have a shorter plain-English version that keeps the same meaning, send that and I’ll use it.