What changed
FACT (cited): Google Play now permits alternative billing at lower fees for digital goods in the UK/EEA (June 2026 announcement). FACT (cited): Google AI Studio lets non-developers ship installable native Android apps from a prompt. FACT (cited): Stripe Projects lets AI agents provision payment integrations end-to-end. HYPOTHESIS: the combination produces a wave of inexperienced publishers who switch billing without realizing they inherit merchant-of-record obligations Google previously absorbed.
Why now
The billing-choice expansion and agent-provisioned Stripe are both weeks old; the first cohort of switchers hits its first EU VAT/OSS filing window within months. The information asymmetry (fee saving is visible, MoR liability is invisible) is largest right now, before content marketing from MoR vendors saturates the topic.
Converging signals
Play alternative billing in UK/EEA (platform) + prompt-to-app publisher surge (android) + one-click agent Stripe provisioning (platform) => switching is frictionless while the compliance consequence is hidden. The causal chain is plausible, but note: every link about *publisher behavior* (that many will switch, and switch naively) is HYPOTHESIS — the signals prove capability, not adoption.
Customer pain
HYPOTHESIS — no demand_evidence was provided. The claimed pain (fear of VAT liability, EU consumer-law exposure after leaving Play billing) is structurally plausible but unproven in this input: zero complaints, zero questions, zero hiring signals. Worse, the pain is latent: the target buyer typically does not yet know they have the problem, which means the product must first educate before it can sell.
Who pays
Two candidate payers, both unproven here: (1) UK/EEA app developers with meaningful Play revenue weighing the switch — they might pay for a decision report; (2) MoR providers (Paddle-type) paying referral/affiliate fees for qualified switchers. Payer (2) is the more realistic near-term revenue and is genuinely reachable (partner programs exist — HYPOTHESIS, not cited in input), but that makes this a lead-gen media asset, not a sellable product with recurring revenue.
Solved today
HYPOTHESIS: accountants specializing in EU VAT/OSS, MoR vendors' own marketing content and fee calculators, and blog posts/forum threads. Paddle, Lemon Squeezy (Stripe-owned) and RevenueCat all publish exactly this 'true cost of self-billing' content for free as top-of-funnel marketing.
Why current solutions are bad
Existing content is vendor-biased (MoR providers have an incentive to overstate compliance burden) and generic (not Play-specific, not modeling the exact new UK/EEA fee tiers). A neutral, numbers-in/verdict-out calculator specific to the June 2026 Play terms does not obviously exist yet. That said, the gap is thin: any MoR vendor could ship the same calculator in a week.
Proposed product
Free interactive calculator (Play revenue, mix of UK/EEA sales, refund rate → net saving or loss after service fee delta, PSP fees, MoR fees, VAT/OSS filing costs, accountant costs) that gates a paid output: a personalized 'switch / don't switch / switch-via-MoR' report with a compliance checklist and a guided MoR-selection wizard wired to referral links.
MVP version
Single-page web calculator with the June 2026 Play fee tiers hard-coded, a 10-question wizard, and a generated PDF verdict report. No accounts, no backend beyond Stripe checkout for the paid report. 2-3 weeks of AI-assisted build; founder has capital to pay for design polish and a VAT-specialist accountant to review the logic once (~£1-2k, per the capital-and-runway lesson this is not a penalty).
30-day build
Ship calculator + landing page. Seed it in r/androiddev, IndieHackers, X Android-dev circles, and the AI-Studio prompt-to-app communities. Apply to Paddle/Lemon Squeezy partner programs. Success metric: 500 calculator completions and >3% paid-report conversion, or kill.
60-day build
Add the MoR-selection wizard with referral tracking. Publish 5-8 SEO pieces targeting 'Play alternative billing VAT' style queries while competition is near zero. Pitch 2-3 MoR vendors a flat sponsorship of the calculator.
90-day revenue plan
Blend of paid reports (£99-£199), MoR referral commissions, and one sponsorship. Realistic 90-day revenue is low four figures — this is a modest cash asset, not a scaling wedge, unless report volume proves surprising demand.
Distribution path
SEO on brand-new query space, developer communities, and the MoR vendors themselves (they benefit from a 'neutral' referrer). No ad spend needed. Weakness: the founder sells through demonstrated value, which the free calculator does deliver, but reaching unaware buyers requires content marketing, which is slower than his proven forced-buyer motions.
Pricing hypothesis
Free calculator; £99-£199 one-time personalized verdict report; MoR referral commissions (typically % of first-year volume or flat bounty — HYPOTHESIS); £2-5k calculator sponsorship per MoR vendor per quarter.
Technical difficulty
Low. The hard part is not code, it's getting the VAT/consumer-law logic right — solvable with one paid specialist review. Founder's AI-assisted prototyping makes the build trivial.
Legal / regulatory risk
Moderate and real: the product gives quasi-tax/legal guidance. Mitigate with 'educational, not tax advice' framing and an accountant-reviewed rules engine; the paid report edges toward regulated advice territory in some member states — keep it decision-support, not filing advice. HYPOTHESIS: manageable, but it caps how prescriptive the paid report can be.
Platform dependency
The product itself is a web app with no marketplace approval risk, but its entire premise depends on Google's UK/EEA billing terms staying stable; a Google policy revision or a Google-published official calculator kills it overnight.
Founder fit
Mixed — and notably NOT the proven government-portal shape. There is no forced filer and no portal to automate; the buyer has a choice and is unaware of the problem. It does play to systems thinking, fast prototyping, and compliance framing, but monetization is affiliate/content, which is outside his proven per-transaction filing model. The accumulated lesson that portal-mandate opportunities fit him best (confidence 0.80) argues this is a B-fit at best.
Breakout potential
Limited as scoped. Plausible expansion: the calculator is the top of a funnel toward an actual per-transaction product — a 'mini-MoR compliance layer' (VAT OSS filing automation for switched developers), which WOULD resemble his ELDT shape (recurring compelled filings, per-filing fee). That follow-on, not the calculator, is where durable revenue would live — but OSS filing automation is a materially harder, heavier-compliance build.
Final recommendation
HOLD / cheap smoke test only — do not commit the 3-6 month build budget. The convergence logic is sound and the build is trivially solo-feasible, but with empty demand_evidence, an unaware buyer, affiliate-dependent monetization, and incumbents positioned to give the product away free, this fails the sellability bar as a standalone product. Worth a 2-week, low-cost validation (landing page + calculator + paid-report gate) purely to harvest real demand data; treat any signal about VAT-filing pain as scouting for the more founder-shaped follow-on (per-filing OSS automation). Do not prioritize over any live government-portal-mandate candidate.
Next action
Spend ≤2 weeks and ≤£1k: ship the free calculator with a £149 gated report, post it to r/androiddev and IndieHackers, and measure completions and paid conversion. Kill if <3% of completers click the paid gate; escalate to the MoR-selection wizard and vendor sponsorship pitches only on evidence.