I Agonized Over a Platform Decision for Two Weeks. Here's What I Got Wrong (and Right).
A personal confession about Skool, the Hub, a 180-degree pivot, and what Leverage-First founders can learn from my very expensive lesson in distraction.
Recent Episodes on Exponential Scale
EP030 — Stay in the Game Long Enough to Build an 8-Figure Business
Max Kang built Cupkin — a bootstrapped children's sticker book brand — to eight figures with fewer than 10 people, no VC, and no senior hires. One product, one channel, relentless focus. Nearly 1 million books sold per year.
EP029 — $9M ARR, 110 to 55 People, and a Platform Rebuild
Kyle Racki built Proposify from an agency background to $9M ARR, grew to 110 people, hit a cash crunch, cut the team in half, and rebuilt the platform from scratch. An honest conversation about what scaling really looks like.
EP028 — $500M From Watching, Not Asking
Alex Hillman co-created the 30x500 methodology that generated $500M+ in student earnings. The "get out of your head" framework for Sales Safari, ebombs, and building a ready-to-buy audience before you ever launch a product.
EP027 — Million-Dollar Solo Founder Hardware Product
Scott Heimendinger spent five years building the world's first ultrasonic chef's knife — solo, with $2M in pre-seed funding. What hardware without headcount actually looks like from the inside.
EP026 — $6M ARR With All Agents and 1 Employee
Ben Broca built Polsia to $5.6M ARR with one human employee and ~5,000 companies running on autonomous AI agents — 10,000+ tasks per day, while he sleeps. The lever-first operating model made concrete.
Let me tell you a story I'm mildly embarrassed about. Not deeply embarrassed — just enough to fuel a newsletter article and a public reckoning with my own decision-making.
A few weeks ago, I made a very analyzed, very reasoned, very "I-ran-multiple-frameworks-on-this" decision to move our community to Skool instead of the Scalebrate Hub. Pro/con lists. Strategic fit models. AI-assisted analysis. I consulted the guides. I consulted my own brain. Multiple times.
Then I started building it.
Two weeks later, I blew the whole thing up and went back to the Hub.
Which is either a story about terrible decision-making or excellent decision-making. Depending on how charitable you're feeling.
The Very Convincing Path to the Wrong Answer
Here's how it started.
Our own Hub platform had gaps — gamification wasn't where I wanted it, some UX friction existed, a few features still needed building. Skool, by contrast, had network effects, built-in discoverability, a growing ecosystem of communities. Multiple analyses pointed toward Skool.
So I committed. Locked the display name. Built out the classrooms. Configured the tiers. Wrote onboarding flows. Started picturing a thriving community of leverage-first founders scaling with the Skool tailwind behind them.
"I've done the analysis," I told myself. "This is disciplined strategic thinking. This is what good founders do."
And then I actually started using Skool seriously.
The cracks appeared fast.
No real API or webhook integration. Which meant Skool would never properly talk to the Hub. Members would need two separate accounts, two separate login experiences, two separate purchases. I'd be maintaining two parallel content pipelines forever.
The Skool ecosystem — and I say this with only mild snark — has a vibe. It leans toward "six-figure course launch" energy and "hey bro, want to borrow my audience?" energy. Less "leverage-first founders building real businesses," more "growth-hack influencer content." Not exactly the neighborhood I want Scalebrate in.
And then the biggest gut punch: discoverability on Skool is real, but it's also full of copycats. Which was simultaneously validating (yes, the market exists) and deflating (also, everyone's here already).
But the real kicker — the one that made me put down the laptop and stare at the ceiling — was this realization:
The Hub's problems were fixable. Skool's problems were structural.
And more importantly: none of this was actually solving the real problem. The real problem was customers. Without customers, the platform was irrelevant. And I was burning my scarcest resource — focused attention — building on a platform I'd already found fault with.
"I thought I'd made the right call. I'd done the analysis. The analysis was right. And somehow I was still wrong."
The Iceberg Problem with Strategic Analysis
Here's the concept I keep bumping into: analysis tells you about the top of the iceberg. It's what you can see — the features, the pros, the cons, the strategic fit score.
What it doesn't show you is operational reality. The underwater mass. The "week three of actually building this" experience.
Most founders who think in systems and frameworks — and I include myself firmly in this category — are excellent at the visible part. We love a good framework. We love structured analysis. We love when the data points somewhere.
But the iceberg test is different. It asks: When you're living this decision in the third week, does the analysis hold up?
The answer, in this case, was no. And it took actually building it to find that out.
Why This Matters Especially for Leverage-First Founders
If you're running a small team, you don't have the slack budget to run parallel experiments indefinitely. A 500-person company can maintain two community platforms while figuring out which one to consolidate. You cannot.
Here's what platform ambiguity actually costs:
- Split attention — every hour on Skool was an hour not spent on actual customer acquisition
- Operational overhead — two platforms means two content pipelines, two onboarding flows, two sets of integrations, two sources of support questions
- Brand confusion — sending your audience to two different homes signals "we haven't made up our minds yet"
- Decision debt — unresolved strategic choices accrue compound interest on your attention every single day
The Leverage-First principle isn't just about doing more with less. It's about not generating negative leverage — the complexity, overhead, and parallel systems that slow everything down.
The moment I mapped out what it would actually take to run both platforms simultaneously, the decision made itself.
The Decision Reversal Framework (So You Don't Repeat My Expensive Lesson)
Was this a bad decision? Here's my honest answer: it was a correctable decision — which is better than a stuck one.
Here's the framework I'm using now before committing to any major platform or tooling decision:
Step 1: Reality-test before committing. Before building, actually use the platform for a real use case — not a demo, not a tour. A real workflow. A real user journey. One week of hands-on work will tell you what a spreadsheet can't.
Step 2: Hunt for structural walls, not feature gaps. The question isn't "does this have good features?" It's: "What are the constraints I can never work around?" API limitations, ecosystem misalignment, integration blockers — these are load-bearing walls, not annoyances.
Step 3: Name the actual problem. Write it down. Not the supporting problem, the core problem. In my case: we need customers. Platform choice is a supporting decision. When supporting decisions start eating core execution time, something has gone wrong.
Step 4: Make peace with the reversal — fast. Two weeks of course correction is infinitely cheaper than six months of platform debt. Reversing a decision when you have new information isn't failure. It's exactly what good judgment looks like.
Step 5: Burn the ships after you reverse. No hedging. No "maybe we'll revisit Skool in Q3." One platform, full commitment, full attention. Complexity is the enemy of execution.
Today's 10-Minute Action Plan
Are you holding onto a "committed" decision that reality has been quietly poking holes in?
- Name it — What strategic commitment has been eating background attention?
- Run the iceberg test — What's the operational reality you've been glossing over in the analysis?
- Find the structural wall — Is there a constraint in this decision that will never resolve itself?
- Restate the core problem — Is this decision still solving the actual problem you named?
- Decide and close the loop — Reverse it cleanly, recommit fully, or run a 1-week reality test. But don't leave it in limbo.
The Honest Punchline (And a Direct Ask)
The Scalebrate Hub isn't perfect yet. The functionality gaps are real — gamification, course prerequisites, referral tracking, onboarding depth. We know exactly what needs to be built. And we're building it.
But here's the thing: customers don't care about platforms. They care about value, community, and whether the experience delivers on its promise. The Hub's gaps are a roadmap. Skool's problems were a ceiling.
So we're all in on the Hub. One platform. One community. One place where leverage-first founders come to build, learn, and scale without adding headcount or chaos to their businesses.
If you've been thinking about joining — this is the moment. We're building something genuinely different: a community grounded in real frameworks, peer accountability, and systems that actually scale. Not another Skool clone. Not another Discord server where messages disappear into the void.
Join the Scalebrate Hub and become a founding member →
Founding membership is open now. First 50 members who complete onboarding and three workshops earn the Founding Member badge — the permanent record of being here before this thing got big.
Come join us. I've already agonized over enough decisions for both of us.
Stay Lean. Think Big. Scale Smarter.
What's a strategic decision you've been holding onto that reality has been quietly poking holes in? Hit reply — I read every one.