What changed
FACT (cited): Google Play expanded alternative billing with lower fees for UK/EEA developers (Play blog, 2026-06). FACT (cited): Stripe Projects now lets AI agents provision and configure Stripe integrations end-to-end (Stripe blog). FACT (cited): Google AI Studio lets non-developers ship installable native Android apps from a prompt. HYPOTHESIS: the combination creates a cohort of publishers who switch billing without realizing they inherit merchant-of-record obligations (VAT registration/remittance, consumer-rights refunds, chargebacks).
Why now
The billing choice just expanded and agent-provisioned Stripe setup just shipped; the first switcher cohort is deciding now, before tax-notice horror stories educate the market. HYPOTHESIS: a 6-12 month window before content marketing from Paddle/Stripe closes the awareness gap.
Converging signals
Play UK/EEA alternative billing (platform) + agent-provisioned Stripe integrations (platform) + prompt-built Android publisher flood from AI Studio (android). The abundance is cheap self-billing; the second-order scarcity is compliance-aware migration.
Customer pain
HYPOTHESIS — no demand_evidence was provided. The inferred pain: an indie dev switches to save 10-15% in fees, then discovers EU VAT registration/OSS filings, refund-rights handling, and chargeback management that Play-as-MoR previously absorbed. Real but currently invisible pain; zero complaints/hiring signals were supplied to prove anyone feels it yet.
Who pays
UK/EEA Android developers and small studios with meaningful digital-goods revenue (roughly >€5k/mo, where fee savings exceed compliance cost). HYPOTHESIS: below that threshold the rational answer is 'don't switch,' which a free calculator answers in one visit — no recurring payment.
Solved today
FACT (general knowledge, not from sources): existing merchant-of-record providers — Paddle, Lemon Squeezy (now Stripe-owned), FastSpring — already sell exactly this safety net; Stripe Tax + accountants cover the DIY path; RevenueCat handles subscription plumbing. The 'switcher' just picks an MoR checkout instead of raw Stripe.
Why current solutions are bad
The gap is narrow: existing MoR providers are web-checkout-centric and none packages a Play-specific 'should you switch, and here is the compliant stack' migration. But that gap is a feature/content play for them, not a moat for a newcomer.
Proposed product
A two-part product: (1) free switch-or-stay calculator (Play fee tier vs. alt-billing fee + Stripe fees + VAT/OSS burden + support load) as lead gen; (2) paid migration service/tool that provisions Stripe + Stripe Tax (or routes to an MoR) with correct UK/EEA VAT configuration, refund-policy templates, and a compliance monitor that alerts on threshold crossings (VAT registration triggers, OSS deadlines).
MVP version
Calculator (static app, 2-3 weeks) + productized migration checklist/provisioning script using Stripe's agent-integration APIs. Do 5 migrations manually at a fixed fee before automating.
30-day build
Ship calculator; post in r/androiddev, Indie Hackers, Play developer communities; collect emails and switching-intent data — this doubles as the demand validation this brief currently lacks.
60-day build
Sell 5 fixed-fee migrations (£750-1,500 each) as concierge; codify into provisioning templates; publish 'what MoR meant' teardown content targeting 'Play alternative billing VAT' searches.
90-day revenue plan
Concierge migration fees plus first subscriptions to the compliance monitor (£29-79/mo). HYPOTHESIS: realistic first revenue day 90-150, not 30.
Distribution path
SEO/content on a brand-new question ('does Play alternative billing save me money'), Reddit/Indie Hackers, Android dev newsletters. Weak: no owned audience in this niche, and the founder's demonstrated channels (demonstrated value in industrial/gov niches) don't transfer directly.
Pricing hypothesis
Free calculator → £990 fixed-fee migration → £49/mo compliance monitor. HYPOTHESIS: unvalidated.
Technical difficulty
Moderate. Calculator is trivial; Stripe+Tax provisioning is well-documented; the hard part is keeping UK/EEA VAT logic correct — an ongoing content/expertise cost, not a code cost.
Legal / regulatory risk
Real: the product's core output is effectively tax advice to EU/UK taxpayers from an unlicensed US operator. Mitigable with disclaimers and partnering with an EU VAT accountant, but errors create liability and one public miss kills trust. The founder must NOT become the MoR himself — that's a balance-sheet business.
Platform dependency
High on two axes: Google can change alt-billing fees/terms (it has iterated repeatedly), and Stripe/Lemon Squeezy can ship this exact guidance natively. Both have direct incentive to.
Founder fit
Mixed. Matches his compliance-monitor/automation pattern and per-transaction monetization instinct. But this is NOT the proven government-portal shape (no mandate compels anyone to switch — switching is optional, which inverts the forced-buyer dynamic), the buyers are UK/EEA devs he has no channel to, and EU VAT is outside his operational-credibility domains. Lesson 'government-portal mandates fit best' (conf 0.80) applies negatively here.
Breakout potential
Moderate: could expand to Apple's EU alternative billing, web-shop external purchases, and a general 'app-store exit compliance' suite if third-party billing keeps opening up.
Final recommendation
KILL as a standalone product bet; REVISIT if the 30-day calculator test produces real switching-intent signups. The problem is plausibly real but currently evidence-free, the incumbent answer (use an existing MoR) is one Google search away, and the buyer is optional-not-forced — the inverse of this founder's proven wedge. The only cheap, sane move is the free calculator as a demand probe, not a product build.
Next action
If pursuing at all: ship the free switch-or-stay calculator in <3 weeks and post it to r/androiddev and Play dev communities purely to harvest demand evidence (emails + inputs showing revenue bands of would-be switchers). No further build until >100 qualified signups.