BreezeDoc lifetime deal

Choose the paid feature, not an assumed document upgrade

Individual costs $19 once. Reminders, customized signing emails and a redirect after signing are clear reasons for a solo business to consider it. Agency costs $49 and adds shared team work, 10 members per team and a custom logo.

The document-volume decision is currently less clear. The AppSumo purchase page and September help reference list 20 sent documents per calendar month for Individual. The vendor’s current pricing page and homepage now advertise unlimited documents on every plan, including Free. This page keeps the AppSumo allowance in the purchase table and flags the disagreement instead of silently granting a broader entitlement.

If volume or API access is the only reason you would pay, inspect the current Free account offer and ask which limit applies to your account before upgrading. Free has no automatic reminders or custom sending email in the current pricing comparison. Agency is easier to justify for shared work than for an unconfirmed need to remove a document cap.

Count separate agreements, not signatures or drafts

Under the capped workflow described by the help centre, a document counts when it is emailed or when its signing links are generated. Drafts, unsent clones and templates do not consume the allowance. The calendar-month counter resets on the first and unused capacity does not carry over. Multiple signers on one agreement are different from multiple separate agreements.

For example, sending a proposal, service contract and change request to each of eight clients produces 24 documents. That exceeds the AppSumo-listed Individual allowance even though there are only eight clients. Use this calculation only if the capped terms apply to your account; the newer unlimited pricing language must be clarified.

BreezeDoc does not currently provide native bulk sending or a shared public link that creates a fresh signed copy for everyone. The September founder answer suggests a template copy for each recipient, manually or through the API. A registration campaign can therefore add setup work and API throughput limits even on an unlimited-document plan.

Signing order is enforced by emails, not every direct link

The standard email flow contacts the first party, then emails the next after the preceding signer finishes. If you manually share a later signer’s direct signing link, that person can open it before their turn. Do not use such links as evidence of a locked sequential approval process.

A document view link is also not the same as a signer’s link. Give each recipient only their own signing link and use a clear document title. The founder says document search matches titles, not names entered inside the signed fields; a naming scheme such as client, purpose and date makes retrieval more reliable.

The ordinary editor guide sets an upload limit of 5 MB and supports PDF, Word, Excel, JPG and PNG. For long documents, each signature field must still be placed page by page; the founder says there is no one-click field placement across every page. A signer creates their signature once, but that does not remove the sender’s field-setup work.

Agency removes the logo, but a copyright footer remains

The Agency table says no BreezeDoc branding. A September 23 founder answer narrows that claim: the BreezeDoc logo is removed and your logo can appear, but the copyright text remains in recipient emails with no setting to remove it. If complete white-label delivery is essential, Agency does not clearly satisfy it as documented.

Paid automatic reminders run about every three days, up to three per signer, and stop once the signer finishes. The standard reminder interval is fixed. A separate expiry reminder is documented three days before the deadline. If your process needs escalation after a specific number of hours or a manager notification, confirm that workflow separately.

Several April–May reviews report email delivery trouble, and a September reviewer describes domain blocks. A founder response says a particular link-generation/email-cancellation bug was fixed in August; that does not demonstrate that every delivery complaint is resolved. Before moving time-sensitive work, evaluate delivery to the actual kinds of recipient inboxes you use and keep a direct-contact fallback.

Match automation to the API version your account can use

The September help guide describes the established API with 60 requests per minute, 100 document creations per day and 20 document sends per hour. It says tokens expire after a year and status changes must be polled because that API has no webhooks. API access does not remove a plan’s sending allowance or those throughput caps.

A newer developer page, explicitly labelled Developer Preview and dated October 23, describes a different team-scoped API, signed webhooks and an OAuth MCP connection for AI assistants. It also documents a 25 MB PDF limit and a 100-page cap for that preview upload route, compared with the standard editor guide’s smaller upload allowance. Those are version-specific descriptions, not permission to assume the same limits everywhere.

The preview is a reason to ask about account access, not to claim BreezeDoc has no automation improvements. Confirm the enabled API, team ownership, production readiness and entitlement before building around webhook or MCP delivery. External automation tools, hosting and an AI assistant may have separate costs.

Check the required identity step before choosing a signer tool

A passcode is available per recipient, but you supply and share it yourself. The founder explicitly says BreezeDoc does not send one-time verification codes or provide a separate dedicated approval flow for specific contract clauses. Additional signature/initial fields can be placed, but they are not the same feature as an identity-verification service.

Completed documents include an activity record and a completion certificate according to the vendor. These features help retain a record; they do not establish that a particular document, organization or jurisdiction accepts this workflow. Keep requirements such as identity checks, retention and restricted access explicit when evaluating a replacement.

Older licences and payment collection need separate checks

A legacy plan can show a different allowance from today’s Individual or Agency. The current help guide preserves legacy limits, and a September 2026 founder reply says moving legacy Tier 4 to Agency is paid with the earlier purchase value deducted. A 2025 Reddit response from an identified AppSumo manager described legacy-update mapping differently. Resolve the entitlement on the actual account before paying again or promising a team upgrade.

No AI-credit system or recurring BreezeDoc licence fee is specified for the standard paid offer. Hidden cost here is more often workflow effort: field preparation, document conversion, an external automation service and payment-provider charges if you use invoicing. The newer website makes Stripe card collection a paid feature; older help lists Stripe and PayPal more broadly. Confirm payment availability and provider fees rather than treating invoicing as free payment processing.