Nobody trusts their numbers.
GA4 says one thing, Stripe says another, and the tracking plan in someone's head stopped matching what actually fires months ago. i find the gap and put it in writing, for a fixed price, on a fixed clock. no retainer, no discovery-call theater.
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
no checkout here. you email, we scope, i invoice half upfront (direct bank transfer), the rest is due on delivery.
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 am i
i'm Arjun, the maker of smolanalytics (open source, MIT). the audits run on the same machinery the product ships. the longer story is in why i built smolanalytics.