You Can’t Outsource Unclear Thinking

Most early-stage founders have a version of the same thought at some point: "If I just hire someone, this will be fixed." The pipeline problem. The ops bottleneck. The product debt that keeps compounding. Hiring feels like the responsible response, until the person is in the role and the problem is still there, wearing a different shape.

Håkon Høgetveit, Vouch’s CEO, spent 15 years building and scaling teams before starting the company. When he looks back at his own hiring mistakes, he doesn’t blame the candidates. Every single one, he says, came down to him not actually understanding what he was hiring for.

"Every single hiring mistake I’ve made over the last 15 years had nothing to do with the candidate. It was because I didn’t actually understand what I was hiring for."
- Håkon Høgetveit, Vouch CEO

That’s an uncomfortable thing to sit with. It means the problem wasn’t talent, or timing, or bad luck. It was the clarity of the person doing the hiring.

The pattern that causes the most damage in early-stage teams isn’t hiring the wrong person. It’s hiring before you know what the right person would actually do. Founders hire to relieve stress, to feel like they’ve acted on a problem. They hire to avoid an uncomfortable thing they don’t want to keep doing themselves. They hire before they’ve answered the most basic question: what, exactly, should this person accomplish in their first month? What would good look like, and what would failure look like?

When those answers aren’t there before the hire, they won’t be there after it either.

The principle that tends to save early-stage hiring is unglamorous: you should only hire for something you’ve already done yourself. Not necessarily with excellence, and not necessarily at scale, but done it enough to know what hard looks like, what good looks like, and what it costs you every week not to have someone doing it well. If it hurts you weekly and you know what great looks like, you can transfer the scope. If you can’t articulate the role in terms of weekly output rather than a job title, you’re not ready.

A founder who hires a “Head of Sales” because that sounds like the next step is playing a different game than one who hires specifically to take thirty outbound calls a week, turn them into qualified demos, and build the playbook for everything that comes after. Same function, very different clarity.

Early-stage team building is closer to risk management than most founders want to admit. Every person who joins before you reach twenty changes the company, the culture, the way work gets done, what the next hire looks like. The cost of a bad early hire isn’t just the salary and the months lost. It’s the version of the company you were trying to build, now bent in a direction you didn’t intend.

Before you post the next role, five questions are worth sitting with honestly: What problem, exactly? What does great look like? What would failure look like? Can you battle-test the collaboration before a full commitment? And, perhaps most importantly, are you acting from clarity or from panic?

If you can’t answer those, the hire probably isn’t ready.

Vouch was built around this problem. The most important moment in a good hire happens before the interview, in the scoping conversation a founder is willing to have with themselves.

The earliest hires don’t just change your headcount. They change your company.