Consulting
Mobile payments architecture audit.
A focused, two-week engagement for consumer Android apps with >100K MAU. I find the cracks in your subscription stack before your users do.
Who this is for
- You run a consumer mobile app with subscription revenue on Google Play.
- You have >100K MAU and recurring billing complexity (renewals, upgrades, refunds, edge cases).
- You suspect there’s revenue leakage, hidden instability, or accumulating tech debt in your billing stack — but no one internally has time to dig in.
- You want a senior outside read in writing, not a sales pitch.
What you get
- Architecture review. I read your billing-related code, your subscription state machine, your receipt-verification flow, and the surrounding observability. I look at it the way I look at Adobe Acrobat’s — the same lens that ships Play Billing changes to 95M+ MAU without incidents.
- Findings report. A written document organized by severity (P0/P1/P2), each finding with: the issue, the user-visible impact, the revenue/stability risk, and a concrete remediation. Nothing vague.
- Readout call. A 90-minute video call with your engineering & product leadership to walk through findings, prioritize, and answer questions live.
- 30 days of async follow-up. As your team starts the remediation work, you can email me questions or share a PR for spot review. No new meetings, just unblocking.
Scope & pricing
Pricing is intentionally bespoke — complexity varies. I’ll give you a fixed number after a 20-minute scoping call.
Why me
I own end-to-end stability of Adobe Acrobat Android’s in-app payments stack — one of the most-installed Android apps in the world. I’ve shipped Acrobat Mobile’s first cross-product subscription upgrade / downgrade / cross-grade architecture (Jan 2026, zero production incidents since launch, adopted by other Acrobat apps), instituted the controlled-rollback playbook for payments, and reduced payment-related incidents 23% quarter-over-quarter.
What I bring isn’t generic mobile architecture advice. It’s a specific lens on subscription state machines, revenue observability, and the failure modes that show up at billion-install scale.
Get in touch
Tell me a bit about your app (MAU, what flavor of subscription complexity, any recent incidents), and I’ll come back with a 20-minute scoping-call slot.