You have a business idea that’s been rattling around in your head for weeks. Maybe months. It surfaces when you’re in the shower, during your commute, in the middle of meetings where you should be paying attention. You keep thinking about it, but you haven’t done anything with it.
This weekend, you’re going to change that.
Not next weekend. This one. In roughly 36 hours of focused work — Saturday morning through Sunday night — you’re going to take that idea from speculation to signal. You won’t have a finished product. But you will have a real answer about whether this idea has enough potential to deserve more of your time.
I’ve run versions of this sprint with startups at the Startup Burgenland accelerator and with individual founders I advise. The compressed timeline is the feature, not the limitation. Constraints create clarity. Here’s the exact playbook.
Friday Night: Preparation (30 Minutes)
Before the sprint starts, do three things:
1. Write your hypothesis. One sentence: “I believe [specific people] will pay [specific price] for [specific solution] because [specific reason].” If you can’t write this sentence, you’re not ready for a sprint — you’re still in the problem-discovery phase.
2. Make your contact list. Write down 15-20 people who might be your customers. Real names. Real contact methods. These can be people you know, people in relevant communities, or people whose contact information is publicly available.
3. Clear your schedule. No errands, no social plans, no “I’ll squeeze it in around other things.” This weekend has one purpose. Everything else waits.
Saturday Morning (8am-12pm): Customer Discovery
Hours 1-2: Outreach
Send messages to all 15-20 people on your list. Keep it simple:
“Hey [name], I’m working on something this weekend and could use your input. I’m exploring [problem area] and want to understand your experience. Would you have 10 minutes for a quick call today?”
Also post in 2-3 relevant online communities: “I’m researching [problem]. If you deal with this, I’d love a quick 10-minute conversation this weekend. DM me.”
Hours 2-4: Discovery Calls
As responses come in, run quick conversations. Aim for 6-8 calls by noon. For each one:
- Confirm they have the problem (don’t assume)
- Ask how they currently handle it
- Ask what’s most frustrating about their current approach
- Ask how much time or money the problem costs them
- Ask what a good solution would look like
Don’t pitch. Don’t describe your solution. Just listen and take notes.
Decision point at noon: Do 4+ out of your conversations confirm the problem exists and matters? If yes, continue. If no, your hypothesis might be wrong — either adjust your target audience and try new conversations in the afternoon, or pivot to a different problem entirely.
This is the same rigor I describe in validating in 72 hours, compressed further. The principles are identical — the timeline is just tighter.
Saturday Afternoon (1pm-6pm): Build the Offer
Hour 1: Synthesize Your Conversations
Write down the patterns from your morning calls:
- The most common description of the problem
- The exact words people used (their language, not yours)
- The current solutions they’re using and where those solutions fail
- What they said a good solution would need to do
Hours 2-4: Create Your Landing Page
Build a simple page that presents your offer. Use Carrd, a Notion page with a payment link, or any tool that lets you work fast. The page needs:
- Headline using the exact language your potential customers used
- Three bullet points explaining what you’ll deliver
- One specific price
- One call to action (email capture, waitlist signup, or pre-order)
Don’t worry about design. Don’t worry about perfection. This page exists to test a specific question: will people commit when presented with a clear offer?
Hour 5: Create a “Concierge” Delivery Plan
If people buy, how will you deliver the value? For this sprint, the answer should be manual. If your product would eventually be software, deliver the first version as a service. If it would be a course, deliver it as live coaching. If it would be a physical product, deliver a handmade version.
The concierge MVP approach is perfect for weekend sprints because it requires zero technical infrastructure. You’re selling the outcome, not the mechanism.
Write a simple plan: “When someone signs up, I will [specific manual steps] to deliver [specific outcome] within [specific timeline].”
Saturday Evening (7pm-9pm): Pre-Launch Outreach
Go back to everyone you talked to in the morning. Send them the landing page:
“Hey [name], based on our conversation this morning, I put together something that might help with [the specific frustration they mentioned]. Take a look: [link]. If it sounds useful, I’d love you to be one of my first users.”
Also share the page in the communities where you posted earlier. Be direct about what you’re offering and who it’s for.
Then stop. Go do something relaxing. You need to let the outreach marinate overnight.
Sunday Morning (8am-12pm): Gather and Analyze Signals
Hours 1-2: Check Results
Open your analytics. Check your email. Look at your sign-up or payment page. Answer these questions:
- How many people visited the page?
- How many took the action (signed up, joined waitlist, pre-ordered)?
- Did anyone reach out with questions?
- Did anyone share the page with others?
Hours 2-4: Follow Up
For everyone who visited but didn’t act, send a follow-up: “Hey, noticed you checked out the page. Any questions I can answer? Curious what you thought.”
For everyone who acted (signed up or paid), send a thank-you and confirm delivery details. Ask: “What made you decide to sign up?”
For everyone from your morning conversations who didn’t visit the page, send a gentle reminder.
The follow-up matters enormously. Most people who are interested but didn’t act just got distracted. A simple nudge converts a surprising percentage.
Sunday Afternoon (1pm-4pm): Make the Call
Now you have data. Not a mountain of it — a weekend’s worth. But it’s real data from real people about a real offer, which is infinitely more valuable than months of theoretical planning.
Strong Signal (Continue Building)
You should continue if:
- 3+ people committed (paid, signed up with email, or offered to be early testers)
- The language on your page clicked (people said “yes, exactly” or “where has this been?”)
- At least one person shared the page or referred someone without being asked
- You’re energized by the conversations you had
If this is you, your next step is to deliver the value to your first users and learn from the experience. Plan your first week of delivery.
Moderate Signal (Iterate)
You should iterate if:
- 1-2 people showed strong interest but didn’t commit
- The problem landed but the solution framing didn’t quite land
- People asked questions that revealed a mismatch between your offer and their need
- You see potential but the current angle needs adjustment
If this is you, adjust the hypothesis and run another sprint next weekend. Change one variable: the target audience, the offer framing, or the price. Don’t change everything — change one thing and test again.
Weak Signal (Park or Kill)
You should stop if:
- Zero people committed despite reasonable traffic
- Conversations revealed the problem isn’t painful enough to drive action
- You had to explain the problem to people rather than having them recognize it
- You found yourself making excuses for the results (“they just didn’t understand it”)
If this is you, consider whether to park or kill the idea. Parking means writing down what you learned and revisiting in 3-6 months. Killing means moving on entirely.
Sunday Evening (4pm-6pm): Document and Decide
Regardless of your signal, spend the last two hours documenting:
- What you hypothesized vs. what you found
- The most surprising thing you learned
- The exact language customers used to describe the problem
- Your decision: continue, iterate, or park/kill
- If continuing: your three specific next actions for Monday
This documentation is invaluable. Even if you kill this idea, the customer language, the patterns you observed, and the lessons you learned will inform everything you do next.
Why Weekends Work
The weekend sprint works for a specific reason: it eliminates the slow drift of prolonged “validation” that never produces a clear answer.
When you give yourself months to validate, you fill the time with preparation activities that feel productive but produce no signal: more research, more planning, more waiting for the perfect time. A weekend forces you to do the only things that actually produce signal: talking to people and making an offer.
It’s uncomfortable. It’s fast. And it produces more clarity in 36 hours than most founders get in 36 weeks.
Takeaways
- Friday night: prepare. Write your hypothesis, list 15-20 contacts, clear your schedule.
- Saturday morning: discover. Talk to 6-8 potential customers. Confirm the problem exists and matters.
- Saturday afternoon: build. Create a simple landing page with a clear offer, price, and call to action.
- Sunday morning: measure. Check results, follow up with everyone, gather real data.
- Sunday afternoon: decide. Strong signal means continue. Moderate means iterate. Weak means park or kill. Document everything regardless.
