Home/Blog/Early Hiring/Who to Hire First at a Startup: Start wi…
Early Hiring

Who to Hire First at a Startup: Start with the Constraint

Who to hire first at a startup: name the one thing holding everything else up, test whether a hire is the answer, then choose the role that removes it.

Cover of the FIKR Space guide: Who to Hire First at a Startup: Start with the Constraint

Who to hire first at a startup is decided by the current constraint, not by a wish list: hire the person whose work removes the one thing holding everything else up. The order of your first ten roles matters because each one decides what the company can do next.

It sounds obvious, and yet most early teams are not built that way. They are assembled from the accumulated ambitions of the last year. Each ambition was reasonable. None of them was the constraint at the moment it was hired.

Who to hire first at a startup: the question that replaces "what role?"

The natural question is which role to add. It leads to lists of functions the company would like to have, and every item on such a list is defensible. The better question is different: what is the single thing most limiting us right now, and what is the cheapest way to remove it?

Notice the phrase cheapest way. It leaves room for an answer that is not a hire at all. That outcome is legitimate, and founders rarely consider it once they have started thinking about a role. Before you write a job description, write one sentence that names the constraint, and keep it to this quarter.

Why a long list is a warning sign

If the sentence you write has five parts, you have not found the constraint yet. You have found your ambitions. The test is whether removing the thing would let the other items on the list move. The constraint is the thing holding the rest up. The remainder are simply other things you would like to be better at.

Founders who skip this step tend to hire against whichever pain is loudest on the day. The loudest pain and the real constraint are often different things, which is why it helps to write the sentence down rather than carry it in your head.

Free guide, 33 pages: The First Ten Hires Playbook. Send me the guide.

How the order shapes what the company can do

The sequence of the first ten roles is a strategy decision disguised as a staffing one. Two examples show the principle.

If the real constraint isThen hiring thisProduces
Nobody can sellA second engineerCapability the company cannot use
There is no message yetA marketerActivity without direction

Both hires might be excellent people doing good work. Neither moves the company, because the thing that was limiting it sits somewhere else. This is the sense in which order is strategy: the person you add first changes what the company is able to attempt in the following months.

Check the alternatives before you hire

Once the constraint is named, ask what would remove it, and only then ask whether a person is the answer. The options worth considering are short.

  • A contractor, for work that is real but not permanent.
  • A tool, where the constraint is mechanical.
  • A process change, where the work exists but is done awkwardly.
  • A reallocation of your own time, where the constraint is how you spend your week.

None of these is a lesser outcome. A contractor who clears the constraint in a month may be worth more than a permanent hire who would have cleared it in a year. The point is to choose on purpose, which is also why the next step is to see what a hire would cost.

Test the choice against what you will stop doing

A useful question is what you will stop doing, or do differently, once this person arrives. If the honest answer is nothing, the role may not be addressing the constraint at all. A real constraint, once removed, changes something about how the company works, and you should be able to say what.

This also exposes a quieter problem, which is delegation. Every founder says they want senior people who take things off their plate. Rather fewer let go once someone arrives. They keep the decisions, review the work and rebuild what was delivered. A capable senior person will diagnose that within weeks and start looking. If the constraint is really your willingness to hand things over, a new hire will not remove it, and it is better to know that before you spend months of runway.

Know what comes next, and why this one is first

Choosing the first role well is easier when you can say which role comes after it. You do not need a full plan for ten people. You need to be able to explain why this role is first and what would have to be true for the next one to take its place.

This protects you against drift. Without it, each hire is judged on its own merits and the team becomes a collection of individually sensible choices. With it, you can see the sequence, and the sequence is the strategy.

QuestionWhy it matters
What is limiting us this quarter?Names the constraint instead of a wish
What would remove it most cheaply?Leaves room for a contractor, a tool or a process change
What will we stop or change when they arrive?Checks the role is real
Which role comes next, and why is this first?Makes the order a deliberate choice

Put a price on the choice

Once you know who, the next question is whether the company can afford their contribution to arrive late. Two roles can look equally affordable in salary terms and very different in the thing you are actually short of, which is time. The way to compare them is set out in generalist vs specialist hire, which prices the hire in months of runway.

Then describe what the person must produce, because a role you cannot describe is a role you do not yet understand. That step is covered in how to write a ninety day role outcome. If you cannot write it, you are not ready to hire. You are ready to think about what you need.

FIKR People, team and HR for founders: hiring, onboarding and reviews in one workspace. See FIKR People.

How to write the constraint sentence

Keep it plain and keep it to one thing. A good sentence says what is stopping progress, not which function you wish you had. Compare the two forms.

FormWhat it sounds likeWhat it tells you
A wishWe need to be better at several thingsNothing you can act on this quarter
A constraintOne named thing is holding everything else upWhat would remove it, and whether a person is the answer

The second form is harder to write because it forces a choice. That difficulty is the point. If you cannot choose, you do not yet know enough about the company's current position, and no interview will tell you.

Show the sentence to someone else

A constraint that only you have seen is easy to bend. Give the sentence to a person you trust and ask whether it matches what they see. If they point at a different bottleneck, that disagreement is useful information, and it is far cheaper to have the argument now than after an offer has been made.

This is a small version of a habit that matters throughout hiring: letting someone who is not desperate to fill the seat look at your reasoning. Early team members often notice things a founder misses, partly because they are not the one who needs the role filled.

Mistakes when choosing the first hire

  • Hiring the wish. A role that would be nice, rather than one that removes the bottleneck.
  • Hiring for a feeling. Being overstretched is not the same as having a real role. The test is whether you can say what will exist when it goes well.
  • Treating the list as permanent. The constraint changes. A role that was right last quarter may not be the right next one.
  • Skipping the alternatives. Not asking whether a tool, a contractor or a change in your own time would do the job.
  • Ignoring your own habits. Hiring senior people and then keeping every decision.

Each of these is a failure of definition, not a failure of judgement about people. That is good news, because definition can be fixed before you meet a single candidate.

Free guide, 33 pages: The First Ten Hires Playbook. Send me the guide.

Where this fits in the whole sequence

Choosing the role is the first of several decisions made before anyone is interviewed. The overview in how to make your first hire shows how the pieces connect, from the need to the bar. After the role is defined, the work moves to running a process that predicts performance, and then to the weeks after the yes.

You do not have to do all of it perfectly. You do have to do the first part deliberately, because the later steps can only improve a hire that was aimed at the right problem.

FIKR People, team and HR for founders: hiring, onboarding and reviews in one workspace. See FIKR People.

Frequently asked questions

What if I have several urgent problems?

Choose the one that is genuinely holding the others up. If you cannot tell which it is, ask what would let the rest move once it was removed. The answer is usually the constraint.

Is it ever right not to hire?

Yes. The cheapest way to remove a constraint is sometimes a contractor, a tool, a process change or a different use of your own time. Reaching that conclusion before you open a role is a good outcome.

Should my first hire be someone who does the work I dislike?

Only if that work is the constraint. Hiring to relieve a dislike, rather than to remove the thing limiting the company, is one way a team ends up built from wishes.

How far ahead should I plan the order?

Far enough to say why this role is first and which role comes next. You do not need a complete plan for ten people, and the constraint will change, but you should be able to explain the sequence you have chosen.

The full method, with the checklists, is in The First Ten Hires Playbook, a free 33-page playbook.

LG

Luis Goncalves

// Founder & CEO at FIKR Space

Three-time founder. Built and exited Evolution4All before this. Now building FIKR Space — the operating infrastructure underneath every innovation ecosystem (startups, accelerators, governments, investors). Lisbon-based, works global.

Claim your founding member spot.

Every founding member is hand-reviewed. Tell us who you are and how you want to co-create — we get back inside 48 hours.

Role
Job Title
Country
Cookies

We use cookies.

Essential ones keep the site working. The rest only run if you say so. No dark patterns, no pre-ticked boxes.Privacy policy

Co-create with us. It's about building it together.Co-Create With Us