Senior Product Manager

I build products
people actually need.

11 years of customer empathy, a systems thinker's mind, and a builder's hands. I create strategy where one doesn't exist and ship products that earn real trust.

Scroll

I listen differently
than most PMs.

I came up through technical support — 500+ customer interactions a week, spotting patterns before they showed up in metrics. That experience gave me something most PMs don't have: I know the difference between what customers say and what they actually mean.

For most of my product career I've been the sole PM at a B2B MarTech company serving 30K+ customers. No playbook handed to me. I built the strategy, championed the roadmap, and drove outcomes from discovery to shipped.

Most recently I've pushed into a new gear — using Claude Code to actually ship: 15 PRs and 13 production releases. Features that used to take months now take days or weeks. I'm not a PM who throws requirements over a wall. I'm in it with the team.

Ship to learn

The longer you wait to get something in customer hands, the higher the chance you overbuild or miss the thing you would have learned from real behavior.

Signal first

Data, usage, customer conversations, and market movement — always before committing. And I know that customers don't always say what they mean.

Own it fully

When something goes wrong, I'm in the room driving the fix. Not pointing fingers, not waiting for someone else to call it.

Systems thinker

I think about the whole ecosystem — how things connect, where integration points become failure surfaces, and what the second-order effects are.

$15-17K
MRR from a 0-to-1 add-on I championed, sustained for 2+ years
2.4x
Trial conversion improvement — 20% to 48% through value-based gating
<1day
Time to publish, down from 2.5 days after shipping Brand Kits
15PRs
Production releases shipped personally using Claude Code in 13 releases

Products I've driven
from zero to shipped.

0 to 1 · Monetization

Brand Kits

Customers were losing days to repetitive formatting work before a single page went live. I identified the gap, built the solution, and made it a foundation for AI-generated content that actually looks and feels like the user's brand.

Time to publish: 2.5 days → under 1 day
0 to 1 · Expansion MRR

User Permissions Add-On

The number one customer request for years — consistently deprioritized. I made the case, scoped it to ship fast, and got it across the line. It's been running strong ever since.

$15-17K MRR sustained for 2+ years · 1.79% churn
Product Decision · Conversion

Trial Publish Gating

A platform risk required a hard product decision that fundamentally changed how we measured trial value. What started as a defensive call became one of the highest-impact conversion moves we made.

Trial conversion: 20% → 48% · Revenue window: 14 days → 7
AI · Builder

Claude Code — PM as Builder

Expanded from decision-maker to hands-on builder — personally shipping production code alongside the engineering team. Also built AI-powered internal workflows that compressed the full discovery-to-kickoff cycle.

15 PRs · 13 releases · 40% faster discovery-to-kickoff

My approach to
building products.

01

Start with signal

Company goals, usage data, customer conversations, and market movement — before anything else. I form hypotheses and find the fastest path to validate them, whether that's an interview, a prototype, or a small build.

02

Create strategy in ambiguity

I've spent most of my career without a clear top-down strategy. That means I've learned to find the customer-valid version of any directive, identify opportunities no one assigned me, and build the case from the ground up.

03

Ship to learn

The longer you wait, the higher the chance you overbuild or miss critical learnings. MVPs, betas, prototypes — whatever gets something in customer hands fastest so you can stop guessing.

04

Trust is earned through output

Especially in AI products, users are skeptical until something actually works for them. Generic output loses them. Output that feels like it knows their business keeps them. I build for the latter.

05

Team, not handoff

Engineering is a partner, not a downstream recipient. I bring enough technical fluency to ask the right questions, challenge assumptions, and now — put up PRs they can review.

06

Own the outcome

When something goes wrong I'm in the room driving the fix — not pointing fingers, not waiting. And when something goes well, the metrics tell the story.

Let's build something
worth being proud of.

I'm a Senior PM with deep B2B SaaS roots, AI product experience, and a genuine love for the craft of building things customers actually need.
If that sounds like a fit, let's talk.