Build the magic before the machinery
Put the core experience in front of real people before you spend the sprint on accounts, payments, and scale.
Ben Sufiani · The article: The Pirate Launch Plan
A working prototype can answer the question faster
Ben used to validate an app with a landing page and a customer-development survey. Once a focused prototype became faster to make than that research setup, the prototype itself became the clearest way to show the idea and watch whether someone understood it.
The speed does not justify building the whole product. It shortens the distance between the idea and the first piece of real behavior.
“It's now easier to build the complete prototype than to set up the landing page and a survey. With vibe coding, it's so much faster to get to the first prototype.”
Start with the magic interaction
The magic interaction is the smallest moment that makes the product different: the result someone came for, without the surrounding account system, payment flow, or scale work. Ben asks builders to name that moment and make it work on a live URL.
A database, sign-in, billing, and rate limits may all matter later. Building them first only postpones the question of whether the core experience deserves a product around it.
“Try to wrap your mind around the magic interaction you are promising your customer, and don't build all of the scaffolding around it yet.”
Make contact before you make the product complete
Once the prototype is live, the next move is not another building session. Ben recommends listing ten people or places where the intended audience can see it, then watching for the critical behavior: do they use the interaction as expected, and what surprises them?
At this stage the prototype does not need to scale or look finished. It needs to be concrete enough that a real person can react to the experience instead of the pitch.
“It doesn't need to be stable. It doesn't need to be pretty. It needs to be something magical, and you need to put it into the hands of people.”
Add the shell only after the core earns it
Feedback from the magic interaction decides what deserves a real product shell. Then the team can add the clear landing page, secure account boundary, database, onboarding, and payment path needed for a customer to use it properly.
Ben frames commitment as a ladder. Trying the interaction asks little; signing up asks more; a trial with payment details or a purchase gives stronger evidence. The right rung depends on the product, but the goal is evidence rather than decorative completeness.
“The important question is: is this something that people want? Then you don't even need to worry about the tech stack you're using.”
Grow through one channel, then repeat
The first growth pass stays as narrow as the first build. Choose organic distribution, paid acquisition, or direct outreach based on where the audience can realistically be reached, then focus on whether the first few people receive value.
From there, the bottleneck chooses the work. If the experience disappoints, build. If the right people never reach it, grow. The launch becomes a loop rather than a handoff from a building phase to a later marketing phase.
“Idea, prototype, contact, build, grow, repeat – build, grow, build, grow.”
Dive deeper
Follow the six stages as a practical checklist for your next focused product sprint.
Read the insightBring the product moment you want to test and discuss the smallest useful launch with the community.
Register freeKeep the complete library of practical sessions available with the Pirate Pass.
Every recording with the Pirate Pass