[et_pb_section fb_built=”1″ theme_builder_area=”post_content” _builder_version=”4.27.4″ _module_preset=”default” custom_padding=”17px|||||”][et_pb_row _builder_version=”4.27.4″ _module_preset=”default” theme_builder_area=”post_content”][et_pb_column type=”4_4″ _builder_version=”4.27.4″ _module_preset=”default” theme_builder_area=”post_content”][et_pb_text _builder_version=”4.27.4″ _module_preset=”default” text_font_size=”17px” text_line_height=”1.7em” header_2_font=”|800|||||||” header_2_font_size=”28px” theme_builder_area=”post_content”]<\/p>\n
Most mentoring programs don’t have a mentor problem. They have a request problem. A founder writes “we need help with go-to-market.” The program manager scans a long mentor list, picks three names from memory and sends an intro email. Two weeks later, nobody is sure the conversation happened.<\/p>\n
That works with ten ventures. It quietly breaks at forty. What fixes it is rarely a bigger mentor network. It’s a better request, and a simple flow around it that gets the right expert into the right conversation and leaves a trail you can actually report on.<\/p>\n
A vague request pushes all the thinking onto the wrong person. The program manager has to guess what the founder really means. The mentor has to spend the first twenty minutes of the call figuring out the question. By the time everyone understands the problem, the hour is mostly gone.<\/p>\n
Vague requests also make matching a memory game. If the ask is “go-to-market,” almost any mentor with a commercial background could plausibly fit, so the manager defaults to the people they spoke to last week. The same five generous mentors get every intro, and the forty others on the list never hear from you.<\/p>\n
Then there is the follow-up gap. The intro email goes out, the founder and mentor take it to their calendars, and the program loses sight of it. Did they meet? Was it useful? Should there be a second session? At ten ventures you can ask around. At forty, you find out at demo day, when a team’s pitch makes it painfully clear that nobody ever helped them with pricing.<\/p>\n
\nA sharp question gets a useful hour. A vague one gets a pleasant chat.<\/p>\n<\/blockquote>\n
What a good mentoring request looks like<\/h2>\n
The fix starts with the venture. Before anyone gets matched, the founder states what they need in a format that forces a little clarity. It doesn’t need to be long. It needs six things:<\/p>\n
\n
- The question.<\/strong> One specific question, written as a question. Not a topic.<\/li>\n
- Context.<\/strong> Two or three sentences on the business and why this question matters now.<\/li>\n
- Stage.<\/strong> Idea, pre-revenue, first customers, scaling. The same question has very different answers at each.<\/li>\n
- What’s been tried.<\/strong> What the team already did and what happened. This saves the mentor from suggesting the obvious.<\/li>\n
- Desired outcome.<\/strong> What the founder wants to walk away with: a decision, a shortlist, a reviewed draft, an introduction.<\/li>\n
- Timeframe.<\/strong> When the answer is needed, and why. “Before our pilot proposal on the 14th” beats “soon.”<\/li>\n<\/ol>\n
Here is the difference in practice, with a hypothetical venture.<\/p>\n
Bad request:<\/strong> “We need help with go-to-market.”<\/p>\n
Good request:<\/strong> “Should we sell to facility managers or to procurement first? We make a sensor that cuts energy waste in office buildings. We’re pre-revenue with two free pilots running. We cold-emailed 60 facility managers and got 4 replies, all positive but none with budget. We want to leave the session with a clear choice of first buyer and a rough outline for the next 30 outreach emails. We need this before we draft our paid pilot proposal in three weeks.”<\/p>\n
The second version takes maybe five more minutes to write. It also tells you exactly which kind of expert to look for: someone who has sold B2B hardware into commercial real estate, not just “a sales person.” And it gives that expert a reason to say yes.<\/p>\n
Match by expertise, not by memory<\/h2>\n
Once requests are specific, matching stops being a favor you do from memory and becomes a process. A workable flow looks like this:<\/p>\n
\n
- The venture submits a structured request<\/strong> with the six fields above, so every request arrives in the same shape.<\/li>\n
- The request is matched to experts by expertise,<\/strong> using tags or profiles your mentors maintain themselves, rather than by who the manager happens to remember.<\/li>\n
- The expert accepts or declines,<\/strong> then schedules the session directly. No three-way email chains about Tuesday versus Thursday.<\/li>\n
- After the session, the expert leaves short structured feedback:<\/strong> was the question clear, what was covered, is a follow-up needed.<\/li>\n
- The program sees every request and session in one place,<\/strong> so gaps show up before the demo day does.<\/li>\n<\/ul>\n
That last point is where the program manager wins back their week. Instead of chasing people for updates, you can see which ventures have open requests with no match, which mentors are stretched thin, and which topics keep coming up across the cohort. If six teams ask about pricing in the same month, that’s not six mentoring sessions. That’s a workshop you should probably run.<\/p>\n
How to keep mentors motivated<\/h2>\n
Mentors are usually volunteers, or close to it. They show up because they like being useful. The fastest way to lose them is to make them feel used instead. Three habits make a real difference.<\/p>\n
Send well-scoped asks.<\/strong> An experienced operator will happily give an hour to a sharp question in their area. They will quietly stop answering emails after the third “can you chat with this team about strategy?” A good request respects their expertise by showing why it is them, specifically, being asked.<\/p>\n
Respect their time.<\/strong> Let mentors set their own availability and capacity, and let them decline without awkwardness. Don’t send intros that require them to do the scheduling legwork. Make sure the founder reads their profile and shows up prepared. A mentor who has two well-run sessions a month will stay for years. One who has six chaotic ones will burn out by spring.<\/p>\n
Close the loop.<\/strong> This is the habit almost every program skips. When a founder acts on advice, tell the mentor. “The team went with procurement first and signed their first paid pilot” is the kind of message that turns a one-off volunteer into a long-term part of your ecosystem. Structured feedback in both directions makes this easy, because you already have a record of who helped with what.<\/p>\n
A quick checklist for this week<\/h2>\n
You don’t need new software to start. You can test the idea with your current cohort:<\/p>\n
\n
- Share the six-field request template with every venture and ask them to use it for the next request.<\/li>\n
- Bounce back any request that is a topic rather than a question. Kindly, with an example.<\/li>\n
- Ask each mentor for five specific areas where they would genuinely like to be asked for help.<\/li>\n
- Keep one shared list of every request, its match, its status and a one-line outcome.<\/li>\n
- After each session, send the mentor a two-question form: was the question clear, and is a follow-up needed.<\/li>\n
- Once a month, read the list for gaps: unmatched requests, overloaded mentors, recurring topics.<\/li>\n<\/ol>\n
If that list starts getting unwieldy around the twentieth venture, that’s the signal the process is working and your spreadsheet isn’t.<\/p>\n
How we built it into Babele<\/h2>\n
This is the thinking behind mentoring and expert matching in Babele<\/a>: structured requests in, matched experts out, a trail you can report on. Ventures submit requests in a consistent format, experts are matched by what they know, they accept and schedule on their own terms, and short feedback is captured after every session.<\/p>\n
Because every session lives in the same place as the rest of your program, it also feeds straight into your program tracking and reporting<\/a>. When a funder asks how many hours of expert support your cohort received, and on what, you can answer with data instead of a guess.<\/p>\n
The takeaway is simple. Before you recruit another twenty mentors, fix the request. Sharper questions get you better sessions, happier mentors and a program you can actually see.<\/p>\n