fixed price · half upfront · 30 day money back

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.

tracking audit
$1,500 fixed
delivered in 2 days

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.
half upfront. 30 day money back if the report tells you nothing new.
book the tracking audit
usage-billing audit
$2,000 fixed
delivered in 2-3 days

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
half upfront. 30 day money back if the report tells you nothing new.
book the billing audit
mcp integration sprint
from $2,500 scoped, $2,500 to $8,000
delivered in 3-10 days

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
half upfront. 30 day money back if it doesn't do what the written scope says.
scope an mcp sprint

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.

questions

How fast is delivery, really?
the clock starts when the upfront half and access (read-only is fine) have both landed. tracking audit: 2 days. usage-billing audit: 2-3 days. mcp sprint: 3-10 days depending on the scope we agree in writing before you pay anything.
What if my numbers turn out to be fine?
then the report says so, with the evidence. and if it told you nothing new, the guarantee applies: everything back, within 30 days, no argument. a clean bill of health you can actually trust is the good outcome, but you don't have to pay for it.
Why should I trust you?
fair question, and i won't fake testimonials: this is a new service. what i can show you: the audit runs on tooling that is open source and public (smolanalytics ships plan check --source=posthog, which reads your data directly), the mcp stack is the same one i shipped for my own products (a 47-tool MCP server, OAuth 2.1, stdio + HTTP transports), and the terms put the risk on me: half upfront, everything back within 30 days if it wasn't worth it.