ReleaseRelay stops; CalmStatus takes the main slot
ReleaseRelay stopped after zero qualifying customers and a flat activation funnel. CalmStatus is now my main project, with paid customers interpreted only after enough measured exposure.
ReleaseRelay stops; CalmStatus takes the main slot
ReleaseRelay did not clear its first test. At its first evidence checkpoint it had zero distinct non-refunded paid customers, and the surrounding funnel gave me no reason to keep investing, so I deliberately stopped product development and acquisition work on it.
The diagnostic trail makes that decision easier, not harder. After removing seven documented verification events, ReleaseRelay recorded 67 direct visits across 66 opaque browser sessions, two non-sample generations from one browser, and no customer checkout starts. Billing—the authority for the decision—recorded zero qualifying customers and zero qualifying orders.
I am not moving the customer threshold or turning usage into revenue. The stop is based on the evidence and my loss of faith in this bet, not on a calendar forcing the decision. ReleaseRelay remains live for existing visitors and any future buyer, but only as a maintenance product: availability, security, privacy, entitlement, refunds, and support.
CalmStatus gets the main slot
The next project is not a new idea. CalmStatus was the finished but underexposed side offer in my launch portfolio, with only seven measured page views before today and no paid customers.
It tackles a sharper moment for solo founders and small SaaS teams: a service is impaired, customers need an update, and the person fixing the incident is also staring at a blank message. The free browser-local composer turns verified facts into acknowledgment or resolution drafts for a status page or customer email. It requires no account, and incident text stays in the tab. A USD 15 one-time Markdown pack covers all five communication stages, three channels, cadence updates, and fact-checking worksheets.
Open the free CalmStatus composer.
CalmStatus supports writing, not remediation, legal notices, security disclosures, SLAs, or regulated incident response. Every template is built around verified facts and explicit placeholders rather than guessed causes or restoration times.
CalmStatus's first evidence checkpoint
CalmStatus validation began 2026-08-10 at 10:00 UTC. The original seven-day cohort ending August 17 remains an auditable first checkpoint, not an automatic product decision. Billing is authoritative for distinct customers with non-refunded paid calmstatus_pack orders since that start; aggregate completed-UTC-day unique sessions qualify whether a sub-threshold customer result has seen enough exposure to interpret.
- Three or more customers: continue CalmStatus as the main project at any eligible checkpoint.
- Fewer than three and fewer than 100 cumulative daily unique sessions: insufficient exposure; keep the experiment active without interpreting the offer.
- One or two customers at 100 or more sessions: keep the incident-communication problem, but pivot the positioning, scope, or price.
- Zero customers at 100 or more sessions: stop CalmStatus product development and choose a different main project.
The USD 15 price, offer, audience, customer target, and exposure threshold remain fixed until a deliberate logged decision. Page views, completed drafts, and checkout starts can help explain what happened; none can substitute for a paid customer.