JW · Josh Weir
← The Enterprise Architect
Spoke · The Enterprise Architect

Why we decline most engagement enquiries (and why that's the point)

We decline most of the engagement enquiries that come through the door. The decline rate is uncomfortable to talk about publicly because the rest of the consulting category is configured around accepting most of what comes in. The standard playbook is to qualify, propose, accept, and figure out the fit during the engagement. We do not run that playbook because it produces engagements that drift, deliverables that the client did not need, and outcomes that the consulting firm describes as successes while the client quietly reflects that the work did not move them.

The discipline of declining most enquiries is structurally better for both sides. The clients who come through the gate are clients we can genuinely help; the consulting firm is doing work it can stand behind; and the working relationship begins from a position of selection rather than from a position of obligation. This piece is the criteria we apply, the patterns the declined enquiries fall into, and why the discipline is worth maintaining.

What we look for in a credible enquiry

The enquiries that pass the initial gate share several properties.

  • The operator has a specific problem they can describe in their own words. They are not asking for a generic capability; they are asking for help with something concrete that is currently costing them.
  • The operator has tried to solve the problem themselves, and they can describe what they tried and why it did not work. This signals seriousness and gives us a starting point.
  • The operator's organisation has the operating maturity to act on architectural recommendations. We are not the right firm for organisations that need tactical implementation help; the work we do produces architectural shifts that require an organisation able to absorb them.
  • The operator is willing to pay for an audit before any larger engagement. Operators who want a free strategic conversation as the entry point are, in our experience, not yet committed enough for the work that follows.
  • The timeline is realistic. Operations that need a critical decision in two weeks rarely benefit from the kind of work we do; they need fast tactical help, which is a different category.

An enquiry that passes all five is unusual. Most fall short on at least one, and most of those are correctly declined because we cannot do good work under the conditions they describe.

The patterns we decline

The declined enquiries fall into recognisable patterns.

The strategic-advice request. An operator wants a strategic conversation about their direction, with no specific problem and no commitment to act. We decline because the value of strategic advice is in the implementation that follows, and operations that are not ready to implement do not benefit from strategic advice. They benefit from operating differently for a year first and then asking the question again.

The competitive-leverage request. An operator wants us to build something so they can sell it to their clients as our work. We decline because the engagement model produces neither good outcomes for their clients nor a working relationship we can stand behind. The right shape for that is a partnership or a license, not an engagement.

The fixed-price all-inclusive request. An operator wants a fixed price for an undefined scope, with the expectation that any complications during delivery will be absorbed in the original number. We decline because architectural work is genuinely uncertain on the inputs and the right pricing model is one that aligns risk with information. Fixed prices on undefined scopes produce either degraded delivery or contract disputes.

The political-cover request. An operator wants a written report that supports a decision they have already made internally. We decline because the integrity of the work depends on the work being able to disagree with the operator's prior conclusions. Reports that confirm pre-existing decisions are political instruments, not consulting work.

The mismatched-scale request. An organisation whose internal complexity is far above what a small firm can sensibly engage with — or, more often, far below the threshold where our engagement model makes sense. We decline and recommend a firm that fits.

Why the discipline is good for the clients we accept

The decline rate is, paradoxically, the most consequential signal of the value of the engagements that do happen. Clients who pass through the gate know that the gate is real; the engagement begins from a position of selection rather than from a position where the firm accepted whatever was offered.

The discipline produces a working relationship in which the firm can disagree with the client without losing the engagement, can recommend that the client not pursue something, can decline to extend an engagement when the value has already been delivered. None of these is possible in a consulting relationship structured around the firm's incentive to maximise revenue per client. All of them are possible in a relationship structured around the firm's selectivity in who it works with.

The clients we work with under this model report consistently that the difference is felt from the first conversation onward. They are dealing with a firm that has chosen to work with them, and the choice is reciprocated. The work that follows is materially different from what they would get in a relationship that began with the firm being relieved to have closed the deal.

Why the discipline is good for the firm

The compounding effect of the decline rate on the firm itself is the most important durability signal. A firm that selects clients carefully accumulates a portfolio of engagements that it can stand behind publicly. Every successful engagement strengthens the reputation. Every declined enquiry that subsequently turned out to be a bad fit reinforces the discipline. The track record over years is genuinely robust because it was built on selection.

The opposite trajectory is also visible in the consulting category. Firms that accept most of what comes through the door accumulate a portfolio with a long tail of mediocre outcomes. The successful engagements are real but are mixed in with engagements that produced little, and the public posture has to either acknowledge this or maintain a fiction. Both options weaken the firm over time.

The mathematics of selection compound; the mathematics of acceptance dilute. On a five-to-ten-year horizon, the difference is structural rather than incidental.

What an external operator should ask

The questions a serious operator should ask of any consulting firm they are evaluating are similar to the questions about a commodity intermediary's decline rate. What proportion of enquiries do you accept? What are the most common reasons for decline? Can you describe a representative declined enquiry without naming the operator? What would the engagement process look like if I brought you my problem today?

A firm that can answer these clearly, consistently, and without embarrassment is signalling that the gate is real. A firm that deflects, dismisses the question, or reports an implausibly high acceptance rate is signalling something else. The choice of which to engage with is then a much easier conversation than the surface narratives would suggest.

The takeaway

Declining most engagement enquiries is unconventional in the consulting category and structurally correct in the architectural-work category. The clients who come through the gate are the ones we can genuinely help. The work that results is work both sides can stand behind. The track record over years is built from selection rather than from acceptance, and the difference compounds.

For operators evaluating whether a consulting firm's posture matches the work they need done, the decline rate is the question worth asking. The firms that have built their model around it will answer plainly. The firms that have not will answer otherwise. That difference is the most useful signal an operator gets in the procurement conversation.

Working on this?

For operators evaluating sovereign-infrastructure architecture for a business of meaningful scale, we run a quarterly cohort of stack-design engagements.

Get in touch

Search terms this article addresses

consulting client selectionarchitecture consulting ukselective consulting practiceoperator-grade consultingconsulting decline rateboutique consulting practicesmall business architecture consultingconsulting integrity practice

Related under The Enterprise Architect