The Frameworks
How I think about
shipping the next thing.
Named frameworks for founders and builders past the build stage. One umbrella — Founder's Cut — and three sub-frameworks for the specific decisions that get builders stuck after they've shipped something real.
The Umbrella
Founder's Cut: A Founder Coaching Framework for Builders Past the Build Stage
Founder coaching for the awkward stage between shipping something real and scaling. Founder's Cut is a 90-day framework — Clarity, Systems, Velocity — for founders and builders who already proved they can build but don't yet know what to build next.
The 90-Day Arc
-
01
Clarity
Cut before you build.
-
02
Systems
Install the repeatable stuff.
-
03
Velocity
Measure, decide, delegate.
The Sub-Frameworks
The Clarity Filter: How to Beat Feature Creep and Know What to Stop Building
Feature creep is a clarity problem, not a discipline problem. Here's the 4-question filter I run when a roadmap is bloated and the founder can't tell what to cut.
The Prioritization Formula: A Product Prioritization Framework for Solo Founders
RICE, ICE, Kano, MoSCoW, Lean Prioritization — every prioritization framework was built for product teams, not solo founders. Here's a 5-input formula that synthesizes the best of all five for the 1-person company.
The Delegation Decision: When to Hire Your First Employee as a Founder
Most founders hire too late, then hire too generic. The Delegation Decision is a 3-question test for figuring out what to take off your plate first — and whether the answer is a fractional, a contractor, or a full-time first hire.
Methodology, not theory
Frameworks are scaffolding for decisions you already have to make.
Every founder past the build stage runs into the same four questions: which customer am I serving, what should I stop building, which feature comes next, and what do I take off my plate. Founder's Cut exists because most founder advice answers those questions generically. These frameworks are how I answer them with the specific founder in front of me.