Mobile-Readiness Audit

One week · $3,500 flat · the plan is yours to use with anyone

The question it answers

“What would a real native app take for our product?” — answered specifically for your stack and your product, in writing, with a fixed price attached if you ever want to use it.

What happens during the week

1. Stack review. I read how your product is actually built — framework, auth/session model, API surface, data layer. Mutual NDA signed before access, standard. Access is read-only and scoped (a guest seat or a walkthrough call both work), revoked at delivery.
2. The hard-20% map. Every SaaS product has a handful of things that carry most of the mobile risk: push notification architecture, auth handoff between web and native, offline/background behavior, the payments/IAP boundary (what Apple’s 30% does and doesn’t touch), App Store review exposure. Your dev — or an AI tool with repo access — can map your code; what they can’t give you is App Store review precedent, where Apple’s IAP line actually falls for your billing model, and which parts I’d deliberately not build. Those are the judgment calls this document exists for.
3. Architecture call, with tradeoffs. Native Swift, React Native, Hotwire Native, or Capacitor — chosen for your product and your team, including what I would deliberately not build in v1. If the honest answer is “your web app is fine for now — revisit when X,” the audit says that in writing.
4. App Store readiness. What in the current product would trip review today (minimum-functionality rules, sign-in requirements, in-app-purchase policy), plus the developer-account and provisioning setup you’ll need no matter who builds.
5. Effort map + fixed quote. The plan broken into phases with effort estimates. My fixed-price quote to build it is the appendix — not the point of the document.

What you walk away with

A written plan you can hand to me, to a hire, or to any competent shop. If you’re hiring a mobile developer, it doubles as the technical half of your job spec and their first-week onboarding doc.

Here’s a redacted-style sample so you know exactly what you’re buying: Sample audit →

What it isn’t

A sales brochure with a quote stapled on. The plan stands on its own if we never talk again.

Logistics

• One week from access.
• $3,500 flat — 50% to start, 50% on delivery, with an objective test instead of my say-so: send the plan to any competent shop, and if they can’t produce a fixed bid from it, the second half doesn’t get invoiced.
• If you decide to build with me within 90 days, the full $3,500 is credited against the build. One credit per client.

Who’s writing it

Micah Hurst — 22 years shipping software, iOS since 2010. Built all four of HomeTown Ticketing’s original apps (iOS and Android, gate-scanning and fan-facing); the iOS pair is on the App Store today: Hometown Fan · Hometown Gate. Three-plus years on Quantum Health’s consumer mobile apps, ending as lead mobile architect (LinkedIn). elementalappsolutions.com