reference
Open questions for Blair — 2026-05-20
One-sheet of everything currently waiting on a call from Blair as of 2026-05-20 — pricing first (launch packaging trio, Free-tier dial defaults, token budgets), then hiring, naming, architecture sign-offs (ADR-0006), privacy (Allen's late-May review), and operational items. Two hard near-term deadlines: May 22 for the Free-tier circuit-breaker rubric and ADR-0006 signature.
Blair —
Here’s everything currently waiting on a call from you. Pricing first since you asked. Anything where I have a read I’m flagging it; anything where I genuinely don’t have one I’m just asking.
Pricing & packaging
1. Launch packaging — three calls that should land together.
Best decided as a trio because they reinforce each other.
- 50% off Pro for 3 months for the first 100 paid customers — yes or no?
- One-time 30-day Pro trial for existing MP customers as a launch promo — yes or no?
- Brand presentation — “MemberIntel” (standalone) with a Pro upsell, vs. “MemberIntel Free,” vs. “MemberPress Insights Free”?
My read from your May 11 prep: no launch discount (it distorts the 60-day conversion read), yes 30-day trial for existing MP customers, brand it “MemberIntel” with Pro as the upsell. Worth confirming before Santiago drafts launch comms in Phase 4.
2. Free-tier circuit-breaker dial defaults.
Santiago owes you the rubric by May 22 (two days). The shape of the call you’ll need to make: ship Free with conservative defaults (assume 3% conversion, protect margin) or generous defaults (assume 5%+, protect the conversion engine). The dials are runtime-tunable — but ship defaults set the early read.
3. Token budgets per tier.
Seth and Santiago are bringing you a ceiling, not a number. Still owed. The number that comes back will land inside the May 22 rubric above.
4. Quarterly Free-tier review rubric.
Approval is downstream of #2 — same rubric drives both. Ready to sign when #2 lands.
Hiring & team
5. Senior AI Engineer.
Target close mid-June. Pipeline depends on your external posting + interview availability. Where are we? If sourcing has slipped, mid-August “productive” target slips with it, and that pushes the eval-suite milestone.
6. Sam’s transition from MP support → Brain Content Lead.
Gated on the MP support-assist light reducing his ticket load. Date not committed at the May 11 session — need it pinned, because Sam’s transition gates the brain growth target (200+ approved entries by month 6 of V1 launch). See Sam’s JD.
7. Possible second support agent on the brain content team.
You floated “possibly one other technically-inclined support agent” on May 11. Still open. Tied to #6 — capacity math only works if it’s just Sam, or just Sam + 1, not undefined.
8. Russ — full-time conversion date.
Decision point end of Phase 2 (June 30). Worth pre-flagging if direction is leaning either way — the Phase 3 design load assumes Russ is full-time by then.
9. Ronald’s final title.
JD is drafted at /ronald-jd. Currently labelled “Backend / Platform Engineer (working title).” Other options: “Senior WordPress Engineer” or something else. Your call.
Naming & brand
10. Final product name.
Domains secured for two candidates. You were leaning toward standalone “MemberIntel” at the May 11 session but no final decision. Trademark check still owed — that’s a Phase-4-blocker, not a today-blocker, but worth not letting it drift.
Architecture sign-offs
11. ADR-0006 — LLM tracing tool.
Seth’s recommendation is self-hosted Langfuse on Cloud Run (avoids routing user prompts through a third party — a GDPR/CCPA call, not just observability). Skeleton was owed Monday; signature owed by May 22. This is the last V1 observability piece open.
12. Eval release-gate threshold.
Seth brings the methodology at the Phase 3 milestone. You sign the pass bar (the actual number that gates release). Heads up that this lands later — flagging now so you’re not surprised at Phase 3 when the methodology shows up needing your number.
Privacy / counsel
13. Allen’s late-May architecture review — is it on the calendar?
If it slips, the June 1 gate slips, and that’s a public call you’d have to make about delaying GA. The memo Allen will read is at /privacy-strategy-for-counsel. Active panel for it is Brandeis, Lessig, Sunstein, Rawls.
14. Audit log retention.
Deferred to Allen’s review. If he flags retention as a V1 obligation, this promotes to a launch-gate item — not a V1.5 deferral. Worth knowing before you walk into his session.
Operational
15. Daily KB review.
You committed at the May 11 session to start each morning on memberintel.caseproofagent.com, answering open questions and reviewing the standup. The daily standup email reminder is wired up — confirm it’s landing in your inbox.
Already deferred (not asking — just so you know what’s waiting)
These have explicit reopen triggers; not on your plate until the trigger fires:
- BuddyBoss launch date / partnership terms / admin UX / REST API / second content lead / multi-platform accounts / BB support model — reopen when V1.5 ships AND BB Memberships has a confirmed launch date.
- Cross-pollination cadence — reopen when the brain has 30+ playbooks.
- Customer support model for Free users — reopen at 1,000 Free signups or the first support escalation, whichever comes first.
That’s everything I have open for you as of today. Tell me which ones you want to talk through live vs. async, and I’ll route accordingly.
— Seth