Pricing
Not published yet, and here is why.
PactMeter is new. No customer has used it on real data, so any list price we showed would be invented. This is how we intend to charge, and what we are testing.
Start
A paid pilot on your own files
A fixed fee for your first few checks on real contracts and real invoice lines, with a written review of each result. You keep the output. The point is to find out, together, whether the answer is useful enough to run on your next change.
Then
An annual workspace subscription
Priced per workspace with a fair-use number of checks. Not per seat: the people who need this are a small pricing or finance team, and the value comes from each change checked, not from headcount. Not per row: the size of your data is not what you are buying.
Later
Scale: more of the business, checked every cycle
More product lines and teams in separate workspaces, and invoice preflight on every billing run. What would move the price is how many changes and billing runs are checked, not how many rows they contain.
Included from the pilot onwards
Every working control listed on the controls page: Change Guard with comparison and golden accounts, the Change Evidence Pack, promise drift, invoice preflight, discount, usage, credit and configuration checks, the renewal guard, the customer passport, findings, evidence and recovery cases. There is no feature held back for a higher tier.
What we are comparing ourselves with
Enterprise pricing and billing platforms are quoted per customer and usually come with an implementation project and a system migration. PactMeter starts from PDFs and two CSV files and needs no integration, so the honest comparison is analyst time and the cost of a price change that breaks a promise, not another platform.
Everything above is a hypothesis. It is described in the documentation alongside the limits of the product, and it will change when real buyers tell us what they would pay for.