The Pitch Is the Hard Part

Replit just released Episode 5 of Race to Revenue — “The Pitch.” The theme was deceptively simple: take a product that’s already live and learn to explain why it matters — on camera, in about a minute.

It turns out that’s the hard part.

I can talk reorder points and lead-time variance for an hour. Compressing a five-app supply-chain operating system into sixty seconds, with a clock running, is a completely different muscle. You find out fast which parts of your story are real and which are scaffolding you’ve been leaning on.

What the clock taught me

1. One sentence, or you don’t understand it yet

If it takes more than a sentence to say what the product does, you don’t understand it yet. We rewrote the Forthsuite one-liner four times that week before it stopped sounding like a feature list and started sounding like a problem a merchant actually has.

2. Demos beat adjectives

“AI-powered forecasting” means nothing to a busy store owner. Showing a single product about to run out — flagged three weeks before it would have — means everything. Concrete beats clever every time.

3. Nobody cares that it was hard to build

Every minute I spent in the pitch explaining the modelling was a minute I should have spent showing the result. Merchants don’t care how the forecast is made. They care that it’s right, and that acting on it takes a click, not an afternoon.

4. The questions you dread are your roadmap

The thing I kept hand-waving past on camera turned out to be the exact thing I needed to go fix in the product. The pitch didn’t just test the story — it pointed straight at the next thing to build.

Where this leaves Forthcast

For anyone landing here from the episode: Forthcast is the forecasting app inside Forthsuite. It reads a Shopify store’s sales history and tells the merchant what to reorder, how much, and when — so planning replenishment doesn’t mean guessing in a spreadsheet. The pitch exercise didn’t change what it does. It changed how plainly I say it.

If you’re heads-down building something, try explaining it to a stranger in sixty seconds this week. It’s uncomfortable, and it’s clarifying.

Why the Sixty-Second Rule Matters for Your Business

The impulse to explain everything comes from a good place. When you've spent months building a product, every feature feels essential. But Shopify merchants live in constant triage—they're managing inventory, handling customer service, chasing cash flow. A sixty-second constraint isn't a limitation; it's a filter for signal over noise.

The discipline forces you to identify what actually moves the needle for a merchant. If you can't explain why someone should care in that window, you haven't solved a real problem yet. You've built something clever. That's different. Apply this test to your own marketing: landing page copy, email pitches, even how you onboard new users. Can you explain the core benefit in one sentence? If not, your customer probably can't either—which means they won't act on it.

Building a Pitch When Your Product Does Multiple Things

Supply-chain tools are inherently complex. A forecasting system needs to account for lead times, seasonal patterns, stockout costs, and cash constraints. A single-app pitch seems impossible when your product touches five different workflows.

The answer isn't to list all five things. It's to anchor on the moment of friction that merchant experiences first. For demand forecasting, that's usually the fear of running out—a stockout that kills a sale, disappoints a customer, or forces an expensive expedited order. Start there. That's the sentence. Everything else (the automation, the data inputs, the monthly predictions) is proof that the solution actually works.

When you pitch to a prospect or a reviewer, you're competing for mental real estate. You won't get it by being comprehensive. You get it by being specific about a problem they already feel. The technical depth can follow in a demo or a conversation. The first sixty seconds are about recognition: Oh, this person understands what I'm dealing with.

How to Find Your One-Liner (and Know When You've Got It)

The test isn't how clever the sentence sounds. It's how a merchant reacts to it. A good one-liner should make someone nod and say, "Yeah, exactly"—not "Huh, that's interesting, tell me more." The latter means you've intrigued them. The former means you've named their problem.

Start by talking to five customers (or prospects) without a prepared pitch. Ask them to describe the worst moment related to your product category. Listen for the words they use. The emotion. The outcome they feared. That's your raw material.

Then write ten versions of a one-liner. Read them aloud. Try them on people in your slack community, or on a social post. The one that draws recognition—not applause—is usually the real one. It should feel obvious once you've said it, not surprising.

A common trap: your one-liner is still too focused on solution rather than outcome. "We predict demand using machine learning" is not as strong as "We tell you what to reorder three weeks before you run out." One describes what you built. The other describes what changes for the merchant.

What Happens After You Get the Pitch Right?

A clear pitch doesn't close deals by itself. But it eliminates a category of friction. A prospect doesn't waste time wondering what you do. Your sales team doesn't struggle to explain the product. Your content, ads, and emails all align because they're answering the same question.

More importantly, a tight pitch forces product clarity. If you can't say it simply, something in the product or positioning is unresolved. The camera (or the conversation) exposes that. Use it. Fix what it shows you. The pitch isn't just a sales tool—it's a diagnostic for whether you've actually solved a problem or just built something complicated.