SignRequest Pricing: Tiers and TCO

You searched for "signrequest pricing" because finance asked what SignRequest actually costs after the free trial ends. SignRequest (now part of the wider SignRequest / Xodosign family in many markets) sells straightforward e-sign for SMBs. This page explains how tiers usually work, where hidden costs appear, and when usage-priced APIs beat seat bundles.

> Share: SignRequest pricing looks simple until you count bots and peak months separately.

What SignRequest Sells

SignRequest targets teams that want send-and-sign without DocuSign enterprise minimums. Typical product includes:

• Dashboard upload and send
• Templates for repeat documents
• Team folders and basic roles
• REST API on paid plans
• Branded signer emails

Pricing pages change by region and rebrand (SignRequest vs Xodo Sign branding). Always pull current list price from the vendor site before board slides.

How SignRequest Tiers Usually Price

SignRequest historically published per-user monthly plans with document caps. Higher tiers raise caps and add API access, custom branding, and team admin.

Web tiers charge per seat with envelopes included per billing cycle. Overage fees apply when sales exceeds the cap.

API pricing on paid tiers often still ties to the same account document limits unless you negotiate enterprise. Read fine print on whether API creates, sends, and completed signatures each count.

Total Cost Questions for Finance

Ask these before you sign an annual SignRequest contract:

• How many humans need dashboard login versus how many envelopes ship from code?
• Do sandbox or test sends count against quota?
• Are template-only storage seats billed separately?
• What happens in your peak month (fundraising, seasonal hiring, year-end renewals)?
• Does every Zapier or n8n retry consume a document credit?

Seat math punishes startups when five engineers each need API access but only send twenty envelopes total. Envelope math punishes when one automation account sends five hundred.

SignRequest Pricing vs DocuSign

DocuSign list price exceeds SignRequest for most SMB comparisons. DocuSign wins enterprise RFPs on brand and connector depth, not headline per-seat rows.

SignRequest wins when:

• No Salesforce mandate forces DocuSign
• Legal accepts SignRequest audit trail for your document types
• Volume stays in hundreds per month, not tens of thousands

DocuSign wins when:

• Procurement standardized on DocuSign language in MSAs
• You need deep Salesforce or CLM connectors
• Recipient authentication options exceed SignRequest scope

See DocuSign comparison for incumbent context.

SignRequest Pricing vs API-first Alternatives

Teams outgrow SignRequest pricing when:

• Cron jobs and agents send more than humans
• Per-seat caps block engineering from shared API keys
• Review-before-send on ad-hoc uploads needs custom glue

Usage-priced APIs charge per envelope sent, not per dashboard login. Atlas charges one credit per send after five free envelopes. Drafts and field detection are free.

curl -X POST https://atlaswork.ai/api/envelope \
 -H "Authorization: Bearer $ATLAS_API_KEY" \
 -H "Content-Type: application/json" \
 -d '{
 "document_url": "https://example.com/nda.pdf",
 "parties": [{"email": "signer@example.com", "name": "Signer", "role": "Customer"}]
 }'

Response includes review_url. Send consumes one credit. No seat for the cron job.

See SignRequest alternative for migration notes.

When SignRequest Pricing Makes Sense

• Small team sends dozens of contracts monthly from dashboard
• Finance wants predictable monthly line under DocuSign quotes
• Templates cover most document shapes with minimal API
• No agent or MCP send path on roadmap this quarter

When to Re-shop SignRequest Pricing

• Engineering owns more sends than sales reps
• Peak month blew through overage fees twice
• You need MCP tools for Claude without building OAuth wrapper
• Idempotent API retries spawn duplicate billable events

Hidden Costs Beyond List Price

Implementation hours. Template migration, webhook handlers, and CRM field mapping cost more than year-one license rows for many teams.

Admin time. Someone still chases signers, fixes wrong email addresses, and re-sends expired links.

Opportunity cost. Slow signing cycles delay revenue recognition. Price per seat ignores deal velocity.

Vendor lock-in. Annual prepay discounts trade cash for exit friction.

Sample Tco Worksheet

Build a spreadsheet with these rows for your actual peak month:

Compare three-year total, not month-one promo price.

Negotiation Tips

Ask SignRequest sales for:

• Annual cap with true-up instead of hard overage cutoffs
• API-only identity that does not consume rep seats
• Sandbox environment that does not debit production quota
• Exit clause if volume tier changes mid-contract

If negotiation stalls, pilot usage-priced API on one document type before rip-and-replace.

Atlas Pricing Contrast

Atlas model:

• Five free sends on signup
• One credit per envelope sent
• Drafts free
• Field detection free
• No per-seat minimum for API or MCP

Fit when SignRequest seat rows block shared automation keys.

Sign up to run envelope math on your peak month PDF.

FAQ

Is SignRequest the same as Xodo Sign?

Branding varies by region after acquisition moves. Confirm which entity bills your contract.

Does SignRequest charge per signature or per envelope?

Read current plan terms. Many SMB tiers count completed documents per period.

Can I use SignRequest API without dashboard seats?

Depends on plan. Ask sales explicitly before coding automation.

Does Atlas replace SignRequest org-wide?

Atlas fits dev-led and agent-led sends. Dashboard-first teams may keep SignRequest for reps during pilot.

PDF and DOCX on Atlas?

Both accepted at create. DOCX becomes PDF before signing.

Related Reading

• SignRequest alternative
• SignRequest API alternative
• BoldSign pricing
• Credit-based e-sign pricing