Case 03 · Rentvine · Hands-on
PMs as builders.
With modern AI tools, product managers can be builders, not just spec writers. Before asking my team to work that way, I proved it on myself: an owner-facing financial reporting feature, taken to production with real database schema changes, behind a feature flag.
- Role
- Chief Product Officer, and the engineer
- Built with
- Claude Code · Phalcon PHP · MySQL
- Outcome
- Validated in production
- Proved
- PMs can be builders
Problem
AI tools are changing who can ship software. I wanted to test the claim for real: could a product manager be a builder, and take a feature through schema changes and into production instead of handing off a mockup?
The feature itself: owner-facing financial reporting that helps property managers move the owner conversation from transactional management to investment strategy. Details after launch
My role
Everything from spec to production: product definition, data model, implementation and release.
What I did
- 01Spec
- 02Schema change
- 03Feature build
- 04Feature flag
- 05Validated in prod
I started with customers: several conversations to validate the concept. Then I made a Claude artifact explaining the data architecture it needed, built on Rentvine’s existing data structures, and found existing libraries to reuse instead of writing new ones. It passed architecture review with only naming changes for a few data tables.
Outcome
- Shipped and validated in production behind a feature flag.
- Proved that PMs can be builders, shipping complex features that include database schema changes.
- PMs on the team earned the right to build and ship. They still have to earn the right not to create endless PR reviews.
What I’d do next
I’d do it again. It gave me real confidence in our new operating model: small pods can deliver at massive scale.