Commercial and customer outcomes
- managed a EUR1.5M ARR portfolio across 40+ enterprise accounts
- ranked as a top contributor in growth motions at Atlassian
- improved onboarding, adoption, and churn visibility through better systems
Proof
Real outcomes, current signal.
The proof is strongest when past outcomes and present systems point in the same direction. Commercial results, workflow redesign, and current build lanes all matter here.
Numbers people ask for first
The useful metric is the one that still means something after the meeting.
$6.8M
net-new ARR generated at Atlassian
27%
of total team output in that motion
22%
faster time-to-value through onboarding redesign
40%
less repeated validation work through tooling
Current systems proof
- Master OS is a live operating model, not a slide deck
- BrowserOS and career lanes show repeatable workflow design
- Smaller automation work proves the taste for useful constraints
How I work
I do best in environments where architecture still has to survive contact with real operations.
Working style
Builder-heavy
Meetings should support motion. They should not replace it.
Problem fit
Ambiguity to structure
I like turning scattered pressure into a design people can actually run.
Automation posture
Guarded by design
AI helps inside a governed workflow. Judgment stays with the operator.