Case Study
A first app for a first-time client
Consumer video-portfolio startup · Project Manager III · 2024-2025
At a glance
Role
Project Manager (Level III)
Duration
6+ months
Team
6
Platform
Mobile — the company's first mobile app
Tracking
Microsoft Project
The situation
Two firsts at once. The company's first mobile application, and my first client without a corporate delivery background — a consumer startup where nobody had been through a structured software engagement before.
The challenge
Mobile delivery carries constraints my prior web and enterprise work didn't: app-store review cycles, device fragmentation, release mechanics that don't allow you to hotfix your way out of a bad deploy. The bigger adjustment was the client. Enterprise clients know what a sprint review is and what a sign-off means. These clients didn't — not from any deficiency, they simply hadn't worked this way before. Standard process language would have read as bureaucracy, and treating them as though they should already know the ceremonies would have cost trust early.
What I did
Onboarded the client into the process, not just the project.
Adapted communication style and process framing for stakeholders new to structured delivery — explaining why each ceremony existed rather than just scheduling it.
Ran a disciplined 6-month plan.
Roadmap and timeline tracked in Microsoft Project, with a 6-person team through end-to-end mobile delivery.
Held scope on a consumer product.
Consumer-facing clients with a strong product vision generate ideas continuously. Delivering on time and on budget on a 6-month engagement means that vision got channelled into a roadmap rather than into the current sprint.
The outcome
- Delivered on time and on budget.
- The company's first mobile application, shipped end-to-end.
- 6-person team, 6-month engagement, first-of-its-kind for the organization.
- Client successfully onboarded into a structured delivery process they'd never used.
What I took from it
Process only works if the people subject to it understand what it's for. With enterprise clients you can lean on shared vocabulary; without it, every ceremony needs a reason attached or it reads as overhead.