From First Concept Through To Implementation
We take projects from initial concept through to working implementation, holding responsibility for quality and efficiency at every stage in between. Feasibility, structure, partners and delivery are treated as one continuous piece of work rather than a series of handovers.
Every handover in a project is a place where accountability can be put down and not picked up again. The developer who wrote the feasibility study is rarely the one explaining, four years later, why the assumption behind it did not hold. We stay on it.
Six Phases, One Team Across All Of Them
The same people carry a project from the first viability question to the day it is running. Nothing is handed to a delivery team that was not in the room when the commitments were made, and no phase begins before the one before it has closed against its deliverables. The sequence below is deliberately unglamorous: most of what determines whether a project succeeds is decided in the first two phases, long before anything is visible on site.
- 01 Concept
- 02 Feasibility
- 03 Structuring
- 04 Financing
- 05 Delivery
- 06 Operation
Responsibility That Does Not Transfer Mid-Project
Six disciplines held by the same team, from the first viability question through to a running asset.
Concept & Feasibility
Testing the idea against cost, regulation and market reality before it becomes a commitment.
Structuring & Financing
Establishing the commercial and financial structures a project needs in order to proceed.
Delivery Management
Holding scope, budget and programme together through construction and commissioning.
Handover & Operation
Transferring a completed project into steady operation with the documentation and support that requires.
Stakeholder & Consent
Managing the authorities, landowners and communities whose agreement the programme depends on.
Procurement & Contracts
Selecting contractors and negotiating terms that place risk where it can actually be carried.
Deliverables At Every Gate
Each phase closes against a defined set of documents. Nothing progresses on assurances alone.
-
Concept note with the commercial logic stated in one page
-
Feasibility study to lender and authority standard
-
Financial model, maintained and version-controlled throughout
-
Risk register with named owners and live mitigation status
-
Permitting schedule mapped to the responsible authority
-
Procurement strategy and an evaluated contractor shortlist
-
Construction reporting on a fixed monthly cycle
-
Independent cost and programme review at each gate
-
Stakeholder and consent log with the current position of each authority
-
Operations manual, as-built drawings and trained personnel at handover
Developing A Project With Us
What sponsors ask before appointing a development partner.
Earlier is cheaper. Most of a project's eventual cost is fixed during concept and feasibility, when very little has been spent, so that is where our involvement changes the outcome most. We do also take on projects that have stalled later, though the options available by then are narrower.
Not as a rule. We work on a fee basis so that our advice on whether a project should proceed stays separable from whether it proceeds. Where a sponsor specifically wants aligned exposure we will discuss it, but it is the exception.
We do, for the parts of the programme within our scope, and the reporting shows it monthly rather than at the point it becomes unavoidable. Where the delay sits with a contractor or an authority we say that too, with the evidence.
Yes, and a meaningful share of our work arrives that way. The first step is a short review of what has actually been committed against what has been documented, because those two rarely match on a project that has changed hands.
We expect to work inside your governance rather than beside it, reporting into the same steering group as everyone else on the project. Where you have capability we use it; where a discipline is missing we fill it and then train someone to hold it, because a development team that cannot operate without us has not been handed over properly.
We say so, in writing, with the analysis that led there. Stopping a project at feasibility costs a fraction of one per cent of what stopping it after financial close costs, and a developer who has never recommended against their own continued engagement is not giving you an independent view.
