Plans without products
Rolled out Plan and Product terminology behind a feature flag across settings, signup pages, invoices, activity and validation copy, so a subscription no longer needs a product.
Senior Technical Product Manager · San Antonio, TX
Product manager who ships: from product brief to merged pull request.
I have 14 years of experience in billing, payments and infrastructure. At Maxio I write the strategy, the specs and the code for metering, wallets, entitlements and pricing. I also built the Claude Code tooling that engineers there now use and extend.
Featured projects
Three projects from Maxio, each taken from the problem to the shipped result.
Metered customers wanted to override usage rates on a single subscription, per pricing segment, without forking their catalog. I took it from the first deep-dive to production in about three months.
Read case study →Wallets · Prepaid · EntitlementsI scoped the Wallet & Entitlements MVP, a board-level bet on AI-platform billing. Then I built the prepaid rollover and expiration controls, fixed the issues found at launch, and wrote the public API docs.
Read case study →AI tooling · Developer experienceI treated the team's AI setup as a product. I packaged our conventions into Claude Code plugins and skills, so any engineer or PM gets the same rules, setup help and path from ticket to PR in one install.
Read case study →More work
Rolled out Plan and Product terminology behind a feature flag across settings, signup pages, invoices, activity and validation copy, so a subscription no longer needs a product.
Redesigned the meter field modal, the event stream pages, the schema preview and the usage warnings, and fixed the formula meter editor.
Restyled the main dashboard and added widgets that customers can customize.
Ran customer feedback sessions and turned the findings into prioritized work and fast-follow releases, including monthly accruals for metering and clearer zero-usage invoice lines.
Added international date formats to CSV imports, contract numbers on statements, notes carried over to renewals, partial months in pricing formulas, and new VAT countries.
Wrote a billing best-practices article that became a five-day marketing campaign.
How I build
AI let me ship more, so I added more review around everything I shipped.
Bigger features start as a deep-dive and a plan for each milestone, reviewed like code, so each decision is made once and written down.
I run several Claude Code sessions, each in its own git worktree with one ticket, so independent fixes move forward at the same time without colliding.
Automated AI review, a second review by a different model, and hands-on functional testing all happen before I ask a teammate to look.
Each PR carries one change, a clear title, the ticket, and how I tested it.