Hiring guide/Signals someone will deliver — and signals they won’t

Signals someone will deliver — and signals they won’t

The behaviours that predict a good outcome, the ones that predict a bad one, and the single best question to ask.

5 minute read

Capability and delivery are different things. The wall tells you someone can make the thing; nothing on it tells you they will make your thing, on time, without you chasing. Those signals show up in the first two exchanges, and they are surprisingly consistent.

Signals that predict a good outcome

They ask questions before quoting. The single most reliable indicator. Anyone who can price your project from a paragraph either does the same job every time or is guessing. Good questions are uncomfortable ones: who signs off, what happens if the deadline slips, what does the current thing actually do.

They quote with assumptions listed. “€2,400, assuming you supply the photography, the copy is final by the 3rd, and there is one round of revisions.” That is a person who has been burned and learned. The assumptions are where the disagreement was going to be.

They tell you what they will not do. Scope refusals early are a gift. “I do not do logo work” or “I would not build this in that CMS, and here is why” costs them the upsell and saves you the disaster.

They push back on something. Not everything — one thing. Someone who takes the brief entirely as written is either unusually lucky or not really reading it.

They describe a process with a middle. Not “brief, then delivery”, but the checkpoints between: a structure to review before writing, a first cut before colour, a staging link at the halfway mark. A middle is what lets you correct course before it is expensive.

Signals that predict a bad one

An instant fixed price with no questions. Fast is not the problem; certainty without information is.

Agreement with everything. Especially with contradictory things. If your brief asks for a launch in three weeks and a scope that plainly takes six, and nobody mentions it, it has not been read — it has been skimmed for a number.

Full payment up front, on a first project. A deposit is normal and fair. The whole amount before anything exists removes the only leverage you have, and a maker with a working practice does not need it.

No written scope. If after two emails you still do not have a list of what you are getting, you will be arguing about it later. That is not pessimism; it is arithmetic.

Vagueness about who does the work. If the person you are talking to might hand it to someone unnamed, you are hiring an agency, and should price and check it like one.

The single best question

Pick a piece on their page and ask:

What was the hardest problem in this one, and what did you end up doing about it?

It is very hard to answer well without having done the work, and very easy to answer well if you did. You are listening for a specific constraint and a specific trade-off — “the client's stock photography was unusable, so we shot the three images that mattered and cropped hard everywhere else.” You are listening against a smooth, general answer about collaboration and passion.

It also tells you something the wall cannot: how they behave when a project goes sideways. Every project goes sideways.

A note on being easy to work with

Delivery runs both ways. The most common cause of a late project is not a slow maker; it is a client who takes nine days to answer a question that blocks everything. If you cannot commit to turning feedback around quickly, say so at the start and let the timeline reflect it. A maker who plans around your real speed will hit the date. One who plans around your optimistic speed will not.

The whole guide is five pieces.

Read the rest, or go straight to the work.