One price per project. Published, not negotiated.
EarnedCurve is metered on the size of the work, not the size of the team. A project sits in the lowest band whose budget-hours ceiling covers it, and that band's price is the whole price — every feature, every login, every period. There is no enterprise tier that unlocks the features you actually came for.
| Band | Budget hours (project) | Price | What changes |
|---|---|---|---|
| Freeno card | up to 2,000 | £0 | Nothing. The complete engine, not a trial or a feature-capped tier. |
| Small | up to 10,000 | £199 /mo | Nothing. |
| Mediummost projects | up to 50,000 | £599 /mo | Nothing. |
| Large | up to 250,000 | £1,499 /mo | Nothing. |
| XL | up to 1,000,000 | £3,499 /mo | Nothing. |
| XL+ | above 1,000,000 | £3,499 + £1,000 per started 500,000 hours over 1M | Nothing — and it is a formula on this page, not a sales call. |
Per project, per month, GBP, excluding VAT. Budget hours are the project's own summarised budget — the same figure the register rolls up.
Three rules, and no small print under them
A project that grows is a good problem. The meter is built so that growing never costs you your data, your access, or your ability to keep working while you sort out the paperwork.
Your band is derived, not chosen
A project falls into the lowest band whose ceiling covers its budget hours. Nothing to declare, nothing to true up at renewal. A project with no derivable summary yet is treated as the floor — free.
Crossing a band starts a 30-day clock
When the observed band rises above the one you are entitled to, you get 30 days. During that window everything works exactly as before — the grace period exists so a growing project never stops mid-cut-off.
Only reporting ever freezes
If the 30 days pass unresolved, roll-ups and reports hold at the last figures. Writes are never blocked, in any state. Your team keeps claiming; the numbers you can publish are what pause. Settle the band and reporting resumes where it left off.
What real projects land on
| Project | Budget hours | Band | Per month |
|---|---|---|---|
| A single discipline's detail-design package | 1,800 | Free | £0 |
| A brownfield tie-in package, 3 disciplines | 9,400 | Small | £199 |
| A mid-size EPC engineering scope | 46,000 | Medium | £599 |
| A full plant EPC, engineering + procurement + commissioning | 230,000 | Large | £1,499 |
| A multi-train megaproject | 1,600,000 | XL+ | £5,499 (3,499 + 2 × 1,000) |
Every band gets every feature
There is no list of things the cheap tier can't do. The band changes the price and nothing else.
- Rules-of-credit templates with weighted objective steps
- Milestone mode for documents, ITR counts for commissioning
- Dual-basis budgets — hours and value, conserved through the roll-up
- LOE quarantine, reported separately from deliverable progress
- Control account (WBS × OBS) and CAM on every item
- P6 .xer import, step-band L4 → L3 mapping, variance and write-back
- Weekly MDR snapshots with week-on-week diff
- EDMS auto-claim by document number, with a human review queue
- Evidence ledger on every proposal
- Immutable cut-off snapshots and an open-period-only write rule
- S-curve, period histogram and deliverable skyline
- Computed scope-change reconciliation on the period report
- Portfolio and enterprise roll-up with scoped report definitions
- SV, CV, SPI, CPI and EAC from the same evidenced figures
- Project roles — admin, controller, contributor, viewer
- Discipline-scoped contributors, enforced server-side
- Audit log on role, approval and baseline changes
- CSV, XER and Excel export
- Unlimited logins — seats are never the meter
- Local-first computation; project data never uploaded