Latest / The Founder's Journey with Fexingo: First-Time Entrepreneurs, Failures, and Lessons Learned / Why Your First Hire Made Or Broke The Startup
Transcript
- Lucas: There is a specific kind of panic that sets in around month eighteen of a startup's life. It happens when you have twelve employees, you are burning cash faster than your runway can sustain it, and you realize the person who wrote your original code base doesn't know how to structure a database for scale. Luna: The classic 'I built this, so I'm the only one who can fix it' bottleneck. It feels like heroism until it becomes a liability. Lucas: Exactly. And most founders double down instead of admitting they need to bring in someone better. Today we are looking at the single most expensive decision a founder makes: the tenth hire. Not the co-founder, not the first engineer, but that critical mid-level manager or specialist who bridges the gap between scrappy chaos and operational discipline. Luna: Because up until ten people, everyone knows everyone. After ten, you need systems, and systems require people who understand process, not just passion. Lucas: Right. And here is the trap. Founders often hire for culture fit at this stage. They want someone who vibes with the team, drinks the same coffee, and shares their vision. But what you actually need is someone who can execute without constant supervision. I read a study last week showing that startups that prioritized skill fit over culture fit in their first ten hires grew forty percent faster over three years. Luna: That seems counterintuitive if you think culture is everything, but I guess you can't scale a vibe. You have to scale output. Lucas: It is about defining culture correctly. Culture isn't just ping pong tables and casual Fridays. It is how decisions get made. If your culture is 'move fast and break things,' you need a hire who can break things safely, not someone who just breaks them recklessly. Lucas: So let us get back to that tenth hire. The mistake is usually assuming that a senior person from a large company will automatically elevate your team. They often don't. They bring baggage, expectations, and a reliance on resources you simply do not have. Luna: Or they try to impose too much structure too soon, which kills the agility that got you to twelve employees in the first place. Lucas: Precisely. I spoke with a founder last month who hired a VP of Sales from a Fortune五百 company. She came in with a six-month ramp-up plan, complex CRM requirements, and rigid reporting structures. Within sixty days, she had demoralized the existing sales team, who were used to closing deals via text message and intuition. Luna: Wow. So she tried to run a marathon before they could even walk. What was the outcome? Lucas: She left after eight months. Revenue dropped twenty percent during her tenure because the team was confused about priorities. The founder then had to spend another six months rebuilding trust. That is nearly a year of lost momentum for a single bad hire. Luna: It highlights the importance of context. You aren't hiring for a job description; you are hiring for a specific moment in your company's lifecycle. Lucas: And that brings us to the concept of 'stage-appropriate' hiring. In the seed stage, you need generalists who can wear five hats. In the Series A stage, you need specialists who can deepen one hat significantly. The tenth hire is usually the first specialist role that truly matters. Luna: Like bringing in a dedicated operations lead so the CEO stops doing payroll and scheduling. Freeing up the founder's time is a huge ROI. Lucas: Yes. But the interview process changes too. At this stage, you cannot rely solely on the founder's gut feeling. You need structured interviews that test for problem-solving under ambiguity. Because unlike in a large corporation, ambiguity is the default state for your team. Luna: So you give them a real-world problem from your actual business and ask them to solve it? That tests both skill and cultural alignment simultaneously. Lucas: Exactly. Let them fail in the interview room rather than in the product. One framework we recommend is the 'Pre-mortem.' Ask the candidate: imagine this hire failed six months from now. Why did it happen? Their answer tells you everything about their self-awareness and risk assessment. Luna: That is brilliant. It forces them to think critically about their own weaknesses and the environment they are entering. Lucas: It also reveals whether they are arrogant enough to think they will never fail. Nobody succeeds without failure in a startup. You want someone who learns quickly. Luna: Learning speed is probably the most underrated metric in early-stage hiring. Faster learning means shorter time to value. Lucas: Let us talk about compensation. This is where many founders lose money. They offer low salary and high equity, thinking the equity will attract top talent. But for the tenth hire, cash matters more than most people admit. Luna: Because they likely have mortgages and families, unlike the earlier employees who might be living in their parents' basements. Lucas: Spot on. Data shows that candidates at this stage prioritize total cash compensation over equity upside by a significant margin. If you underpay them, they will leave as soon as the company gets funding or stable revenue. You need market-rate salaries to retain institutional knowledge. Luna: So you pay for stability. You buy loyalty through fairness rather than hope. Lucas: Exactly. And that leads to the onboarding process. Most startups skip proper onboarding. They throw the new hire into the deep end and say 'figure it out.' This is a massive error. Luna: It wastes their time and frustrates them. They start asking questions that have been asked a hundred times before because nobody documented the answers. Lucas: Documentation is key. Before that tenth hire starts, you should have basic playbooks for common tasks. If they are spending their first two weeks figuring out how to access the server, you have already lost productivity. Luna: It signals respect. It says, 'We value your time and want you to succeed quickly.' That builds immediate trust. Lucas: Trust is the currency of early-stage teams. Without it, you spend half your energy managing friction instead of building product. Luna: What about the feedback loop? How do you know if that tenth hire is actually working out? Lucas: You set clear thirty-day, sixty-day, and ninety-day goals. These shouldn't be vague aspirations. They should be measurable outcomes. Did they ship the feature? Did they close the deal? Did they reduce churn by two percent? Luna: If they miss those goals, is it a performance issue or a support issue? That distinction is crucial. Lucas: Always assume it is a support issue first. Maybe they didn't have the right tools, or the brief was unclear. Remove obstacles before you blame the person. Luna: That shifts the dynamic from adversarial to collaborative. It reinforces the idea that you are on the same team. Lucas: And if, after removing obstacles, they still underperform, then you part ways quickly. Keeping a misfit is cruel to them and toxic to the team. Early exits are better than long-term drag. Luna: Hard to do emotionally, but necessary for the health of the organization. Lucas: It is. And remember, firing someone is not a failure of the founder. It is a correction of the portfolio. Just like you pivot your product, you pivot your team composition based on data. Luna: So the tenth hire is really a test of the founder's ability to evolve from operator to manager. Lucas: Yes. You stop being the best player and start being the coach. That is a hard transition for many technical founders. They miss the coding, the designing, the direct creation. Luna: But if you can't let go, you become the ceiling for everyone else's growth. You create dependency instead of empowerment. Lucas: Empowerment is the goal. You want your tenth hire to feel like they own their domain. Give them autonomy, hold them accountable, and remove roadblocks. Luna: Autonomy with accountability. That balance is everything. Lucas: It is. And when you get it right, that tenth hire becomes a force multiplier. They start hiring their own reports, they build processes, they free you up to focus on strategy and fundraising. Luna: Which is exactly when the company starts to feel less like a project and more like an institution. Lucas: An institution with a soul. Because the culture you codify with that hire sets the tone for the next fifty employees. It ripples outward. Luna: So the question isn't just 'can they do the job?' It's 'who will they become, and who will they inspire?' Lucas: Exactly. You are hiring for the future version of your company, not just the present needs. Think ahead six months. What skills will you need then? Bring someone who has those skills today. Luna: Anticipatory hiring. Planning for the gap before it appears. Lucas: Yes. Don't wait for the fire to start buying the extinguisher. Have it ready on the wall. Luna: A practical metaphor for a very abstract challenge. I think many founders overlook that preparation phase entirely. Lucas: They do. They react instead of proact. But the companies that survive the leap from small to medium are the ones that plan deliberately. Luna: Deliberate planning reduces the anxiety of the unknown. It turns a scary leap into a manageable step. Lucas: And that confidence radiates to the rest of the team. People follow leaders who seem sure of the path, even if the terrain is rough. Luna: So the tenth hire is less about filling a seat and more about setting the trajectory for the next chapter. Lucas: Precisely. It is the hinge upon which the next phase of growth swings. Get it wrong, and you stall. Get it right, and you fly. Luna: One decision, massive leverage. It reminds us that leadership is ultimately about making the right choices at the right time. Lucas: And hoping that those choices compound over time into something durable.