I lead the platform layer at Thryv. Public APIs, an integrations marketplace, partner and developer tooling, and customer-facing AI features built on them. Most of what my teams build is infrastructure that other products depend on, and that changes how you weigh a decision. A broken feature affects one workflow. A broken framework affects everyone building on top of it.
I came into product from solutions engineering, sitting with customers while they explained what they wanted. What I took from those years is that the stated requirement and the actual problem are rarely the same sentence. It still shapes how I prioritize. Before we design anything, I want to know what exact problem we're solving and whether the market will pay to have it solved.
These days the part I care about most is the team. I've got two Product Managers and a Product Owner, and the goal is pretty simple: make them capable of making the call without me. Two of the people I've coached have earned promotions, and that's the outcome I'd point to first.
Three projects that show the pattern. Each one includes what it cost, not just what it returned.
Inherited a quarter and a half behind schedule.
A selling point that was breaking in customers' hands.
The problem was hiding its own evidence.
Start with the exact problem.
Outcomes over output.
Data leads, judgment fills the gaps.
Ship small, learn fast, fail cheap.
Buy-in upfront, trust through consistency.
Develop owners, not order-takers.
Side projects, built to learn rather than to launch.
Competitive intelligence for local small businesses.
A working website for a friend's trucking company.
Ask it about my experience.
I travel when I can and take a camera with me, which means I come home with far more photographs than any trip could reasonably justify, most of which I could not explain if asked.
Most of what I read is history. Most of what I watch is science fiction.
Sports are non-negotiable. Soccer, almost any match, almost any league. Football, mostly Gators, with the emotional consequences that implies. And a strategy game when I want to think slowly about something that does not matter.




Always up for a conversation about platform and product work. Tell me what you're building.
Connect on LinkedIn