Project36 pricing
Clear scope. Clear responsibility. Clear investment
Every Project36 engagement is shaped around the problem that needs solving and the work required to solve it properly.
We consider the teams, systems, processes, investigation, implementation and specialist responsibility involved. Before work begins, we agree what Project36 will do, what the client will do, the intended outcomes and the price.
Before any engagement begins
- The problem we’re solving is written down and agreed
- The scope of the work is defined
- Responsibilities on both sides are clear
- The intended outcomes are agreed
- The price is agreed
Pricing reflects the work needed to solve the problem properly, not a generic bundle of hours or tasks.
How engagements work
Three stages. Each scoped around what is needed
01 · Notice the drift
Drift Diagnostic
Establish where leadership intent and operational reality have separated, what the consequences are and what should be corrected first.
Scope and price
The diagnostic is priced after an initial fit conversation. Its scope reflects the organisation, the people involved, the available evidence and the complexity of the problem.
02 · Correct the drift
CORE™ Alignment Programme
Translate leadership direction into departmental objectives, agreed results, accountable execution, operating processes and the systems required to support them.
Scope and price
The programme is scoped following the Drift Diagnostic. The price reflects the correction, implementation, enablement and technical work required.
03 · Keep it true
Flex subscription
Maintain alignment, detect new drift and continue improving commercial performance as the organisation changes.
From £5,000 per month
- Initial three-month commitment
- Final scope is agreed following the Drift Diagnostic
Scope and price
Each partnership is planned around an agreed set of priorities and responsibilities. If the organisation introduces a materially different objective, we agree the revised scope before proceeding.
Scoping
What shapes the scope?
Teams involved
The departments, leaders and users that need to participate.
Systems involved
The CRM, reporting, integrations and other platforms affected.
Depth of change
Whether the work requires clarification, redesign, implementation or organisational adoption.
Implementation required
The processes, reporting, automation and technical changes Project36 must deliver.
Pace
The timescale and sequencing needed to complete the work responsibly.
Ongoing responsibility
The level of continuing leadership, challenge, implementation and support required.
Delivery
Different ways to deliver the work
Following the Drift Diagnostic, Project36 may present different delivery approaches. These aren’t fixed packages. They show how responsibility for the work could be divided.
The price of each option reflects the work and responsibility included.
Client-led
Project36 diagnoses, designs and advises. The client leads implementation.
Co-delivered
Project36 and the client share delivery and responsibility.
Project36-led
Project36 leads the correction, implementation, enablement and embedding.
Pricing FAQ
Common questions.
Clear answers.
Start by establishing what is actually wrong
Tell us what is happening, what it’s affecting and what needs to change.