GOOD IDEAS. GREAT COMPANY.DAN + STEF / BASECAMP KOH TAO · OCTOBER 2026
15–17 OCTOBER 202618¾ FOCUSED HOURSNEXT ADVENTURE: SINGAPORE · NOVEMBER
YOUR INVITATION / FOUNDING CREW: TWO
Stef, welcome aboard.
I’ve made us a little founders retreat. Three days. You and me. Something we create together.
We’ve worked on WeGoDive together before. This time, let’s choose the idea together from the beginning: something we both care about, can make real, and might turn into a little business.
There’ll be coffee, workshops, proper making time, workouts, dog walks and a celebration dinner on Saturday. A bit of structure to get us moving, with room for the fun parts.
No competition. No pressure to create a unicorn. Let’s finish with something tangible, learn how we like working together and get excited about where we can take it.
Equal partners. Different strengths. Both shaping what we make. Love, Dan
Your retreat brief
Make something real. Get excited about it together.
By Saturday at 18:00, have a working first version you both feel excited to show someone, a clear offer and a realistic path to selling it.
Choose the idea together on Thursday. Build a tiny tool, digital product or clearly defined service. Start with the customer, then use your existing infrastructure to make the experiment real. The purpose is shared excitement and a product you want to keep developing.
WE
Made by both of you
The result should feel like yours together: useful, tangible and worth continuing. Customer feedback helps shape it; a sale is welcome whenever it comes.
What we will have created
One chosen customer, problem, offer and price.
One usable first version and a clear offer you are happy to show potential customers.
A clear route to payment and delivery using SideEye Labs infrastructure; test checkout if the product is ready.
Useful feedback from a few relevant people; aim for three conversations, without turning it into a quota.
A shared demo, notes on what you learned and a next step you both want to take.
Tick as you go. These checks and your notes save in this browser only; they do not sync between devices. Export a backup before switching.
Each workshop has a focus, questions for both of us, timed steps and a place to record our decisions. Think separately, compare, then make something together. Alternate who facilitates; neither person gets the final say by default.
Notes are saved on this browser, not shared between devices. Use one laptop for the joint record and export a backup. No accounts or backend syncing.
DAY 1 / THURSDAY
Find our spark
Discover a problem, choose together and start making.
Suggested base: Tropico for the morning, home for afternoon sprints. Check opening hours, Wi-Fi and permission for a longer laptop session on Wednesday; the home table is your fallback. Venue visits are not booked.
Dog walk
Fresh air. No product meeting required.
Breakfast & get ready
A slow start; breakfast stays protected.
Travel & settle in
Travel or settle in. Handle larger chores at lunch or after 18:00.
01 / Find the spark · TOGETHER
15 min welcome + interests; 20 min solo problem lists; 30 min share with equal airtime; 30 min generate ideas; 25 min reflect on excitement and fit. Output: three ideas you both want to explore.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
What would we both enjoy making that solves a real problem?
How to run it
Use the opening reflection, solo writing, sharing, idea generation and shortlist timeboxes in the agenda. Alternate who speaks first. Keep a visible list.
Prompts
Write separately before sharing. Ask: when did this last annoy someone? What do they do today? What makes each of us excited?
Leave with
Three shared candidates, each with a customer and a problem.
Ready to move on when
Both can explain why at least one idea is interesting.
If we get stuck
If ideas are too broad, choose one customer and one recent frustration; do not choose the technology yet.
15 min choose one idea by mutual yes; 20 min define customer, offer and price; 40 min interview/message five relevant people. Output: one offer + five test requests sent.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
Which small idea deserves a first test?
How to run it
15 min mutual choice; 20 min one-sentence offer + rough price; 40 min send five discovery requests or hold conversations.
Prompts
For each candidate: who needs it, can we reach them today, what could we make by Saturday, and do we both want to? Ask customers about the last time they faced the problem.
Leave with
One candidate, one offer and a short list of assumptions with requests sent.
Ready to move on when
Both say yes; the customer and first deliverable are specific.
If we get stuck
If nobody replies, use known examples and mark assumptions clearly. Arrange later conversations; do not pretend silence is validation.
Eat, do a small chore, check replies. No compulsory working lunch.
03 / Make the call · TOGETHER
20 min review evidence; 20 min simplify scope; 20 min agree owners and acceptance criteria. Output: build / adjust / stop decision + three essential features max.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
What is the smallest useful version we will actually make?
How to run it
20 min evidence; 20 min scope; 20 min owners and acceptance criteria. Keep three essential features maximum.
Prompts
What did we learn? Which assumption matters most? What must happen for someone to get value? What can be manual?
Leave with
A one-page brief: customer, promise, price hypothesis, scope, owners and spend limit.
Ready to move on when
Both know their next task and how we will tell it is done.
If we get stuck
Cut a feature or choose a manual delivery. If the customer problem has collapsed, revisit the strongest alternative together.
10 min agree tasks; 60 min work side by side with distinct ownership; 20 min demo to each other. Output: rough usable flow + offer page draft. Leave a clear Friday build list.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
Can we turn the brief into something we can demonstrate?
How to run it
10 min task agreement; 60 min side-by-side making; 20 min shared demo. Put unrelated ideas in a parking list.
Prompts
What will we show each other in 60 minutes? Who owns the actual deliverable, offer and customer experience?
Leave with
A rough usable customer flow, offer draft and Friday build list.
Ready to move on when
Show an actual artefact; both contributed to a visible part.
If we get stuck
If setup consumes the sprint, switch to a manual sample and simple page. Save technical extras for later.
Evening walk as needed; finish small jobs. Hard stop on work.
Recap & post mortem, Dinner & off duty
A relaxed 10-minute recap: what worked, what we enjoyed, what to adjust tomorrow. Then dinner and off duty.
Dog walk
Fresh air. No product meeting required.
Breakfast & get ready
A slow start; breakfast stays protected.
Travel & settle in
Travel or settle in. Handle larger chores at lunch or after 18:00.
05 / Build the core · SHARED SPRINT
15 min check-in and replies; 80 min create the smallest useful customer flow; 25 min joint demo. Output: a usable core, including a manual service if simpler.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
Does our first version solve the one problem we chose?
How to run it
15 min check-in; 80 min focused making; 25 min joint demo. Ask for help early, without taking over ownership.
Prompts
Run one realistic example from start to finish. What would the customer get? What can we reuse from existing tools?
Leave with
A usable core with one worked customer example.
Ready to move on when
The example delivers the promised result, even if some steps are manual.
If we get stuck
Remove automation and deliver the value directly. Do not spend the whole session perfecting architecture.
Eat, do a small chore, check replies. No compulsory working lunch.
07 / Test with people · TOGETHER
15 min invite three relevant testers; 30 min observe a walkthrough or test together while awaiting replies; 15 min log confusion and blockers. Output: feedback requests + priority fixes. Real users are the target, not guaranteed attendance.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
Where does the experience confuse a real person?
How to run it
15 min invite three testers; 30 min walkthroughs or a founder test while waiting; 15 min capture observations.
Prompts
Ask a tester to try a realistic task. Observe before explaining. What did they expect? What would they change?
Leave with
Evidence log and three highest-impact blockers.
Ready to move on when
Separate observed behaviour from opinions and our own guesses.
If we get stuck
If testers are unavailable, record the founder walkthrough as internal testing; schedule external feedback for Saturday.
10 min select blockers; 50 min fix and set up payment; 20 min test the transaction and fulfilment in test mode; 10 min prepare launch copy. Output: launch-ready draft + Saturday checklist.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
What is genuinely blocking a usable first release?
How to run it
10 min prioritise; 50 min fixes and payment setup; 20 min transaction/fulfilment test; 10 min launch copy.
Prompts
Which issue stops value or payment? What is merely cosmetic? What must be tested before sharing?
Leave with
Launch-ready draft, test record and Saturday checklist.
Ready to move on when
No known blocker in the main flow; the offer matches actual delivery.
If we get stuck
If checkout is not ready, share a demo and collect interest with honest pricing. Do not take money for a broken journey.
Evening walk as needed; finish small jobs. Hard stop on work.
Recap & post mortem, Dinner & off duty
A relaxed 10-minute recap: what worked, what we enjoyed, what to adjust tomorrow. Then dinner and off duty.
Dog walk
Fresh air. No product meeting required.
Breakfast & get ready
A slow start; breakfast stays protected.
Travel & settle in
Travel or settle in. Handle larger chores at lunch or after 18:00.
09 / Ready to sell · TOGETHER
20 min review new feedback; 65 min final purchase/delivery test and fixes; 35 min publish the offer. Output: live link, price, payment route and delivery/refund terms.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
Are we comfortable putting our names on this first version?
How to run it
20 min review feedback; 65 min end-to-end test and fixes; 35 min publish and check the live link.
Prompts
Run the customer journey on mobile. Verify price, payment, receipt, delivery, support and refund wording where applicable.
Leave with
Live product or shareable demo, clear offer and tested journey.
Ready to move on when
Both approve the promise; someone can get useful value.
If we get stuck
Release a limited pilot with clear boundaries or a demo. A payment deadline never overrides product readiness.
15 min choose a few relevant people; 45 min personally invite them to buy or try; 15 min log results. Output: a small set of thoughtful invitations sent. Take turns leading conversations.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
Who would benefit, and how will we show them personally?
How to run it
15 min choose a few relevant people; 45 min thoughtful invitations; 15 min record replies. Take turns leading.
Prompts
Explain the benefit, scope and price simply. Ask for a specific next step: try, reply, book or buy. Who is a good fit?
Leave with
A few personal invitations and an evidence log.
Ready to move on when
People understand what is offered; no revenue quota.
If we get stuck
If outreach feels vague, pick one community and a more concrete use case. Do not replace relevance with mass messaging.
Eat, do a small chore, check replies. No compulsory working lunch.
11 / Listen & improve · TOGETHER
20 min gather replies; 30 min fix one repeated blocker or deliver the first order; 10 min update the evidence log. Output: one evidence-led improvement. Avoid a new feature sprint.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
What should change based on the feedback we actually received?
How to run it
20 min collect feedback; 30 min one improvement or first fulfilment; 10 min update the log.
Prompts
What repeats? Is it a problem with clarity, value, price or delivery? What is the smallest improvement?
Leave with
One evidence-led improvement and recorded before/after.
Ready to move on when
The change addresses a real observation, not a new pet feature.
If we get stuck
If replies are sparse, improve one observed usability issue and record the unanswered question for next week.
20 min demo end to end; 20 min review evidence, sales and costs; 20 min continue / pivot / park; 20 min Singapore review and one next experiment each; 10 min closing screenshot. Output: launch record + joint next steps.
Session framework · stay on track ↗
Partners first
Alternate the facilitator. Both speak before decisions; each owns meaningful work. The presenter rotates at the demo.
The question
What did we create, and what do we want to carry to Singapore?
How to run it
20 min demo; 20 min evidence and costs; 20 min continue/pivot/park; 20 min Singapore lessons and owners; 10 min closing record.
Prompts
Demo it. What excited each of us? What worked about our collaboration? What evidence supports the next step?
Leave with
Working demo, shared decision, one next experiment each and a Singapore carry-forward brief.
Ready to move on when
Both can name their contribution, what they enjoyed and the next step.
If we get stuck
If we disagree on continuing, park it with a defined test and review date. Celebrate the work we did, not a sales number.
Evening walk as needed; finish small jobs. Hard stop on work.
Recap, celebration dinner & off duty
Briefly reflect on what we made and want to take to Singapore. Dress up a little, toast what you made and enjoy a proper closing dinner together. Choose and book your restaurant together before Saturday; no booking is included.
The crew agreement
Partners. Equal voices. Shared direction.
Equal partners from the start. Both shape the idea, priorities and product. Take turns facilitating; both have equal voice in decisions.
Both must say yes to the idea. Reflect separately before comparing; either person can decline an idea.
Choose meaningful work by interest and strengths. Each owns a concrete outcome, has room to create it and reviews the other’s work. Technical skill does not confer the final say.
When stuck: name the question, allow two minutes each, then pick the smallest reversible test. Park debates after ten minutes.
Anyone can call a ten-minute reset. Say when you will return; finish one decision at a time.
Protect training and the 18:00 finish. Cut scope when behind. Keep the 19:00 recap brief, then enjoy dinner and switch off.
Wednesday: a 20-minute pack check
Choose the venue; bring chargers, headphones, notebook and a backup connection. Confirm infrastructure access without sharing credentials. List chores and arrange dog care for the work blocks.
Set the experiment cap together
US$300 to get shit done. A budget to move the product forward, not a target to spend. Dinner and ordinary meals are separate.
Good uses: a domain we will actually use; API credits to power or test a feature; a licensed asset that improves the product; a small outsourced task that saves build time; or a tightly scoped test with relevant customers.
Make the return explicit: what will this unlock, how will we know it helped, and can we do it with what we already have? Spend only when the expected benefit is worth the cost. Unspent money stays unspent.
Use AI as a neutral facilitator
“Ask each founder the same questions. Summarise both views fairly. Separate facts, assumptions and preferences. Offer a small test when we disagree. Do not choose for us. Keep us within this session’s time.”
Your SideEye Labs Basecamp programme. This is a professionally structured self-run programme; no external organiser or reservation is implied.
Your working notebook
Less blank-page panic. More useful scribbles.
Two partners. Equal voice. Write separately for the first exercise, then compare. For a shared record, use the printed workbook or nominate one device. Exported notes are a backup; keep the live link and evidence there too.
Write separately, then share. Three frustrations you know well; two communities you can reach; two things you would enjoy creating.
FIELD NOTES
02 / Choose the smallest bet
Discuss each idea: do we both care about it, who needs it, could they pay, can we reach them and can we make a useful version in three days? Choose by mutual enthusiasm; use ratings only if helpful.
FIELD NOTES
03 / Customer evidence
Ask about their last experience, existing workaround and what it costs. Then show a specific offer and price. Record behaviour and exact feedback; distinguish interest from payment.
FIELD NOTES
04 / The one-page brief
Complete together before building. Promise only what you can deliver. A small manual service or digital product is welcome.
FIELD NOTES
05 / Launch checklist
Before taking payment: specify what is delivered, by when, support contact and refund terms. Use test mode first; test live payment only with an agreed real purchase. Never paste credentials into prompts.
FIELD NOTES
Budget / Make the money work
US$300 to get shit done. Use it for a useful domain, API credits, licensed assets, a small outsourced task or a targeted customer test. Spend for an expected return, not because the budget is there. Dinner and meals are separate.
FIELD NOTES
06 / Debrief & Singapore
Review the experiment, not each other’s worth. Discuss what you enjoyed, what you made and whether you want to continue. Sales are useful feedback, never a condition for celebration.
NEXT STOP / PUTTING OUR PRACTICE TO WORK
From the beach to Singapore.
25–27 November 2026 · Three days · Dan + Stef
This week is our chance to try building together in a fun, manageable way. In November, we take what works to the inaugural SideEye Labs Founders Retreat in Singapore.
Bring what we create here, the lessons we learn and a working rhythm we enjoy. In Singapore, develop it further or choose a fresh idea together. The birthday concert and time together stay part of the adventure.
Marina Bay Sands
A little big-city inspiration for our next chapter.
The Hive Carpenter
A characterful coworking option with day-pass memberships. Explore the space ↗
JustCo Marina Square
A modern Marina Square workspace with flexible day-pass options. Explore the space ↗
A shortlist to explore together, not booked venues. Confirm two day passes and a suitable work area for 25–27 November. Photos: dronepicr / Wikimedia Commons (CC BY 2.0, resized); venue photos from The Hive and JustCo.
GOOD IDEAS.
