Pricing
Measure a launch

Make your next launch measurable.

Describe the change and what you expect it to do. Skene drafts the measurement plan, finds the signals still missing, and reads the result after launch.

Start freeSee how plans work

No card required. Sign in, connect a source, describe what you are shipping.

Illustrative product view. One document connects plan, evidence and result.
plan
Trial activation
target4.0%
required evidence
setup_completedaccount_id
SupabasePostHogMixpanelBigQueryResend
Before launch

The plan names what is missing.

Verification checks each required event and field against the available evidence. Ready, missing and unverified describe different situations. A named requirement tells your team what needs attention.

Illustrative product view. The check names the missing evidence.
plan
setup_completed
event
account_id
user_id
plan
source
events + fields5/5
check
Ready
After launch

See whether your launch is moving toward its goal.

Follow the milestones you defined in your plan. See which features users are adopting, where progress stalls, and whether activation is moving toward your target.

Illustrative product view. Tracked milestones connect feature use to activation. Sample activation rises from 3.2% to 3.8%, below the 4.0% target.
Activation experimentLatest cohort · 1,000 new users
  1. 01Connected a source120 users12.0% of cohort
  2. 02Created a workflow76 users7.6% of cohort
  3. 03Completed first run38 users3.8% of cohort

Activated = completed all three milestones within seven days.

Activation rate3.8%

Up 0.6 percentage points from before launch.

Moving toward the 4.0% targetTarget not yet reached
Before launchLaunch weekFollowing week

Each cohort has a full seven days to activate.

Milestone counts include every preceding step. Change shows direction, not what caused it.

The next launch

Start the next version with the evidence still attached.

A check can suggest a Next version focus. Keep the previous plan on the record while you decide what to test next.

Keep the result. Change the next hypothesis.

Create next version preserves the previous hypothesis and verification results. The new version is where the next change belongs.

Illustrative product view. Plan progress and measured results are separate.
plan
Launch ready
5/6workflow
FAQ

Before you describe what you're shipping.

The questions a plan owner asks first.

What happens after I click Start free?
Sign in, create a workspace and connect a source. The free audit shows what your product already collects. A plan scopes the evidence to a change you want to launch.
What does the GitHub App and Supabase connection touch?
The GitHub App requests read and write permissions so it can post reviews and propose fixes. It never pushes to your default branch. Supabase access starts read-only and can be upgraded to read-write if you choose.
What does the free tier include?
The free audit returns one audit of what your product collects, once per workspace, with no card required.
What happens once the after-launch Check needs real data?
The plan needs a success formula and data for its inputs. Finding an event in code does not create a metric value. Run check uses the data available for the reporting window and shows where each input came from.

Give the next launch a result you can read.

Start freeSee the release check