Scattered clues
- Fifty replays on a Sunday
- Raw SQL guesses
- A fix that waits for the weekend
Analytics tools show where people leave. Anku tells you what to fix.
The stack you already ship
PostHog and Stripe are read-only. GitHub opens one branch and one pull request. Resend sends inside your policy. Identity is read-only. A human merges. Every key is revoked in one click.
Diagnosis before dashboards
Stop scrubbing fifty session replays on a Sunday night.
Joins the three events you named with the billing facts to name the step that leaks.
111 reached the aha event. 170 did not. The gap is recorded, not modeled.
The code writer grounds a defect to a file, writes the fix and one test, and opens a draft PR. A human merges. The send path stays inside your policy.
The recorded case has no repo connected, so its artifact is the spec, not a PR.
A verified receipt needs the Anku link and the same invoice paid inside 72 hours. One event is recovered, not attributed. The books never blend.
The recorded $29 is recovered, not attributed. Never a verified receipt.
Built around restraint
Play A2 queued for n•••@example.com. Waiting on your click.
Recorded gap · [EXAMPLE]
Play A2 queued for n•••@example.com. Waiting on your click.
Recorded gap · [EXAMPLE]
Contract ledger
Scroll or select a card to inspect the source.
Product specimen · Lamplight dark
Cohorts, the grounded fix, the capped note, and the ledger on one sheet.
A paying user's card expired and the last payment failed.
Evidence
Hard questions and current limits
Select a question
Then the case says so. The acquisition stop, the PMF gate, the no-dominant-leak check, and the not-a-funnel stop all stage nothing and hand over the work that can still be done. A no is a deliverable.
Two independent facts: the same invoice paid, and a card update came through Anku's link inside 72 hours. The receipt carries both source ids. If the invoice paid without the link, it is recovered elsewhere, not attributed. The recorded $29 is that second kind.
The public scan reads four surfaces and no further. It cannot see signups, activation, retention, or revenue without a read-only connection. PostHog is read-only. Stripe is a labeled test event. Auth is not connected.
The case says the count is too small for a verdict. Below 30 visitors it is distribution. Between 30 and 99 it is not enough for a verdict. At 100 the stop reopens. Nothing is staged on noise.
Policy decides. You can require a click for every send, or set a daily cap and a quiet window and let a send run inside that policy. A kill switch stops a loop. No live customer send exists yet.
The case is free. Pro is $49 flat when it opens. It is not on sale yet, and the request writes an access request, not a charge. A stop is not a separate charge.
The scheduled run is one weekly Monday pass at 09:00 UTC. Scans are also on demand. There is no rolling multi-day timer.
Then the case says so. The acquisition stop, the PMF gate, the no-dominant-leak check, and the not-a-funnel stop all stage nothing and hand over the work that can still be done. A no is a deliverable.
The limits that stay
Simple flat pricing
Flat workspace price. No cut of recovered revenue. Pro is not on sale yet; request access and we email you when your data can join.
Paste any public SaaS URL. Open Case #0001 across four read-only checks.
Connect PostHog, Stripe, and GitHub for grounded draft PRs, capped sends, and the proof ledger.
Pro is not on sale yet. Request access and we email you when your data can join. No card is taken while Pro is closed; when it opens, cards are entered only on Polar-hosted pages.
Ready when your funnel is
Start with your public URL for a free read-only check. No keys, no card, no discount sequences.