Summary

  • IAM Standard and Professional pair unlimited ordinary web and mobile application sending with a separate Automation Sends allowance. The public Singapore page lists a total of 100 per user per year on annual plans and up to ten per month on monthly plans.
  • The initiating route matters: Bulk Send counts as automation even when a person clicks the button. APIs, forms and Workflow Builder have specific classifications, while the described sales-channel subscriptions add pooling, term and order-date rules.

The saving is a human step; the replacement has a unit

A signing integration can remove a dull piece of work. Instead of an employee opening an application, preparing a request and sending it, the company’s own system starts the signature request. The recipient may still see the familiar signing experience. Inside DocuSign IAM’s commercial description, the initiating route can move the task to a different allowance.

The public Singapore IAM page gives Standard and Professional unlimited envelope sending through the web or mobile application. It places Automation Sends on another line: annual plans include a total of 100 per user per year; monthly plans include up to ten per user per month. Web Forms, PowerForms, Bulk Send and custom or partner API integrations sit in that automation category.

“Total” is doing useful work beside the more impressive adjective. Several ways into automation share the stated category. Turning on four features does not deliver four separate bundles of 100. The unit is a send for signature, rather than an arbitrary API request, a file or a signer.

For a buyer moving ordinary application sending into a custom API integration, the business objective can stay the same while the commercial route changes. Time saved belongs in the project calculation. So does the purchased capacity that the replacement process will use. Efficiency has acquired a second line in the spreadsheet.

A thousand test envelopes prompted the obvious question

On 30 June 2025, a user named wbdoc posted in the official DocuSign community that a developer account was showing an envelope-allowance error. The user reported sending 1,000 testing envelopes that month and asked whether unlimited meant 1,000. In a subsequent reply, wbdoc said the implementation used embedding.

Alexandre.Augusto, identified on the page as a DocuSign employee, first asked whether sending came from the web application or an automated route such as an API. He then said the screenshot appeared to show a Demo account at its automation limit, and pointed to the commercial allowance page for paid plans.

The thousand was the user’s reported test volume. A paid subscription gets its quantities from its applicable commercial terms. What makes the exchange instructive is the first diagnostic question: where did the send begin? The developer had already connected the signing experience; the subscription vocabulary still needed connecting to the implementation.

That distinction survives the journey from a demonstration to a business process. A document can look the same to its recipient while the system that starts it uses a different category of service.

A human can press the automation button

The official allowance explanation for sales and partner subscriptions explicitly counts Bulk Send as Automation Sends. Each resulting envelope requiring signature counts as one Automation Send. As an approximation, DocuSign points to each populated data row in the bulk template, excluding the header.

One uploaded file and one click can produce many signature requests. That compression is the feature’s value. The subscription follows the resulting envelopes while the operator remembers a single action. Budgeting by uploaded spreadsheets would measure the interface’s convenience rather than the service being consumed.

Workflow Builder supplies another route distinction. Starting a signature-sending workflow from the web or mobile application falls within the described web category. Starting it through a custom API or integration, when it sends for signature, falls within automation. For IAM Standard and Professional, the page also includes the corresponding third-party API and integration routes.

A Workflow Run has its own count: each trigger of a published workflow is a run. An API-started workflow that sends for signature can therefore engage both its run count and its Automation Send count. “Workflow” is a useful word for organising the project, but too broad to stand alone in the quantity column.

A Web Form or PowerForm counts as automation when it results in a send for signature. Opening a form and producing that send are different events. The useful operational record follows the event that defines the purchased unit.

The presence of a person or a browser cannot settle the classification. A person can initiate Bulk Send, which belongs to automation. An eligible Workflow Builder send can begin from the application and fall within the web category. The contract is interested in the particular path and result, not the furniture around the screen.

Ten seats buy a pool, and the term changes its shape

The sales-channel page describes allowances pooled across purchased seats. Its own examples are precise: ten full users on a one-year subscription confer 1,000 Automation Sends over that year. Ten users on a three-year subscription confer 3,000, available at any time during those three years.

For seasonal work, availability across the term matters. The described multiyear pool can be used across that period. Dividing an annual quantity by twelve and inventing a monthly ceiling would substitute a different rule. The plan needs the remaining term, remaining allowance and expected peaks on the same calendar.

Pooling also distributes a project’s consequences. One department can save staff time while its integration consumes capacity shared with other departments. The project can succeed and still reduce the stock available to everyone else. Reporting hours saved alongside the change in the common pool gives the buyer both results.

The page expressly covers sales and partner purchases and directs website purchasers to the public pricing page. The purchase channel therefore belongs among the facts about a subscription. A plan name alone leaves part of its commercial identity missing.

Higher plans have dated distinctions too. For IAM Enterprise, IAM for Sales and IAM for CX with an Order Start Date on or after 20 February 2026, the page specifies a separate third-party integration allowance of 200 sends per user per year, pooled at account level. Leaving one allowance can mean drawing from another.

The website has a present; the order has a version

The IAM service schedule dated 15 September 2025 describes a prepaid subscription subject to the Order Form. It makes the applicable version of the linked plan description the one effective when the Order Form is executed. That execution date serves a different purpose from the Order Start Date used in particular allowance changes.

The same schedule provides for per-feature overage fees beyond the agreed Feature Count, at the applicable list price or another amount specified in the order or plan documentation. A money calculation needs the actual additional-unit quote and measured manual time removed. Those figures let the buyer compare saved labour and purchased capacity on the same basis.

The Reasonable Use Policy also provides for possible additional fees and, in rare circumstances, restrictions in the situations it describes, including use outside subscribed allowances or material effects on normal operation, security or integrity. An unlimited subscription category remains a paid service with usage rules.

DocuSign makes ordinary application sending generous and allocates separate capacity to routes that remove repeated human steps. Automation can be a very good purchase. Its economics become clear when the buyer follows the work across that commercial boundary. The click disappears from the employee’s day; its replacement unit knows the way to procurement.