Pricing

Simple company subscriptions. Separate implementation.

CPCS pricing is designed around organisational use. Final plan entitlements, taxes, limits, support commitments, integrations and special requirements are confirmed in the signed proposal.

Core
₦300,000 / month
or ₦3,000,000 annually
One-time implementation: ₦500,000
  • Structured project-control environment
  • Designed for teams adopting disciplined source records
  • Monthly or annual commercial option
Book Core Demo
Enterprise
From ₦1,250,000 / month
Custom annual quote
One-time implementation: ₦2,000,000
  • Complex or larger deployments
  • Scoped commercial requirements
  • Special requirements reviewed separately
Talk to Primavus

Pilot

Start with a bounded pilot.

For organisations that want evidence before wider rollout, Primavus can scope a short pilot around live projects and one management reporting cycle.

Scope a Pilot
2–4 weeksRecommended pilot duration
3–5 projectsProposed live project scope
1 reporting cycleManagement review anchor
Evidence-ledReporting effort, completeness, follow-through and adoption

Implementation

What the one-time implementation fee is for.

The exact scope is confirmed in the proposal, but the standard model is designed to move the client from signed agreement to a working project-control rhythm.

01

Discover & configure

Confirm projects, roles, reporting cadence, naming conventions, source records and access model.

02

Activate data

Load the agreed starting data and validate critical project-control fields.

03

Train the roles

Train users around the controls they are responsible for maintaining and reviewing.

04

Go live & stabilise

Support the first live reporting cycle, close onboarding gaps and confirm the normal operating rhythm.

The launch commercial model is positioned as a company subscription rather than a separate purchase decision for every user. Actual entitlements are confirmed in the live catalogue and proposal.
Yes. Primavus can scope a bounded pilot around selected live projects, a defined reporting cycle and agreed success measures.
Potential integrations require technical review and separate scoping unless expressly included in the signed implementation scope.
The agreed scope typically covers configuration, project and user setup, an agreed starting-data migration, training and a defined go-live support period.