Foundation
Your Cohort
You are the founding class. That means something specific: everything the second cohort, fifth cohort, and twentieth cohort inherits — the culture, the norms, the warmth of the alumni base — gets set by the 15 people in the first one.
Most cohorts spend the program building relationships and the rest of their lives letting them drift. The groups that don't have the same thing in common: someone, early on, made explicit decisions about what kind of group they would be.
Not networking. Infrastructure.
Standard networking is transactional. The cohort is not that. You didn't select each other from a conference list. You were chosen for the same program, share the same schedule and pressures, and have months of shared context before any professional exchange happens.
Granovetter showed that most opportunities travel through weak ties. Putnam showed that trust built through shared experience creates the strongest professional bridges. Your cohort members are not weak ties. They are strong ties that will function as bridge connections into completely different domains, geographies, and industries — for thirty years.
What this cohort actually covers
Between 15 people, this cohort spans:
- ›Embedded systems and AI quantization at semiconductor scale
- ›Autonomous navigation, sensor fusion, and robotics
- ›Drone operations and industrial inspection (confined space, BVLOS, NDT)
- ›Cybersecurity product management (XDR, threat intelligence, identity)
- ›AI product management and machine learning systems
- ›Corporate strategy, PMO, and revenue operations
- ›Defense R&D and counter-UAV systems
- ›Capital markets, M&A, and institutional finance (IPOs, SPACs, cross-sector deal execution)
- ›Fintech product management
- ›Blue economy, marine biology, and sustainable technology ventures
- ›Blockchain, Web3, and digital product management
- ›B2B SaaS, startup operations, and early-stage venture
- ›Space and satellite software, sovereign customer partnerships
That is a legitimate expert panel on a wide range of domains. Use it before you go external.
You are founding an institution
First cohort onlyEvery program that becomes known eventually looks back at its founding class as the cohort that established what the program produces. You are building that answer in real time. In five years, when you introduce yourself as a first-cohort member, the question is: “what did that class go on to do?” You are writing that answer now.
The programs with the best alumni cultures — Rhodes, YC, West Point, INSEAD, elite military units — don't have them by accident. They have them because someone, early on, made the implicit explicit. You have the rarest possible opportunity: you can decide, while you're still in the room together, what kind of people you want to be to each other in 20 years.
Three things to decide at the next peak week
Name yourselves
Not "the first cohort." Something you chose. Every Rhodes cohort, every USAFA class, every YC batch has an identity. The name becomes shorthand for what you stand for — and makes the credential permanent in a way "first cohort" doesn't.
Write a one-page founding compact
What do we believe? What do we commit to each other? What kind of alumni association will this be? Signed. Kept. Read at every reunion. This makes the implicit explicit and holds everyone to something they agreed to.
Set Founding Day
Pick the date — first day of first peak week. Mark it every year, forever. Even if it's just a WhatsApp thread that reactivates. Twenty years from now, everyone in the first cohort knows what date it is on that day.
Peak week traditions
In-person time is your scarcest resource. It needs rituals that make it different from the online time.
The first dinner
Every peak week, the cohort eats together the first night. No phones during the meal. This only works if it's sacred — once it becomes optional, it stops being the thing.
The last morning
30 minutes before everyone disperses. Two questions for the table: what did I realize this week, and what am I going to do about it before the next peak week? The pressure of departure creates honesty.
The adversity archive
At some point each peak week, someone asks: what's the hardest thing you're carrying right now, professionally or otherwise? You're not solving each other's problems. You're bearing witness. The relationships it builds are qualitatively different.
The annual bet
At the first peak week of each year, everyone makes one professional prediction — about the ecosystem, their path, the market — and commits to it. Read back a year later. The point isn't to be right. It's to practice having a view and being wrong in front of people you trust.
Rotate deliberately
Don't eat every meal with the same people. The conversation over dinner is where the context that makes all subsequent professional exchange feel natural gets built. Move around.
The shared adversity log
When something hard happens during the program — a cancelled flight, a failed pitch, a rough week — name it and remember it. 'Remember peak week 3 when the whole group was stuck at Ben Gurion' will still be a story in 2040.
The three norms
The YC network became the most powerful in startup land not because YC founders are nicer. Because they agreed, explicitly, on how they treat each other. These three norms, internalized and practiced, are what separates a network from a community.
The warm introduction compact
When a cohort member sends a warm intro request, you respond within 72 hours — always. Not a favor. A norm. An explicit ask is a sign of trust. Meet it as one.
Ask yourself: could I make this introduction? If yes, make it or say explicitly why you can't. Don't let it drift.
The honest read
Any cohort member can ask any other for a real opinion — on their pitch, their decision, their career move, their LinkedIn post. And the expectation is that you give them the real one. Not supportive. Not diplomatic. The one you'd give a brother or sister.
When someone asks "what do you think?" — they want your actual view. Dugri. Give it.
Close the loop, always
When someone helps you — intro, advice, feedback — you report back what happened. 'The intro you made led to a call, which became a pilot partnership.' Most people never do this. Reporting back is what turns a one-time helper into a recurring resource.
Before you need anything new, send one update on something old. The loop-close builds the social capital you'll need later.
The long arc
The groups with the best long-term cohesion have a standing reason to be in contact that doesn't require someone to manufacture an occasion. Without structure, the natural entropy of adult life — kids, careers, geography — wins every time.
Year 1 post-graduation
Give to the cohort. Before you need anything, make one warm introduction between a cohort member and someone in your network. It costs almost nothing and sets the reciprocal norm.
Year 3
Mentor one person in the next cohort. You now know what the first six months feel like. Pass that on.
Year 5 — the reunion with an agenda
Not a dinner. An actual agenda: here's what we said we'd do. Here's what happened. Here's what we got wrong. Here's what we're building now. Here's what we need from each other in the next five years.
Annual — State of the Cohort
One person (rotating) writes a short annual update: where is everyone, what did we do this year, what changed, what stayed the same. Sent to everyone on Founding Day. This creates a living record of the group's arc.
Year 10
Lead something — a working group, a scholarship, a tradition. Help define what the program becomes.
Year 20
Graduate with your kids? Be the guest speaker? Whatever it is — you're the ones who built this when there was nothing to build on. That's permanent.
What to borrow from other groups
YC
"Pay it forward" as the cultural operating system — not a value, a practice. You help other YC founders because that's what you do. Full stop.
Rhodes Scholars
The "find me anywhere" compact. A Rhodes Scholar cold email to another Rhodes Scholar has a near-100% response rate because the shared identity creates immediate trust. Build that. It requires the identity to be strong enough that the credential means something.
West Point / Long Gray Line
Obligation that runs both ways across time. Senior members look out for junior ones. Junior ones contribute back. The network has real economic solidarity because everyone understands they're part of something larger.
INSEAD
Intensity as bonding agent. Your hybrid program has fewer hours than INSEAD's one-year format, which means peak weeks need to do more work. Be more deliberate than INSEAD students — you have less time.
Israeli unit culture (8200, Shayetet)
Reputation travels through the network before you arrive anywhere. Know each other in the way unit members do — by what people actually do, not what their LinkedIn says. Extend that norm to the full cohort.
Peace Corps
The shared outsider experience as permanent bond. No one else will ever have exactly your experience — first cohort, hybrid, Israeli deep tech ecosystem, this specific 22-month window. Name it as something that makes you permanently intelligible to each other.
Map the cohort before you need anything from it
For each cohort member, be able to answer:
- What is their primary technical or commercial domain?
- What path are they on — investor, founder, operator, enterprise?
- What company, fund, or ecosystem are they most connected to?
- What are they genuinely trying to figure out right now?
You don't need a spreadsheet. You need enough intentional conversation in the first peak weeks to know these things. Most cohort members won't do this deliberately. The ones who do will have a fundamentally different experience of the program — and a fundamentally more useful network by graduation.