BY NUMBER7 AIOpen AIdaptIQ ↗Book a demo →Pricing and commercial options
Choose how AIdaptIQ enters your operation. Your proposal states the volume, included work, integrations, implementation and support.
Checks, review and the agreed accounting handoff.
The agreed structured result in your own workflow.
Pricing is scoped to expected processing volume, document mix, client entities, workflow complexity, integrations and support. Final charging units, rates and overages are stated in the commercial proposal.
Two ways to buy
AP workflow deployment
Invoice intake, checks, client context, exceptions, approvals and the agreed accounting handoff.
Embedded document API
Document processing and the agreed structured result inside your own software and workflow.
What the proposal states
Scroll across to compare the columns
| Item | What must be explicit |
|---|---|
| Recurring usage | Charging unit, included volume, document or transaction mix and overage terms. |
| One-time implementation | Configuration, named integrations, migration or access work and customer responsibilities. |
| Workflow coverage | Included checks, review, approval and the agreed downstream outcome. |
| Deployment and support | Deployment requirements, operational support, service expectations and exclusions. |
| Acceptance | The evaluation population, required outcomes and production sign-off criteria. |
From interest to a commercial decision
Volume, systems and the result your team needs.
A demonstration or a representative document diagnostic.
Usage, implementation, support and exclusions.
Accepted outcomes and named production owners.
Next step
Tell us whether your team will operate in AIdaptIQ or embed the API, then share the expected volume and systems.
Understand the volume
| Unit | What it means | What to supply |
|---|---|---|
| PDF / file | An uploaded container. One file can contain multiple business documents. | File counts and whether the PDFs are mixed. |
| Page | One page within a file. | Page volume and typical pages per business document. |
| Bill / invoice | One supplier billing document, which may span pages. | Invoices per month, separately from PDF counts. |
| Document | A business document such as an invoice, PO or credit note. | Document types and counts; define the meaning in the proposal. |
| API call | One request to an endpoint; upload and polling need not have the same commercial treatment. | Expected request pattern and monthly volume. |
| Transaction | The business work connecting evidence, checks, review and a required accounting result. | Workflow scope, entities and completion criteria. |
A four-page PDF can contain two invoices and one credit note. That describes the content, not a public billing formula. The billable unit, mixed-PDF treatment, limits and overages must be specified in the agreed proposal.
Ask the proposal to itemize onboarding, connectors, seats, exception review, usage limits, support and customer-hosted responsibilities where applicable. No universal entitlement or price band is published here.
Example scope without a price: two client entities, QuickBooks bill handoff, mixed PDFs, estimated invoice and page counts, and explicit approval requirements.
Request workflow or API pricingScope and action
Confirm company scope, credentials, approval and the returned accounting record. A prepared bill is distinct from an accepted QuickBooks record.
Action: Approval required.
Read the workflow scopeRequest the verified integration contract and hosting scope. Public guidance is not a validated machine-readable specification or a promise of SDK availability.
Action: Scope agreement required.
Read the workflow scopeConfirm the connector, supported entities, tax fields and permitted actions for your environment. Listing an ERP does not establish a ready connector for every deployment.
Action: Scope agreement required.
Read the workflow scopeThe recorded product-owner confirmation applies to the named capabilities. Deployment scope, integration permissions and approval requirements are agreed separately.