Pricing
Unlimited requesters on every plan
You should never be charged for inviting the people whose spend you are trying to control. We price on controller seats instead.
Core
Single entity, first formal purchasing process
$390
per month, billed annually
- Unlimited requesters and approvers
- 5 controller seats
- Requisitions and purchase orders
- Amount-based approval routing
- Supplier records and documents
- Accounting sync (one entity)
Most chosen
Control
Multi-site teams that need budget enforcement
$890
per month, billed annually
- Everything in Core
- 15 controller seats
- Category and department routing, parallel approvals
- Budget checks at request time
- Two- and three-way matching with tolerances
- Contract register with renewal alerts
- Catalogues and preferred suppliers
Group
Multi-entity groups and regulated categories
Custom
annual agreement
- Everything in Control
- Unlimited controller seats
- Multi-entity, multi-currency consolidation
- SSO and SCIM provisioning
- Custom approval logic and API access
- Named implementation lead
Compare
What each plan includes
| Capability | Core | Control | Group |
|---|---|---|---|
| Requesters and approvers | Unlimited | Unlimited | Unlimited |
| Controller seats | 5 | 15 | Unlimited |
| Purchase orders per year | 2,500 | 15,000 | Unlimited |
| Approval routing | By amount | Amount, category, department | Fully custom |
| Parallel approvals | — | Yes | Yes |
| Budget enforcement at request | — | Yes | Yes |
| Three-way matching | — | Yes | Yes |
| Contract renewal register | — | Yes | Yes |
| Multi-entity consolidation | — | — | Yes |
| SSO / SCIM | — | SSO | SSO + SCIM |
| API access | Read | Read + write | Read + write |
| Support | Email, 1 business day | Priority, 4 hours | Named lead |
Questions
Pricing FAQ
- Do you charge per purchase order?
- No. Plans are priced on controller seats, with fair-use annual purchase order limits on Core and Control. Requesters and approvers are always unlimited, because charging for them discourages exactly the participation that makes spend control work.
- What is a controller seat?
- A controller is someone who configures the system or works in it daily: procurement staff, accounts payable, and finance administrators. Employees who raise requests or approve them are not controllers and are never charged.
- How long does implementation take?
- A single-entity rollout typically takes two weeks: one week to configure categories, approval thresholds, and the accounting sync, and one week of parallel running before you switch off the old process. Multi-entity groups usually run four to six weeks.
- Can we export our data?
- Yes. Full history — requisitions, purchase orders, receipts, suppliers, approvals, and documents — exports in CSV and JSON at any time, without vendor assistance and without a fee.
- What does it integrate with?
- Two-way sync with the major mid-market accounting systems, SSO through any SAML provider on Control and above, and a REST API for everything else. Sync failures surface as alerts rather than silently queueing. There is no certified connector for tier-one ERPs; those integrate through the API and take real engineering time on your side.
- What is not included at any price?
- Punchout catalogues, supplier credit and sanctions screening, procurement card reconciliation, inventory management, and contract clause extraction. Some of those we may build; none are available today, and no plan unlocks them.
- What happens if we exceed the purchase order limit?
- Nothing breaks and nothing is blocked. We flag it, and at renewal we either move you up a tier or leave you where you are if the overage was a one-off project. Mid-term forced upgrades are not how we would like to be treated either.
Not sure which plan fits?
Tell us your approval thresholds and supplier count and we will tell you plainly — including when Core is enough.