Mastermind · January 24, 2026
Daydreamers Academy and hackathons are the same thing
The reframe that landed on this week's call was simple enough that I can't believe I hadn't seen it: Daydreamers Academy and the hackathons I run are the same product at different cadences.
I'd been carrying them in separate boxes. The Academy was education, the hackathons were events, and MentorMates was the platform underneath, and I'd been treating the three as three workstreams with three roadmaps. When I described it that way on the call, Xisen paused on it. His read: those aren't three things. They're one thing running at different time scales.
The Academy is a multi-week structured learning cohort. A hackathon is a 48-hour structured learning cohort. One has more theory and more mentorship, the other has more velocity and more pressure. Both funnel the same user, a builder learning to ship, through the same platform surface. The only real difference is dose and duration.
Once you see it that way, the roadmap stops fracturing. The questions I'd been asking in triplicate, which educators are we serving, which events are we running, which features do we build first, collapse down to one question: what does the builder journey look like from hackathon to cohort to cohort to flagship? The platform has to serve the same person across those cadences, or none of the pieces compound.
This matters for the fundraising framing too, and that's a place I've been tripping over myself. I kept asking whether we're an education company, an events company, or a platform company. The category question only matters in a deck. In product work, the category is wherever the user's attention is going, and in our case it's going to the whole arc. A builder who does a Daydreamers weekend, then a Hong Kong hackathon, then a longer cohort, is using the same infrastructure the whole time. The category is that infrastructure.
The other thing this call clarified was how to handle investor conversations I've been dragging forward. I'd been keeping a few threads warm with mentors and investors without pushing each to a concrete next step. The frame I landed on was: every conversation either has a concrete next step out of it, or I close the loop. Open-ended warmth is expensive when you have ten of them. The cost is my attention, and I've been subsidizing it without noticing.
Xisen was dealing with a version of the same problem from the opposite side. He'd come out of a hackathon week feeling stretched across four research threads, and the call pushed him to commit to one and close the rest down to the back burner. The shape of the fix is identical. Neither of us can afford optionality that doesn't compound, and both of us keep accidentally paying for it when we don't explicitly cancel.
What I want to stop doing is treating each event as one-off. A hackathon that doesn't plug into the platform is a weekend gig. A hackathon that does plug in is distribution. Everything I'm running between now and the Hong Kong flagship in July has to feed that funnel or get pruned.
One specific example of the reframe in action. I'd been treating workshop revenue and hackathon revenue as side income. If Academy and hackathons are the same product, workshop revenue is actually early cohort ARPU and hackathon revenue is distribution CAC discount. Same dollars, very different meaning. The reporting changes, the roadmap priorities change, and the conversations I have with mentors and investors change too.
The check I'm making on myself this week: every investor conversation ends with a concrete next step or closes. Every hackathon slot on the calendar gets justified by what it feeds into MentorMates. And the Academy writeup gets finished, because I can't sell the arc to users or partners if I haven't written it down for myself first.