From the first conversation to the next release.
A sequence of decisions you can follow. Every phase ends with a concrete artifact and a clear choice about what happens next.
1. Establish fit
Bring the audience, current problem, constraints and an example of the workflow. We clarify what success would look like and whether Purna is the right partner. Confidential material waits for the agreed channel and terms.
2. Make the blueprint
Map the core journey, the smallest useful release and the questions that could change the plan. Review the screen map, priorities, risks and cost assumptions. Decide to build, investigate further or pause.
3. Agree the work
Confirm the statement of work, acceptance checks, payment milestones, timeline assumptions and named owners. Complete the agreed initial payment and access setup before delivery begins.
4. Design, build and review
Review the prototype before committing to the full implementation. During the build, use testable increments and an agreed weekly review. Keep feedback consolidated and record decisions alongside the backlog.
5. Check release readiness
Exercise the important journeys on agreed devices. Check failure states, permissions, privacy disclosures, restore and rollback steps, and store materials. Keep remaining defects and launch dependencies visible.
6. Submit and hand over
Submit from your developer accounts after approval. Record store review outcomes. Hand over the repository, design files, configuration inventory, runbook and agreed acceptance evidence. Submission is not a guarantee of approval.
7. Learn and care
Review actual usage against the agreed definitions. Fix covered defects, prioritize improvements and make the next scope explicit. See the support model.