Coming soon
Track user behaviour
Build what matters
Ship every feature to a slice of your users first. Measure it. Keep what works.
How it works
Four steps. The same four every time.
Track
Install the SDK. One line. Somar captures what your users actually do.
These are your Signals.
Experiment
An experiment is your main branch against a change.
Base — main — what your users get today.
Candidate — new-onboarding — the change you’re testing.
Pick who sees it — 10% of your users. Pick how you’ll know — before it ships.
Analyse
Watch it while it runs, not just when it ends.
“Retention is up 13% on the new onboarding. Revenue is flat. Confidence 96%.” — Somar AI
Ship
Keep the winner, or go back to control.
Cancelling is a toggle, not a rollback. It works at 3am from your phone.
What your users actually do — your metric, answered per version.
Honest when it doesn’t know — intervals that straddle say “not enough data”. A win overall that loses on paying users is a loss.
- Merged — live in production, flag at 0%, nobody sees it yet
- Flag opened to 10% of new signups — guardrails watching errors and churn
- Verdict: variant B won — loser killed, winner ramps to 100%
Every release, graded. Shipping and releasing are separate — cancel is the flag to 0%.
Drop-off concentrates at step 2. I’ve written two variants —
inline skip, and a shorter form — on branch somar/onboarding-v2, behind
one flag. The PR is open.
Build what matters — and know that it did.
Join the waitlist — we’ll email you when Somar launches.
Join the waitlist