Sustainability Consulting at Scale: Running 10+ Client Carbon Inventories Without Hiring More Staff

The bottleneck in Australian sustainability consulting in 2026 is not expertise. It is the spreadsheet workflow per client. Here is what changes when the data plumbing is systemised.

Denis Patel June 23, 2026 12 min read
Sustainability ConsultingISCAAASB S2NGERPractice Management
Sustainability Consulting at Scale: Running 10+ Client Carbon Inventories Without Hiring More Staff

The growth ceiling for an Australian sustainability consulting practice in 2026 looks like this: a partner has more inbound demand than she can convert. Not because the work has dried up, the opposite. She has ten or twelve active retainer clients across infrastructure, property and food manufacturing, and a pipeline she cannot serve because every new engagement requires another senior consultant.

The maths is brutal once you write it down. One senior consultant, working in spreadsheets, can carry three to five client inventories before the wheels come off. Five if the clients are small, three if they are NGER reporters with complex Scope 3. Beyond that, version control breaks, factor updates get missed, and the consultant spends more time chasing utility bills than doing the work clients actually pay for.

This is not a problem you fix by hiring more consultants. It is a problem you fix by changing what consultants spend their hours on.

The hiring ceiling is real, and it is mathematical

Let's be specific about where the time goes. A typical mid-market client engagement covering Scope 1, 2 and material Scope 3 categories involves roughly:

  • 200 to 400 utility bills, fuel dockets and waste invoices per quarter
  • 30 to 80 supplier emails for primary Scope 3 data
  • Two to four reconciliation cycles per reporting period
  • A baseline restatement question every time someone fixes a mistake
  • Report drafting against whichever framework the client is reporting under

In a spreadsheet workflow, the senior consultant ends up doing data entry. Or worse, a junior does it and the senior re-checks. Either way, the billable hour is being spent on activity that the client does not value and would not pay for if they understood it.

We have written before about the real cost of carbon accounting consultants versus software, and the numbers favour the consultant on strategy and unfavour them on data wrangling. The honest answer is that consultants are not paid to type numbers from PDFs into Excel. They are paid to interpret, to advise on materiality, to defend assumptions to auditors. The data wrangling is the part the practice should automate, not the part it should bill for.

The honest framing: when a client is paying senior advisory rates, they should be buying judgment, not typing. A practitioner with twenty years of climate risk experience copying meter reads into a workbook is a margin problem for the firm and a value problem for the client.

Why one senior covers three to five clients on spreadsheets

The ceiling is not about ability. It is about cognitive load and version control. A spreadsheet-based inventory has no single source of truth, no permission model, no audit trail. Every client folder is its own world. Every emission factor update means hunting through linked formulas. Every restatement means going back through prior periods manually.

Three clients on spreadsheets is uncomfortable. Five is unsustainable. Eight breaks something every quarter.

What changes the maths is not faster typing. It is removing the typing entirely from the bottleneck path, then giving the consultant a workspace structure that holds ten or fifteen clients without bleeding into each other.

The multi-tenant workspace pattern

This is the architectural shift that lets a consulting practice scale. One firm, one Carbonly account, separate locked workspaces per client. Each workspace has its own users, its own data, its own reports, its own period locks. Nothing crosses the wall.

A consulting principal sits at the top with admin access to every workspace. A senior consultant might be assigned to four clients and only sees those four. A junior analyst might be a Contributor on two workspaces, with no access to the rest of the firm's book of business. The client themselves can be invited in as a Viewer or Auditor to see their own data without being able to touch anyone else's.

This is what the six-role permission structure is actually for in a consulting context. Owner, Admin, Manager, Contributor, Auditor, Viewer. The roles map cleanly to how a practice already works. Partners and principals are Owners. Senior consultants are Admins on their accounts. Juniors are Contributors. Clients are Viewers or Auditors. The auditor at the end of the year gets read-only access for assurance without seeing other clients' data.

This matters more than it sounds. The consulting firm's most fragile asset is client confidentiality. If a senior leaves and takes a laptop full of cross-client spreadsheets, that is a problem. If a senior leaves and their workspace access is revoked in two minutes, that is not a problem.

What you put into each workspace once, and never touch again

The setup per client looks the same regardless of size. Each project gets its own ingestion plumbing.

Project-specific email ingestion means the client's utility provider can be configured to forward bills directly to an inbox attached to that workspace. No human in the middle. The consultant configures it once, hands the email address to the client's accounts payable team, and bills start arriving as records.

OneDrive or SharePoint folder sync per project does the same thing for documents that live in the client's cloud storage. The consultant adds a watched folder. New documents land, get extracted, get reconciled against existing meter histories. The senior consultant looks at exceptions, not entries.

The extraction itself works across PDFs, CSVs, Excel files, Word docs, PowerPoint exports, RTF, and image scans. Eight formats. Critical because suppliers send whatever they send. Hotel folios are PDFs. Fleet card statements are CSVs. Waste contractor reports are scanned images of paper logs.

The differentiator most consultants care about, once they have used it, is quantity-based extraction. The AI reads the actual physical activity off the invoice. Litres of diesel. Kilowatt hours. Tonnes of waste to landfill. Not the dollar amount with a spend-based factor applied. We have written about why quantity beats spend-based and for a consultant defending numbers to ASSA 5010 assurance, this is not a marginal preference. It is the difference between a defensible inventory and a margin of error wide enough to embarrass the firm.

What the consultant actually does once the plumbing runs

The work shifts up the value chain. The senior consultant stops being a data entry clerk and starts being what the firm bills them as.

They review extraction exceptions, which are flagged by the system rather than discovered by accident. They sit with the client on materiality questions, scope boundaries, and operational control determinations. They run scenario analysis for the climate transition plan the client owes under AASB S2 paragraph 14(a)(iv). They prepare the audit trail evidence pack for the assurance provider.

In practical terms, a consultant who previously carried four clients can carry ten to twelve. Not because they have become faster typists. Because the typing has been removed from their job description.

Plugging ChatGPT or Claude into a client's live carbon data

Here is the workflow change that has surprised consultants the most in the last six months. You can now connect ChatGPT or Claude directly to a client's live carbon data inside Carbonly, ask questions in plain English, and get answers without opening a single file.

A consultant on a call with a CFO who asks "what's our Scope 3 split this quarter?" used to need to open the workbook, filter the data, build a quick pivot, and come back in five minutes. Now they ask the AI assistant on their phone, get the breakdown read back to them, and answer in the next breath.

This works on the firm side too. A principal preparing for a board meeting can ask "what changed in the materiality threshold for emissions errors at this client between Q2 and Q3?" and get the answer drawn from the actual ledger, not from memory. The AI assistant pulls live numbers from the workspace. It is not a chatbot trained on documents. It is a query interface to current data.

The internal version of this, Carbonly Co-Pilot, sits inside the platform itself and handles questions, anomaly explanations, and report drafting in the same way. Same principle. Different surface.

The reason this matters for a consultancy is meeting density. A senior consultant in any given week has five client calls, two internal reviews, a board presentation and a workshop. Every single one of those used to require pre-work in Excel. Most of them now do not.

One ledger, many frameworks

The other architectural truth that becomes obvious once you have run a few clients through a proper system is that the frameworks overlap more than the consulting world admits.

ISCA infrastructure rating submissions under the IS Design v2.1, IS As Built v2.1 or IS Operations v2.0 schemes draw from the same activity data as the client's NGER submission. The NGER submission draws from the same activity data as the AASB S2 climate disclosure. The Climate Active certification draws from the same activity data again. The GHG Protocol inventory underneath all of them is one inventory.

What differs is the curation. ISCA wants embodied carbon in materials. NGER wants Scope 1 and 2 against thresholds. AASB S2 wants Scope 1, 2 and material Scope 3 with scenario analysis. Climate Active wants the residual emissions claim with offset evidence.

The consulting work is curation and interpretation, not data wrangling. If the underlying ledger is right, multiple framework reports come out of the same numbers. We covered this pattern in multi-framework reporting for Australia. The pattern is the same whether you are running one client or fifteen.

Where this gets interesting for infrastructure consultancies specifically is mandates like Major Road Projects Victoria requiring ISCA ratings on tier-one projects, or Transport for NSW requiring carbon estimates against the CERT methodology. Cross River Rail in Brisbane, Snowy 2.0, Inland Rail and Western Sydney Airport all carry sustainability targets that need the same activity data the design firm is already gathering. Carbonly does not push directly into the ISCA submission tool or the TfNSW CERT. What it does is give the consultant a clean, auditable activity dataset to draw from when populating those tools. The submission still needs the practitioner. The ledger underneath does not need to be rebuilt for each one.

Hourly billing versus fixed-fee retainer

This is where the commercial model starts to bend.

A consulting practice charging $250 to $400 per hour for senior time, on a workflow that includes data entry, has a margin problem the moment they try to scale. Hours billed match hours worked. The cap is human bandwidth.

A consulting practice charging a fixed monthly retainer per client, on a workflow where data entry is systemised, has a different shape. The retainer covers ongoing inventory maintenance, quarterly reviews, annual reporting and one or two strategic projects per year. The fixed fee is justified by the strategic value, not by the hours of data entry that used to fill the engagement.

Consulting firms we talk to are already moving this direction. Fixed-fee retainer at $4,000 to $12,000 per month per client, depending on size and complexity, with consultants able to carry ten or more retainers. The per-client revenue is lower than the old hourly model used to generate at peak. The aggregate revenue across a properly tooled practice is significantly higher.

We are still working out what the right pricing model is at the platform level for this. Carbonly is per-project, not per-seat. The practice pays a workspace fee plus a tier per client. Adding consultants to the practice does not cost more. Adding clients does. This aligns to how the consultancy bills its own clients, which is the only reason the maths works.

The honest limitations

A few things this does not solve, which we should not pretend it does.

Scope 3 is still messy. Supplier engagement still takes longer than anyone wants. Spend-based estimates are still the starting point for most categories until primary data arrives. We cover this in Scope 3 Category 1 supplier engagement and the pattern has not fundamentally changed because the supplier data quality has not fundamentally changed.

Scenario analysis for AASB S2 disclosures still requires human judgement. Materiality assessments still require the consultant to argue with the client about what is in and what is out. Audit committee briefings still need the consultant in the room. None of this is going away.

What goes away is the typing. What goes away is the version control nightmare. What goes away is the consultant spending Saturday morning rebuilding a workbook because someone broke a formula.

The action that actually moves the needle

If you are running a practice with three to five active clients per senior, and you are sitting on a pipeline you cannot convert without hiring, the next step is not to hire. The next step is to take your most complex client, set them up in their own workspace, point project email ingestion and a SharePoint folder at the workspace, and run a quarter through it.

Then look at how many hours the senior spent on that client versus the prior quarter. That number is your hiring plan answer.

Related reading

External references: Infrastructure Sustainability Council, AASB Sustainability Standards, AUASB ASSA 5010, IFRS Foundation ISSB, Transport for NSW Sustainability, Major Road Projects Victoria.

Take the Next Step

Ready to automate your carbon reporting? Carbonly.ai is working with a select group of Australian organisations.

Join the Waitlist