Hi, I'm Jordan.
I build products that move revenue.
Principal Product Manager, 10 years across PropTech and B2B2C SaaS. I join early, take products 0→1, instrument everything, and ship with AI — not around it. Scroll for the receipts.
Ask my career anything.
The same answers I'd give you on a call. Pick a question — or watch it answer on its own.
Case studies with the messy middles
Every card opens the full story: the discovery, the calls I got wrong, and what the business got out of it.
Resident platform, 0→1
- Why it made money
- Upgrades 0% → 18% pilot → 23% GA, a compliance moat that wins deals, and the scaling ceiling removed. 75K units, 85% same-day execution.
Self-guided touring
- Why it made money
- After-5pm leads were revenue nobody collected. Dead hours became signed leases, the lockbox wedge opened a land grab — and Lennar signed.
Renovation workflow OS
- Why it made money
- Cycle time is the P&L in renovation — capital turned almost 3x faster, and the Salesforce migration cut 30% of OPEX on top.
Shipping with AI
- Why it made money
- The 250-customer quarter was impossible at current onboarding cost — opex was the growth lever, and AI I built myself pulled it.
Signal-to-Spec
- Why it matters
- A governed MCP + Claude skill that turns raw customer feedback into a ranked, evidence-backed, spec'd roadmap — a human gate at every step. A challenge I set myself, built in an evening. Try the live tool.
Don't take my word for it. Click something.
Personal side projects I build nights and weekends — working software, not slideware. Prototyping is how I communicate.
Playvia
WandrAI
Flux
Discovery isn't a phase. It's a habit.
Revenue, acquisition, retention — then the operational story. Never the reverse.
Ride-alongs, CABs I founded, CEOs on weekly calls. Roadmaps come from rooms, not dashboards.
Metrics defined before a line of code. A 60% drop-off taught me once; once was enough.
CSAT 6→9 came from a plumbing decision nobody asked for. The data asked for it.
Don't just take it from me
Pulled from LinkedIn — managers, engineers, and designers I've shipped with.
"One of the best Product people I've worked with. He has an innate ability to look past what most PMs might only see on the surface to quickly uncover root cause issues… and deliver elegant solutions that truly drive business impact."
"What truly sets Jordan apart is his courage as a leader; he understands that a clear 'no' is often more valuable than a 'yes'… he ensured our products were intuitive from day one."
"By far the most technically minded product manager I have ever worked with. He knows the system so well that he can often inform newer engineers how something is established in the database — and how that connects to the end goal."
"Jordan is a 1st round draft pick for any company — and they will soon find themselves with an all star. Tactical, thoughtful, and thorough in all of his process steps."
What the work taught me
Sometimes the best product decision is a plumbing decision.
The unglamorous DOCX→PDF migration beat every shiny roadmap item: zero rendering failures, CSAT 6→9.
Saying no is easy. Getting the asker to agree with the no is the skill.
Map the ask to the asker's own KPIs, and "not right now" closes itself.
If the math doesn't work, change the math.
250 customers couldn't be onboarded by hand. AI tagging made the quarter possible — and I built it myself.