How to Win the Shipyard Creator Contest: A Builder's Playbook
The Shipyard Creator Contest is a short, high-intensity event in which participants build a real, monetized mobile app for an influencer audience. With so little time on the clock, the strongest entries tend to be the ones that pick a problem worth solving, iterate in small loops, and present a clear story at the end. What follows is a four-step working plan plus the checkpoints that help a small team stay on course. Rules, dates, and eligibility are set by the organizers, so verify them before you commit (OWNER_CONTEST_RULES_URL).
The four moves that decide the outcome
In a compressed contest, the deciding factor is rarely raw polish. It is whether you picked a problem worth solving, tested it with the people who have it, and kept improving the thing in public. The sequence below is a loop: choose a creator brief and shape an idea around it; interview people who match that brief's audience; build in short, purposeful blocks and launch early; recruit testers and learn from the ones who leave; then package the result as a short video and a written proposal. Each step feeds the next, so expect to revisit earlier decisions as feedback arrives. The organizers run the contest and publish the rules; treat this guide as a working plan, not an official brief.
Step 1: Choose a brief and shape the idea
Begin with the creator briefs, not with a concept you are already attached to. Seven briefs are available, and they vary enough that one will suit your instincts better than the others. Trying to force an existing idea into a brief seldom yields a strong entry. Choose the brief that resonates, then keep your first version of the idea modest; it does not have to break new ground yet. A short checklist can help you decide: review all seven briefs before committing; identify the audience each brief implies, not just its subject; state your idea as a single sentence about the problem, tied to that audience; check whether you can find three real people matching the audience within the week; and set aside any idea that demands major infrastructure before the first user test. The organizers publish the briefs, so confirm the current set before you start (OWNER_CONTEST_RULES_URL).
Talk to people before you build
Great ideas usually emerge from conversation, not from solitary brainstorming. Take your preliminary concept to people who resemble the brief's target customer. Start with open-ended questions about the problem they experience and how they imagine it could be solved. The aim is empathy: understand the problem well enough that you can predict what a good solution would feel like to them.
A worked example: if a brief points to creators who struggle to plan content, do not open with 'would you use an app that plans your posts?' Instead ask how they currently decide what to post, where that process breaks down, and what they have tried. The answers tell you whether the real pain is planning, scheduling, or something else entirely. You are ready to build when you feel you must build this specific app because you understand the customer better than anyone else does.
Step 2: Build in three time-boxed blocks
Set a timeline and keep to it. Waiting for inspiration is a losing strategy in a short contest; the productive move is to start building and let feedback steer you. The three-block rhythm below gives each phase a distinct purpose so you do not over-invest too early.
| Block | Purpose | What 'done' looks like |
|---|---|---|
| 4 hours | Prove the concept works | Something barely functional that convinces you the idea is real; minimal UI, no heavy infrastructure |
| 8 hours | Make it showable to a customer | Polished enough to demo; mock data and simulated requests are acceptable; it should feel like it works |
| 24 hours | Make it usable without you | Incorporate feedback, drop what users ignored, add what enough people asked for; launch if possible |
The 8-hour block is where many teams stall. The test is not whether the app is finished but whether you would be willing to put it in front of a customer. If showing it feels slightly embarrassing, that is a sign you are testing early enough. After the 24-hour block, keep shipping: add features, fix bugs, and never let more than a day or two pass before improvements reach users.
Step 3: Grow your user count
Finding users is the genuinely difficult part. An app-store launch is not required by the contest, though it does no harm: a store listing makes it easier for customers to find and pay for the app, and a larger user base raises revenue potential. The bigger early benefit is feedback, since acting on what users tell you is what turns a rough build into a serious contender. Recruit testers through the organizer-run Shipyard community channel (OWNER_DISCORD_INVITE). Expect churn, because people abandon an app once it stops being useful, and a first version may lose nearly everyone. That is the reason to relaunch repeatedly. The most informative conversations are with users who left, since they can name the missing features that drove them away, so make an effort to reach them directly.
Step 4: Tell your story in the submission
This last step concerns presentation more than the app itself. Under the organizers' submission guidelines (OWNER_SUBMISSION_REQUIREMENTS), an entry includes a short video and a written proposal, and judges will examine both closely. Clear messaging is necessary but not enough: a strong story frames the problem so it lands emotionally and casts you and your app as the answer. A simple narrative structure helps. Establish the problem, show the struggle, present your solution as the turning point, and close with the outcome you want for the user. Use the same arc in the video and the written proposal, and begin both well before the deadline rather than the night before. With a clear structure, each piece should take only a few hours.
Make use of the Shipping Container
The organizers put together a curated bundle of partner tools and credits, called the Shipping Container, to reduce friction while you build, launch, and monetize your app. You are free to use whatever tools you prefer; the bundle is simply an accelerator. Registration details and how the bundle reaches you depend on the current program setup, so check your inbox, junk folder included, and verify the delivery method with the organizers (bundle access: (OWNER_BUNDLE_ACCESS); program window: (OWNER_CONTEST_DATES)). Treat the bundle contents as conditional until the organizers confirm them for this edition (OWNER_BUNDLE_PARTNERS). If the bundle is active, two categories are worth planning around. For ideation and design, Mobbin lets you study real-world UI and UX patterns, including onboarding and paywall examples from popular apps, so you can adapt proven patterns for your own monetization and experience. Manus can support analysis during ideation and growth, and can help produce landing pages; think of it as an extra team member for the contest. For building, the bundle has included AI-assisted app tools such as Fastshot, Anything, Replit, and Rork, usable through their mobile apps or web editors. Where those tools are configured for the subscription platform, you authenticate with your subscription platform account and can then prompt the AI to add subscriptions, lifetime upgrades, entitlements, subscription-platform-powered paywalls, and more. Once in-app purchases work, Paddle has also been part of the bundle, letting you add web-based payments alongside them and test additional monetization paths. Confirm the current partner list and credit terms before relying on any of these (OWNER_BUNDLE_PARTNERS).
Finish line: ship the app, not the concept
What matters at the end is a working app in people's hands, not a polished concept document. Build something people love, and something you enjoy working on. Get it to users early; once real feedback starts arriving, momentum usually follows. The linked deep-dive guides on idea selection, fast building, growth, and pitching offer more detail on any single step. The organizers publish the official rules and deadlines, so confirm them before you submit (OWNER_CONTEST_RULES_URL).
Frequently asked questions
How many creator briefs are there, and how should I choose one?
There are seven briefs, and they differ substantially. Watch all of them before committing, then pick the one that resonates most with your instincts. Avoid forcing an existing idea into a brief; start from the brief and let the idea take shape around its audience.
Do I need a fully finished app to enter?
No. An MVP is enough, provided it is a real, monetized mobile app. The build rhythm in this guide is designed to get you to a usable version quickly, then improve it through repeated launches rather than one big release.
Does Shipyard require an app-store launch?
It does not require one, but launching does not hurt. An app-store presence makes it easier for customers to find and pay for the app, and more users means more feedback and more revenue potential.
How do I add subscriptions and payments during the contest?
Where the bundled AI-assisted build tools are configured for the subscription platform, authenticate with your subscription platform account, then prompt the tool to add subscriptions, lifetime upgrades, entitlements, and subscription-platform-powered paywalls. Once in-app purchases work, Paddle has also been available in the bundle for web-based payments alongside them. Because partner availability and credit terms can change, confirm the current list with the organizers before you build around any of these tools (OWNER_BUNDLE_PARTNERS).
What does the final submission need besides the app?
A short video and a written proposal. Judges will examine both closely, so state clearly what the app is about and frame the problem so it lands emotionally. Start both early; with a clear structure, each should take only a few hours. Confirm the current requirements with the organizers (OWNER_SUBMISSION_REQUIREMENTS).