Pricing for enterprise field data capture

IndeForms is sold as a subscription for your organisation, not a per-form licence. What follows is the honest version: the three shapes we sell, exactly what the platform meters, and every capability in the product mapped against them. Final numbers come from a conversation, because an air-gapped install and a twelve-agent cloud account are not the same purchase.

Three subscriptions

They differ by how far a submission travels after an agent hits submit, and by whose infrastructure it lands on. Pick by the last capability you need, not by headcount.

Capture

Get the forms off paper and into the field.

Teams replacing checklists, logbooks and inspection sheets on a defined set of forms.


Form builder: pages, sections and 28 question types

Repeatable sections with calculation and aggregation footers

IF/THEN/ELSE rules on questions, pages and sections, scoped by rule group

Offline capture on Android and iOS, plus the same forms in a browser

Direct, pull and broadcast dispatch to field agents

Submission exports in XLSX and CSV, and the operations dashboard

Component-level RBAC and a separate database for each customer


Subscription, metered on user seats and submissions.

Talk to us

Operate

Automate what happens after submit.

Operations where a submission has to be approved, escalated, signed, and landed in another system without anyone re-typing it.


Everything in Capture

Workflow canvas: conditions, branches, timers, loops, spawn-form and invoke-API nodes

Approval nodes with all, any, quorum, majority, consensus and advisory policies

Escalation and reminders on a parked approval, and send-for-edit with a rework cap

E-signature on approval and on submit, by password or signature pad

Scheduled cron dispatch from an Excel roster, and scheduled email reports

Connectors and the API question type for two-way traffic with your systems

Analytics across all your submissions, saved queries and custom dashboards

SAML 2.0 and OIDC single sign-on


Subscription, metered on user seats, submissions, storage and API calls.

Talk to us

Enterprise

Run the whole platform inside your own boundary.

Regulated operations, data-residency mandates, and sites that have no outbound internet at all.


Everything in Operate

Deploy into your own cloud account or your own data centre

Air-gapped installs with signed licence and update bundles, no phone-home required

Object storage on AWS S3 or Azure Blob, in the region you nominate

Retention policies and GDPR DSAR export and erasure tooling

Mobile data-at-rest encryption with PIN-derived keys and biometric unlock

Per-customer egress allowlist, SSRF guard and encrypted connector credentials


Annual licence, priced on install footprint and seat count.

Talk to us

What the platform actually meters

Four counters, written per customer per day and rolled up nightly. You see the same numbers we do. A quota warns while there is still room and blocks only the specific action that would cross it, so a full storage quota never silently swallows a field agent submission.

User seats

Enabled user accounts in your account. Deactivate a user and the seat is free again on the next check.

Submissions

Completed submissions, counted per customer per day and rolled up nightly.

Stored bytes

Submission payloads and captured media held in object storage, snapshotted daily.

API calls

Outbound calls made by API questions and connectors on your behalf.

What is in each subscription

Read this as a map of the product, not a wall. Everything listed is built and running today.

IndeForms capabilities by subscription: Capture, Operate and Enterprise
CapabilityCaptureOperateEnterprise
Building forms
28 question types across pages, sections and repeatable sectionsIncludedIncludedIncluded
IF/THEN/ELSE rules targeting a question, a page or a whole sectionIncludedIncludedIncluded
Rule groups: choose which rules fire for a given dispatchIncludedIncludedIncluded
DREL prefill expressions that carry answers into labels, defaults and callsIncludedIncludedIncluded
Multi-language forms with per-field translationsIncludedIncludedIncluded
Form versioning, with restore of an earlier published version as a draftIncludedIncludedIncluded
AI form assistant, and drafting a form from a photo of the paper originalNot includedIncludedIncluded
Field capture
Offline capture on Android and iOS, queued and synced on reconnectIncludedIncludedIncluded
Browser form filling, embeddable as an iframe in your own appIncludedIncludedIncluded
Camera, GPS, barcode, sketch, signature and audio-note questionsIncludedIncludedIncluded
On-device OCR into a field, and on-device voice-to-text dictationIncludedIncludedIncluded
Per-field timestamps and geostamps on every answerIncludedIncludedIncluded
Mobile data-at-rest encryption, PIN-derived keys and biometric unlockNot includedNot includedIncluded
Dispatch
Direct dispatch to named agents, and pull from a self-serve listIncludedIncludedIncluded
Broadcast dispatch: the first agent to accept claims the jobIncludedIncludedIncluded
Scheduled cron dispatch driven by an Excel roster with per-column defaultsNot includedIncludedIncluded
Teams, shared recipient picker and a organisation-wide dispatch calendarNot includedIncludedIncluded
Workflow and approvals
Workflow canvas: conditions, branches, timers, loops and spawn-form nodesNot includedIncludedIncluded
Approval nodes with all, any, quorum, majority, consensus or advisory policyNot includedIncludedIncluded
Approver resolution by user, group, manager, form field or an earlier nodeNot includedIncludedIncluded
Escalation and reminders while a run is parked on an approvalNot includedIncludedIncluded
E-signature by password or signature pad, enforced server-side on web and mobileNot includedIncludedIncluded
Send-for-edit back to the submitter, with a rework-count capNot includedIncludedIncluded
Run-scoped variables and cross-form conditionsNot includedIncludedIncluded
Integrations and API
File and mail connectors: Email, FTP, S3, OneDrive, SharePoint, Box, Dropbox, Google SheetsNot includedIncludedIncluded
Business-system connectors: Salesforce, ServiceNow, SAP S/4HANA, Dynamics 365, Veeva Vault, TrackWise, MuleSoftNot includedIncludedIncluded
API question type: call your endpoint mid-form, 7 auth types, dry-run in the builderNot includedIncludedIncluded
Outbound webhooks and a per-customer egress allowlistNot includedIncludedIncluded
Redacted API call log with configurable retentionNot includedIncludedIncluded
Analytics and reporting
Submission export in XLSX and CSV, plus queued exports for large pullsIncludedIncludedIncluded
Operations dashboard: dispatch, agents, reviews, data quality, geo and timeIncludedIncludedIncluded
Columnar analytics over Parquet with DuckDBNot includedIncludedIncluded
Ask a question in English, get SQL and a chart backNot includedIncludedIncluded
Saved queries, drag-and-drop custom dashboards and scheduled email reportsNot includedIncludedIncluded
Statistical anomaly review on submitted valuesNot includedIncludedIncluded
Security and administration
Component-level RBAC, per role, on every routeIncludedIncludedIncluded
A separate database for each customer, never shared tablesIncludedIncludedIncluded
Usage metering on seats, submissions, storage and API callsIncludedIncludedIncluded
Support acts through named, audited actions, never an impersonated loginIncludedIncludedIncluded
SAML 2.0 and OIDC single sign-on with per-customer home-realm discoveryNot includedIncludedIncluded
Retention policies, and GDPR DSAR export and erasure runsNot includedNot includedIncluded
Deployment and data
Managed cloud, operated by usIncludedIncludedIncluded
Object storage on AWS S3 or Azure Blob, in the region you nominateNot includedIncludedIncluded
Install into your own cloud account or your own data centreNot includedNot includedIncluded
Air-gapped install with signed licence and update bundlesNot includedNot includedIncluded

Every capability in this table is in the product today. Which of them sit in your subscription is set in your agreement, so if you need one from a higher row, ask and we will price it rather than tell you it is impossible.

AI-assisted features need a model provider configured. Point them at a self-hosted model and nothing leaves your environment; point them at a commercial provider and only form structure and aggregate statistics are ever sent.

Where it runs

The same product in all three cases. What changes is whose infrastructure holds the data, who applies upgrades, and how the licence reaches the install.

Managed cloud

We run it. You get an account with its own database.

Your own database, provisioned from the same schema every customer runs

Submission payloads and media in object storage we operate

Upgrades applied by us, on our release cadence

Usage metered nightly, with a quota warning before anything is blocked

Your cloud account

The same install, inside your subscription and your region.

Admin, client, auth and both batch workers run under your account

central customer registry plus a separate database for each customer, all yours

Object storage on AWS S3 or Azure Blob, region of your choosing

A signed heartbeat carries licence and config to the install; no vendor code runs inside it

On-premise and air-gapped

No outbound internet, no exceptions.

Licence is an RS256 token checked at boot, with a 14-day grace window before writes stop

Air-gapped sites take licence and update bundles as signed files, hand-carried in

Self-hosted models keep every AI feature inside the network, including dictation and transcription

Diagnostic support bundles are exported for us to read, rather than us reaching in

Start with your own forms, not a demo account

Send us the two or three forms that cause the most re-typing. We will build them, dispatch them to a handful of your agents, and you can judge the platform on your own paperwork before anyone talks about a contract.

Pricing questions we get asked

The commercial and practical questions that come up in the first call, answered here so you do not have to book one to find out.

How is IndeForms priced?

As a subscription for your organisation rather than a shrink-wrapped seat price. What we meter is visible above: enabled user seats, submissions, stored bytes and outbound API calls. Cloud subscriptions are quoted against those four numbers; an on-premise or air-gapped install is an annual licence quoted on install footprint and seat count. Billing cadence, currency and invoicing terms are set on your order form, so tell us how your procurement works and we will quote to it.

A user account that is enabled in your account. Deactivating an account releases the seat at the next quota check, and the platform counts seats itself rather than asking you to declare them. When you try to add a user beyond the cap, the request is refused with an explicit seat-cap message naming the cap and the current count, so an admin knows exactly what happened instead of hitting a silent failure.

They keep working. The form definition, its option sources and its rules are already on the device, so validation, calculations, rule evaluation and media capture all run locally with no network. Completed submissions queue on the device and upload when connectivity returns; a partially completed form survives the app being closed. Nothing about the capture experience degrades on a site with no signal, which is the reason the mobile app is offline-first rather than a wrapper around a web page.

No. There is no per-form licence and no per-question fee, so a form that grows from 20 fields to 200 does not change what you pay. The meters are seats, submissions, storage and API calls. Build as many forms, versions and rule groups as your operation needs.

Yes, and it is a first-class deployment rather than a special build. The customer-side install is the admin, client, auth and batch services plus a central customer registry and a separate database for each customer, all inside your boundary. Nothing of ours runs in there: the install phones home over a signed heartbeat for licence and configuration, and a fully air-gapped site takes those as signed bundles instead. Support acts through named, audited actions on your side, never by logging in as one of your users.

You do. Submissions live in your account database and your object storage, and you can pull them out at any time as XLSX or CSV, as a queued export for large ranges, or as a scheduled report mailed on a cron. Retention policies expire data on your schedule, and the GDPR tooling runs subject access and erasure requests as auditable jobs. There is no export fee and no lock-in period on the data itself.

No, and that is enforced structurally rather than promised. Model calls receive form structure, your typed question and aggregate statistics; they never receive answer values, captured media or credentials. When you ask an analytics question in English, the generated SQL runs against your own data locally and the result rows are never sent back to the model. The two features that inherently involve answer content, voice dictation and transcription, only function when the configured model is self-hosted in your environment. With AI switched off, nothing leaves at all.

There is no self-serve signup today, and we would rather say so than park you in a sandbox full of demo data. Evaluations start with a walkthrough on your own use case, then a scoped pilot: we build two or three of your real forms, dispatch them to a handful of your agents, and you judge the platform on your own paperwork. Tell us the forms you want to try and we will scope it.

Channels and response targets are written into your agreement rather than published as a badge here, because they differ between a managed-cloud account and an air-gapped site. What does not differ is how support behaves: our staff cannot log in as one of your users. Every support action is a specific, named operation such as unlocking a submission or replaying a failed connector row, and every one of them is written to an audit log you can export.

Usually less than expected. A paper original can be photographed and drafted into a form automatically, and the AI assistant will scaffold structure and rules from a plain-language description, which you then correct in the builder. Existing reference data comes in as option sources, and an existing system of record can be read mid-form through an API question rather than migrated at all. Bring the three forms that hurt most to the pilot and you will know the real number within a week.