Straightforward, volume-based pricing

DynamoDocs is a managed, per-customer service with published, volume-based plans: Starter at $1,500/month for up to 500 documents, Growth at $3,000/month for up to 2,500 documents and all document types, and custom Enterprise pricing for high-volume or multi-entity operations. Plans are billed annually and paid monthly, and there are no per-seat charges for the staff who review exceptions. Documents above your plan's included volume are billed per document ($1.20 on Starter, $0.80 on Growth). Most teams evaluating DynamoDocs are replacing 0.5–3 full-time-equivalents of manual keying, so the subscription typically costs a fraction of the labor it removes. Model your own numbers with the savings calculator before you talk to us.

Each plan includes document capture, AI extraction, validation, exception review, and posting into your ERP for the included document volume and ERP integrations shown. Product capabilities are not the upsell: approval routing, duplicate detection, credit-memo linkage, statement reconciliation, supplier order confirmations, the inbound shipment board, supplier scorecards, payment-file export, outbound webhooks, and the read-only API are part of every plan. What a plan actually controls is volume, how many systems we integrate with, which document families you capture, and matching depth. A capability that reads a family you are not on simply has nothing to work with: supplier order confirmations need the purchase orders you send, so an AP-only Starter plan gets the shipment board and scorecards from receipts and invoices, and adds confirmations when it adds order entry. On Starter, credit memos and vendor statements ride along with invoices rather than counting as a separate type. One-time implementation and onboarding (connecting your mailbox and ERP, configuring document types, validation rules, and field mappings, and training on your samples) is scoped and billed separately per engagement, because setup depth varies by ERP and document mix. There are no per-seat fees: everyone on your team who reviews exceptions is included. EDI connections beyond your plan's included count are the one recurring add-on, and each connection carries a one-time setup fee.

The capability is included on every plan. There is no separate EDI product or licence, and no per-document EDI surcharge. An EDI document counts toward your plan volume exactly like a PDF does, and costs us less to process than one, because X12 parses deterministically with no AI extraction step. What is metered is connections: Growth includes two and Enterprise includes unlimited; on Starter, and beyond the two on Growth, each connection is $150/month, dropping to $100 beyond 11. Setting up each connection is a one-time fee from $1,000, scoped to the partner, because the work varies: a retail partner with its own implementation guide takes more test rounds than adding a buyer to a network you are already connected to.

One channel to one counterparty or network. For classic retail EDI that is normally one connection per trading partner, because each retailer publishes its own implementation guide and runs its own certification cycle against it. For a supplier network (SAP Ariba, Coupa, Jaggaer, or a VAN), it is one connection to the network, and buyers you add underneath it are configuration rather than a new integration. The distinction matters if you sell to a long tail: a distributor with a hundred customers might reach almost all of them through four or five channels, and you are billed for the channels, not the customer list. If you are not sure which shape you are, send us your counterparty list and we will count it with you before you commit.

No. Goods receipts, packing slips, and advance ship notices are included on every plan and are never counted. They post nothing to your ERP and nobody pays them; they exist to feed the three-way match, the inbound shipment board, and supplier scorecards, all of which you are already paying for. If capturing them cost you volume, the rational move would be to stop capturing them, which would break the checks you bought the product for. The same reasoning is why there is no per-document surcharge on EDI.

Because the subscription is not purely a per-document price. Every customer runs on their own isolated instance with its own database, connectors, and configuration, and that costs the same to run whether you send 200 documents or 500. The subscription covers operating that instance; the overage rate covers only the marginal cost of one more document. The effect is that the effective per-document price falls as you grow: around $3.00 a document at Starter's 500, about $1.20 at Growth's 2,500, and lower again at Enterprise volumes. The comparison that matters is against the $2 to $6 of manual keying you are replacing, not against the overage rate.

No. Supplier order confirmations, the inbound shipment board, and supplier scorecards are part of every plan, and there is no per-supplier, per-link, or per-message charge. A response link is a signed URL, not a seat, so inviting your whole supply base costs nothing and no supplier is ever asked to create an account or pay a fee to answer you. That is deliberate: supplier-facing tools fail when the supplier has to sign up, and a price per supplier would push you to invite only the big ones, which are the ones already reachable by EDI. The scorecards and shipment board are built from documents already flowing, so they carry no incremental cost either.

There is something better: a fully working copy of the product at demo.dynamodocs.app, with no signup, no email, and no sales gate. It is seeded with a fictional distributor's paperwork, it is private to you, you can upload your own documents into it, and you can reset it whenever you like. When you want to see it on your own ERP and your own document mix, book a 30-minute working session and bring two or three real documents; we run them through extraction, validation, and a mapping to your ERP live on the call.

Mainly your monthly document volume and how many ERP or system integrations you need. Growth adds every document type together (invoices, credit memos, POs, RFQs, and vendor statements), custom validation rules, two- and three-way matching, and two EDI connections rather than metering them from the first. The usual reason to move from Starter to Growth is not volume but the second document family: an AP team that starts sending its own purchase orders through the same instance, which is also what turns on supplier order confirmations and the full three-way match. Enterprise is usually driven by one of three things: volume, multiple entities or ERPs, or enough EDI connections that unlimited is cheaper than metering them, which tends to happen around eight to ten. Enterprise covers multiple ERPs or legal entities, self-hosting, SSO, and procurement or security requirements. If you are unsure, the savings calculator plus a short demo will point you to the right tier.