The gap between
"someone should build this"
and "someone did."

Product Manager, Embedded. I've shipped internal tools, automated workflows, and built customer-facing features end to end.

Workflow Automation Internal Tools API Integrations
See My Work
Selected Work
01
Agentic
Asset Generation Tool — LogoFlow
Five people were doing a job that shouldn't require five people. 150 accounts a year, 30–40 manual actions each. Something had to change.
Internal Tool 4,500–6,000 manual actions eliminated per year
Read Case Study
02
AI-Powered
AI-Powered Landing Page Platform
SQUIRE had a validated product and a broken delivery model. Two-month turnarounds. No customer ownership. $310K in revenue sitting unrealized.
Platform Strategy 75% reduction in turnaround — 2 months to 14 days
Read Case Study
03
Agentic
Apple Pay Certificate Pipeline
A 15-minute cert process lived in one person's head with no documentation and no backup — embedded as a manual step inside an onboarding pipeline built to run without them.
Agentic Onboarding 15-min process → 2-min automated operation
Read Case Study
How I Work
01
Discover
I map assumptions before writing a single requirement. That means talking to the people closest to the problem — not just stakeholders, but the ones doing the actual work — and questioning every "we've always done it this way."
02
Define
I write the problem in one sentence before I touch a brief. If I can't, I don't understand it yet. The definition work is where the real decision gets made — what's in scope, and more critically, what isn't.
03
Build
I ship iteratively and get feedback before the product is "done." The first version exists to learn, not to launch. I'd rather put something flawed in front of real users in week two than present something polished to a committee in week eight.
04
Measure
I define what success looks like before we build — not after. That means agreeing on a measurable outcome upfront: time saved, error rate reduced, adoption achieved. Without a number, "it's working" is just a feeling.
About

The work
came first.

For the past five years, I've functioned as a Product Manager — embedded as Senior Digital Enablement Specialist. I've owned requirements, run discovery sessions, shipped tools used by product, operations, and support teams, and sat in the room where trade-offs get made. I know what it means to ship something real.

Product management isn't a pivot. It's the formalization of work I've already been doing. My strength comes from owning scope and building with the authority the work actually demands. I believe the best products don't just solve problems — they change how people move through their lives. I'm drawn specifically to AI implementation because I've seen firsthand how the idea of AI alone has already shifted entire industries. I'm determined to become masterful in its execution.

My background gives product teams something they can't hire for in a straight line. I've done the work that happens after the spec is written — the implementation meetings, the breakage in prod, the processes rebuilt from scratch without a clean slate. That operational fluency changes how I write requirements. I don't just manage the product. I discover, ideate, and execute.

Meta
How I Built This
Treating the portfolio itself as a product.
Problem
Hiring managers spend 90 seconds on a portfolio. Mine needed to work harder than a resume — not list what I've done, but demonstrate how I think.
Decision
Structured every case study to answer three questions: Did this person ship something real? Do they understand what a PM does? Would I want to talk to them? Everything else was cut.
Outcome
Site launched [date]. First application sent [date]. This section will be updated — because a PM who doesn't measure outcomes is just guessing.
Back to Work
Automation

Automated Reporting Pipeline

Outcome: Reduced process time by 70%
The Problem
placeholder
Discovery
placeholder
The Decision
placeholder
Artifact — flow diagram / wireframe / annotated screenshot
Fig 1. Replace with actual artifact — system flow, wireframe, or annotated screenshot
The Outcome
placeholder
Retrospective
placeholder