gsingal

Weekly Launch Review — Week of 2026-06-08

93 monitoring launches reviewed. 10 deep-dived (Tier-1), 83 orchestrator-assessed.

TL;DR

1. Pro Plan experiment (abc-pro-plan-pricing-v3) is structurally unresolvable — control deprecated Day 6, only 47 exposures. Pro adoption only 3.5-7.9% of purchasers. Needs human decision: graduate best variant or re-run.
2. Blog migration working — impressions +49%, clicks +53% in recent 14d vs pre-migration. But KPI pipeline is broken (collecting garbage numbers). Fix metric collection, set real targets.
3. Internal linking SEO shows WORSE rankings on 7/8 city pages — opposite of hypothesis. Needs human review before continuing.
4. 5 launches ready to graduate — map-markers, address-autocomplete, mobile-address-input, email-pii-removal, free-listing-deferred-activation. All 30-75 days monitoring with zero regressions.

gsingal

Skylight — Store Checklist & Buy Guide

Project: cpaczek/skylight — decode live aircraft radio (ADS-B) and project planes onto the ceiling at their true overhead positions, mixed with sun/moon/stars/ISS. Date: 2026-06-07 · For: Boston same-day + order-online plan

---

The one thing we will NOT compromise on

The most interesting, valuable part of this project is the radio receiver — the SDR dongle + antenna that pulls real planes out of the air. Everything downstream (computer, projector) is interchangeable. So the rule is:

gsingal

Message Liquidity Diagnostics + Evidence-Backed June Shortlist

Run 2026-05-20 against the prod read replica. Pairs with the ideation menu at docs/strategy/2026-05-18-message-liquidity-ideation.md.

TL;DR

Three SQL diagnostics against the ideation menu confirm one theme: lister responsiveness is the binding constraint on message liquidity, not seeker inquiry volume. Over half of all inquiries get no lister reply within 72h, and listers who ignore their inquiries churn ~12pts worse.

The strategic insight: that 12pt churn gap is best attacked rehabilitatively, not punitively. Making non-replying listers aware of their waiting inbox (nudge them to respond → they get hits → they see RR working → they churn less) is positive-sum for both sides. Routing demand away from non-repliers is the fallback, not the first move, because non-replying is likely a symptom of "I think RR is dead" and writing them off confirms that belief. This reframes the in-flight P1 unread-reminder work from a messaging-v

gsingal

Week of May 4 — Team plan

One-page summary. Detailed plan + checklists in docs/plans/2026-04-30-week-of-may-4-board-plan.md (in repo). Read that for the full skill invocations and per-task details.

---

What we're driving

Single Q2 metric: Demand Distribution — paid rooms with ≥1 inquiry in 14d. Currently 53.1%, Q2 goal ≥60%. Everything below either moves this directly (more messages, fewer blocked messages) or unblocks future work that will move it.

gsingal

PostHog Experiment v5 — Execute Today

Goal: Get the redesigned pricing-abc-pro experiment (v5) live today. The current v4 dashboard shows wrong rates for every metric — abandonment + completion > 100% for some variants — and we cannot make a Day-14 ship decision on it. v5 fixes the underlying event instrumentation, redesigns the metric set, and resets the experiment.

Owners today:

• Mahmoud — review + merge two FE PRs ([A2] + [A3])
• Ahmed — review + merge one BE PR ([A1]), then deploy + verify + run launch
• Gaurav — available for questions; will not act on these PRs

---

gsingal

QA Smoke Deterministic Reset Foundation

For Claude: REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

Problem & Why Now ← Dimension 1

Every smoke run inherits state from prior runs because QA server state is never fully reset between runs. The team has been patching symptoms for months — ownership guards for stale listing.json (PR #4283), silent-skip fallbacks when the demo user is fraud-flagged (PR #4279), test.skip() cascades when ephemeral lister state is wrong, content tests that accept "any of three states" as passing (#3655 Playwright specs). Each workaround makes the suite weaker: it proves fewer things, accepts more failure modes as "green," and hides real regressions under fake passes.

The 2026-04-21 smoke audit made the cost concrete: 4 of Megan's 7 dispositioned findings were not real app bugs but cross-run state drift. The 3 remaining required app-code fixes in PR #4279 — but those fixes only unblock the workaround

gsingal

Pro Plan Clean Extraction — Remediation Plan (v5)

For Claude: REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

Review history:

• v1: Full-file diff-and-apply. Codex R1: controllers carry security regressions. → REVISE
• v2: Hunk-level triage with denylist. Codex R2: Room.php missing, frontend misclassified, Stripe broken. → REVISE
• v3: 4-category system. Codex R3: "clean diff" files have removals, Payment.vue copy-then-restore unsafe. → REVISE
• v4: Master-first principle. Codex R4: Plan broke its own rule with "Maybe" copy items. PlanService missing buildPlanCode/getGroupedPlans. Non-failing patch loop. → REVISE
• v5: No "Maybe" — every file definitive. PlanService fully specified. Fail-fast on apply.

gsingal

Deploy Cadence + Process — Proposal for Team Review

UPDATE 2026-04-13 PM — Cadence finalized: Tue + Thu pushes.

After team feedback (Ahmed +1'd alternate-day on this gist; Gaurav locked in the specific days), the cadence is:

Day	What happens
Mon	Build deployment/ branch → forward-integrate master → QA in PM → Megan signs off by 5pm
Tue AM	Push Mon's approved package → prod

gsingal

KPI Measurement Guide

Single source of truth for how RotatingRoom defines, validates, and tracks metrics. Referenced by: CLAUDE.md, /launch, /writing-plans, /reviewing-plans, /launch-metrics, /monitor-launches

Last updated: 2026-04-13

---

Philosophy

gsingal

Inquiry → Retention Deep Dive

First-time paid subscribers only (n=2,099). Endpoint: subscription still active. Since July 2025.

---

1. Window Comparison: First 7d vs 14d vs 21d vs 28d

Question: Which window best separates retainers from churners?