Mike Mullaney All articles
Opinion

Putting a Number on the Door: A Year of Publishing My Day Rate

Mike Mullaney
Putting a Number on the Door: A Year of Publishing My Day Rate

Photo: UK business consultant pricing page on laptop screen with day rate figures, desk with notebook and coffee, via as2.ftcdn.net

Every consultancy website in Britain has the same page. It goes under "Pricing" or "How We Work" and it says something like: every project is different, so get in touch for a tailored proposal. I wrote that sentence for years, and I half believed it. It felt cautious and professional. What it actually was, if I'm honest, was a door with no handle on it.

Twelve months ago I took the door off. I put a day rate on the site — a real one, plus VAT, in plain numbers, sitting next to a sentence explaining what it does and doesn't cover. This is what happened.

What I actually put on the page

Three things, in this order:

  1. A headline day rate for consultancy and delivery work.
  2. A line about fixed-price projects — that the day rate is a reference point, not a quote, and that most of my work is priced as an outcome rather than a timesheet.
  3. A note on what's excluded: travel outside a sensible radius, weekend work, third-party licences, and anything that needs me to be somewhere at 6am.

That's it. No rate card by seniority, no five-tier ladder, no "from £X" hedging. A number, a caveat, and an invitation to argue with either.

The enquiries that stopped coming

Within about six weeks, my inbound volume fell by roughly a third. I'd love to tell you I watched it happen with zen-like calm. I did not. I refreshed my inbox like a man checking a slow-cooked brisket.

But look at what left the building. The "quick question — what's your ballpark?" emails, sent before anyone had described the work. The prospect who wanted three days of advisory support and had £400 to spend. The agency middleman who needed a senior pair of hands at a junior rate and thought the negotiation started at 60% off. All gone.

The enquiries that arrived instead were shorter and better. People who had read the number, decided it was survivable, and turned up ready to talk about the problem. Roughly half mentioned the rate in their first message — and the smart half mentioned it approvingly, because they'd already compared it against two other quotes and found transparency less exhausting than a discovery call that turns into a sales pitch.

That was the unexpected part. I expected the rate to filter out tyre-kickers. I did not expect it to do any selling. But a public number says something about you that a case study can't: that you know what you're worth, that you're not going to invent a different figure for every conversation, and that you won't waste someone's afternoon before revealing the price.

Procurement: the awkward bit

Here's the part I underestimated. Publishing a rate invites a particular kind of buyer to hold you to it in a particular kind of way.

Two examples. First, a public sector buyer who asked me to justify the rate against their internal banding for a delivery manager post. Second, a procurement team who wanted a rate card broken down by role and task, then asked me to confirm that my day rate would hold for the whole of a nine-month engagement, expenses included, regardless of scope change.

Both conversations were entirely reasonable and both were faintly excruciating. The answer I've landed on is: the number is a starting position for a commercial conversation, not a commitment to freeze time. If a project runs nine months, the scope will move, and pretending otherwise helps nobody — least of all the person signing the purchase order.

I've also learned to be quicker about saying what the rate isn't. It isn't a cap. It isn't a discount floor. It isn't the same figure for every shape of work. Saying that early, in plain words, saves a fortnight of email ping-pong later.

What stays flexible

Publishing a number doesn't mean publishing a tariff. Here's where I keep the wriggle room, deliberately:

What I don't do is quietly cut the number to win a job and then make it back in change requests. That's the behaviour publishing a rate is meant to rule out.

How I defend it when someone pushes

Three moves, in order:

Reframe to outcome. "Happy to talk about the number — but let's first agree what a good result looks like, because that's what you're actually buying." If the outcome is worth £40k, the day rate is arithmetic, not philosophy.

Shrink the scope, not the rate. If the budget is £5k, I'll offer a smaller piece of work at the published rate. The number stays; the ambition changes. This is the single most useful sentence in my commercial vocabulary.

Say no, kindly, once. "That's below where I can do this work properly, and I'd rather tell you now than disappoint you in month two." Nobody has ever been angry about that. A few have come back six months later.

Would I do it again?

Yes, and I'd have done it sooner. Fewer enquiries, better enquiries, and a shorter path from first email to a real conversation about the work. The cost is that you have to be able to say the number out loud, to a stranger, without flinching — and then defend it with something more interesting than "that's my rate".

If you're sitting on the fence: publish one number for one service. Not the whole menu. Watch what leaves your inbox and what arrives to replace it. Give it a quarter before you panic. Then tell me whether the silence in week three was worth the clarity in week twelve.

All Articles

Related Articles

Reply Tomorrow: The Client Boundary That Makes You Easier to Trust

Reply Tomorrow: The Client Boundary That Makes You Easier to Trust

The Enquiries I Don't Chase — and the Margin I Keep

The Enquiries I Don't Chase — and the Margin I Keep

Nobody Claps for Fixed Invoicing — and That's Exactly the Problem

Nobody Claps for Fixed Invoicing — and That's Exactly the Problem