Ten years building products. Lately, I ship in weeks.

I set product and design direction across seven products at Sovren. I find the problem by watching people use the product, prototype the fix in code, and build the spec with engineering from what the prototype proves.

Recent Milestones

  1. 2016Owned Skylab’s B2B onboarding: 200+ clients, $10K to $1M each
  2. 2022One of Sovren’s first 4 employees. Integrated 2 acquisitions.
  3. 2023Built a team of 12 direct reports across six functions
  4. 2024Co-founded CrushSuite, 0 to 1 in a year
  5. 2025Launched the self-serve ad platform
  6. 2026Launched Triton Cloud, 0 to 1
  7. 2026Rebuilt Pay on Stripe’s wallet stack in 4 weeks
Building products
10+years
The first half leading design at Skylab Apps, including onboarding for 200+ enterprise clients and the Command Center admin. Product and design together at Sovren since 2022.
On the platform
15M+users
Across seven products: Social, Play, Pay, Shop, Ads, Creator Studio and Triton Cloud.
Building against it
100+engineers
The direction I set is what five product managers and their teams build against.
Triton Cloud
$600K+one client
Prototype in under three weeks.
Domain fluency 0→1 Payments & Fintech Developer platforms Ads & Marketplaces Trust & Safety Ships with AI

Three cases, start to finish.

The host’s screen of an audio room before and after: the old one dimmed, with raised hands hidden behind chat; the new one with a raised-hands banner on the stage and an Invite toast by the thumb.
Audio Rooms

The hands were already up.

I was tasked with getting more people speaking in audio rooms. Too few rooms got past one voice. Two weeks in live rooms showed listeners were raising their hands, and hosts never saw them behind chat. I redesigned the host’s screen.

+37%rooms with 2+ speakers, against a 15%+ goal

Read the case →
Pay’s home screen before and after the rebuild: a flat token list and price charts, then a balance, Send, Receive, Swap and Buy, a pending request and assets grouped by network.
Payments

A new wallet in four weeks.

I was tasked with opening Pay to more chains and a card. The wallet was built on one token, so every feature meant custom chain work. I bet the rebuild on Privy, which Stripe bought, and prototyped the app before the spec.

4 weeksagainst a six-month estimate, with 7 engineers and 2 QA

Read the case →
Trust and Safety

I owned Trust & Safety, and cut the bill 52%+.

I owned moderation for the social apps. The vendor handled the clear calls; the gray area was silencing people by accident, and the AI bill grew with every post. I wrote the gray-area rules and a timeout that doubles instead of bans.

−52%+AI moderation bill, moderator time down 26%+

Read the case →

More case studies.

Shorter reads.

How I run product.

The prototype comes first

I build a working version in Claude Code or Cursor, on our real code when I can, and walk engineering through it before a design file exists. Pay’s prototype took days.

We write the PRD together

Engineering pressure-tests the prototype: where am I overbuilding, and how does the flow feel. The PRD comes out of that conversation, from what the prototype proved and the assumptions it broke. Nothing ships without QA sign-off.

I watch what people do

Research is behavior: where people’s eyes go, where they hesitate, what they never touch. When I asked hosts about raised hands, most couldn’t remember one. Two weeks in live rooms showed why. Support and community report to me, so I see what breaks in the tickets.

A metric and a guardrail for every launch

Every launch names the number it should move and the one it must not break: speakers against chat, the moderation bill against time to action.

Open to the right product seat.

Head of Product on a small team · Staff, Senior or Lead Product Manager on a big one