The first contractor is a dangerous milestone.

It makes the project feel real.

That feeling can be useful. It can also be expensive theater.

A contractor should not be hired to create momentum. They should be hired to remove a bottleneck that real demand has exposed.

The question is not:

Can someone help me?

The question is:

Which proven bottleneck is now worth paying to remove?

The principle

Hire for bottlenecks, not fantasies.

Bad reason:

I need a designer so this feels like a real company.

Better reason:

Landing page traffic is converting below target, user feedback points to trust/design issues, and a better page can be tested within two weeks.

Bad reason:

I need a developer to build the full app.

Better reason:

Twenty users completed the manual workflow, twelve asked for repeat use, and the manual delivery is now the bottleneck.

The four contractor types

1. Production contractor

They help make assets.

Examples:

  • designer;
  • developer;
  • video editor;
  • writer;
  • no-code builder.

Use when:

The asset is clearly defined and demand justifies speed.

2. Specialist contractor

They bring expertise.

Examples:

  • paid search expert;
  • legal advisor;
  • analytics setup;
  • conversion copywriter;
  • ASO consultant.

Use when:

Mistakes are costly or expertise compresses learning.

3. Operator contractor

They run a repeatable process.

Examples:

  • research assistant;
  • outreach assistant;
  • customer support;
  • content ops;
  • data cleanup.

Use when:

The process is documented and repeated.

4. Strategic contractor

They advise direction.

Use carefully.

Strategy without evidence becomes expensive opinion.

The first contractor checklist

Before hiring, answer:

What bottleneck are we removing?
What evidence proves this bottleneck matters?
What exact deliverable do we need?
What does good look like?
What is the budget?
What is the deadline?
What will we measure after delivery?
What can go wrong?
Who owns final judgment?

If you cannot answer, do not hire yet.

The brief

A contractor brief should include:

Context
Objective
Target audience
Deliverable
Examples/references
Constraints
Deadline
Success criteria
Review process
Payment terms

Good contractors become better with better briefs.

A vague brief creates expensive ambiguity.

The budget rule

Spend less on contractor work than the evidence can justify.

Example:

If a landing page has generated 200 qualified visits and 20 signups, spending €500–€1,000 to improve conversion may be rational.

Example:

If no one has visited the page and no one understands the offer, spending €5,000 on design is premature.

The delegation trap

Do not outsource judgment too early.

You can outsource production. You can outsource research. You can outsource editing. You can outsource implementation.

But the founder owns:

  • customer understanding;
  • positioning;
  • pricing;
  • prioritization;
  • quality;
  • decision rules;
  • ethics;
  • company direction.

A contractor can help build the asset.

They cannot care more than the founder.

The founder lesson

The first contractor should make the business sharper, not just larger.

Hire when the work is defined, the bottleneck is real and the output will create evidence.

A contractor is not a sign that the company is serious.

A clear brief is.

References