Zero to one
Taking mobile testing from 0 to 1
I led mobile testing from early customer discovery through product definition, design, pricing inputs, launch planning, and release. It grew to roughly $1M in revenue in its first year.
The problem
Customers were testing web and API in mabl and handling mobile somewhere else. [Add one or two sentences on what customers told you in discovery and why it mattered.]
What I did
- I ran early customer discovery. [How many customers or interviews, and what you learned.]
- I defined the product. [Platforms, first use cases, and what you left out of v1.]
- I worked with design on the core experience. [The main workflow you designed.]
- I gave inputs to pricing. [What you recommended and why.]
- I planned the launch with sales, customer success, and marketing. [Beta, early customers, enablement.]
- We released it and it grew to roughly $1M in revenue in its first year.
What I learned
- Discovery sets the scope. [What discovery made you cut or add.]
- Pricing is a product decision. PMs should shape it early. [Adjust or replace with your own takeaway.]
- Launch planning starts at definition. Sales and support need time to learn it.
- [Add one lesson you would tell a PM starting a 0 to 1 product.]