PlanSure

Commercial model

Commercial terms built around how you deploy PlanSure.

PlanSure is deployed around the governance requirements of the organisation — from an individual project through to multi-project and enterprise-wide use. Commercial scope reflects the breadth of deployment, project environment and implementation requirements.

Book a DemonstrationExplore the Platform

Start with the deployment scope that fits the organisation. Expand the framework as requirements develop.

Deployment scopeIllustrative
  • Single projectProject
  • Multiple projectsPortfolio
  • Organisation-wideEnterprise

The same governance framework, applied at the scope the organisation requires.

Deployment scopes shown for reference — no commercial figures are published.

02Deployment options

Choose the deployment scope that fits your organisation.

The same structured governance framework can be applied at different levels of an organisation. Deployment scope determines how widely PlanSure is implemented and the commercial requirements around that implementation.

01Project

For an individual project requiring a structured and repeatable governance framework.

Suitable for
  • A defined project environment
  • Project-level governance
  • Project roles and responsibilities
  • A controlled Governance Week
  • Readiness, actions and governance records
Discuss Project Deployment

02Portfolio

For organisations applying the PlanSure governance framework across multiple projects.

Suitable for
  • Multiple active projects
  • Cross-project visibility
  • Consistent governance structure
  • Portfolio-level oversight
  • Governance information across projects
Discuss Portfolio Deployment

03Enterprise

For organisation-wide implementation of a consistent project governance framework.

Suitable for
  • Wider organisational rollout
  • Multiple projects and teams
  • Administrative oversight
  • Organisation-level governance structure
  • Broader implementation and support requirements
Discuss Enterprise Deployment

03One governance framework

The governance framework remains consistent.

Deployment scale changes how widely PlanSure is applied — not the fundamental governance method being introduced.

01

Governance Week

A structured weekly governance rhythm for reviewing commitments, readiness, ownership and outcomes.

02

Evidence-based readiness

Readiness is reviewed against the evidence required to support delivery commitments.

03

Controlled actions

Required actions retain ownership and remain visible through to an accountable outcome.

04

Controlled Weekly Plan

Weekly commitments are carried forward within the governance process.

05

Planner To-Do

Planning requirements arising through governance remain visible and accountable.

06

Governance record

Reviews, actions, decisions and outcomes create a retained record of the governance process.

04Commercial scope

Pricing reflects the scope of deployment.

Rather than forcing project governance into a simple per-seat licensing model, commercial scope is agreed around the environment in which PlanSure will be deployed.

01

Active projects

The number of projects operating within the PlanSure governance framework.

02

Users and responsibilities

The number and structure of people participating in governance, including the roles and responsibilities required.

03

Rollout scope

Whether PlanSure is being introduced to an individual project, a portfolio or more widely across the organisation.

04

Implementation support

The onboarding, configuration and implementation involvement required for the agreed deployment.

The objective is a commercial structure that supports effective adoption without unnecessary licensing complexity.

05Engagement

A defined route from demonstration to deployment.

Every organisation has a different project environment. A demonstration allows the governance framework to be understood first; deployment scope and commercial requirements can then be defined around the organisation.

  1. 01

    Demonstration

    Understand the PlanSure governance framework and how it operates within a live project environment.

  2. 02

    Scope

    Agree the intended deployment, project environment, organisational requirements and implementation considerations.

  3. 03

    Proposal

    Define the commercial scope and implementation approach for the agreed deployment.

  4. 04

    Implementation

    Configure the agreed environment, establish the governance structure and support adoption into the project operating rhythm.

The exact implementation approach is agreed during scoping and reflects the size and complexity of the deployment.

Book a Demonstration

06Questions

Commercial questions.

Discuss your requirements

Discuss the right PlanSure deployment for your organisation.

See the governance framework in operation, then discuss the project environment, deployment scope and implementation requirements with us.

Book a DemonstrationSee How It Works