Tactical insights for first-time founders to outsmart the burn, the churn & the breakdown.

Hey Founder,

One of the fastest ways founders burn runway is hiring for the wrong job.

And it’s almost never the person. It’s the role.

The job you hire for and the job the business actually needs are often two different things.

Imagine you have two weak acquisition channels. What the company needs is someone to make one of them work.

Instead, you hire a VP of Marketing because that's what companies are supposed to have.

You hired someone to run a machine when the real job was to build one.

That's the trap.

Founders translate business problems into familiar job titles instead of the outcomes they actually need.

This issue is about one idea that fixes it: role-market fit, building roles around outcomes, not org charts. 

You already know product-market fit: customers want what you’re selling.

Role-market fit is similar: the company genuinely needs the work you’re hiring for, and that work exists now in enough volume and clarity for one person to own it and drive measurable outcomes.

The real trigger for a hire is simple: either your current team can’t reach an important outcome with the skills they have, or the work has outgrown the people already carrying it.

That’s when a new seat might make sense.

But most founders skip that step. They go straight from “we have a problem” to “we need a [title].”

You borrow titles from bigger companies, copy org charts from startups that made it, and assume the same label will fix your version of the problem.

That’s not strategy. It’s pattern matching.

A messy workflow becomes “we need a Head of AI.”
A messy sales process becomes “we need RevOps.”
“I’m overwhelmed” becomes a Chief of Staff post on LinkedIn.

The titles aren’t necessarily wrong. They’re just early.

YC has warned founders about this for years: don’t hire a VP of Sales before you’ve built a repeatable sales motion. If the founder hasn’t figured out how to sell, a VP can’t magically scale it.

Brian Chesky learned a version of this too. He hired great executives, empowered them, and stepped back. The result, in his words, was “devastating”, not because the people were bad, but because the seats assumed a machine existed.

It didn’t. 

That’s the pattern: the work is real, but the founder names it too quickly.

The seat gets invented before the job is clear, and no résumé can fill a hole nobody has properly defined. 

Most org charts were built for a world where work was slow, expensive, and people were the only way to get it done.

So companies added layers: people doing the work, managers coordinating them, and leaders coordinating the managers.

That world is disappearing.

Today, one great operator with the right AI tools can do work that once required a team.

Which means titles like "VP of X" stop describing the job.

You can't borrow yesterday's org chart anymore.
You have to design the seat around the outcome. 

For an pre-scale startup, every role should pass five tests:

1. One bottleneck. One outcome.

Hire to remove one clear constraint with one measurable outcome, not to "help with marketing" or "support operations."

2. AI-first leverage.

The right person asks, "What can AI handle?" before "Who can I hire?" They build systems, not manual work.

3. End-to-end ownership.

They turn messy problems into plans, execute without hand-holding, and report outcomes, not activity.

4. Comfort with ambiguity.

The role will change. The tools will change. They learn fast and redesign how they work as the company evolves.

5. Judgment you trust.

In a small company, every hiring another version of you to make calls when you’re not in the room. Skill gets the work done. Judgment decides what work is even worth doing.

The workforce is starting to look like an hourglass: more senior strategists, more AI-savvy operators, and a shrinking middle.

So the question is no longer: "Who should I hire?"
It's: "What's the smallest solution that closes this gap?" 

Sometimes that's a senior individual contributor who owns the work end to end.
Sometimes it's a fractional leader for a few hours a week.
Sometimes it's a contractor for a six-week project.
Sometimes it's not a person at all.

It's an AI agent handling the workflow while your team provides the judgment.

Only move to a bigger hire when the smaller solution has genuinely reached its limit. 

Start with the outcome.

Before you write a job description, finish this sentence: "I'm paying for ____ to happen over the next 12 months."

Then ask:

The role is whatever is left after every simpler answer fails. 

Pain sounds like: “I’m overwhelmed.”

A job sounds like: “This outcome needs a dedicated owner.”

Write the bottleneck this role exists to fix, then list the work that has shown up repeatedly over the last 8–12 weeks.

If you can’t find enough real, recurring work to fill most of someone’s week, you don’t have role-market fit yet. You have pain wearing a job title. 

Before borrowing a title from a bigger company, write what should change in the business.

What should be true by day 90?

What should be true by month 6?

Which 2–4 metrics will this person directly own?

If you can’t name the outcomes, the role hasn’t taken shape yet. 

Pick the function this seat belongs to, then write 3–7 core responsibilities.

For each one, finish the sentence: “This seat is accountable for…” 

Then ask whether this is one coherent job, or two or three roles bundled together.

If you can’t define it simply, you don’t have a seat. You have a wish list. 

A lot of bad hires come from hiring for the company you hope to become.

Be honest about your stage, strategy, and current AI/workflow maturity.

Does this role assume brand, channels, org layers, or infrastructure you don’t have yet?

If yes, you’re hiring too early.

Before publishing the JD, ask:
If we don’t hire this person, what breaks in the next six months?
Could a contractor or fractional hire test this first?
Would a strong person actually want this seat at our stage?
Is this still my job for another 6–12 months?

If nothing breaks, or a lighter option could test it, don’t open the role yet.

No backlog, no outcome, no roadmap, no role.

Bonus: decide IC vs exec honestly

Look at the work.

If most of it is doing, not managing or setting direction, hire a senior 

A founder asked:

Fight the narrow legal part, then move on and out-execute them.

The anger is fair. You paid for this in time, mistakes, and burn. They got the shortcut.

But separate what’s protected from what’s copyable. If they stole your name, logo, or copy word-for-word, send one short lawyer-drafted C&D and move on.

Everything else - offer, angle, packaging, price - is public. You don’t own that.

Treat it as market feedback: they copied what’s working.

The losing move is making them the reference point. Don’t drop prices, clone their clone, or rebuild your roadmap around beating them.

Use the energy where they can’t follow: better onboarding, sharper outcomes, stronger support, faster shipping.

Protect the brand once. Then raise your value until their version of you is always one release behind. 

Send it my way, just hit reply.

3 reads on different aspects of building:

Before you go…

Every founder wants to make great hires.

The sharper goal is to make only necessary ones.

When you stop chasing titles and design roles around real outcomes, hiring becomes less of a gamble and more of a force multiplier.

That’s the moat.

See you next Thursday,

— Mariya

Hit reply and let me know. I read every single one (for real).

Hey, I’m Mariya, a startup CFO and founder of FounderFirst. After 10 years working alongside founders at early and growth-stage startups, I know how tough it is to make the right calls when resources are tight and the stakes are high. I started this newsletter to share the practical playbook I wish every founder had from day one, packed with lessons I’ve learned (and mistakes I’ve made) helping teams scale.

Mariya Valeva

Find me on LinkedIn