S1 · App Store makeover: go-to-market

Why the old price was too high

The prompt test: price is capped by the buyer's cheapest credible alternative, not by agency rates. If 80% of a service can be had from a $10 tool or a $30 gig, it can't carry a $500 price on its own.

The new shape of S1

What this means for the math: S1 alone no longer reaches $10k; at ~$100 it would need ~100 sales a month. Its job is to open conversations with app studios that S3 and the monthly plan then monetise. These are my estimates, not measured prices.

Who buys and where we find them

Aim at the paying middle: big enough to earn, too small for an agency. A typical subscription app earns about $72 a month after a year, so the money is in the top quarter.

At 3,000 emails a month this pool lasts 3–5 months. After that, growth comes from Store care renewals, Canada and newly growing apps (about 50k new Play apps launch each month).

Where we look, legally: Play app pages at human pace, Apple's Search API (about 20 calls a minute), Apple product pages, seller websites. Never Play search, review or batch endpoints.

Fix before launch: your ASO tool's Play suggest, search and review calls (where the 229k autosuggest set came from) and its iOS suggest call use paths the stores' robots.txt blocks. Keep them out of S1.

The result-first experience

flowchart TD
  A["Detector flags an app: English-only listing, unanswered reviews"] --> B["Agent builds their sample page"]
  B --> C["Email with one link"]
  C --> D["They see their page before and after, 4 languages, 3 replies"]
  D --> E{"Ready to buy?"}
  E -->|"question"| F["AI assistant answers and says it is an AI"]
  F --> E
  E -->|"yes"| G["Payoneer link or wire"]
  G --> H["Intake: tier, languages, approve flagged facts"]
  H --> I["Full build, automatic checks, your 10-minute look"]
  I --> J["a. Files"]
  I --> K["b. We apply through a one-app role"]
  I --> L["c. API key for replies"]
  J --> M["Day-30 re-score and Store care offer"]
  K --> M
  L --> M

Open the listing preview mockup

Risks and how we handle them:

• iOS waits for their next build: name, subtitle, keywords and screenshots change only with a new version (promo text and custom product pages don't), so we pitch "your next version".
• Store review: automatic checks block competitor names, prices, unprovable claims, "#1", "Best", "Top" or "New" on screenshots, and captions covering over 20% of the image.
• Too much access: Play's store role also covers pricing, so we edit listing fields only and log every change. We never accept Apple team keys, which see every app.
• Replies: no personal data, marketing or incentives, under 350 characters. Facts we can't verify are highlighted, and the client approves 1–2 star replies in month one.
• No ranking promises: we sell the deliverables and a coverage score.

What we sell

Superseded: these were the original tiers before the price check above. Use the new shape: $79–149 refresh, $99–149/month care, $490–790 App growth pack.

Extras: a language for $90, 50 more replies for $40. One free revision within 7 days, otherwise a full refund.

Anchors: Fiverr ASO $30–95; ASOMobile's agency $249–449 one-off, $1,000 a month; Clutch agencies $1,000–5,000+ minimum, $1,000–3,500 monthly retainers; translation $0.07–0.18 a word.

What we need from the client

How we reach out

• Channel: the developer email Google shows on every Play listing (8 of 8 pages checked). For iOS-only apps, the contact on the seller's website.
• Who: US developers, companies or individuals (US law needs an opt-out, not consent), and UK limited companies. Suppress Germany, Poland, the Netherlands and UK sole traders.
• Format: plain text, one link, no tracking pixel, a postal address and "reply stop".

Replies: an AI assistant answers by email and in the sample-page chat. It opens with "I'm an AI assistant", sends the pay link, and passes refunds over $250, legal and angry messages to you. Voice waits until email proves demand.

Timing: send 1–3 weeks after an iOS update, so the makeover lands in the next version. Play has no build constraint.

What clients will ask

4-week test

gantt
  title S1 kill test
  dateFormat YYYY-MM-DD
  axisFormat %d %b
  tickInterval 1week
  todayMarker off
  section Build
  Detector :b1, 2026-10-21, 4d
  Sample page :b2, 2026-10-21, 8d
  QA gate :b3, 2026-10-28, 3d
  section Send
  Warm-up :s1, 2026-10-21, 14d
  300 emails :s2, 2026-11-04, 7d
  700 emails :s3, 2026-11-11, 7d
  section Sell
  Replies and delivery :d1, 2026-11-04, 15d
  Decision :milestone, m1, 2026-11-18, 0d

Track: qualified share, sample pass rate, replies, paid per 100 contacts, average order, Store care take-up, refunds, your minutes per job.

Sources

1. Full notes with every citation: research_notes/Round 3 GTM/s1_appstore_gtm.md
2. Own measurements, 2026-10-20: Apple Search API survey (899 apps, 40-app storefront check), 8-app Google Play sample, and an inspection of the ASO tool's code
3. AppBrain: apps by downloads · developers by country
4. RevenueCat: State of Subscription Apps 2026
5. Apple: roles · responding to reviews · per-app access · API keys
6. Apple: product page guide · App Review Guidelines · localisations
7. Google Play: permissions · Reply to Reviews API · review timing · screenshot rules · developer info shown
8. fastlane deliver · fastlane supply
9. Play robots.txt · Apple Search API
10. Price anchors: AppFollow · AppTweak · ASO.dev · Astro · ASOMobile agency · Clutch · Gengo
11. FTC: CAN-SPAM guide · ICO: email marketing · Google: sender guidelines