A useful app starts with a clear plan.
From an app blueprint to design, iPhone and Android development, store submission and ongoing care. Start with the phase you need.
App blueprint
A one-week working sprint to choose the first audience, map the core journey and decide what version one should include. The proposed fixed fee is $2,500.
- Founder working session and review of existing material.
- Core screen map, prioritized feature list and assumptions to test.
- Technical risks, running-cost assumptions and a scoped build recommendation.
- A reviewable brief you can take to Purna or another team.
Design & brand
A coherent identity and a clickable app prototype before a larger build commitment. Proposed engagements start at $9,500, with a 3–4 week planning range.
- Navigation, key screens, loading, empty, error and permission states.
- Typography, color, components and a practical identity guide.
- A clickable prototype and an agreed review plan.
- App-store and landing-page assets when included in the scope.
App build
Turn the approved scope into an iPhone and Android release. Proposed builds start at $24,000 with a 6–8 week planning range; integrations and unknowns can change that range.
- Client-owned repository, hosting and developer accounts.
- Testable builds, recorded decisions and a weekly review cadence.
- Agreed authentication, data flows, integrations and measurement.
- Device checks, release notes, store submission and handoff. Store approval remains Apple’s and Google’s decision.
Care & insights
Keep the app useful after launch. The proposed starting plan is $3,500/month for up to 20 studio hours. Coverage, priorities and response targets are agreed before work starts.
- Maintenance and small improvements from an agreed backlog.
- A defined dashboard using your approved event data.
- Optional public-feedback and sentiment reviews, with source links and human review.
- Monthly work log, risks, spending and the next priorities.
A workflow that is not a mobile app?
Internal software and AI workflow projects begin with discovery. We assess the existing systems, data permissions and acceptance criteria before proposing a build. Describe the workflow; a legacy integration is never assumed to be simple.