Axia AI.
Taking a founding-stage product to revenue, then making it repeatable.
Product & Growth
Measure first
Numbers before the roadmap.
I owned the metrics framework for a founding-stage product. I defined how we measured activation and retention, then ran the experiments that reordered the roadmap.
- ActivationDefined what counts
- RetentionDefined what counts
- ExperimentsTested what moves them
- RoadmapReprioritized on the results
$0 → $20K
Revenue in ten months
+19%
Year-over-year revenue
An ML feature
Handwritten pages, made readable.
With engineering, I scoped and shipped an ML feature that transcribes and summarizes handwritten documents, so language stops getting in users' way.
Line 2 press – bearing noisy again.
Swap before Fri.
40 units waiting on QC.
Order spares.
- Asset
- Press, line 2
- Issue
- Bearing noise, repeat
- Action
- Replace by Friday
- Blocked
- 40 units awaiting QC
- Follow-up
- Order spares
The ERP rollout
One rollout, every team on the same plan.
I led end-to-end program execution for a bespoke ERP rollout, running cross-functional workstreams across operations, product and client teams.
Cycle time
The playbook
The second rollout should be faster than the first.
I wrote standard implementation playbooks and SOPs that locked in the improved ERP delivery process. Rollouts for similar manufacturing clients now start from a template, not a blank page.
- Rollout 1Learn what works
- Playbook and SOPsWrite it down once
- Rollout 2Start from the template
- Rollout 3 and onFaster every time
What this changed about how I work
Early at a startup, you build the product and the process together. The metrics told us what to build; the playbook meant we only had to learn each lesson once.
Taking a product from first customers to a repeatable motion?