What It's Like to Build
400+ Products

Working alongside Sam over hundreds of product builds, I've observed his ruthless ability to strip away complexity and identify the actual revenue mechanic within 48 hours — he asks questions that immediately expose whether a problem is real or ego-driven. His unwillingness to accept 'good enough' means he'll push back on feature sprawl, demand payment validation before engineering, and quietly redirect the entire team when the unit economics don't work.

Working with Sam across 400+ builds, I've watched him make ruthless trade-offs that most people can't stomach — he'll kill a feature mid-build if the unit economics don't stack, but he'll spend weeks perfecting positioning if it moves the needle on conversion. His obsession with payment-first validation means we ship faster and smarter than teams chasing vanity metrics.

Working with Sam over 400+ builds has shown me someone who refuses complexity when simplicity works — he'll kill a feature in seconds if it doesn't directly drive revenue or solve a real user problem. His decision-making is ruthless about speed and feedback loops; he'd rather ship a rough version and iterate on real data than debate perfection for weeks.

Working with Sam across 400+ builds has shown me someone who moves at uncommon speed because he makes decisions on incomplete data rather than waiting for perfect information — he'll smoke test a hypothesis with $50 and real users before spending a week in analysis. He doesn't optimize for vanity metrics; every feature, every ad spend decision traces back to actual paying customers.

Working with Sam across 400+ product launches, I've observed his ruthless focus on unit economics from day one — he'll kill a feature that doesn't move the revenue needle, even if it takes weeks to build. His speed of iteration is striking; he doesn't get attached to ideas, just to data, which means we pivot fast and waste nothing.

Working with Sam is like being paired with someone who operates at 2x speed — he makes decisive calls on market fit within hours, not weeks, and isn't afraid to kill projects that don't pass the smoke test. His obsession with unit economics from day one forces us to build lean and ship fast.

Working with Sam is like watching someone play chess at 3x speed — he sees three moves ahead on every product decision, kills ideas ruthlessly if the unit economics don't work, and expects the team to validate assumptions through real revenue, not vanity metrics. He pushes hardest on conversion funnels and payment friction.

Working with Sam means operating in a constant state of rapid iteration — he builds conviction through data, not intuition, and will kill a 90% complete product without hesitation if the metrics don't validate the problem. His obsession with lean tooling keeps every product actually useful rather than feature-bloated.

Working with Sam across 400+ builds, I've watched him make ruthless prioritization calls that kill features before they waste resources — he sees the smoke test before anyone else does. His obsession with practical execution means he'd rather ship a solution a junior developer can maintain than chase the perfect tech stack.

Working with Sam means operating in a ruthlessly empirical environment where every decision is tested against real market signals — he moves fast on validated ideas and kills weak ones without ego, which forces the entire team to stay sharp and honest. His obsession with unit economics from day one means he'll pause a promising build to nail the payment flow first.

Working with Sam, I've watched him make ruthless prioritization calls that others would overthink for weeks — he trusts data and intuition equally, which means we ship fast and iterate faster. His obsession with unit economics from day one means he doesn't build features, he builds payment mechanisms wrapped in features.

I've logged 400+ product launches with Sam, and what stands out is his ruthless prioritization of paying users over vanity metrics — he'll kill a feature mid-build if the smoke test data says customers won't pay for it. His vision is fundamentally different: he doesn't ask 'what's possible' but 'what's profitable,' which forces elegant constraints that actually ship faster.