CRM & Sales Pipeline
The machinery between a lead and a customer. Most founders run it in their head, their inbox, and a spreadsheet they stopped updating.
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 make the machinery between a lead, a conversation and a customer meaningfully better inside your startup.**
No CRM at all is a valid starting point, and so is a CRM with four hundred stale deals in it. The second one is usually worse.
By Sunday there should be a pipeline you can open and trust. The test is simple: can you say, without thinking, what the three most likely deals to close this month are, and what the next action is on each?
Possible directions: Lead capture. Enrichment. Qualification. Pipeline stages. Meeting logging. Next actions. Follow-up automation. Reporting. Getting data in without typing it. Something else entirely.
This is a build weekend. By Sunday there should be something running that was not running on Friday.
Plus the workflow: where you started, what you did in order, what did not work, what you would change.