How I work

The habits behind the work, each with the case study that proves it.

Out-of-the-box thinking

I question the default before I follow it. Social apps share by default, so at Logg we made privacy the default instead. Apple made it App of the Week and Product Hunt made it App of the Day.

Proof: Logg

Critical thinking with AI

I use AI agents every day, but I own what ships. User stories and behavioural checks tell them how the code must behave under load and across tangled dependencies, so they work like clones of me. I review their output like a new hire's, and evals and tests, not a confident answer, decide when it is done. That is how broken replies went from about 7% to zero.

Proof: Rezolve Ai

Problem solving under constraints

When the obvious fix is too slow or too costly, I find another way in, with a bias toward execution. A cloud-only SaaS became an on-premise product in two weeks because I made its data layer point at another database instead of rebuilding it.

Proof: Upsolve on-prem

Product mindset

I build what users will pay for, not what's fun to build. At Commented, customers and sales data showed us where the value was, so we moved from a general commenting tool to collaboration between software teams and their clients. Since launch, 800+ teams have left 56,000+ comments on it.

Proof: Commented

Agile

Product plans become sprint plans, and sprints land. At Decktopus AI I turned product plans into sprints with the team and reviewed the work so the old editor kept serving customers. We delivered 90% of planned sprints on time.

Proof: Decktopus AI

Root causes, not symptoms

I start with what success looks like and the people closest to the problem, then fix the cause. A gap I saw in pharma sales became a CRM product, not another spreadsheet.

Proof: DIGIEGGS and Cosmegg

Quality by default

Written plans and reviewed code, not hope. I spot quality gaps early, from broken UX to missing API contracts, and step in to close them myself.

Proof: Karshare takeover

One design, every team

Security, DevOps and customer teams rarely want the same thing. I write the trade-offs down, hear each team's constraints, and land one design they all stand behind.

Proof: Writer Agent Deployment

Close to the customer

I go to the people using the product before I build. At Commented I was in more than 200 sales, demo and customer success meetings, which is where we heard what customers really wanted.

Proof: Commented