Justin McKelvey
Fractional CTO · 15 years, 50+ products shipped
The McKelvey Method: A Founder Coaching Framework for the Post-MVP Stage
TL;DR: For Founders Stuck Between MVP and Real Business
You shipped something. People are using it. Maybe paying for it. And now you're staring at a list of 50 next moves with no idea which one actually matters — and every founder you ask gives you a different answer. That's the stage this is built for. The McKelvey Method is a 90-day founder coaching framework — Clarity, Systems, Velocity — for founders past the build stage who need to stop guessing and start operating. Most founder coaching, CEO coach, and executive coaching engagements miss this stage entirely — they focus on mindset when the actual problem is product decisions and where you spend your time. As of 2026: $1,500/month with a 3-month minimum, or $3,999 paid in full.
Why Post-MVP Founders Need Coaching, Not Advice
Once you ship something that works, your problem changes. The first problem was technical: can I build this? The second problem is strategic: should I? Most founder advice — books, podcasts, accelerator programs — is built for the first problem. There's almost nothing built for the second.
You're probably feeling this right now. Your roadmap is a guess. Your week is reactive. Customers want different things. You don't know whose feedback to trust or which deal to chase. None of this means you're doing it wrong; it means you've graduated from one problem to a harder one.
The advice trap: You ask five founders what to do next. You get five answers. They're all reasonable, but they contradict each other. You pick the one that feels right and build for two months. Then you ask five more founders. Different five answers. You pivot. You're now four months in and your roadmap is a graveyard of half-finished features.
The fix isn't more advice. It's a framework that forces you to make your own decisions in a structured way and lets a coach push on the assumptions inside those decisions. That's what coaching actually is — not handing you answers but making sure you can defend the ones you give yourself.
Founder Coaching vs. CEO Coach vs. Executive Coaching for Founders
These terms get used interchangeably and they shouldn't. The differences matter when you're deciding what kind of help you need.
Executive coaching for founders is the broadest category. It usually focuses on self-management — how you communicate, how you handle stress, how you lead a team. It's the right fit for founders running real organizations with direct reports and board pressure. Less useful at the post-MVP solo stage.
CEO coach work overlaps heavily with executive coaching but adds business-strategy framing. CEO coach engagements typically assume you have a leadership team and your job is to run them. The conversations are about delegation, hiring, and operating cadence.
Founder coaching — at the post-MVP stage specifically — is about the decisions only the founder can make: which customer to focus on, which features to cut, how to spend the next 90 days. The McKelvey Method sits in this third category. It's narrower than CEO coach work because the company isn't big enough yet to need executive-level coaching. It's more product-focused than generic founder coaching because that's where the bottleneck usually is.
Month 1: Clarity — Cut Before You Build
Most founders have too many ideas, not too few. Month 1 is about cutting until what's left is obviously right. No new features get built this month. The work is decisions, not code.
Three questions drive Month 1:
Who is your customer, actually? Not the persona deck. The specific person. By name, if you can. If you can't name three real people who would buy this product right now, you don't have a customer — you have a hypothesis about a customer. The work this month is to either find three real people or change the product so that three real people show up.
What problem are you really solving? Founders are notorious for confusing the feature with the problem. A consumer marketplace I worked on didn't solve "tennis players need an app." It solved "tennis players can't find local hitting partners because the existing platforms are dead." The shape of the problem is what tells you which features matter and which don't. Most roadmaps look bloated because the problem statement is vague.
What should you stop building? This is the hard one. Every founder has features they've half-built or fully built that nobody uses. The instinct is to keep them — sunk cost. The right move is usually to cut. Month 1 of the McKelvey Method walks through the specific filter for deciding what to cut. The framework for that lives in The Clarity Filter.
The output of Month 1 is a one-page document: who the customer is, what problem you solve, and what's no longer on the roadmap. Most founders find this exercise emotionally expensive. That's normal. It's also the most leveraged work you'll do all quarter.
Month 2: Systems — Install the Repeatable Stuff
Month 2 turns one-off wins into systems that don't depend on you grinding harder. You install three: a repeatable sales motion, a prioritization system, and an execution rhythm.
Repeatable sales motion. Most post-MVP founders have closed a few deals through hustle — DMs, intro calls, friends-of-friends. That's not a sales motion. A motion is a sequence of steps that consistently produces qualified conversations. Month 2 maps your hustle into a process you can repeat without thinking. The shape varies by business — outbound, content, partnerships, ads — but the principle is the same: turn the thing that worked once into the thing you do on Tuesdays.
Prioritization system. Founders default to whatever feels urgent. That's how roadmaps explode. The McKelvey Method uses a specific prioritization formula that scores features against five inputs and outputs a ranked list. The full breakdown is in The Prioritization Formula. The point isn't the formula itself — there are dozens of decent ones (RICE, ICE, Kano, MoSCoW). The point is using one consistently so you stop relitigating priorities every Monday.
Weekly execution rhythm. What does your week look like? Most founders can't answer this without lying. The rhythm is: when you do customer calls, when you build, when you sell, when you think. Without a rhythm, every week is reactive — whoever pings you loudest wins. With one, you protect the deep work that actually moves the business.
By the end of Month 2, your business should run a noticeable amount on autopilot. Not literally — you're still doing most of the work — but the work is structured instead of frantic.
Month 3: Velocity — Measure, Decide, Delegate
Month 3 is about reading the data from the systems you just installed and making the next round of decisions, including the first one about not doing everything yourself.
The pipeline review is the first thing. After 30+ days of running a real sales motion, you have data. Where are leads stalling? Which sources convert? Which customer profiles close fast vs. slow? The answers reshape the next quarter's priorities. They also usually surface that you're spending time on the wrong customer segment — that's the most common Month 3 finding.
The first delegation decision is the second thing. Founders default to doing everything because they're cheap and accountable. That breaks somewhere around month 3-6 of operating with real customers. The question isn't "do I need help?" — it's "what's the highest-leverage thing to take off my plate first?" The full breakdown lives in The Delegation Decision. For most post-MVP founders, the answer is fractional support before full-time hires — a fractional CTO, a fractional ops person, or a part-time SDR — because the cost of a wrong full-time hire at this stage is brutal.
The 90-day plan is the third thing. By Month 3, you have enough signal to plan the next quarter with conviction. Not vibes. Specific bets, specific bets-against, and specific check-in points. The output is a one-page plan you actually believe.
What Founder Coaching Isn't
A few things I've watched the term "founder coaching" get used for that the McKelvey Method explicitly isn't.
It isn't therapy. Founders carry real psychological weight, and that work matters. It's not what coaching is for. If you're navigating burnout, anxiety, or relationship stress, see a therapist. The coaching work assumes you have the bandwidth to make decisions; if you don't, the order of operations is wrong.
It isn't an accelerator. Accelerators are 1-to-many programs that teach a generic curriculum to a cohort. Coaching is 1-to-1 work on your specific situation. Both have value; they're different products.
It isn't a course. Courses are content. Coaching is decisions. You can read 50 books on prioritization and still freeze when you have to choose between two real features. The framework is the structure; the conversation is what gets you to commit.
It isn't a CTO. If your code is on fire, you don't need coaching — you need engineering help. A fractional CTO is a different role and you can run them in parallel with a coaching engagement if both are needed.
How to Run the McKelvey Method (With or Without a Coach)
If you want to run the framework yourself, here's the abbreviated version.
Block out 90 days. Commit. The temptation to abandon the structure 3 weeks in is very real — resist it.
Month 1: write the one-page document — customer, problem, kill list. Show it to three people who'll push back honestly. Edit. The kill list should hurt a little.
Month 2: install the three systems. Sales motion, prioritization, weekly rhythm. Each one is a 1-2 day project, not a 30-day project. The 30 days are for running them, not designing them.
Month 3: review what the systems told you. Decide on the first piece of leverage you're adding (delegation, hire, fractional, automation). Write the next 90-day plan.
If you want help running it — or want to make sure the cuts in Month 1 are honest — that's what the coaching engagement is for. Book a strategy call and I'll walk you through whether the framework is the right fit for where you are. If you're earlier than post-MVP, start with the 6-week MVP framework first — coaching at the wrong stage is wasted money.
Frequently Asked Questions
- What is founder coaching?
- Founder coaching is structured 1:1 work with someone who has shipped products and run companies, focused on the specific decisions a founder is making right now. It's narrower than executive coaching (which is mostly about leadership and self-management) and broader than a fractional CTO engagement (which is mostly about technical leadership). A good founder coach pushes on product decisions, sales motions, and how the founder spends their time. They don't run plays for you — they make sure you're running the right ones.
- How is the McKelvey Method different from generic founder coaching?
- Most founder coaching and executive coaching for founders is mindset work — confidence, communication, fear, focus. Useful, but not what's broken at the post-MVP stage. The McKelvey Method assumes you have the founder fundamentals already and need help deciding what to do, not how to feel about doing it. The 90-day arc — Clarity, Systems, Velocity — moves through specific decisions you need to make about your product, customers, and time. Less psychology, more decision-making.
- Who is this for?
- Founders who shipped something real — usually with vibe coding tools, no-code, or a small team — and are now staring at a list of 50 next moves with no obvious priority. You probably have early traction, some customers or strong intent signals, and a roadmap that's mostly guesses. You don't need help building. You need help deciding. If you're pre-product or pre-traction, this isn't the right framework yet — go ship something first.
- Why 90 days?
- Three months is long enough to surface real patterns in your business and short enough to force decisions. Most founder coaching engagements are open-ended retainers, which lets the work drift. A 90-day arc forces every conversation to lead somewhere. Month 1 is for cutting and clarifying. Month 2 is for installing repeatable systems. Month 3 is for measuring and deciding what comes next. After 90 days, most founders either don't need ongoing coaching or have a clear reason to extend.
- How much does founder coaching cost?
- The McKelvey Method runs $1,500/month with a 3-month minimum, or $3,999 paid in full. That includes 2 monthly 1:1 calls, async Slack access, and a small group cohort. CEO coach engagements typically run $500-3,000/hr or $5,000-15,000/month. Executive coaching for founders at the partner level can hit $30,000+ per quarter. The pricing here is intentionally lower than CEO coach rates because the focus is narrower — product and operating decisions, not full executive leadership.
- Can I run this framework on my own?
- Yes, and a lot of the value is in the framework itself, not the coaching. The three phases — Clarity, Systems, Velocity — work whether you're running them solo or with a coach. The hard part of doing it solo is honesty. Most founders skip the cutting phase because it's emotionally expensive to kill features and ideas. A coach makes that part faster. If you have a co-founder or peer who'll push back honestly, you can run the framework yourself. If you don't, that's the role a coach plays.
- What happens after the 90 days?
- Three outcomes are common. About a third of founders are clearly ready to operate independently — they have a system, a pipeline, and a plan. About a third want a lighter touch — quarterly check-ins or async-only support to keep the systems running. The last third have grown into a different problem — they need a fractional CTO, a fractional product manager, or a real first hire — and the engagement transitions into help finding that. The framework's job is to make the next move obvious, not to make you dependent.
More on Product Leadership
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 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.
How to Build an MVP in 2026: The 6-Week Framework
Most MVPs fail because founders build too much. Here's the 6-week framework I use with clients to go from idea to paying customers — with real examples from products I've shipped.
The MVP Trap: Why Most Founders Build Too Much
Your MVP should take 4-6 weeks, not 6 months. After building 50+ products, I've watched the same mistake kill startups over and over: building too much before talking to customers.