The specialists your team is missing. Already in the system.
At your size the team exists — and every person on it is covering two specialist jobs they never trained for. AppDNA doesn't add another tool to the twelve you already run. It adds the specialists: agents that watch every module around the clock, diagnose, and draft. Your team approves; the SDK ships.
AppDNA is the App Growth OS for subscription apps. For mid-size apps — 100K to 500K monthly active users, typically run by a growth team of two or three — it fills the specialist roles the team hasn't hired: ASO, lifecycle, and monetization exist as agents in the system that watch the funnel, diagnose problems, and draft fixes for the team to approve. One SDK ships approved changes without an App Store release, collapsing the typical 3–6 week experiment cycle toward 1–2 weeks with a single owner.
What growth looks like at 100K–500K MAU
Big enough to have a team. Not big enough to have specialists.
The typical industry cycle is 3–6 weeks and 4–6 people per experiment — a designer, an engineer, an analyst, a release slot. At your size, that means the growth team's throughput is set by everyone else's calendar.
Two or three people covering ASO, lifecycle, paid, monetization, and analytics. Each of those is a full-time craft at bigger apps. The gap doesn't show up as failure — it shows up as levers nobody has time to pull.
"Did the onboarding change move revenue?" With data split across 8–12 tools, that answer is a week of SQL and exports — so mostly it goes unanswered, and decisions run on the metric each tool happens to show.
8 out of 10 teams can't tell you what they tested last year; the other 2 send 50 Excel files — our founder's observation from a decade of agency work, and mid-size teams are its center of gravity: enough experiments to matter, no system that remembers them.
The six things AppDNA changes at your size
One system, six differences — sized for a 2–3 person growth team.
ASO, lifecycle, monetization, onboarding — they exist as agents in the system, each one watching its module's data around the clock, diagnosing, and drafting fixes. Your team stops covering six crafts with three people and starts reviewing the work of nine specialists. Every change waits for your approval before it ships.
The industry's typical 3–6 weeks with 4–6 people becomes a system designed for 1–2 weeks with one owner — because the design, the build, and the release step disappear. Approved changes go live on devices in minutes, no App Store release, no engineering ticket.
One event pipeline owns the whole chain, so cross-module cause-and-effect — the onboarding change that moved paywall conversion — is a view, not a week of SQL. The question your tools structurally can't answer is the one this system is built around.
The team keeps control of everything that ships: approval gates on every change, rollouts starting at 10% of traffic, stop-losses on the metrics you guard, full audit trail. On Autopilot, you can go further and encode your own playbook — how your team does growth — and the agents work your process. (Process encoding is an Autopilot and Enterprise capability.)
Category benchmarks fill the gaps where you have no specialist to ask; every experiment your team runs compounds in Growth Memory, so the learning survives quarters, reorgs, and departures. Anonymized market patterns flow in; your data never flows out.
AppDNA reads your existing stack — RevenueCat, Adapty, Firebase, AppsFlyer and the rest — from day one. Nothing to rip out, nothing to re-instrument. And the price scales with your monthly active users, working out to cents per paying user.
Your plan & path
What this costs at your size.
Pro — at 100K–250K MAU: $599/mo founding pricing (list $899); at 250K–500K MAU: $699/mo founding pricing (list $1,399). Pro carries all nine modules, the full zero-deploy SDK, the experiments engine, and 3 included team seats (add more for $49/mo). When you're ready for the agents to run a longer leash inside your guardrails — and to encode your own process — Autopilot starts at $1,299/mo founding pricing at 100K–250K MAU (list $2,499).
teams at this size get the most from pairing the platform with implementation — the rollout is where systems succeed or stall. Guided — 8 weeks, weekly 1:1 with an App Growth Architect, your hands on the keyboard — is $6,900. Done-for-you — we configure the workspace, integrate the stack, ship the first experiments with your team, and hand over a working rhythm — is from $15,000 (founding implementation pricing: we're building our public case-study library and founding customers are part of it).
We already know where your team is losing the most.
Across our audits, 85% of apps share the same biggest revenue leak: onboarding that fails to create the aha moment — costing at least a third of potential conversion. At 100K–500K MAU that's not a rounding error; it's the difference between a flat quarter and the one where the trial-to-paid line finally moved.
Get the audit your team would run if it had a spare week.
Paste your App Store or Google Play link. Get your Growth Score, your biggest funnel leak, and a 90-day plan — free. It doubles as the internal doc that gets your roadmap unblocked.
Frequently asked questions
Six questions growth teams at 100K–500K MAU ask us before connecting their app.
What if it ships something bad to 300K users?+
We already run RevenueCat, Amplitude, and Braze. Is this a rip-and-replace?+
Our engineers already say no to growth tickets. What are we asking of them?+
Does our funnel data feed a model our competitors benefit from?+
We have a growth PM and two marketers. Doesn't this overlap with their jobs?+
If we roll this out and it stalls, what has the team lost?+
Missing your question? Ask us directly — a human replies within one business day.
When you outgrow this page
At 500K+ MAU, the conversation changes — deployment, compliance, your own Growth OS configuration: that's the enterprise page. See AppDNA for enterprise →
See your app’s biggest leak — free, in 2 minutes.
Everything your app needs to grow. In one system.