GRAIL
Our work What we do Why GRAIL Essays Industry Briefings Book a call

Contents

14 min read
What's Changing in How Your Projects Compound, GRAIL industry briefing cover
An Industry Briefing from GRAIL

What's Changing in How Your Projects Compound

Your engagement margin is drifting. The specialist who ran your first offshore wind assessments just took a developer's call. Your delivery cycle has not shortened despite the pipeline doubling. Three problems that are one. A briefing for operations leaders at energy and environmental advisory firms.

Energy & Environment · COO
Prepared by Johan Grönstedt  ·  GRAIL
For European mid-market energy
and environmental advisory leaders
Date April 2026
Reading time14 min
Read the briefing
Executive Summary

You have seen this on your project floor

Why is our margin drifting on project types we have delivered before?What happens to our project capability when a frontier specialist takes a developer's call?Why does a preliminary assessment for a project type we have done before take ten days?

Every Head of Delivery at a mid-sized energy advisory in Europe has had the same Tuesday morning. Project one: an offshore wind EIA for a Nordic developer. The permitting specialist who knows the Swedish Marine Areas Planning Act spent two days reconstructing precedent from the firm's last four comparable projects. The client is asking why the view is taking longer than expected. Project two: a hydrogen pathway feasibility study. The client wants a first read by Thursday. The team needs ten days because rebuilding the regulatory baseline takes three days, even though the firm completed a comparable study eight months ago. Project three: a senior environmental specialist mentions she had a call from a developer in London. You know what the call was about. The firm's three-year head start on BESS permitting expertise is about to walk out with her.

Something changed. The energy transition generates new specialist knowledge through every frontier project. Each offshore wind assessment, each hydrogen pathway study, each BESS permitting engagement generates regulatory precedent worth more next year than today. Most of it lives in the heads of specialists being recruited at 40% salary premiums by the developers they advise.

This is a sector problem and a delivery-engine problem, happening at the same time. Most advisory operations leaders are treating them as two. The ones who see them as one will own the next decade of European energy advisory.

This briefing covers what is happening in your sector, what it means inside your delivery engine, and the three questions your operations team should answer before the next board cycle.

Lens One  ·  Your Industry

Energy advisory just entered the decade where knowledge compounds or evaporates

The energy transition is the largest infrastructure build of this generation. Nordic offshore wind alone is on track to grow from under 4 GW today to 65 GW by 2050. Green hydrogen capacity is targeting 4-6 GW by 2030 across Nordic markets. BESS grid integration, CCUS advisory, and marine spatial planning are disciplines that barely existed as professional specialisations five years ago. For an energy and environmental advisory firm, that is not a market forecast. It is a decade of compounding opportunity, if the firm can move fast enough to capture it.

The catch is structural. Every major project in a new technology area generates regulatory and technical precedent that will govern commercial opportunity for the next twenty years. The firm that was present at Norway's first three offshore wind EIAs knows how the Norwegian Environment Agency forms its view on cumulative impact, what community engagement approaches have succeeded, and which technical standards the regulator reads as dispositive. That knowledge did not come from a training course or a published guideline. It came from doing the work. And in most firms, it exists in the head of the specialist who did it.

Each new project type your firm runs generates precedent worth more next year than today. In most advisory firms, that precedent is biographical. It leaves with the specialist.

AI is accelerating the pattern on both sides. The analysis and research layer that used to absorb most of the mid-tier project hours can now be done in a fraction of the time by platforms that developers are already subscribing to. Under hourly billing, compressed delivery at the same rate card means lower revenue on comparable engagements. Client procurement is showing up at tenders with benchmarks that already account for AI-efficient delivery. Your rate card is under pressure from below, at the same time as your most valuable knowledge is under pressure from above. The firms that are compounding project knowledge systematically are positioned to hold their rate on complex advisory while opening project types that were not economically viable before. The firms that are not are competing on rate.

Lens Two  ·  Your Function

Your delivery engine, your bench, and your client continuity are feeling it every week

Your delivery engine. Project managers are spending the first two to three days of every engagement rebuilding the regulatory baseline for a project type the firm has delivered before. The methodology from the last comparable study. The regulator contacts who shaped the previous outcome. None of it is accessible without the specialist who ran it. The firm pays for the same knowledge twice: once when it learned it, and again when it reconstructs it.

Your technical quality. The quality floor holds because your senior specialists are in every critical review. But those same seniors are spending 40% of project time on analysis and documentation that platforms your clients already own could deliver in hours. Their judgment is the scarcest resource in the firm. It is spending half its week on work that does not need it.

Your specialist bench. Mid-level specialists bill at rates that assumed more of their week would be analytical. As AI compresses that layer, the rate card justification erodes project by project. Your best mid-level people know this. The ones who have thought it through are either building toward specialist status faster, or they are taking calls from developers.

Your senior experts. The five to fifteen specialists who carry your frontier knowledge are building regulatory intelligence and assessment methodology on every project that your next client needs. None of it is encoded in a form the next specialist can access. When one of them takes a developer's call, years of compounding knowledge moves with them.

Your client continuity. Developer clients buy a firm that knows their project history, their regulator's priorities, and the precedent from their last permitting round. That knowledge lives in the specialist who served the relationship. When that specialist joins the developer's in-house team, the next comparable project often follows them.

Delivery. Knowledge. Continuity.

The firms pulling ahead are building one piece of infrastructure

Your sector is generating knowledge faster than any advisory sector in a generation. Your delivery engine is running slower than it should because that knowledge is biographical rather than institutional. Your margin is drifting because clients can now measure what AI-efficient delivery should cost. These look like three separate problems. They are not.

You do not have three problems. You have one. The knowledge your specialists build through frontier project work has never been separated from the people who earned it. Every margin problem, every slow start on a comparable project, every departure that cost you a client relationship is a symptom of that single unsolved thing. The firm that fixes it does not just protect what it has. It builds something a new entrant cannot replicate through hiring.

Think about what the first firm to encode its offshore wind EIA precedent systematically actually has. A competitor entering the same market two years later can hire a specialist. They cannot buy four years of accumulated regulatory interaction intelligence, encoded from every permitting correspondence and authority response the early firm received on its first ten projects. That intelligence compounds. It makes the eleventh project faster than the tenth, and the fifteenth faster than the eleventh. The late entrant is always playing catch-up on a gap that widens each year.

You can tell which camp a firm is in from one question. When your team kicks off the next comparable project in a technology area you have worked in before, do they start from everything the firm has learned, or do they start from scratch? Most advisory firms cannot answer honestly. The ones that can have already made the shift.

You have eighteen to twenty-four months before this gap becomes structural. The encoding work takes time, and the first-mover advantage in each technology area establishes itself project by project. The question is whether your firm is building the infrastructure your delivery engine will run on for the next decade, or waiting for someone else to build it first.

Two Paths

What most firms are doing. What the winners are doing instead.

Every energy advisory COO has had the AI conversation. Most are making the same four decisions. A smaller group is making different ones.

The default pathRebuild the baseline on every comparable projectLet departures reset first-mover knowledgeDeploy AI tools on top of existing project structureTreat developer relationships as specialist relationshipsThe winners' pathEncode precedent as a side-effect of every projectExtract specialist reasoning from the artefacts of paid workRebuild project structure around encoded precedentBuild client intelligence on firm infrastructure
The default path The winners' path
Rebuild the baseline on every comparable projectMethodology and precedent reconstructed at each kick-off. The firm pays for the same knowledge twice while clients benchmark AI-efficient delivery rates. Encode precedent as a side-effect of every projectEach engagement feeds the firm's intelligence layer. The next comparable project starts where the last one finished.
Let departures reset first-mover knowledgeSpecialist takes a developer's call. Three years of frontier regulatory intelligence walks out. The next client starts from scratch. Extract specialist reasoning from the artefacts of paid workPermitting correspondence, assessment notes, authority responses encode the reasoning as work happens. Departure impact drops.
Deploy AI tools on top of existing project structureIndividual productivity rises. Delivery cycle does not move. Knowledge is still biographical. The architecture is still 2021. Rebuild project structure around encoded precedentJunior specialists pair with the firm's knowledge corpus from day one. Five-year curve compresses to eighteen months.
Treat developer relationships as specialist relationshipsContinuity depends on the specialist staying. When they leave, the relationship often follows them. Build client intelligence on firm infrastructureProject history and regulator notes encode on firm architecture. Rotation and departure become managed events.

Same projects. Same specialists. Same eighteen months. Opposite trajectories. The difference is the architecture, not the ambition.

Three Questions

Project Margin. Knowledge Continuity. Delivery Speed.

Three questions every energy advisory COO is tracked against. None of them used to be the same question. They are now.

01 · Project Margin02 · Knowledge Continuity03 · Delivery Speed
01  ·  Project Margin

Why is our margin drifting on project types we have delivered before?

Your rate card has not changed. But clients are arriving at tenders with benchmarks that already account for what AI-efficient delivery should cost on a standard environmental assessment or a regulatory filing. The analysis layer that justified mid-tier billing is compressing. The firms that hold margin on comparable work are the ones where each project costs less to deliver because the last one encoded something the next one can use. The firms rebuilding from scratch are competing on rate.

02  ·  Knowledge Continuity

What happens to our project capability when a frontier specialist takes a developer's call?

One of your BESS permitting specialists, or your offshore wind EIA lead, or your hydrogen pathway expert spent the last three years building regulatory intelligence that will govern your clients' projects for the next decade. It is in their head. When they join a developer's in-house team, it goes with them. The clients who know that specialist now have a choice between the developer's in-house capability and whatever your firm can reconstruct. You already know which conversations are coming.

03  ·  Delivery Speed

Why does a preliminary assessment for a project type we have done before take ten days?

The answer is almost always the same. The team rebuilds the regulatory baseline, the technical methodology, and the community context from the last comparable project because none of it is accessible without the specialist who ran it. The firms that close comparable assessments in four to five days are the ones where each project made the next one faster. Same specialists. Forty percent of the elapsed time recovered. A capacity expansion in a market constrained by specialist availability, not a productivity story.

Four Moves

What the firms winning this play are actually doing

Four moves any energy advisory operations team can start this quarter. One per part of the delivery engine.

1234
1

Delivery: decompose each project type to task level, price the tasks that still command specialist rates

List every task bundle inside each engagement your firm sells. Mark each: agent-assisted, composite, or specialist-only. What remains is a different project at a different cost base and a defensible price point. The operations leader with the task-level map owns the pricing conversation. The ones running project-type P&Ls are running the 2021 playbook.

2

Technical quality: extract specialist reasoning from the artefacts of daily work, not from documentation sprints

Documentation projects have failed in every advisory firm for thirty years. Extract from what specialists already produce: permitting correspondence, assessment notes, authority responses. The reasoning encodes as a side-effect of paid work. Specialists are not asked to explain themselves. Their role shifts toward escalation and novel judgment. The knowledge stops walking out.

3

Bench: redesign junior onboarding around encoded precedent from day one, not from rebuilding baselines

New specialists pair with the firm's precedent corpus from their first engagement. They handle review and exception work alongside seniors from the start. The five-year curve compresses to eighteen months. The junior who joins in 2026 has more regulatory judgment by 2028 than the 2022 junior had by 2027.

4

Client continuity: build developer relationships on firm infrastructure, not on specialist biography

Treat every major developer client relationship as a small intelligence asset. Project history. Regulator relationship notes. The authority's unwritten preferences. The issues that nearly derailed the last permitting round. When the specialist who built that relationship rotates or takes a developer's call, the next specialist inherits the asset. The relationship holds on the firm's architecture.

GRAIL  ·  How We Think

The only firm that builds knowledge infrastructure alongside the advisory

Four places to go for help. None can do what we do, and each for a specific reason.

The big consulting firms' operations practices will sell a diagnostic that produces a knowledge strategy document. They cannot put working precedent infrastructure into a project team in three months. Their revenue model depends on the advisory hours the infrastructure would replace.

The knowledge-management and document platforms treat your senior specialist's regulatory reasoning as a document to tag. Every energy advisory firm has watched that purchase deliver a filing system the project team does not use. The reasoning is not in the document.

The domain software vendors offering AI modules are the layer compressing your analysis billing in the first place. Adding their AI module accelerates the rate-card pressure without solving the precedent gap that determines whether your margin holds.

Your internal IT function builds document search tools and intranet knowledge bases. IT optimises for standardisation. It does not sit close enough to how a permitting specialist reasons to encode the judgment, only the output.

The market offers four things you have already seen fail once. GRAIL is the fifth option.
What You GetWhy It Matters
What You Get
  • Advisory grounded in delivery-floor reality
  • Working precedent infrastructure your teams use the same week
  • Custom tools built on your projects and regulatory markets
  • A knowledge layer your specialists feed through daily work
  • No vendor dependency at any phase
Why It Matters
  • Founded by operators who ran professional-services delivery
  • Business first, technology second
  • Three weeks from first meeting to working infrastructure
  • Your teams keep the infrastructure, you own the IP
  • Every next step earned by what shipped
GRAIL  ·  How We Work

Three sessions with your delivery leadership. Working infrastructure from week one.

We start with your delivery leadership team because the change cannot outrun the team's understanding of what is possible. Three workshops. Each delivers standalone value. Each earns the right to the next.

How to thinkYour delivery infrastructureReady to run
Workshop 01

How to think

Walk through what is happening in your sector and inside your delivery engine. Build the first piece of infrastructure in the room: a project-specific precedent tool for one of your real technology areas, built from the project archive you already have. Your operations team leaves with a shared view of what to do next and the first piece of working infrastructure in their hands.

Workshop 02

Your delivery infrastructure

A half-day build. Your Head of Delivery, Head of Practice, Head of Quality, and Head of Bench each leave with five to ten pieces of working infrastructure tuned to their function. Precedent capture tools. Regulatory monitoring for your active technology areas. Client intelligence structures. Assessment methodology libraries. Infrastructure your project teams use the same week, not plans for infrastructure.

Workshop 03

Ready to run

Refined infrastructure from real use. The rollout plan for your wider delivery organisation. The precedent-capture plan for your frontier technology specialists. The onboarding pathway for your junior specialists. And the CEO and CFO conversation with numbers they can check: revenue per specialist, delivery cycle by project type, and the departure-impact estimate before the next recruitment call lands.

Three weeks. No IT project. No board approval needed to start. The infrastructure your delivery engine is already running on when we finish.

Five Questions

For your next operations review

The questions where your operations team cannot agree on an answer are the ones worth an hour on the agenda. Ask these honestly.

When your team kicks off the next comparable project in a technology area you have worked in before, how many days of the first week go into rebuilding regulatory context and methodology the firm already earned on a previous engagement?

Name the three specialists whose departure would cost the firm the most in project capability. Is the knowledge they carry in a form anyone else in the firm can access today?

Of the last five times a developer client relationship moved when a specialist departed, how many times did the relationship follow the specialist rather than stay with the firm?

What is your firm's first-mover advantage in one frontier technology area worth if a competitor can hire two of your specialists and replicate it in eighteen months? What would it be worth if it were encoded in infrastructure they could not take with them?

Is your junior specialist onboarding building judgment faster than your retention risk is emptying the bench? At the current rate, what does your senior specialist profile look like in 2030?

The knowledge your specialists build through frontier project work is the scarcest asset in your sector. It is also the only one that compounds. Build the infrastructure to hold it.

Industry Briefings

Continue reading

GRAIL  ·  www.grail.works  ·  Johan Grönstedt  ·  April 2026
Talk to GRAIL about your management team
Sources and limitations

This briefing draws on GRAIL's engagement experience with leadership teams and on public company disclosures. Figures are illustrative unless a source is named beside them. A sourced edition is in preparation.