Hiring a developer
Work out whether to hire a developer, before you do.
Hiring a developer feels like progress, but it only helps when the direction is already clear. Before you write the job post or sign a contract, let us work out whether you should hire at all, who you actually need and when.
What we work out
The questions we answer together.
- 01
Whether you should hire at all, or sharpen the direction first.
- 02
Who you need: junior, senior, generalist, specialist or contractor.
- 03
When the moment is right, and what should be true before then.
- 04
Whether a developer is even the bottleneck, or something else is.
How it works
From "I should hire someone" to a clear plan.
- 01
You bring the situation.
What you are building, where it is stuck, what you can spend and what you have tried. A few sentences is enough.
- 02
We pressure-test the hire.
We look at the real problem, the level and profile that fits it, the scope of the first brief and who keeps product ownership.
- 03
You leave with a clear way forward.
Hire now, wait and sharpen first, bring in a contractor, or solve it without a hire. Plus a clear first brief if you do hire.
What you leave with
What you get back.
- 01
A clear answer on whether, who and when to hire.
- 02
A sharper first brief and role description if you do hire.
- 03
A plan for the first three months, including what to do if it is not working.
Relevant frameworks
Read up before we talk.
When to hire a developer
Most startups hire developers before they have enough clarity. A decision framework for founders deciding whether the next move is a hire, a scope sharpen, or something else.
Agency or internal team?
An agency buys speed and breadth, but the knowledge leaves when they do. An internal team retains knowledge but is slow and expensive to assemble. A decision framework for founders choosing how to build.
Ready to talk?
Do you really need to hire yet?
Many startups think they need a developer when the real bottleneck is somewhere else.