Growth Loops
One loop where using the product makes the next user. Build the smallest version that actually turns.
Why give it a weekend
No prizes for this one
This jam does not award prize money or credits. Everything below is what you take away from it, and it is the reason most people come.
An expert on your actual problem
An hour of questions about your product and your list, not the topic in general.
Everyone else’s workflow, not just your own
Everyone publishes how they did it. You write one and you read the rest.
A finished thing, not a plan
A hard deadline and a room of people working the same 48 hours.
A permanent entry in the archive
Your submission stays up under your name. Hide it whenever you want.
How the 48 hours run
- Done
Joining opens
Anyone can claim a place. Joining closes 24 hours before the deadline so there is time left to ship.
- Next up
Kickoff
The jam opens, the brief goes live and the resource pack unlocks.
Joining closes
The last moment to claim a place. After this the jam runs to the end with whoever is in.
Deliverables due
Submit what you shipped and the workflow behind it. Both are public by default, and you can hide yours at any time.
The expert
To be announced before the jam opens. The session runs live during the jam and takes questions about your product and your list, not the topic in general.
What you submit
**You have 48 hours to get one growth loop running inside your startup.**
A loop is not a campaign. A campaign stops when you stop paying for it. A loop is a path where somebody using the product produces the next person who does.
Build the smallest version that genuinely closes. One referral path working end to end beats three half-built ones, and unlike a growth plan, a loop either turns or it does not.
Possible directions: Referral mechanics. Invite flows. Shared artefacts that carry your name. Public profiles. Embeds and widgets. Content the product generates. Network effects between users. The instrumentation to see whether it turns. Something else entirely.
This is a build weekend. By Sunday the loop should be live, and you should be able to point at the step where one user becomes two.
Plus the workflow: where you started, what you did in order, what did not work, what you would change.