Most accelerators, incubators, and university programs will tell you the same thing: the advisor layer is the hardest part of the program to run well. The talent is there. The interest from founders is there. What breaks down is everything in between. Matches live in a Google Doc. Sessions get logged in an inbox. Context lives in someone's head. The advisor who met with a founder in January has no record of what was discussed by April. The program director spends Friday afternoons chasing confirmations.
That is the real problem with mentor program management in early-stage ecosystems. The structure that should compound relationship value over time ends up eroding it instead.
The Advisors module inside Startup Science was built for this exact problem, and this week we shipped its full rebuild. The scope is large enough that it changes how ESO admins, advisors, and founders interact inside the platform. This post walks through what changed, who it matters to, and what we are solving for underneath the surface.
Why mentor program management fails inside most ESOs
Three patterns show up across nearly every program that struggles with its advisor layer.
Fragmentation. Matches exist in one place. Sessions exist somewhere else. Notes, if they exist at all, live in an advisor's private drafts. Founders upload context into a form that no one revisits. The program operates as if each session is its own isolated transaction, rather than a single thread inside a longer relationship.
Context loss. An advisor meeting a founder for the third time should know what was discussed the first two. Most programs have no way to preserve that context without asking the advisor to maintain their own system. This pushes the relationship toward small talk and away from compounding value.
Invisible health. The program director has no signal on which matches are actually working. A match that has not had a session in thirty days looks the same as a match that had one yesterday. By the time the program notices a problem, the founder has already disengaged.
These patterns are not advisor problems. They are system problems. A program with thirty advisors and eighty founders cannot be run from memory and email threads. It needs infrastructure.
What the Advisors rebuild actually changes
The rebuild transforms the module from a session-tracking tool into a full relationship management system. Here is what that means in practice.
Per-match workspaces
Every advisor-founder pairing now has its own workspace with five tabs: Overview, Sessions, Activities, Context, and Notes.
The Overview tab shows status, open activities, and a timeline of recent work on the relationship. Sessions lives as a filterable list with scheduling, logging, confirmation, and dispute flow. Activities are task-like items scoped to the specific match, with priorities and due dates. Context is founder-editable and holds the business information advisors need before each session, plus any shared files. Notes is advisor-created and has three visibility levels: Insight, Action, or Private. Private notes remain invisible to the founder, which lets advisors keep candid observations without friction.
Workspaces solve the fragmentation problem. Every relationship has one container. When an advisor opens their next session, the entire history is one click away.
Advisor pool management
Administrators now manage the full pool from a dedicated tab. Each advisor shows a status indicator (Active, Invited, or Inactive), profile completion percentage, expertise tags, and match count.
Visibility controls are the core addition. Admins can set an advisor as visible to All Founders, visible to a specific Cohort only, or Hidden entirely. This means a new advisor can be onboarded privately before becoming discoverable, or a specialist can be reserved for one cohort without blocking them from the others.
Bulk import via CSV is in. Invitation by email is in. The pool page is the single surface for sizing and maintaining the advisor roster.
Find an Advisor
Founders browse a filterable directory by name, expertise, or stage focus. Each advisor card shows expertise, bio, stage focus, and a capacity indicator (green or yellow) based on whether they are accepting new matches.
Visibility rules from the pool page flow through here automatically. Founders only see advisors appropriate for their cohort.
One-click match requests carry real-time status (available, pending, or connected). If the program requires admin approval on requests, a separate approval queue handles it.
Preferences for both sides
Founders set up to five challenge areas to help with matching. Advisors build a detailed profile with tagline, bio, core expertise (up to five), stage focus, industry expertise, capacity limits, and a switch for whether they are accepting new matches.
These preferences drive better first matches and give admins the data to run the program without guessing.
Session flagging
Session flagging is a lighter alternative to formal disputes. Either party can flag a session with a reason, which notifies the other party and admins without changing the session's status.
This is the feature that mattered most when we interviewed program directors. Dispute flows felt too heavy for minor issues (wrong date logged, missing topics, disagreement about what was covered), so problems either escalated or got ignored. Flags give both sides a way to raise a concern without triggering a formal process.
CSV exports and configurable health monitoring
Admins can export matches, founders, and sessions as CSV files for external reporting. Exports stream for memory efficiency on large datasets.
Match health now uses a two-state system (Active or At Risk) with a configurable threshold. The default is fifteen days without activity. Admins can tune this between seven and ninety days in Advisory Settings based on how frequently their program expects sessions to happen.
Expanded settings
Admins now control match caps (between one and fifty advisors per founder, and between one and fifty founders per advisor), connection rules (who can initiate a match request), the at-risk threshold, and notification toggles across match requests, disputes, and at-risk alerts.
Caps apply only to concurrent active matches. Paused or ended matches do not count toward the limit.
What this means for each role
For ESO administrators, the rebuild is the layer that turns a list of advisors into a running program. Visibility controls, approval queues, health thresholds, and CSV exports are the operational hooks you need to actually manage the program week to week instead of quarter to quarter.
For advisors, private notes and per-match workspaces change the working surface. You stop maintaining a personal system outside the platform. Your history with each founder lives where you need it, and what you share versus what you keep private is a deliberate choice.
For founders, the Find an Advisor directory plus editable business context means you drive more of your own advisory experience. You see which advisors are accepting matches, you request the ones that fit, and you keep your own context up to date so every session starts closer to the work.
How this fits the rest of the platform
The Advisors module is one of five business units inside Startup Science, alongside ESO program management, the Providers marketplace, the Investor layer, and Direct-to-Founder. The point of running them on the same infrastructure is that a founder inside a program gets one environment to work in, and a program director gets one dashboard to run from.
Mentor program management does not live in isolation. It is part of how a founder moves through the Startup Lifecycle with the right support at the right phase. Advisors tend to be most useful during Vision and Product, then again during Growth. An ecosystem that unifies the surrounding tools (programs, providers, capital) around that journey makes the advisor layer work harder, because it is anchored to real context instead of floating alongside it.
We wrote more about why program structure matters more than program size in this piece on whether your ESO is built for what comes next.
How to get started
If you run an ESO and want to see the Advisors module in the context of your program, book a walkthrough. We will show you the pool management view, the workspace surface, and the exports you would run on day one.
If you are already a customer, the new Advisors surface is live in your portal. Your admin can tune thresholds and caps inside Advisory Settings.
More is in flight. The roadmap includes deeper Impact reporting, better matching heuristics, and tighter integration with the Sessions calendar. We will post updates as they ship.
Frequently Asked Questions
What is the difference between the Advisors module and generic mentor management software?
Generic mentor management software handles matches and session logs. The Advisors module handles matches, session logs, per-match workspaces, advisor pool visibility rules, founder self-discovery, session flagging, CSV exports, and configurable health monitoring, all inside the same portal that runs the rest of your ESO program. Mentor program management without the broader program context loses value fast.
Can founders see an advisor's private notes?
No. Private notes are scoped to the author only. Founders can see notes marked Insight or Action. Private notes do not appear in the activity feed at all.
How does advisor pool visibility work?
Each advisor has a visibility setting: All Founders, Cohort Only, or Hidden. Cohort Only lets admins assign an advisor to specific cohorts so they only appear to founders in those cohorts. Hidden keeps the advisor out of the Find an Advisor directory entirely. This is useful for onboarding new advisors privately or reserving specialists for specific programs.
What is the default at-risk threshold and can I change it?
The default is fifteen days without activity. Admins can set this to any value between seven and ninety days inside Advisory Settings.
Can founders and advisors end their own matches, or does an admin have to do it?
Both founders and advisors can pause or end their own match. Previously this was admin-only. Admins retain the same controls across all matches in the portal.
Do paused matches count toward match caps?
No. Match caps apply only to concurrent active matches. Paused or ended matches do not count toward the limit.
