PROFESSIONAL SERVICES / AFTER THE PROPOSALS ARRIVE

Comparing Professional-Service Proposals When the Scopes Do Not Match

One firm offers a diagnosis. Another offers a plan and a pilot. A third offers access to senior advice. The committee has three prices and three different purchases.

By Dr. Robert Urban · PaperBoat Media · 8-minute read

The committee agrees on the problem, until it reads the scopes.

Consider a fictional business advisory engagement. A regional distributor wants to decide how to improve its customer onboarding process. Sales says the handoff is slow. Operations says the information arriving from sales is incomplete. Leadership wants an agreed process and a practical first test before committing to a wider rollout.

Three shortlisted firms submit proposals. The finance leader opens a spreadsheet with columns for fee and duration. The operations leader asks who will actually run the test. The CEO wants to know whether the senior person from the pitch will still be involved.

Those are reasonable questions, but they address different parts of the purchase. The committee needs a shared description of the work before it can judge the differences. This example uses invented firms, offers and timelines. It contains no client proposal, market fee benchmark or claimed result.

Choosing a professional-services firm begins with relevance and trust. The task here starts later, when credible firms have put different boundaries around the same assignment.

Write the decision the engagement must support.

The committee’s working brief is one sentence: Choose an onboarding process, test it in one branch and decide whether it is ready for a wider rollout. That sentence exposes three decisions: what to change, how to test the change and what the test supports.

A diagnostic can contribute to the first decision without covering the other two. Ongoing advice may support all three while leaving the client responsible for producing every working document. A pilot package may include execution support but depend on staff time the client has not reserved.

The UK Cabinet Office’s Consultancy Playbook, version 1.1, distinguishes desired outcomes from the deliverables that support them and calls for clear client and supplier responsibilities. It is guidance for government commissioning. Those distinctions are useful here as vocabulary; this private-company example does not import its procurement rules.

Keep the brief stable while comparing. If the committee discovers it only needs a diagnosis now, change the brief explicitly. Do not quietly penalize a narrowly scoped firm for work the buyer never clearly requested.

Three proposals, read against the same decisions

Here are the fictional offers before any clarification. The table preserves each firm’s approach. An empty commitment stays unresolved; a stated exclusion stays an exclusion.

What the distributor would actually be buying
Question	Firm A: diagnostic	Firm B: design and pilot	Firm C: advisory retainer
Promised output	Interview findings, current-process map and prioritized recommendations.	Process design, pilot materials, facilitation of one branch test and a review of the test.	Senior advice at agreed meetings and review of client-prepared materials. No separate process map or pilot report promised.
Client’s work	Provide records, arrange interviews, select recommendations and run any subsequent test.	Name a branch lead, release staff for the test, provide records and make operating decisions.	Prepare analysis, write documents, organize the test and bring questions for review.
Timing and fee basis	Fixed fee for a four-week diagnostic after required records and interviews are available.	Fixed fee for an eight-week design-and-pilot engagement, dependent on branch access and decisions.	Monthly fee for three months of defined meeting and review access. Additional work needs a separate agreement.
Senior involvement	Named lead conducts the interviews; partner reviews recommendations.	Delivery lead manages the work; proposal does not say which decisions include the senior specialist.	Named senior advisor attends the included meetings. Availability between meetings is not established.
After the engagement	Implementation and rollout explicitly excluded.	One-branch pilot included. Wider rollout excluded. Handoff format needs clarification.	Continuing access requires a further engagement. Ownership of unfinished client work remains with the client.

Firm A has not submitted a weaker version of Firm B’s offer. It has stopped at an earlier decision. Firm C places more production responsibility inside the client organization. Neither fact establishes value by itself.

The fee comparison becomes meaningful when the buyer chooses a common boundary. For this brief, the committee needs to understand the total work through the pilot review. Firm A’s fee does not include that boundary. Firm C’s three monthly fees cover access over time, not a promise that the client will complete a pilot in that period.

Record the actual quoted amounts and currencies, expenses, applicable separate charges and approved optional work in the real comparison. Keep unpriced work visibly unpriced. A guessed implementation fee would make the spreadsheet look more complete while making the decision less dependable.

The missing resource is on the buyer’s side.

Now add one fictional fact: the distributor has a capable branch supervisor who can lead a test, but no available analyst to build a process map, prepare pilot materials and document the findings. The supervisor can contribute operating judgment and make time for the test. She cannot absorb all of the project production.

That fact changes how the committee reads Firm C. Senior advice could be valuable, but the retainer leaves a large body of work with a client team that has not staffed it. Calling the proposal “flexible support” does not fill the gap.

Firm A also leaves the pilot preparation and execution outside its scope. It could still be the right first phase if leadership wants a diagnosis before authorizing a test. Under the current brief, however, the committee must identify who will do the next phase and how that work will be approved.

Firm B comes closest to the stated boundary, but the committee still needs to establish senior involvement, the client’s actual time commitment and what it receives at handoff. The comparison has produced a conditional preference and several precise questions. It has not proved that Firm B can deliver well.

Ask each firm the question its proposal creates.

To Firm A: “Your diagnostic ends with recommendations. If we proceed to a branch test, which materials from your work would support it, and what additional work would someone need to perform? Please separate any optional follow-on scope from the diagnostic price.” This respects the original boundary while revealing the work beyond it.

To Firm B: “Please identify the senior specialist’s role in choosing the process and interpreting the test. What will our branch lead need to provide, and what records and editable materials will we receive at handoff?” Ask for a representative, shareable example of the type of pilot output, with confidential material removed. A promise of a report is easier to evaluate when the buyer understands what the report must enable.

To Firm C: “Which analysis and documents must our team produce before each review? What response arrangements apply between meetings? If we cannot supply the production work internally, do you offer it separately, and would that change the engagement?” A named advisor and a meeting schedule do not answer these questions.

Keep the responses with the proposal date and version. If a clarification changes scope, timing or price, request an updated written offer that reflects it. The committee should not vote on three original documents plus three people’s memories of different calls.

This is also where institutional trust in a professional firm becomes concrete. The delivery team, senior judgment and handoffs need to be visible in the engagement being purchased.

A decision memo the committee can disagree with usefully

For the distributor, the memo might read as follows. It is a working recommendation, contingent on the unresolved evidence.

Decision sought: Authorize an engagement through the review of one branch pilot. Wider rollout will be a separate decision.
Preferred approach and reason: Continue clarification with Firm B because its proposed outputs cover process design and pilot execution support, and the client lacks an available analyst to produce those materials.
Work the client retains: Name the branch lead, supply source records, release staff for the agreed test activities and make the operating decisions. Confirm the required time before approving the schedule.
Conditions before selection: Confirm the senior specialist’s role, review suitable evidence of comparable delivery, agree what makes the pilot materials ready to use, and establish the handoff contents and separate costs.
Alternatives preserved: Choose Firm A if leadership limits the immediate assignment to diagnosis and accepts a separate decision about the next phase. Reconsider Firm C if the client can provide the production team its model requires.
Unresolved question and owner: The operations sponsor must confirm branch capacity. The committee lead must obtain and circulate the revised offer and evidence before requesting a final decision.

A reusable memo needs these same kinds of information: the decision, the chosen scope boundary, the reason for the preference, the client’s responsibilities, evidence still needed and the next accountable step. It does not need a numerical score for every adjective in the proposal.

What a tidy comparison cannot establish

A clearly described scope may still be delivered badly. A vague proposal may come from a capable firm that needs to explain its offer better. The table helps identify what is being promised; references, relevant work, conversations with the delivery team and appropriate review of the engagement remain separate parts of the decision.

Do not treat a provider’s proposed method as an interchangeable list of tasks. One firm may have a sound reason to diagnose before designing a pilot. Ask it to explain that reasoning. If the explanation changes the committee’s understanding of the assignment, revisit the brief openly.

For agency work, the existing Agency Proposal Scope Comparator can help retain wording and unresolved questions. This article’s committee memo serves a different purpose: explaining why one delivery arrangement fits the buyer’s needs and capacity.

For firms writing proposals, the lesson is equally practical. Explain what the client will be able to decide, what you will deliver to support it and what you need the client to do. Make your approach easier to evaluate on its own merits.

My professional-services consulting connects positioning, proposals and the operating experience behind them. If a promising conversation keeps becoming a confused comparison, bring the scope question. It is often the most useful place to begin.