I turn unclear product problems into something a team can solve.
Nine years a Product Owner in payments, fraud, subscriptions and live operations. Before that, the support and risk desks where the consequences land.
- 40%
- less account fraudless player-account fraud
- 3 → 1
- actions per withdrawalactions per withdrawal
- ~45%
- less processing timeless case processing time
Where I fit
An unclear problem with complex flows, several stakeholders, integrations or operational constraints, where the right answer is not worked out yet.
Built on my own time
The code is AI’s. Every product decision is mine.
Claude and Codex wrote essentially all the code. The scope, the decisions and the testing are mine. Vard CRM was the first, a frontend, a backend and a database. Before it I had built prototypes, not products.
Why I keep building
Between roles since March, building is how I keep doing product work for real instead of only talking about it.
It also teaches where my own judgement runs out. Architecture, security and what the code will cost to change are where a developer’s judgement lives, not mine.
Archive Lens
A searchable catalogue for a friend's photograph collection. Originals stay in Google Drive. OCR suggests, a person approves, and only approved records reach the catalogue.
Watch the 40s walkthrough →
Resume Builder
A structured CV editor that keeps reusable content separate from layout, with fast previews while editing and a rendered PDF check before export.
Watch the 40s walkthrough →
Vard CRM
A narrow CRM built around one freelance photographer's actual workflow rather than a general feature set.
Read more →
Shipped in a product role
Six things that were costing something
Each date is when the thing happened, not how long I was there. I joined King in 2008 and have been in product since 2015. The numbers are my own, worked out at the time rather than audited afterwards.
Username here, email there, payment details elsewhere. Analysts held the pattern in their heads, one account at a time.
One place to search usernames, email patterns, IPs, registration and payment data together. Accounts working as a group finally looked like one. Several of those groups ran to hundreds of accounts, the largest past a thousand.
One specialist on existing data, instead of waiting for developer resources that were never coming.
Exercises I set myself · neither shipped
Both write-ups →One thing on this page was never used and two never shipped. They are here on purpose.
About me
Who you would be hiring
I started in customer service, payments and fraud, then moved into product at King.
What that background is for
I notice the manual work, the unwritten decisions and the edge cases that stay invisible when a product is only seen through its interface.
How I work
I prototype early so problems surface before delivery gets expensive, and I stay through the decisions.