Latest / The Career Mentor Podcast with Fexingo: Finding Mentors, Sponsors, and Career Advisors / How Non-Technical Founders Can Find a Mentor
Transcript
- Lucas: So you have a great idea for a software product, but you do not write a single line of code. You are what the startup world calls a non-technical founder. And if you have tried to build anything, you know how steep the climb is. Luna: It is one of the most common dilemmas I hear from listeners. They have the domain expertise, the customer insight, but they feel locked out of the building process. Lucas: Right. And a lot of startup advice focuses on finding a technical co-founder. But that relationship often fails, or you end up giving away too much equity. So today I want to talk about a different path: finding a mentor who can guide you through the non-technical side of building a tech company, while you own the product vision. Luna: Can you give us a concrete example of someone who did this well? Lucas: There is a founder named Julia. She was a high school history teacher for eight years. She had no engineering background, but she saw a problem in how teachers collaborate on lesson plans. She built a prototype using a no-code tool. It was clunky, but she showed it to a few people. One of them connected her with a mentor named Tom, a former teacher turned product manager at a major edtech company. Luna: So Tom understood both the domain and the product side. That is key. Lucas: Exactly. Tom did not write code for Julia. He helped her prioritize features, set up user testing, and avoid building things nobody needed. He also introduced her to a freelance developer who built the first real version for a flat fee. Within eighteen months, her tool had fifty thousand active users, and she was able to quit teaching. Luna: That is a great outcome. So where should a non-technical founder start looking for a mentor like Tom? Lucas: I would say three places. First, no-code and low-code communities. Think Bubble, Notion, or Airtable user groups. People there are often former non-technical founders themselves. Second, product management meetups—PMs are natural mentors because they bridge business and tech. Third, LinkedIn, but with a reverse search: look for people who list 'former teacher turned product manager' or 'non-technical founder turned advisor'. Luna: Interesting. So you are going after people with a similar background story. That makes the ask more natural. Lucas: Right. You can say, 'I see you also started without a technical background and now you are running product at a company. I would love to learn how you navigated the early days.' That is a much warmer request than a cold email asking for a co-founder. Luna: What should the first meeting look like? I imagine many non-technical founders are nervous about sounding naive. Lucas: Very understandable. But you should prepare like crazy. Come with a one-page summary of your problem, your target user, and what you have learned so far. Show that you have done homework. And then ask specific questions: 'How did you decide what to build first?' or 'What is the biggest mistake you made with your early product?' People love sharing their scars. It makes the conversation real. Luna: I have had that experience. When I ask for war stories, a mentor usually opens up fast. Lucas: Exactly. And here is a counterintuitive piece: do not ask a potential mentor to validate your idea. That is a recipe for yes-men. Instead, ask them to poke holes. Say, 'What would make this fail?' That shows you are serious about building something durable. Luna: So you are looking for a mentor who challenges you, not one who just cheers you on. Lucas: Exactly. But also someone who respects your domain expertise. A mentor who says 'just learn to code' is not helpful. You need someone who helps you leverage what you already know, and fills the gaps you cannot fill yourself. Luna: What about the risk of being over-mentored? I have seen some founders get stuck in a cycle of taking advice from too many people and never launching. Lucas: That is real. The fix is to have a maximum of two mentors during the building phase. One domain expert and one product/technical translator. And give yourself a deadline to launch a minimal version, no matter what. Mentors are there to accelerate decisions, not to replace them. Luna: Let us talk about the ask. How do you approach someone you do not know? Lucas: Keep it low stakes. Write a short LinkedIn message: 'I am building X in Y space. I respect your work on Z. Could we have a fifteen-minute call to see if there is mutual fit?' Some people will say yes. When they do, be ready to respect their time. If the call goes well, ask if they would be open to a monthly thirty-minute check-in for three months. That gives them an easy out if it is not a match. Luna: And what if they say no? How do you handle that without getting discouraged? Lucas: Rejection is part of the process. You should have a pipeline. Reach out to five to ten people. Most will not reply. A few will. One might become a lasting mentor. Julia messaged about twelve people before Tom said yes. That is normal. Luna: That is a good reality check. So persistence matters. Lucas: It does. But also, consider that the best mentors often come from unexpected places. Not the most senior or famous people, but those who are a few years ahead and still remember the struggle. They are often more generous with time. Luna: I want to circle back to the idea of domain expertise. How do you present your own authority to a potential mentor without sounding arrogant? Lucas: You lead with curiosity, not expertise. Say, 'I have worked in this industry for a decade and I see a gap. But I know I have blind spots on the technology side. That is where I need help.' People respect self-awareness. And it makes them feel like they can actually contribute something valuable. Luna: So the ideal mentor is someone who respects your domain knowledge but complements your technical gaps. Lucas: Exactly. And if you can find someone who has also successfully made the transition from non-technical to product leader, that is gold. They have walked the path. Luna: One last thing: what about the timing of finding a mentor? Should you have one before you even start building? Lucas: It helps. But do not wait too long. The first version can be a scrappy no-code prototype. Show that to a potential mentor. It gives them something concrete to react to. And it proves you are serious. Luna: I think that is a crucial point. Show progress, even if it is imperfect. Lucas: Exactly. And if this kind of career insight has been helpful for you, especially if you are navigating a big career move or side project, I want to mention that listener support is what keeps this podcast ad-free and running. Luna: Yeah, it is a small way to keep the conversations going without interruptions. If you have found value, you can support us at buymeacoffee dot com slash fexingo. Lucas: Even a small contribution helps. And it really does make a difference for us to keep bringing you these deep dives. Now, back to Julia's story. After she launched her tool, her mentor Tom helped her navigate the user feedback loop. She learned to ignore feature requests from the loudest voices and focus on the core workflow. Luna: That discipline is tough for first-time founders. You want to please everyone. Lucas: Right. Tom helped her create a simple framework: classify every request as 'must-have for launch' or 'nice to have for later.' That kept her from building a bloated product. And after a year, she had a loyal base of early adopters who felt heard without overwhelming the roadmap. Luna: That is the power of a mentor who has been through it. They give you the tools to make tough decisions, not the answers. Lucas: Exactly. So if you are a non-technical founder, do not get discouraged by the technology barrier. Your superpower is understanding the problem better than anyone. Find a mentor who can help you translate that into a product, and you are already ahead of most startups that fail because they build something nobody wants. Luna: Well said. And who knows, the next breakout software might start with a teacher in a classroom who just needed a better way to plan lessons. Lucas: I love that image. So go out there, find your Tom, and build something worth sharing.