Speed + Clarity: My Formula for 90-Day Launches
Most founders spend 18 months planning their launch. I compress that into 90 days.
Not by cutting corners. Not by shipping broken products. By combining two things most entrepreneurs think are opposites: ruthless clarity and relentless speed.
I recently sat down with Dutable to talk about my rapid launch framework and how athletic discipline translates to building companies fast.
Before I was launching tech companies, I was a Division 1 golfer competing in the Sun Belt Conference Championship. In golf, you can’t stand over the ball forever analyzing every variable. At some point, you commit and swing. Business works the same way.
That mindset became the foundation for how I approach every venture. I call it “ruthless clarity”—forcing yourself to articulate not just what you’re building, but why it matters and who it’s for. Once that’s defined, you reverse-engineer the steps, build the MVP, and get real feedback immediately.
The article walks through my three-phase process: Strategic Foundation (weeks 1-2), Lean Build and Test (weeks 3-8), and Data-Driven Iteration (weeks 9-12). Each phase is designed to eliminate the perfectionist trap that kills most startups before they start.
One insight that surprised people: I refuse to limit talent searches geographically. From day one, I structure businesses with distributed teams across León, San José, and the U.S. Why? Because there’s no reason to pay Silicon Valley rates when you can access world-class specialists globally. This approach has been essential to the work we do at Pabs Marketing.
But here’s what really matters: speed without clarity is chaos. Clarity without speed is just a nice idea that never happens. You need both.
If you’ve ever wondered how to take an abstract idea and turn it into an operational business in 90 days—without guessing, without burning cash on experiments that don’t matter—this breaks down exactly how.
Read the full framework on Dutable →
The difference between builders and planners is knowing when analysis ends and execution begins.