Celium — Section 3: The Product

Where Celium sits in the stack

Delivery systems

Systems of delivery record

MRV providers · Field data platforms · Jira / ServiceNow · Site management tools · Grant delivery systems · ERP project modules

↓ evidence ingested ↑ eligibility exported

Celium layer

Payability layer — the missing middle

EP — Evidence Pack → VD — Acceptance Decision → PE — Payment Eligibility

Settlement templates · Verification ledger · Policy engine · Workflow integrations · Immutable audit log · Export layer

Celium standardises: when money is allowed to move — and the auditable proof of why

↓ payment payloads exported to AP / ERP / escrow

Payment systems

Systems of payment record

SAP / Oracle / NetSuite · Fund admin platforms · Treasury / escrow systems · AP automation · Payment rails (Stripe, GoCardless)

Who relies on Celium artefacts

Project developersLandholders / operatorsBuyers / programme sponsorsMRV providersAuditors & consultantsFinancial institutionsInsurersRegistries

The product boundary is deliberate. Celium complements Jira, ServiceNow, ERP, AP, and delivery systems — it does not replace them. This makes procurement simpler, implementation faster, and the value proposition cleaner: Celium replaces spreadsheet eligibility, email acceptance, and bespoke reconciliation.

Progressive disclosure — start where the pain is, unlock more as trust builds

Tier 1 — Verify (Starter)

Minimise friction. Get to first cross-party interaction fast.

EP creation, evidence intake, shareable read-only links, basic VD issuance

EP — Evidence PackVD — basicPE — not yet

What you get

Evidence intake with structured fields

Shareable read-only EP links for buyers and auditors

Basic VD issuance — completeness and plausibility checks

Immutable submission history and timestamps

Magic links — onboard counterparties without accounts

Who it’s for

Nature programme operators running first pilots

IT vendors proving delivery against acceptance criteria

Grant recipients demonstrating eligible expenditure

Any team replacing email + spreadsheet evidence workflows

Pricing: Low starter subscription + flat per-claim/EP fee. Goal: first PE in weeks, not months.

Tier 2 — Settle (Programme)

Turn accepted evidence into deterministic payment eligibility.

VD reason codes + governance, PE generation, immutable history, export-first payloads

EPVD — full + reason codesPE — Payment Eligibility

What you get

Full VD with reason codes, policy versioning, reviewer attestations

PE generation — payable lines, holdbacks, deductions, release conditions

Export-first payloads — CSV, JSON, signed PDF to AP/ERP/escrow

Exceptions and disputes workflow with SLA and traceability

Embedded payment rails (Stripe / GoCardless)

Who it’s for

Programme operators needing deterministic payment triggers

Buyers who need a defensible approval record for internal audit

Enterprises replacing bespoke AP reconciliation workflows

Any context where “when will I be paid?” must have a clear answer

Pricing: Core subscription + per-claim fee + per-export/certificate fee + settlement fee per PE event.

Tier 3 — Integrate (Enterprise)

Become a chokepoint in the payment stack. Lock in operational reliance.

Production ERP/AP integrations, delivery tool connectors, enterprise governance

EPVD — full + reason codesPE

What you get

Production integrations — SAP, Oracle, NetSuite, fund admin

Delivery tool connectors — Jira, ServiceNow, project management

SSO, role-based access, policy controls

Hardened audit/export for SOC2 / ISO environments

Integration maintenance as recurring revenue (Line C)

Why it matters

Integrations create structural switching costs, not just stickiness

Each integration makes Celium the operational chokepoint for payment eligibility

Drives Line C recurring revenue — integration maintenance fees

Reduces time-to-PE for future programmes

Pricing: Enterprise subscription + integration setup fee + recurring integration maintenance (Line C) + per-claim + PE settlement fees.

Tier 4 — Assure + Finance (Advanced)

Make cashflows insurable and financeable. Unlock the capital multiplier.

Assurance workflow, insurer attachment hooks, receivables packaging, portfolio reporting

EPVD — finance-gradePE — underwriteable

What you get

Assurance workflow — audit-ready pack templates, sampling regimes

Control reporting — segregation of duties, immutable logs

Insurer attachment hooks — covenants tied to VD/PE artefacts

Receivables packaging outputs — PE bundles ready for financing

Portfolio intelligence — Insights module (Line D)

The finance multiplier

Tier 4 artefacts are what insurers and lenders need to attach capital

2–12× finance availability with well-functioning Tier 3 + 4 artefacts

PE certificates become the covenant basis for drawdown conditions

Transforms impact spending into infrastructure-like cashflows

Pricing: Enterprise subscription + assurance module + benchmarking/data subscription (Line D) + bps on $ settled + per PE event.

Packs are how Celium becomes repeatable without scope drift. Each pack defines what to collect, how to decide, and what becomes payable — for a specific vertical. One deep win before broad expansion.

Evidence schema

Landholder roster and land parcel mapping

MRV artefact schema — NDVI, species counts, habitat surveys

Satellite / remote sensing data linkage

Field verification records with geotagging

Third-party MRV provider attestation

Acceptance logic

Claim rules by outcome type (biodiversity, carbon, water)

Acceptance reason codes per contract clause

Tiered assurance: stewardship → buyer-grade → finance-grade

Partial acceptance logic for multi-parcel programmes

Dispute and remediation workflow

Payability rules

Milestone-based payment schedule linkage

Holdback and release conditions

Performance-linked payment windows

Export to fund admin / buyer AP / escrow

Deployment path

Wedge vertical — highest trust deficit, clearest pain

Magic links pull landholders and MRV providers in without accounts

Pack v1 target: Q2 (per GTM plan)

Why nature first: Capital is available in principle — $384bn needed vs $154bn deployed — but deployment is blocked by fragmented evidence and no shared payability standard. Nature is the proving ground for a much larger category.

Evidence schema

Deliverable taxonomy — milestones, work packages, outputs

SLA measurement records — uptime, response time, incident logs

Jira / ServiceNow ticket resolution linkage

Acceptance criteria per deliverable type

Change control and variation documentation

Acceptance logic

Deliverable acceptance with reason codes per clause

SLA breach calculation — automatic deduction logic

Change control linkage — approval before payability

Dispute workflow with SLA for resolution

Payability rules

Invoice-to-PE mapping — replaces manual reconciliation

Credit / deduction computation against SLA breaches

Export to SAP / Oracle / NetSuite AP module

Deployment path

Second wedge — most familiar enterprise software environment

ServiceNow / Jira integration unlocks fast adoption

Pack v1 target: Q3 (per GTM plan)

Why IT second: IT managed services is the most software-familiar vertical. Buyers already have workflow tool budgets and understand structured acceptance criteria. The Jira/ServiceNow integration creates a repeatable chokepoint at enterprise scale.

Evidence schema

Evidence / compliance requirements per grant programme

Expenditure validation records — receipts, invoices, payroll

Performance monitoring outputs — KPIs, beneficiary data

Programme-specific data requirements

Acceptance logic

Reason codes per grant condition — clause-linked

Ineligible expenditure flagging with audit trail

Clawback risk scoring — identifies vulnerable claims early

Multi-level approval workflow

Payability rules

Reimbursement claim to PE mapping

Eligible vs ineligible spend split logic

Drawdown schedule linkage

Export to government disbursement systems

Deployment path

Long sales cycle (180–360 days) — partner channel critical

Assurance / audit firm partners as primary distribution vector

Pack v0 target: Q5 (per GTM plan)

Why government third: Large GPV pool at $600bn (2026), growing to $1.2tn by 2040. The buyer has fiscal resources; what’s missing is the infrastructure to release them reliably. Long procurement cycles require partner-channel distribution.

Evidence schema

Milestone evidence — site photos, QS sign-off, inspection records

Progress certification — percentage complete by work package

Variation / change order documentation

Retention conditions — practical completion, defects liability

Acceptance logic

QS sign-off logic — certifier identity and authority

Variation approval gate — prevents unapproved scope in PE

Defects deduction logic — clause-linked, reason-coded

Retention release criteria — deterministic, not discretionary

Payability rules

Progress payment application to PE mapping

Retention held / released schedule

Back-charge and deduction computation

Sub-contractor payment cascade

Deployment path

Largest GPV pool — $4tn (2026)

Ecosystem participant tier — 5–10 subs per head contractor

Lighthouse only in Year 1 (Q7+) — scale from Year 3

Why construction last (but largest): The biggest long-run GPV pool but requires the most complex integration playbook. The hub-and-spoke ecosystem participant model is most powerful here — each subscribing head contractor is a hub for 5–10 subcontractors whose payment flows generate additional take-rate revenue.

Celium grows through three product-led vectors that pull counterparties onto the platform without direct sales — and a flywheel that accelerates as each vector compounds on the others.

Magic evidence links — bring in external contributors

An originator creates an Evidence Pack and sends a magic link to landholders, subcontractors, or field operators. Recipients upload evidence directly into the structured EP — no account creation, no onboarding friction, no IT setup.

Originator creates EP→Magic link sent→Contributor uploads evidence→EP complete, VD triggered

Reviewer & auditor links — bring in assurance providers and buyers

When a VD is ready for review, a read-only link is shared with auditors, buyers, or assurance providers. They interact with the artefact in Celium’s interface, leaving review records captured in the immutable audit log. Assurance providers become habitual Celium users through their clients’ programmes.

VD ready for review→Reviewer link sent→Reviewer stamps approval→Review captured in audit log

Shareable buyer-ready packs — drive internal forwarding and repeat use

A signed PE certificate is shareable as a PDF or via a verified link. Buyers circulate it internally for AP approval. Insurers share it with underwriters. Financiers use it as a drawdown attachment. Each circulation event extends Celium’s reach into organisations not yet sold to.

PE certificate generated→Buyer circulates internally→AP / finance / insurer receives→New stakeholder requests access

The growth flywheel

Originators adopt ops console→ Stakeholders onboarded via vectors 1–3→ Artefacts become trusted for payability→ Deal returns improve→ More programmes adopt Celium→ Standard emerges — adoption becomes pull-driven