Riley Tanaka

pretty quiet. kibo already angling for some second dinner situation. year's been... good, actually. not in a huge loud way. stuff's working, people trust me with the real version, and i don't feel behind my own life for once.

Starting the first June workday with the sub-50-seat thing turning from the May 26 pre-discovery decision into real kickoff prep. I have the scoping doc open and I want Tuesday's discussion to stay broader than packaging: eligibility/refusal boundaries, funnel event taxonomy plus what activation definition v3 does to the dashboard layer, pricing-page work without breaking my no-concurrent-layout-change rule, and lifecycle/support fork risk. I'm worried the room will collapse into "when can the pricing page say it?" unless the agenda makes the operating questions first-class. Can you help me turn that into a tight 45-minute agenda, including the decisions I actually need from Priya, Marcus, and Daniela, and wording that does not read like a public launch plan?

Owen sent me two May activation views that don't line up, and I want to answer him without manufacturing an emergency. The dashboard default is on activation definition v3 and it shows a materially lower activation rate than an older notebook still on v2. My strong guess is definition drift, not a product drop: v3 is completed first integration plus at least one in-product event within 14 days, while v2 was first integration plus two logins in 14 days. Can you sanity-check how I should explain that mismatch to Owen, and list the specific checks we should run before anyone edits dashboard labels or forwards May activation numbers?

Ines found a small copy issue in the day-3 activation-help email for growth-tier accounts. The lifecycle program is otherwise still running clean after the onboarding-trigger rollout, and I don't want to touch the CTA or muddy the metrics. I just need the one sentence softened so it stops implying a human rollout review. Can you rewrite only that body sentence into two safe alternatives?

Here's the exact excerpt from Ines: Subject line stays: "Your first integration is connected — here’s the next useful step" Current body sentence: "Once your first integration is connected, book your rollout review with your Helio CSM so we can help your team approve imports and invite the right owners." Ines's note: "This is in day-3 activation help for growth tier. Since `lifecycle_onboarding_trigger_v2` is live, this reads too sales/CS-led for accounts that are moving by product event. I don't want a new CTA, just a softer line."

Thunderstorm just rolled through East Austin while I was trying to reopen the small-business notes. Kibo is under my desk pressed against my foot, and I'm taking that as a decent reason not to keep working late just to feel prepared. I'm leaving the kickoff prep where it is and going to sleep instead of turning the storm into a spreadsheet night.

The Tuesday kickoff landed the way I wanted. I explicitly reframed the May 26 sub-50-seat approval as an internal Self-serve operating model effort, not a pricing-only project or a public launch plan, and Priya backed that in the room. I split the work into four must-answer tracks: eligibility/refusal rules; event taxonomy and dashboards using activation definition v3; pricing-page constraints under the no-concurrent-layout-change rule; and lifecycle/support fork risk. Daniela's team is on engineering scoping, Owen is getting the baseline measurement cuts, and Ines is mapping the lifecycle fork. Can you draft a crisp internal kickoff note that covers that framing, those four tracks, the named asks, and the explicit caveat that this is not yet a public pricing-page launch? I want Marcus and Tomás to understand the June gate without reading it as a Q3 promise.

Daniela replied after the kickoff and she's right that Eng will scope the wrong surface area if we mix who is allowed to try this with what the product can safely support. I want to answer quickly, but I also want Priya to bless the framing before it hardens into an engineering input. Can you turn Daniela's message into a short reply I can send now, and then give me an outline for a one-page eligibility-vs-product-constraints matrix I can run by Priya?

Daniela wrote: "Can we get the cut between 'eligibility rule' and 'product constraint' before Eng sizes this? If the answer is 'every small account can attempt setup unless they ask for imports,' that's a different system than 'we check admin model, seats, SSO, import volume first.' Need a one-pager by Thu or we'll estimate the wrong surface area."

Priya answered my overnight note and approved the eligibility-vs-product-constraints framing. Her one adjustment was to use red/yellow/green buckets and make the refusal language sound like we're protecting customers from a failed self-serve setup, not like Helio thinks small accounts are bad. I have enough to turn this into the one-pager Daniela asked for by Thursday.

Please create a Growth doc titled "Self-serve operating model — eligibility vs product constraints (working draft)" using these notes, and make the caveat clear that the buckets are working inputs for engineering scoping rather than final launch policy: Title: Self-serve operating model — eligibility vs product constraints (working draft) Purpose line: "Working draft for engineering scoping; not final launch policy and not public pricing-page copy." Priya's wording note: "Use red/yellow/green. Refusal rules should sound like protecting customers from a failed self-serve setup, not us saying small accounts are bad." Draft buckets: Green / likely safe to model first: sub-50-seat account, single workspace, standard integration path, one clear admin owner, no import/migration request at setup. Yellow / needs product or support constraint before it can be self-serve: more than one active admin during setup, import request, unclear workspace ownership, integration path that historically requires human troubleshooting. Red / explicit refusal or human-assisted path until proven otherwise: SSO requirement, complex permissions, migration/import volume that would create support load, no identifiable admin owner, or request for custom onboarding. Open questions for Daniela's team: what events prove admin ownership; whether import volume can be gated before setup starts; which failure states route to docs vs human help; what instrumentation must exist before any pricing-page exposure.

Marcus DM'd asking if he can tell Tomás that Q3 is "likely if pricing page work starts now." I want to keep the easy/professional rhythm we have back, but that wording collapses the whole new operating-model gate into a page deliverable and that's not actually the decision anymore. Can you draft a concise DM back that says the Q3 answer depends on the June eligibility, instrumentation, lifecycle, and support gates, not just pricing-page readiness, while still acknowledging why he wants a concrete revenue timeline?

I just finished the hiring-panel debrief for the lifecycle ops contract candidate and need to get my feedback into the packet by end of day. The case work was practical and I do think this person could help Ines with production detail, but I don't think they're ready to own strategy without a stronger analytics partner. Can you turn my rough notes into a balanced scorecard-style assessment with a clear recommendation: yes for a scoped contract/project role, no for a full-time strategic owner role right now?

My notes: Role discussed: lifecycle ops contractor / possible future full-time lifecycle owner. Case prompt: map activation-email changes after an onboarding-trigger adjustment. Observed strengths: found a duplicate trigger; understood holdouts; gave a concrete example from a previous PLG company; was calm when the panel pushed on QA process; would likely pair well with Ines on production detail. Observed gaps: over-indexed on subject-line testing; did not ask about warehouse event reliability until prompted; weak answer on stakeholder pushback; treated segmentation as copy personalization more than measurement integrity. My leaning: yes for scoped contract help under Ines with analyst support, no for full-time strategic owner right now.

Mom texted me a photo of the two watercolors she carried home after Memorial Day, propped up near a window. I wasn't expecting this, but I really miss that quiet kitchen-table painting morning with her after these last two dense workdays. No task here, I just wanted to say the visit is still sitting with me in a good way.

Owen's next cut on EXP-2023-05-expansion-nudge is finally more informative than the n=92 snapshot, but I'm still trying to keep everyone from getting ahead of the data. Treatment is still ahead, around +$5 expansion MRR per account versus control, but the sample is still modest and it's below the original +$8 bar. The lift also isn't broad — it's mostly in accounts with deeper integration usage and more than one active admin. Marcus is already tempted to call it a retained-mid expansion win. I want a measured readout I can use with Marcus, Owen, and Ines: the experiment stays narrow, no copy change, the next cut needs to split integration depth and active-admin count explicitly, and the working hypothesis is usage-readiness rather than a generic day-60 prompt win. Can you draft that?

Daniela's team is doing a monthly reliability review and asked me for a short growth-side note on the Apr 15-12 CS auto-onboarding-nudge outage. I don't want to reopen the churn investigation; I just need to state the impact cleanly for an engineering/reliability audience: the outage created the Apr 17 cohort artifact by shifting activation timing, and it was not a failure of `lifecycle_onboarding_trigger_v2`. Can you draft a factual two-paragraph addendum that makes that distinction without turning into a victory lap?

Priya just pinged after Finance closed May and asked if I'm comfortable letting the board-prep notes say mid-seg churn remains stabilized, without dragging the whole investigation back into the deck. I want a quick data check using the current mid-seg v2 definition, because the old 50-200 versus 75-200 comparison is still very easy to misstate. Can you pull together the latest May-close MRR/churn context for mid-seg v2 and give me a go/no-go recommendation on that sentence, including any caveat we need about the v1/v2 definition change?

After Friday staff I can already see Monday morning getting eaten by meetings, and I need one protected block before I respond to Owen's baseline cuts, Ines's lifecycle-fork map, and Daniela's scoping questions. Please create a private calendar event for Monday, 2023-06-12, from 8:30 to 10:00am America/Chicago titled "Self-serve operating model — baseline + lifecycle review". No attendees. In the body, note that it's to review Owen baseline cuts, Ines lifecycle fork, and Daniela engineering scoping questions.

A Sales Ops comment in the self-serve thread asked whether month-to-month billing should be part of the sub-50-seat offer because it would make small accounts easier to start. I realized billing terms weren't explicit in the four tracks from Tuesday. I don't want to silently add pricing/billing complexity to the scope, but I also don't want to ignore a real refusal-boundary question if billing affects who can safely self-serve. Can you help me decide where billing terms belong in this work — eligibility/refusal rules versus pricing-page constraints — and draft two scope-guard bullets I can drop back into the thread?

Ines sent a first-pass lifecycle fork map for the sub-50 work. It's useful, but it's a little raw: some touchpoints can probably be adapted, some depend on support policy, and some shouldn't move until eligibility is clearer. I want to turn it into triage before Monday so this doesn't become a random pile of copy edits. Can you bucket her notes into safe to reuse/adapt, needs an eligibility or support decision, and definitely not safe yet, with a short rationale for each item?

Here are Ines's notes: SMB / sub-50 fork potential touchpoints: 1. Welcome email: okay if CTA becomes "connect one integration" not "meet your implementation lead." 2. Day 3 activation help: current copy mentions CSM rollout review; probably not safe. 3. Day 7 import nudge: imports can turn into support tickets; needs explicit cap or self-serve docs. 4. Day 10 admin/team invite: copy assumes multiple teams; might not apply. 5. Day 14 webinar CTA: not sure whether Support wants more tiny accounts in live onboarding. 6. Failed integration alert: should route to docs first, not human handoff. 7. First paid month check-in: we need different cancellation-save language. Support handoffs: failed integration twice, import volume > threshold.

I tried to do the usual Saturday-ish Salud reset, but they closed early because the AC was out and the room already felt like a greenhouse. I walked home with iced coffee instead and ended up sketching the condensation ring on the kitchen table. Tiny forced slowdown after a dense week. No task, just context.

I'm doing a Sunday pass on next week and I want a practical sequence, not a polished status update. Monday morning is protected for the self-serve review, but I have competing threads all at once: Owen's baseline cuts for the sub-50 operating model, Ines's lifecycle fork, Daniela's engineering scoping questions, Marcus still wanting a revenue timeline, and the next expansion-nudge cut where I really do not want the +$5 read to turn into rollout momentum. Can you build me a Monday-Wednesday operating plan that sequences the self-serve decisions and the expansion-nudge follow-up, with explicit guardrails against treating sub-50 as a pricing-page launch or the expansion nudge as a broad rollout candidate?

I just came out of my protected self-serve block and the week feels more concrete, but it's still messy. Owen's baseline work needs to split under-50 accounts by deployment and admin complexity, first-week first integration, and the 50-75 seat band instead of turning it into a pure seat-count story. Ines's lifecycle fork map needs to become a triage view, Daniela's questions need red/yellow/green rows that separate eligibility decisions from product constraints, and the Sales Ops billing question needs to live under refusal and eligibility boundaries rather than becoming a pricing-page promise. Can you turn that into a practical checklist for the next few days, with sections for Owen, Ines, Daniela, and the billing guardrail?

Owen reran the May activation mismatch from last week and it was definition drift, not a product drop. The dashboard default was on activation definition v3, while the older notebook was still effectively reading v2 logic, so the gap was just two differently defined views. He labeled the old notebook and isn't using the mixed view in the May-close commentary. I'm relieved I don't have to manufacture an incident out of that.

Sam got the June and early-July rota, and the James Beard semifinalist attention is definitely showing up in more private dinners, press-tasting holds, and later prep blocks. My Helio self-serve work is also taking real shape, so we decided to protect one low-noise shared slot each week after his schedule lands instead of only seeing each other in whatever is left after service and dashboards. For this week we picked Wednesday, June 14, from 8:45pm to 9:45pm at home. Please create a calendar event titled "Low-noise Riley/Sam slot" for that time in America/Chicago, with no attendees. In the body, put: "Protected low-noise shared time. Not a default Helio/service debrief; Kibo walks stay separate unless something actually needs attention."

Priya pinged after Finance's May close and asked if the board-prep notes can say mid-seg churn remains stabilized without dragging the whole investigation back into the deck. I'm comfortable with that, but only if the wording doesn't accidentally compare the old 50-200 seat bucket to the newer 75-200 v2 definition like they're identical. She needs something short today, and I want it clean and boring rather than triumphant. Can you draft two concise board-prep bullets that say the stabilized read under the current v2 definition and lightly keep the historical 50-200 comparison separate?

Daniela asked me for a one-page scoping matrix by Thursday so her team can size the right work. She's right that engineering can only size instrumentation, dashboards, permissions, import, and migration surfaces if I separate who should be allowed into this motion from what the product can safely support. I want the refusal language to sound like we're protecting customers from a failed self-serve setup, not like we think smaller accounts are bad. The rows I'm working with are first integration, admin and permissions complexity, import help, billing exceptions, migration support, and support handoff risk. Can you help me structure a red/yellow/green matrix that keeps eligibility gates separate from product constraints?

Sales Ops came back with a concrete suggestion in the self-serve thread: make month-to-month billing and manual invoice exceptions part of the sub-50 offer because tiny accounts may hesitate on annual terms. I don't want to silently add that complexity to scope or let it turn into a pricing-page promise. My call is that billing exceptions belong in the June eligibility and refusal-risk matrix, not as default offer mechanics unless support and billing workload are explicitly scoped. Please post that as a comment on the small-business-tier scoping doc.

Marcus and Tomás asked Priya and me for a less mushy planning label than "SMB" or "small-business tier" for the Q3 scenario work. I like "Helio Start" as the working name, but only if I say the guardrail out loud in the 11am discussion: it can't become shorthand for a cheap plan or a launch promise before eligibility, refusal rules, instrumentation, lifecycle paths, and support boundaries are ready. Can you give me three crisp sentences to propose the name without letting the room run ahead of the operating model?

The 11am naming conversation actually landed. Marcus and Tomás liked "Helio Start" better than "SMB" or "small-business tier" for scenario work, and I made the condition explicit that it's a working name, not a promise that a cheap plan is launching. Priya backed that in the room and tied the name to the operating-model gates: eligibility, refusal rules, instrumentation, lifecycle paths, and support boundaries all have to be ready before the name implies anything customer-facing or launch-like. Just storing the outcome.

Now that the name landed, someone in the planning-doc thread asked whether we should replace every "sub-50" or "SMB" reference with "Helio Start," including pricing-page sketches. I want to answer quickly before a naming decision turns into public-surface momentum. My rule is: use Helio Start in scenario titles and customer-facing label exploration, keep the measurement tables explicit about sub-50 seats, deployment shape, and eligibility, and do not touch pricing-page copy or imply launch timing. Can you draft a short reply that says that cleanly?

Ines sent a second-pass lifecycle fork map for Helio Start. The useful part is that some existing product-event emails can probably be adapted. The risky part is branches like "import stuck — offer live CS help" and "billing mismatch — reply to CSM," which would quietly create support promises before eligibility and support boundaries are decided. I want to keep the work moving without asking her to rewrite copy that may be excluded later. Can you draft feedback in three buckets: safe to adapt now, depends on eligibility or support policy, and do not touch until the boundaries are decided?

Owen's Thursday cut on EXP-2023-05-expansion-nudge is better than the first two reads, but it's still not a ship decision. Treatment is ahead by about +$5.70 expansion MRR per account versus control at n=248 total, with 126 control and 122 treatment, but the p-value is 0.21, it's still below the original +$8 bar, and the lift is concentrated in accounts with three or more integrations and at least two active admins. Marcus asked whether we can move rollout to 50% next week. My answer is no: keep the flag at 25%, don't change Ines's copy, and have Owen split the next cut by integration depth and admin activity. Can you draft a reply that makes that clear without sounding defensive?

Priya used the mid-seg churn wording in the board-prep notes and came back with one specific need before 4:30: a footnote defining the current cohort without reopening the whole investigation. I want it to say that mid-seg v2 is 75-200 seat paid accounts, the historical v1 50-200 cut is retained only for comparisons, and May's stabilized read is under the v2 definition. I do not want a paragraph about the all-hands or the original spike. Can you write the exact footnote in one or two sentences?

Quick note because I want to remember it: the first protected low-noise slot with Sam actually worked. We sat on the porch for the hour, Kibo wandered in and out, Sam mentioned the press dinner for maybe five minutes, and I did not turn it into a Helio recap. It felt a little artificial at first, but in a good way — chosen time instead of leftovers.

Owen backfilled the baseline cuts I asked for, using activation definition v3 and keeping the 75-200-seat mid-seg v2 cut separate for comparison. The useful result is not a simple seat-count story: under-50 accounts with simple deployment shape and a first integration in the first week activate close to the existing mid-seg+ target range, while under-50 accounts that need permissions, import help, billing exceptions, or migration support lag by more than 15 points. The 50-75 seat band again looks closer to starter behavior than retained mid-seg behavior. I want this to become the measurement spine for the June Helio Start readout without letting anyone summarize it as "under 50 is fine" or "under 50 is bad." Can you help me frame it as an eligibility and admin-complexity signal, with a short "what this does and does not prove" section?

Priya read the baseline summary and asked me to have a Monday pre-read doc ready instead of dropping the findings into Slack. Please create a document in the Growth folder titled "Helio Start pre-discovery readout — measurement spine." It should have five sections: 1) Helio Start is a working name, not a launch promise; 2) measurement method, using activation definition v3, keeping 75-200-seat mid-seg v2 separate, and showing the 50-75 band separately; 3) the baseline finding that simple under-50 deployments with a first-week first integration behave near the target range while permissions, import, billing, and migration complexity lag by more than 15 points; 4) eligibility and refusal-rule implications; and 5) open questions for lifecycle, instrumentation, support, and engineering sizing.

Daniela saw the baseline excerpt and asked a fair scoping question: should permissions, import help, billing exceptions, and migration support be treated as product work her team is supposed to size for Q3, or as exclusion criteria for the first Helio Start eligibility model? My answer is the second one for June. Engineering can note what it would take to support those cases later, but the current readout should treat them as refusal risks so the name doesn't imply a build commitment or a Q3 launch promise. Can you draft that reply?