Know whether you can measure it, before you ship it.
You describe what you are shipping. Skene names the signal nothing records while there is still time to add it, then checks after launch whether the number actually moved.
No card required. Sign in, connect a source, describe what you are shipping.
Not a score. A verdict.
Activation: first project within seven days of signup. Draft reviewed. Gathering evidence from code and arriving events.
signup_completed · not found in code or eventsKnow before you ship
A plan is marked ready to launch only when the signals it needs already exist.
A verdict, not a score
The missing signal is named. Nothing arrives as a number to interpret.
Checked after launch too
The Check runs the success formula against real data and keeps the history.
It names the signal, not a score.
None of the three evaluations reached launch ready. The third needs a trial_expiring signal nothing records, so its metric cannot be computed.
| Evaluation | Metric | Confirmed |
|---|---|---|
| Activation: first project within 7 days | First-week rate | 0 / 10 |
| Dormant accounts resuming usage | 30-day resume rate | 0 / 13 |
| Convert an expiring trial by email | 7-day conversion rate | 0 / 2 |
The Check says how much to trust the number.
Every verdict shows the previous number and reads up to ten prior runs. It flags a history too short to trust.
- Cadence
- Hourly
- Window
- Plan's own, else 30 days
- Query shape
- One bounded aggregate
- SQL accepted
- None
- Rows returned
- Never, single number only
Nobody is asked to write event names.
What reaches engineering is a named signal and the place it is missing, or nothing when the tracking is already there.
Launch not ready.
trial_expiring is required by the success formula and nothing records it. Add the signal, and this plan verifies on the next run.
Before you describe what you're shipping.
These are the questions a plan owner asks first.