The Commercial Question Comes Before the Commercial Solution

Early in my career, working inside an agency, the standard request from a prospective client was simple: "We want a dedicated team. What will it cost?"

The standard mistake, on both sides, was answering that question before actually understanding it.

It's an easy trap to fall into, because it feels responsive. A client asks for a team, you price a team. Everyone moves fast, nobody feels like they're being difficult. But a price built on "we want a team" instead of "here's what's actually happening in your business" is a guess wearing a number.

So I built something to stop myself doing that: a scoping questionnaire, used before any price or team structure was ever discussed. Thirteen questions, in a deliberate order.

It started with money already being spent, not money about to be spent: current creative agency spend, media agency spend, freelance and contractor costs, staff overhead. Then it moved to people: what skills and roles already existed inside the business, and what was actually being asked to be outsourced, as opposed to what just felt easier to hand off. Then process: the on/offline split, which platforms were already in use, how work got approved, where files lived, what reporting already existed. Only after all of that did the conversation turn to the next twelve months, campaign plans, paid search, paid social, and what the business actually needed to see in a report to trust it.

None of that is a complicated idea. It's thirteen fairly ordinary questions. What made it useful wasn't the questions themselves, it was the discipline of asking them before anything got priced, every time, not as an optional nicety when there happened to be time for it.

A commercial solution shouldn't be prescribed before the problem is properly understood.

That's an easy sentence to agree with in the abstract. It's a much harder discipline to actually hold to, because the pressure in the room always points the other way. A prospective client wants an answer, not a questionnaire. Answering fast feels like confidence. Asking thirteen questions before you'll even discuss price can feel, in the moment, like you're making things harder than they need to be.

I'd argue the opposite is true. A price and a team shape that come from genuinely understanding what's already being spent, where the real gaps are, and how the business actually operates, is a better answer than a fast one, even when the fast one would have been easier to deliver in the meeting. The client asking for "a team" usually doesn't yet know whether they need a team, or three fewer freelancers and one clearer reporting line. You can't tell them which, honestly, until you've actually looked.

This is the same instinct Halo is built on, just applied earlier in the process, before there's even a client relationship to speak of. The Commercial Diagnostic and Commercial Audit exist for the same reason this questionnaire did: because the thing someone asks you to fix is rarely described precisely enough, on first mention, to actually fix responsibly. Understanding has to come first, not as a courtesy, but because skipping it produces confident answers to the wrong question.

What this looks like in practice, if you're the one being asked for a quick answer right now:

• Before pricing anything, write down what's currently being spent, on the thing you're about to replace or add to. Not what you assume, what's actually being spent, in full.
• Separate what genuinely needs outsourcing from what just feels easier to hand off. Those aren't always the same list.
• Ask about the process behind the request, not just the request. How work currently gets approved and reported often reveals the real gap faster than the stated problem does.
• Resist the pressure to answer fast. A considered answer that arrives a week later is worth more than a confident one that arrives in the room.

None of this means every quote needs thirteen questions and a week's delay. It means the order matters: understand first, price second. Get that order right consistently enough, across enough different situations, and it stops being a technique and starts being how you actually think.

This is part of a recurring pattern in how commercial problems actually get solved, not just this one instance of it. The broader version of this idea, evidenced across several different businesses over the years, is written up on Insights. It's also the reason Halo starts every engagement with a Commercial Diagnostic rather than a proposal.