Contractor or Consultant: Know Which One You're Actually Hiring

A founder hires a designer to build a new website. She comes in with a clear brief: these pages, this structure, this feel, here are three sites I like. The designer executes it well. The site launches. It's beautiful. And it converts about the same as the old one.

Nothing went wrong with the work. Something went wrong with the hire. She needed someone to tell her the brief was the problem. She hired someone to execute the brief instead.

This is the contractor and consultant distinction, and most founders don't know which one they're hiring until the project is over.

The actual difference

A contractor executes your thinking. You define the problem, you define the solution, you hand over a scope, and they deliver it with a skill you don't have in-house. The judgment is yours but the craft is theirs.

A consultant brings the thinking. You describe a situation, and their job is to tell you what the problem actually is, which is often not the problem you walked in with. The scope is an output of their work, not an input to it. You're paying for their judgment first and their craft second.

Both are legitimate and both are valuable. They are not interchangeable, and they are not priced the same, because they are not the same thing.

The two expensive mistakes

Hiring a contractor when you needed a consultant. This is the website story above. You had a problem you couldn't fully see, you wrote a brief based on your partial view of it, and you hired someone whose job was to execute the brief faithfully. They did. The brief was wrong. And you just paid to make your own blind spot more polished (read that again).

Hiring a consultant and treating them like a contractor. You hired someone for their judgment, and then you overrode it at every turn. You hired the expert and then made yourself the expert. You're paying consultant rates for contractor output, because the moment you stop letting their judgment operate, that's all you're getting.

The first mistake is more common. The second is more frustrating, because the value was right there and you talked yourself out of it.

When you actually need a contractor

You need a contractor when the thinking is genuinely done or in my opinion (depending on the business), when its just starting out.

The problem is well understood. You've diagnosed it correctly, you're confident in that diagnosis, and the path forward is clear. What you're missing is capacity or a specific craft skill. You know exactly what needs to be made. You just can't make it yourself, and you shouldn't be the one spending time on it.

In this situation, a consultant is overkill. You'd be paying someone to re-diagnose a problem you've already solved. Hire the craft, hand over the brief, and get out of their way.

When you actually need a consultant

You need a consultant when any of these are true:

• The problem is fuzzy. You know something isn't working, but you can't name it cleanly, and every time you try to write the brief you end up describing symptoms instead of causes.

• You've already tried the obvious thing. You did the rebrand, ran the ads, rebuilt the site, and the number you cared about didn't move. The obvious fix failing is usually a sign that the obvious diagnosis was wrong (and this could also be this problem).

• The cost of being wrong is high. The decision is expensive enough, or hard enough to reverse, that you want someone whose judgment has been tested on this exact kind of problem before, and who will tell you when your instinct is leading you somewhere you'll regret.

In these situations, hiring a contractor doesn't save you money. It just delays the moment you hire the consultant, and adds the cost of the contractor's work to the bill.

How to tell which one you're hiring

You can usually tell in the sales conversation, before you've signed anything.

A contractor takes your brief. A consultant interrogates it. If someone asks "why" several times before they ask "what," and if they seem more interested in the situation than the deliverables list, you're talking to a consultant.

A contractor prices the scope. A consultant prices the engagement. If the proposal is a line-item list of deliverables with a number next to each, that's contractor pricing. If the proposal opens with a phase of diagnosis and a scope to be defined after it, that's consultant pricing.

What this means for working with us

We do both kinds of work, on purpose, because the founders who come to us aren't all in the same situation.

Our intensives are contractor-mode work. A defined scope, a focused block of time, a clear list of what's getting made. If you've done the thinking, you know what you need, and you want it executed well and fast, an intensive is built for exactly that. It's often the right starting point for founders who are earlier in the journey and don't yet need a standing strategic partner.

Our grow and lead packages are consultant-mode work. They're built with enough time and room for the diagnosis to happen, for us to push back, for the scope to be shaped by what we find rather than what you assumed walking in. This is where the consulting side of what we do actually gets to operate. It isn't a longer intensive. It's a different kind of engagement.

The mistake to avoid is buying the wrong mode for your situation. An intensive can't do consultant work no matter how much you want it to, because the format doesn't leave room for it. And a grow or lead package is more than you need if the thinking is genuinely done and the path is already clear.

If you're not sure which mode your situation calls for, that's the conversation to start. Figuring that out with you is the first piece of consultant work we do.