Why We Charge for Discovery — The Two Weeks That Save You Six Months
Most mobile-app agencies offer free discovery. SEM Nexus charges $4k–$10k for it. Founders sometimes ask why. The answer is the most expensive lesson the mobile-build industry has learned in the past decade: free discovery is, on average, the most expensive line item in your eventual build budget, because the agency that didn't charge for it didn't do it.
This isn't a contrarian take. It's a math problem. Here's what you actually pay for when you skip the paid-discovery step, and what SEM Nexus's two-week discovery produces in exchange.
The "free discovery" trap
When an agency offers free discovery, two things are true. First, they need to make the time back somewhere — typically by building it into the build margin. You pay for it; you just don't see it itemized. Second, because it's free, they spend the minimum time on it required to win the deal — usually 4–8 hours of sales-call work and a templated proposal.
What you get from free discovery:
- A high-level project description (probably what you told them)
- An hourly-rate-times-rough-estimate quote ($X–$2X range, with an implicit reservation that the actual number will float upward)
- No real feature scope
- No real stack analysis
- No real sprint plan
- No real understanding of which feature is the technically hardest part of your project
That last item is what makes free discovery expensive. Every mobile-app build has one or two technically hard parts — an audio engine, an offline-sync flow, a real-time map, a regulated integration — and if those hard parts weren't identified before the build started, the project will slip badly when engineering hits them in week 8.
We see this every quarter. A founder shows up at SEM Nexus four months into a build that was supposed to ship in five, with a vendor who's now asking for $60k–$90k more and another 4 months. The original "free discovery" missed the hard part. The founder paid for that miss with their entire runway buffer.
What SEM Nexus delivers in two paid weeks
Discovery at SEM Nexus is a contractual engagement with a defined deliverable. It produces four documents:
- Market-validation summary (1 page) — who you're serving, what they need, where the demand signal came from. Often informs cuts you didn't know you should make.
- Feature list with v1 / v1.5 / v2 priorities (1–2 pages) — every feature you proposed gets explicitly placed in one of three buckets. The cuts are the value.
- Technical recommendation (1 page) — stack choice (Flutter, React Native, Angular/Ionic, or native), key integrations, the hard part identified by name, the architectural risks named in writing.
- Build quote and sprint timeline (1 page) — fixed quote against v1, sprint-by-sprint plan. The quote is fixed because the work to make it fixed happens during discovery.
Four pages of decision-quality work, not a 40-page deck. You can take all four, fire SEM Nexus, and shop the build to a different agency — the artifacts transfer. We've had clients do exactly that, come back two years later. The point is: the documents are real, not lead-gen.
Want the real artifact instead of the free-discovery deck? Book a two-week discovery and we'll deliver all four documents. The discovery is the only part of the engagement you have to commit to up front.
The hard part: why we name it on paper
Every mobile build has a technical risk that determines whether the project ships on time or slips by months. Naming that risk in week 2 of discovery, in writing, in the technical recommendation document, is the single highest-leverage thing SEM Nexus does in any engagement.
For Cerebyte, the hard part was the audio engine — playing back audio derived from real EEG brain-activity recordings, with the fidelity wellness listeners expect. Discovery named the risk and recommended Flutter because the audio ecosystem on Flutter (just_audio + Dart FFI to C-level libraries) was the strongest available. We had a working audio engine prototype in sprint 1 to retire the risk before downstream sprints depended on it.
For My Home Delivery, the hard part was Stripe Connect multi-party payments — customer pays, platform takes a cut, driver gets paid out. Discovery named this as the risk and we wrote a 60-line proof-of-concept against the Stripe sandbox in week 2 to confirm the model worked end-to-end before quoting the build.
For 360 Medical Consulting, the hard part wasn't engineering — it was the HIPAA audit, the BAA negotiation with three vendors, and the App Store review for medical content. Discovery surfaced all three and added 5 weeks to the build quote. The founder knew exactly what they were paying for. The build hit the quote.
Free discovery doesn't name the hard part because it doesn't spend the time to find it. Paid discovery does — and saves the founder 4–12 weeks of slip downstream.
What the math actually looks like
Numbers from real SEM Nexus engagements:
| Discovery spend | Build saved by naming the hard part early | Net |
|---|---|---|
| $5k (typical) | $40k–$80k of avoided rework | Net positive 8–16x |
| $7k (marketplace scope) | $60k of Stripe Connect rework avoided | Net positive 8x |
| $10k (HIPAA-regulated) | 5 weeks of timeline correctly added upfront | Net positive (calendar) |
The discovery cost is a single-digit-percent slice of the build cost. The downstream savings — in money, calendar, and founder time — are five to ten times the discovery spend. Every founder we've worked with has come out positive on the discovery math. Every single one.
What you should not pay for discovery
Some agencies will quote $15k–$25k for discovery. Be careful here. A real two-week mobile-app discovery costs $4k–$10k depending on scope (single-platform internal tool at $4k, two-sided marketplace with complex integrations at $10k). Above $10k, the agency is either over-scoping discovery to lock you into a larger relationship, or they're charging consulting-firm rates for what should be engineering-led work.
SEM Nexus's range is the honest one. We've never quoted discovery above $10k.
A worked example: the validation outcome
A SaaS founder came to SEM Nexus with a project description for "an iOS app for our existing web product." Three other agencies had quoted $120k–$220k for the build. SEM Nexus discovery took two weeks and surfaced three things:
- 80% of the founder's users only used four specific web features regularly. The other 60+ features were corporate-bloat features that didn't belong in mobile.
- The four features included one that needed offline support — the hard part. We named it.
- v1 scoped down to those four features, with offline support on the most important one. Quote: $58k. Timeline: 14 weeks.
The founder shipped on time, on budget. One of the v1.5 features got cut later because users never asked for it — saving another $18k that would have gone to feature creep.
Discovery cost: $5k. Money saved on misallocated v1 scope: ~$60k. Time saved: roughly 2 months. That's the typical discovery outcome.
Why we still charge
We charge because the discipline only works if the discovery is real. If it were free, the math we just walked through would not be possible — the agency that gave it away would be cutting corners, and the founder would discover the corners in week 8. SEM Nexus charges $4k–$10k because that's the cost of doing it correctly.
If you're scoping a mobile-app build right now and an agency is offering free discovery, take a hard look at what you're actually getting. If you'd rather pay for the version that ships your project on time, SEM Nexus's two-week discovery is the cheapest part of a successful build — and reliably the most leveraged dollar in the entire engagement.
