Your end-to-end tests, written for you.
Give me a URL that is already running. I write the tests that cover the flows that cost you money, get them green, and wire them to your pull requests, for a fixed price on a fixed clock. Or I watch your production site every night and tell you the day something breaks.
Give me a URL that is already running. I write the 10 to 15 sentences that cover the flows that cost you money, run them until they pass, and wire the pull-request workflow so every push after that is checked.
- · tests/*.md: one English sentence per flow, yours to keep and edit
- · Recordings for every passing run, so replays make no model call
- · The GitHub Actions workflow, opening one comment per pull request
- · A published run you can open, for each test, showing what it checked
Three to five read-only checks against your live site, every night. The day one goes red you get the run, with what the browser saw. Nothing is ever submitted, bought or booked on your site.
- · Your checks, one English sentence each, agreed with you first
- · A nightly run against production, replayed with no model call
- · The run link the day anything goes red, not a dashboard to check
- · Cancel any time from the receipt email
I read your GA4 / PostHog / mixed setup and diff what actually fires against what you think fires.
- · A written report: every broken, missing, or double-counted event
- · What each one is costing you, in numbers
- · A fix list ordered by impact, not alphabetically
- · Runs against your existing data. You migrate nothing.
For SaaS that bills on usage: when did you last reconcile what you metered against what you invoiced?
- · Metered vs invoiced, reconciled line by line
- · The leakage number and exactly where it comes from
- · A written report + ordered fix list
- · Most teams that have never reconciled find underreporting somewhere
Your product, operable from Claude and Cursor. A real MCP server, not a wrapper demo.
- · An MCP server for your API: tools, prompts, stdio + HTTP transports
- · OAuth 2.1 if your users connect from claude.ai
- · Docs + a working setup your users can follow
- · Scope agreed in writing before any money moves
The two testing offers are paid by card through Dodo Payments, who handle tax and receipts. The audits are scoped first: you email, we agree the scope, I invoice half upfront.
Who this is for
indie founders and small SaaS teams who feel the gap between their dashboard and their bank account, and don't have a data team to throw at it. if you have a data team, you probably don't need me.
Who I am
i'm Arjun, the maker of smolanalytics. the audits run on the same machinery the product ships. the longer story is in why i built smolanalytics.