Category thesis
Signing a document has become a backend workflow. It is triggered by CRMs, onboarding systems, payment flows, APIs, and automation tools. It should be priced like infrastructure, not like 2000s enterprise SaaS.
E-signatures used to be bought as a department tool. A sales team, legal team, HR team, or operations team would buy a fixed number of seats, send documents manually, and manage the process inside a standalone product.
That world still exists. But a growing share of signing now starts somewhere else: a workflow, an API call, a CRM status change, a form submission, a payment event, or a product action.
At that point, signing is no longer just a SaaS application. It is infrastructure.
Twilio does not ask how many employees can send SMS. Stripe does not charge by how many people work at your company. Cloudflare does not price CDN traffic by department.
So why do signature tools still charge more every time another teammate needs access?What changed
The signing event is increasingly a step inside a larger system, not the destination itself.
A deal closes in the CRM and a contract is sent automatically.
A new hire enters onboarding and an offer letter or NDA is triggered.
A user reaches a compliance step and a disclosure packet is generated.
A customer action inside the product creates an embedded signing flow.
A vendor, lease, waiver, or approval packet moves through a workflow.
An agent prepares a document and routes it for human signature.
Old model
Works for procurement. Gets awkward when signing becomes a workflow primitive.
Infrastructure model
Better for developers, startups, operations teams, and automation-heavy businesses.
The important caveat
Legal documents create a trust problem. If a signing tool is dramatically cheaper, the first reasonable question is: what was cut?
The answer should not be auditability, security, or document integrity. The answer should be: the seat-based pricing model.
That is why infrastructure signing still needs evidence: signer events, timestamps, IP and user-agent context, consent records, signed PDFs, document hashes, certificates, API authentication, and signed webhooks.
We think e-signatures are becoming a primitive for business software. They should be easy to send from a dashboard, easy to trigger from an API, easy to automate from tools like n8n, and easy to verify after the fact.
That leads to a different product shape: unlimited team members for human workflows, usage-based API signing for programmatic workflows, and trust evidence that travels with the completed document.
VisiSign is built around that assumption. Team signing is $49/month. API-only signing is $0.10/request with no monthly fee.
Start with flat-rate team signing, API-only signing, or both.