.png)
How to Win a Hackathon
A Practical Playbook for Developers and Non-Developers Alike
You don't need to be the best coder in the room to win a hackathon. You need to be the most prepared team.
That's not a motivational line, it's what actually happens. The teams that take home prizes are rarely the ones with the cleanest code. They're the ones who picked the right problem, built something that works well enough to demo, and walked into their pitch knowing exactly what the judges cared about.
This guide gives you a practical playbook for doing all three, whether you're a full-stack engineer or someone who's never shipped a line of code. And if you're heading to Hack the Block at Paris Blockchain Week this April, there's a dedicated section at the end with everything you need to show up ready.
1. Pick One Problem and Solve It Completely
Scope kills more hackathon projects than bad code. The temptation is to build something ambitious. Resist it. Pick one specific problem, solve it well, and make sure judges can see the solution working.
A simple test: can you explain your project in one sentence? If not, cut scope until you can.
2. Build a Balanced Team
You need more than developers. The teams that consistently win cover four roles: someone who builds, someone who designs the flow, someone who keeps the team on track, and someone who owns the pitch. If you're not technical, the strategist and pitcher roles are just as important to winning. And harder to fill well.
3. You Don't Need to Code. You Need to Ship
AI tools like Claude Code have changed what's possible in 36 hours. Non-developers are winning top prizes at major hackathons by using AI to build working prototypes step by step. You're not aiming for production-ready. You're aiming for demo-ready. Write out what your product does in plain language, build the core flow iteratively, and test your demo path obsessively before you pitch.
4. Talk to Mentors and Judges Early
Most teams never do this and it's free intelligence. Workshops, coffee breaks, and office hours are a chance to understand what judges actually care about. A five-minute conversation can tell you whether your approach makes sense and how to frame your pitch. By the time you walk into the final presentation, you should already know what will land.
5. Prepare Your Demo for Failure
Live demos break. Plan for it. Build a hardcoded fallback state that shows the end result even if something goes wrong, and record a screen capture of the full working flow as a backup. If something fails mid-pitch, switch to your fallback calmly and keep talking. Judges are evaluating your thinking, not your luck.
6. Your Pitch Is Half the Battle
Structure it simply: the problem, your solution, a live demo, and why it matters in the real world. Rehearse until you can deliver it in under five minutes. Cut anything that isn't core to your value proposition. If a feature isn't finished, say "this ships in v2" and move on. A weak pitch is the one thing you can't recover from.
7. Manage the Clock
Set your own internal deadline a few hours before the real one. This gives you time to run through the demo, fix last-minute issues, and practice the pitch without pressure. The teams that manage their energy — eat, sleep a little, stay calm in the final stretch — consistently outperform the ones running on caffeine and chaos.
Hacking on XRPL at Paris Blockchain Week? Read This Too.
Hack the Block runs April 11–12 at a secret Paris venue. It's a 36-hour sprint judged on Innovation, Execution, Impact, and Pitch, with over €10,000 in prizes and a room full of the investors and tech entrepreneurs you actually want to meet. Teams can register solo or form on-site (2–5 people recommended). No prior hackathon experience required.
Three tracks are in play: Make Waves, Impact Finance, and a Secret Track with full details revealed on the day. That's intentional: the teams that arrive prepared to adapt will have an edge over those who show up with a rigid idea.
Before you arrive:
Get familiar with XRPL's core building blocks: payments, escrows, tokenization, the native DEX, DIDs, and RLUSD (XRPL's native stablecoin). You don't need to master all of them, but knowing which tools are available means you won't waste time discovering them mid-hack.
- 📚 XRPL Commons Training Docs : structured tutorials on XRPL basics, token issuance, the EVM sidechain, and more
- 🛠️ XRPL Commons GitHub : starter repos including scaffold-xrp (a Next.js dev stack with multi-wallet support) and xrpl-dev-skills (a Claude skill built specifically for XRPL dApp development)
- 🧪 Testnet & Faucet : test your transactions for free before the event
On the day, use your mentors. XRPL Commons brings ecosystem experts specifically to support participants. There are two dedicated office hours sessions (Saturday 4–5pm and Sunday 11–11:30am) : use them not just for technical help, but to pressure-test your idea and get feedback on your pitch framing.
Judges will be looking at how well you use XRPL natively. A project that simply processes a payment on-chain will score lower than one that uses escrows, DIDs, or the AMM in a way that only makes sense on XRPL. Think about what your solution needs that a traditional database or generic blockchain can't provide. Then build that part first.
And remember: this hackathon is as much about being discovered as it is about winning. Past participants have walked away with job offers, funding conversations, and pilot integrations. Build something real, pitch it clearly, and treat the weekend as the start of something, not the end.
Sign up for the PBW Hackathon
