From discovery to App Store: how your engagement runs.
Four phases. Specific artifacts at each phase. The same discipline whether you're buying a Build, a Rescue, a Partner engagement, or an Audit, just scaled to the engagement.
Discovery
We scope before we build. Product framing, user flows, a testable wireframe set, and a written proposal with a flat fee and a timeline. No code until the proposal is signed.
Artifacts at this phase:
- • User flow diagrams
- • Wireframe set in Figma
- • Written proposal with flat-fee milestones
- • Stack recommendation (React Native vs native) with one-paragraph justification
Build
Hands-on engineering. Daily builds to your phone via TestFlight and Play Console. Weekly written sync, slack access to Chris, crash and error reporting live from day one.
Artifacts at this phase:
- • TestFlight + Play Console beta invites
- • Daily Crashlytics / Sentry dashboards
- • Weekly written status in your format (email, Slack, or Notion)
- • CI pipeline (CircleCI or GitHub Actions) running on every PR
Ship
Apple and Google review, launch checklist, App Store assets, privacy labels, and a staged release. We submit, we handle review feedback, we cut the final release.
Artifacts at this phase:
- • App Store and Play Store assets (screenshots, descriptions, privacy)
- • Submission and review-response discipline
- • Staged rollout plan (1% → 10% → 50% → 100%)
- • Launch-day monitoring runbook
Stabilize
The 30-day stability window after a Build or Rescue. Biweekly crash-triage ritual: pick the top 2–3 crashes, fix them, notify affected users. Then you pick a path: maintain in-house, hire a new contractor, or graduate to a Partner retainer.
Artifacts at this phase:
- • Biweekly crash-triage cadence
- • Runbook for the next team
- • Handoff documentation
- • Optional: transition to Partner retainer