In 2019, I spent two weeks trying to figure out international shipping logistics for a product I hadn’t even built yet. I read forums. I watched YouTube tutorials. I compared shipping providers across three countries. I built spreadsheets with customs duty calculations that were probably wrong.
Then, at a dinner party, I mentioned the project to an acquaintance who’d been running a cross-border e-commerce business for eight years. She answered my two biggest questions in about four minutes. Four minutes. I’d spent two weeks avoiding a four-minute conversation because asking felt like admitting I didn’t know what I was doing.
Of course I didn’t know what I was doing. I’d never shipped products internationally before. Not knowing was the correct state. But the founder identity — the “I figure things out on my own” identity — made asking for help feel like a character flaw instead of a smart strategy.
This is the invisible skill: knowing when and how to ask for help. It’s invisible because nobody talks about it. Nobody posts on LinkedIn about the mentor who solved their problem in four minutes. Nobody writes case studies about the email they sent asking for advice. The skill is invisible, and it might be the single most valuable capability a founder can develop.
Why Founders Are Uniquely Bad at This
Most people find it somewhat difficult to ask for help. Founders find it almost impossible. There are structural reasons for this.
The self-reliance identity. You started a business because you believe you can build something on your own. Self-reliance isn’t just a trait — it’s your founding story. Asking for help threatens that story. If you need help, maybe you’re not the self-reliant founder you thought you were.
The competence expectation. Once you’re “the founder,” people expect you to have answers. Clients, team members, partners, investors — they all look to you for direction. Admitting you don’t have answers feels like it could undermine the trust that holds everything together.
The time paradox. Asking for help requires finding the right person, crafting the right ask, scheduling the conversation, and then integrating the advice. When you’re drowning in work, this process feels slower than just figuring it out yourself. It almost never is — but it feels that way.
The reciprocity anxiety. Many founders avoid asking for help because they fear they can’t reciprocate. “If she helps me with shipping, what do I owe her?” This anxiety is usually unfounded — most people who help founders enjoy it and don’t expect immediate reciprocation — but it’s real enough to prevent the ask.
I experienced all four of these barriers simultaneously for years. The result was predictable: I reinvented countless wheels, made mistakes others could have warned me about, and spent time on problems that had known solutions. The total cost of not asking for help, across my career, is probably measured in years of wasted effort.
The technician trap isn’t just about doing too much operational work. It’s about insisting on figuring everything out yourself when someone else already has the answer.
The Ask Spectrum: From Terrible to Excellent
Not all asks are created equal. There’s a spectrum, and understanding it dramatically improves your success rate.
Terrible ask: “Can I pick your brain?” This is the worst ask in the English language. It’s vague (about what?), one-sided (what do I get?), and implies an indefinite time commitment (how long?). I get this ask weekly and decline it almost every time, not because I’m unhelpful but because I don’t know what they want or whether I can actually help.
Bad ask: “Can we hop on a call sometime?” Slightly better but still vague. No specific topic, no specific timeframe, no indication of what they need or why they’re asking me specifically.
Decent ask: “I’m trying to figure out how to price my consulting services. You’ve been doing this for years — would you be willing to share how you thought about pricing when you started? I have two specific questions that would take about 15 minutes.” Better. There’s a specific topic, a specific time commitment, and a clear reason for asking this particular person.
Excellent ask: “I’m launching a consulting practice focused on innovation for mid-size manufacturers. I’ve been reading your posts about pricing and I have a specific question: when you moved from hourly to project-based pricing, how did you handle the transition with existing clients? I’ve drafted two approaches and I’d love your feedback on which one makes more sense. Would a 15-minute call this week work?” This is the gold standard. It shows preparation (they’ve done their homework). It’s specific (one question). It’s bounded (15 minutes). It offers something to react to (the two approaches). And it explains why they’re asking this particular person (they’ve read my work).
The difference between a terrible ask and an excellent ask is about three minutes of preparation. That three minutes multiplies your response rate by roughly 5x based on my informal tracking.
The Five Types of Help Every Founder Needs
Over twenty years of building businesses, I’ve identified five types of help that every founder needs at different stages. Knowing which type you need prevents the vague “pick your brain” trap.
Type 1: Domain expertise you don’t have. Shipping logistics. Tax law. Marketing analytics. Employment regulations. These are areas where someone who knows answers your question in minutes, while figuring it out yourself takes days. This is the easiest type to ask for because it’s clearly transactional — you need specific information, not personal guidance.
Type 2: Pattern recognition from someone further along. “I’m experiencing X — have you seen this before?” This is invaluable because founders two or three stages ahead of you have already solved problems you’re encountering for the first time. Their pattern recognition can save you months of trial and error.
I received this type of help when I was building our accelerator program. A director of a more established accelerator spent an hour telling me which of my planned activities would work and which were a waste of time. His predictions were almost perfectly accurate. That hour saved me an entire wasted quarter.
Type 3: Honest feedback on your work. Not cheerleading. Honest feedback. “Here’s my product / pitch / strategy / pricing — what am I missing?” This type of help requires trust and vulnerability. It also requires asking the right person — someone with relevant expertise who respects you enough to be honest rather than polite.
Type 4: Emotional support from peers. “This is hard and I need to say that out loud to someone who gets it.” This isn’t weakness. It’s maintenance. Founders who never process the emotional weight of building a business eventually buckle under it. Having two or three peers who understand the founder experience is essential, and asking them for support is a skill.
Type 5: Introductions and connections. “I need to reach [person/type of person]. Do you know anyone?” The isolation of building a business makes this type especially important — founder loneliness is real, and introductions combat it directly. This is the most common ask and also the most frequently botched. The excellent version includes: who you need, why, what you’d discuss, and how the connection would benefit the person being introduced — not just you.
How to Build a Help Network Before You Need It
The worst time to ask for help is when you desperately need it. Desperation makes your asks needy, your scope vague, and your reciprocation impossible. The best time to build a help network is before you need it.
Here’s the system I’ve developed:
Give before you ask. For every person in my network, I try to provide value at least twice before I ever ask for anything. Share their content. Make an introduction they’d appreciate. Send them an article relevant to something they’re working on. These small deposits create a relationship foundation that makes future asks natural rather than transactional.
Categorize your network by expertise, not closeness. I maintain a simple list — not a fancy CRM, just a document — of people in my network organized by what they know well: finance, marketing, product development, legal, sales, specific industries. When I need help, I can quickly identify who to ask based on the type of expertise needed.
Stay in low-intensity contact. I reach out to twenty people per month with brief, no-ask messages. A comment on their post. A congratulations on an achievement. A forwarded article with a note. This maintenance keeps relationships warm so that when I do need help, I’m not contacting a stranger.
Be a connector. When I meet two people who should know each other, I introduce them. This builds my reputation as someone who adds value to the network, which makes people more willing to help when I ask. It also creates a natural reciprocity loop — people who’ve been helped by my introductions are inclined to help me when I need it.
The compound effect of showing up every day applies to networking just as much as it applies to content creation. Twenty small relationship investments per month compound into a powerful network over a year or two.
How to Receive Help Gracefully
Asking for help is one skill. Receiving it is another. Many founders are decent at asking but terrible at receiving, which prevents them from getting the full benefit of the help and discourages people from helping again.
Listen without defending. When someone gives you feedback or advice, your instinct will be to explain why you already thought of that, or why their suggestion won’t work in your specific situation. Resist this. Listen fully. Process. You can evaluate later. Defending in the moment signals that you didn’t really want help — you wanted validation.
Take notes and follow up. After someone helps you, send a brief message within 48 hours summarizing what you took away and what you’re going to do with it. “Thanks for the conversation yesterday. Your point about separating product pricing from service pricing was really useful — I’m going to restructure my offerings this week.” This closes the loop and tells the helper that their time wasn’t wasted.
Report back on outcomes. Three months after someone helps you, tell them what happened. “Remember when you suggested I try project-based pricing? I made the switch two months ago and my average project value increased by 35%.” This is the most powerful thing you can do for someone who helped you. It validates their advice and makes them feel like their time mattered. It also virtually guarantees they’ll help you again.
Don’t dismiss advice you didn’t want to hear. Sometimes help reveals uncomfortable truths. “Your product isn’t differentiated enough.” “Your pricing is too low.” “You need to hire someone for this role.” The advice that stings is often the advice you most need. Sit with it before discarding it.
Say thank you, and mean it. This sounds obvious. It’s not. Many founders, after receiving help, move immediately to implementation without acknowledging the person who helped. A genuine “thank you” — specific about what was helpful and why — takes thirty seconds and builds a relationship that lasts years.
The Help-Asking Habit
Like any skill, asking for help improves with practice. And like any habit, it requires intentional repetition before it becomes natural.
My challenge to you: for the next 30 days, make one ask per week. Not a big ask. A small one. Ask a friend to review your website copy. Ask a peer how they handle a specific operational challenge. Ask a client what they wish you did differently.
Start small enough that the anxiety is manageable. Each positive experience reduces the anxiety for the next ask. Within a few months, asking for help shifts from something you dread to something you do naturally — because you’ve experienced the returns and they’re undeniable.
The founders who build lasting businesses are not the ones who figure everything out alone. They’re the ones who figure out who to ask and when to ask them. That’s not weakness. That’s strategy.
Key takeaways:
- Craft excellent asks: be specific about the topic, bounded in time (15 minutes), show preparation, and explain why you’re asking this particular person.
- Build your help network before you need it — give value at least twice before asking, and stay in low-intensity contact with twenty people per month.
- Know the five types of help you need: domain expertise, pattern recognition, honest feedback, emotional support, and introductions — each requires a different ask.
- Close the loop: summarize takeaways within 48 hours and report back on outcomes within three months — this is what turns a one-time helper into a long-term advisor.
- Practice weekly: make one small ask per week for 30 days to build the habit and reduce the anxiety that prevents you from accessing the help you need.
