How to Compare CSRD Consulting Proposals: Why One Quote Is €40k and Another €180k

You sent the same brief to four consultants. The quotes came back at €40,000, €95,000, €180,000 and one that says "from €30,000, subject to scoping." Every proposal describes deep ESRS expertise and a proven methodology. Every one includes a timeline that hits your filing date.

This is the point where most companies do one of two things, both wrong. They pick the middle number because it feels safe, or they take the cheapest and treat the difference as savings. Neither is a comparison, because the proposals are not describing the same piece of work — they're describing different amounts of work, done by different people, with different things quietly left out.

Here is how to make them comparable. This guide picks up after proposals land; if you're still writing the brief, start with the CSRD consultant RFP template, and if you're trying to work out whether the numbers are reasonable at all, the CSRD consultant cost guide has the market ranges.

Why the Same Brief Returns a 4x Spread

Four things drive almost all of the variance, and only one of them is margin.

Different scope assumptions. Your brief said "support our first CSRD report." One bidder read that as a full implementation through filing. Another read it as advisory support to your internal team. Both are defensible readings and they differ by a factor of three in effort.

Different effort estimates. Two consultants can agree on scope and disagree by 50% on how many days a double materiality assessment takes, usually because one has done it before and knows where it stalls.

Different seniority mixes. €95,000 delivered by one senior practitioner is roughly 60 days of experienced attention. The same €95,000 from a large firm might be 15 partner days, 40 manager days and 120 analyst days. Not better or worse — different, and you should know which you're buying.

Different exclusions. The cheapest bid is often cheapest because it excludes tagging, assurance support, and the second legal entity. This is the one that hurts, because you don't discover it until month seven.

Margin does vary, of course. But if you assume the €180,000 bid is simply the €40,000 bid with more profit on top, you'll buy the wrong thing.

Step 1: Normalise Every Bid to Days and Seniority

Before you compare anything else, convert each proposal into effort. Ask every bidder for a breakdown by phase showing days by seniority and the day rate for each level. Any consultant who won't provide this has told you something.

Then build one line per bidder:

	Bid A	Bid B	Bid C
Total price	€40,000	€95,000	€180,000
Partner / director days	2	8	22
Senior / manager days	12	45	60
Analyst days	20	30	95
Total days	34	83	177
Blended rate	€1,176	€1,145	€1,017

The moment you do this, the picture inverts. The blended rates are within 15% of each other — this was never a pricing difference. Bid A is a third of the work of Bid B, and Bid C is twice it. The cheapest bid has the highest blended rate, which is the opposite of what everyone assumed in the room.

Now the real questions become answerable. Is 34 days enough for what you need? For a first-time mid-market reporter, almost certainly not for a full implementation — that's a scoping and materiality engagement, and the drafting is on you. Is 177 days too much? Possibly, but not if your group has eleven legal entities and a complex value chain.

Compare effort against your own honest estimate of the work. If you don't have one, that's what a paid scoping engagement is for.

Step 2: Find the Scope Lines That Are Missing

Nine things are routinely left out of CSRD proposals. Take each bid and mark every one as in, out, or unstated. "Unstated" counts as out — it will be out when you argue about it later.

1. XBRL / digital tagging. Frequently excluded, frequently expensive, and a hard requirement.
2. Assurance support. Auditor queries, evidence packs, walkthroughs. This runs for months after you thought the project ended.
3. Value chain and Scope 3 data collection. Facilitating supplier engagement is a large, separate effort from calculating with data you already have.
4. Additional entities. A price built for the parent company that quietly assumes subsidiaries are out of scope.
5. Disclosure drafting versus review. "Support with disclosures" can mean writing forty of them or commenting on your drafts. Enormous difference.
6. Policy and target development. If your transition plan doesn't exist yet, someone has to build it, and it isn't a reporting task.
7. Translations. If you file in a local language and work in English, this is a real line item.
8. Restatements and prior-year comparatives.
9. Software, licences and third-party data. Emissions factor databases and platform subscriptions are often passed through at cost — or bundled at a markup.

When you fill this in, cheap bids usually stop looking cheap. A €40,000 proposal that excludes tagging, assurance support and drafting is not competing with a €95,000 proposal that includes all three; it's a different product.

Step 3: Work Out Who Actually Does the Work

The seniority table tells you the mix. Two follow-up questions tell you what it means in practice.

"Who is on this engagement, named, and what share of their time do we get?" A pyramid is not inherently bad — leverage is how large firms deliver at scale, and analysts do a lot of necessary work well. What's bad is a pyramid you weren't told about, where the senior practitioner who impressed you in the pitch appears for two days a month.

"What happens to the price if we insist on the named team?" The answer is revealing. Firms that intended to staff it as pitched will confirm without much fuss. Firms that intended to substitute will find the question difficult.

For independent consultants the risk is inverted: you'll get the person you met, and the question becomes whether one person has the bandwidth and what happens if they're ill during your crunch. The Big 4 versus independent comparison goes into this trade-off in more depth.

Step 4: Separate "Support" From Deliverables

Read each proposal with a marker and highlight every instance of "support," "assist," "help with," "guidance on" and "alongside your team." Then ask, for each one, what you would receive on the day it's finished.

If you can't name an artefact — a document, a dataset, a populated register, a completed workshop with outputs, a trained team — it isn't a deliverable and it can't be accepted, rejected, or invoiced against. It's an intention.

Rewrite each proposal's scope as a list of artefacts with acceptance criteria. Bids that were hard to compare in prose become easy to compare as lists, and one or two of them will visibly shrink in the process.

Specifically, insist on knowing which party holds the pen. "Support with the double materiality assessment" is compatible with the consultant running the whole thing and with the consultant reviewing your work. Those differ by twenty days.

Step 5: Read the Terms That Decide the Real Price

The headline number is an estimate of what you'll pay. These clauses determine it.

Change control. What triggers a change order, who approves it, at what rate, and is written approval required before work begins? Without this, scope creep is repriced at whatever rate is convenient. This single clause is the most common reason a €60,000 engagement invoices at €110,000.

Fixed price versus time and materials. A fixed price transfers risk to the consultant, who prices that risk in — expect to pay a premium for certainty. Time and materials is cheaper if the scope holds and unbounded if it doesn't. If you go T&M, negotiate a cap, or at minimum a notification threshold at 80% of the estimate.

Assumptions. Every fixed price rests on assumptions about your behaviour: data provided by a date, a number of review rounds, availability of your people, decisions made within a window. When you miss them — and you will miss some — the price changes. Read the assumptions list as carefully as the price.

Payment milestones. Tie payments to accepted deliverables, not to elapsed months. It's the only leverage you retain once the engagement starts.

Ownership and reuse. You should own the deliverables, the underlying data and the populated templates, with the right to reuse them next year without the consultant. Watch for methodologies delivered inside proprietary tooling you lose access to at the end.

Exit and continuity. Notice period, what you receive on termination, and what happens if the lead consultant leaves.

Expenses. Capped or uncapped, and whether travel time is billable. On a year-long engagement with on-site workshops this is not a rounding error.

Red Flags in the Document Itself

Some signals have nothing to do with the number. Read each proposal as a work sample — it is the only example of their output you'll see before you sign.

• No assumptions section. Either they haven't thought about what could go wrong, or they have and would rather you found out later.
• No exclusions list. Every honest fixed price has one.
• Case studies that don't match your situation. A listed manufacturer's case study in a proposal to a mid-sized services firm means the template was reused without much thought.
• Your company name in the wrong font, or a competitor's name left in. Rare, but it happens, and it tells you exactly how much attention this proposal received.
• A timeline that doesn't mention your dependencies. Any credible CSRD plan is gated on your data and your people. A plan with no dependency on you is a plan that hasn't been thought through.
• Certainty about ambiguous requirements. Confidence is not the same as expertise, and parts of the ESRS are genuinely unsettled.
• No mention of the audit trail. If the proposal never discusses documentation and evidence, it was written for a reporting exercise rather than an assured one.

None of these is individually disqualifying. Two or three together usually mean the proposal was assembled rather than written, which is a reasonable proxy for how the engagement will be run.

The Independence Constraint

One rule cuts across all of this: the firm advising you on your CSRD implementation generally cannot also provide your assurance. Independence requirements apply, and they apply to the firm rather than the individual.

This has a practical consequence for comparison. If one bidder is your statutory auditor's advisory arm, engaging them may force you to appoint a different assurance provider — a cost and a disruption that belongs in the comparison, not in a surprise conversation with your audit committee three months later. Ask every bidder directly what their engagement would mean for your assurance arrangements, and treat a hesitant answer as a finding.

The Three Quotes, Decoded

Back to the opening example. With the analysis applied, here is what those numbers usually turn out to be.

€40,000 — Bid A. 34 days. Scoping, materiality assessment, a gap analysis and a roadmap. Drafting, tagging and assurance support are excluded or unstated. This is a genuinely good purchase if you have an internal owner who will write the report. It's a disaster if you assumed it was the whole thing, because you'll be buying the remaining 60% in a hurry, from a position of no leverage, in month seven.

€95,000 — Bid B. 83 days. Full implementation through draft disclosures, tagging via a named partner, a defined allocation of assurance support days. Named team, clear exclusions list, change control at a defined rate. This is what a complete mid-market first-year engagement usually costs.

€180,000 — Bid C. 177 days, heavy analyst leverage, broad scope including value chain data collection and policy development. Genuinely appropriate for a complex multi-entity group. For a single-entity mid-market company it's substantially more effort than the job needs — and note that a large share of those days are junior, which is why the blended rate is the lowest of the three.

"From €30,000, subject to scoping." Not a proposal. Either request a fixed scope and price, or treat it as a bid for a paid scoping exercise only.

Your Comparison Sheet

Put every bid on one page with these rows, then have each reviewer score independently before anyone discusses:

• Total price, and price per day of senior-level effort
• Total days, split by seniority
• Which of the nine scope lines are in, out, or unstated
• Number of named deliverables with acceptance criteria
• Named team, and the share of the work done at senior level
• Change control mechanism and rate
• Assumptions that depend on your team
• What you own at the end
• Impact on your assurance arrangements

Score capability separately from price. Combining them in one number is how companies talk themselves into the cheapest bid — use the 25 screening questions for the capability half, and this sheet for the commercial half. Then decide with both in front of you.

One last discipline: when a proposal is genuinely unclear, ask rather than assume, and get the answer in writing into the contract. Ambiguity resolved in your favour during the sales process has a way of resolving the other way during delivery.

Compare Consultants, Not Just Quotes

A comparison is only as good as the shortlist that produced it. Three bids from the first firms you found is a narrow market view, and it's the most common reason companies overpay.

Browse the CSRD Experts directory to find consultants and firms by country, expertise and industry, and put four or five proposals through this analysis rather than two.

If you're still earlier in the process, see how to hire a CSRD consultant for the full selection sequence, or consultant versus in-house hire if you haven't yet settled whether to buy this work at all.