White-label eSignature for your platform and your customers.
Most “white-label” signing means your logo on someone else’s page. For a platform, that is one layer short. Verdocs powers the workflow, you own the offering and its price, each of your customers signs under their own brand, and none of it says Verdocs.
Four layers, one signing workflow
Multi-tenant white-label eSignature means the branding is set at every layer of the chain, not once at the top. Here is the chain for a lending platform.
- 1
Verdocs powers the workflow
Envelopes, templates, signing, identity, certificates, audit trails, and the compliance program behind them.
What the signer seesInvisible to everyone below this line.
- 2
Your platform owns the offering
You decide what it is called, what it costs, which plan it lives in, and who supports it.
Lending exampleA loan origination platform adds signing as a feature of its own product.
- 3
Your customers deliver signing under their brands
Each business on your platform sends and collects signatures as itself.
Lending exampleClosing documents arrive from the borrower’s own bank, not from the platform and not from us.
- 4
Their customers sign
On a page in the institution’s logo and colors, with a certificate that carries the institution’s name.
Lending exampleThe borrower signs with the bank they chose.
One workflow, three brands that matter to someone, zero that are ours.
Keep the integrations you have. Add an offering you own.
If your product already integrates DocuSign, Adobe Acrobat Sign, or another provider, that integration and a platform-owned eSignature product do different jobs. You can run both.
An integration connects a customer who already pays a vendor to the vendor’s signing experience from inside your product. It is the right answer for customers who have chosen that vendor, negotiated an enterprise agreement with it, or standardized on it across departments. Take nothing away from them.
A platform-owned offering is a product you sell. Customers who have no signing vendor, or who would rather buy signing from you as part of the software they already run, choose it. It carries your name, your price, and your support desk, and every envelope it sends is a line in your revenue, not in a vendor’s.
| Customer-connected integration | Platform-owned offering | |
|---|---|---|
| Who holds the eSignature subscription | Your customer, with the vendor | You, with Verdocs |
| Whose brand the signer sees | The vendor’s, or the vendor’s with a logo | Your customer’s, at every layer |
| Who sets the price your customer pays | The vendor | You |
| Who the customer calls for help | The vendor, usually | You |
| Best for | Customers standardized on a vendor | Customers who want signing from you |
Your product decides which option a customer sees, the same way it decides which payment processor or which document storage a customer has connected. Verdocs does not route between providers or manage another vendor’s integration; it is the engine behind the offering that is yours. For how integrated and embedded signing differ in the product itself, the decision guide covers it. For the objection in full: why an existing integration and an owned offering are not the same decision.
Partner-centric, in practice
“We sell through you, not around you” is a division of labor, not a slogan. This is the division.
Verdocs provides
The signing infrastructure: API, webhooks, 75+ web components, the embedded builder
Legally valid in 50+ countries and 60+ jurisdictions, SOC 2 Type I, HIPAA compliance
Per-customer organizations under your account, with usage reported per customer for your billing
Envelope-pack pricing to you, with no per-seat fees and every capability on every plan
Engineering support to you, and a sandbox for your team
You own
The product: its name, its place in your plans, its price to your customers
The customer relationship, the contract, and the invoice
First-line support, the way you support every other feature you sell
The packaging: an add-on, a premium-tier inclusion, a usage rate, or a bundled allowance
The margin between what your customers pay you and what your envelopes cost
Verdocs bills you for envelopes. How you bill your customers is your decision and your billing system’s job; Verdocs gives you the per-customer usage to do it and stays out of the invoice. The four packaging approaches, with where each fits, are worked through in how platforms monetize eSignature as their own SKU.
Every layer keeps its brand
White-label here covers the whole lifecycle, and it is set per customer, not per platform.
Your customers create and edit their own templates inside your product. The builder ships as components, so it looks like your product and not like a vendor’s tool.
Each customer’s signing requests can send from that customer’s own email domain and sender name, verified through standard SPF, DKIM, and DMARC records. In the inbox, the request comes from the bank, the agency, or the firm.
The signing page renders in your product’s DOM, on your domain, in each customer’s logo and colors.
Disclosures, certificates of completion, and tamper-evident audit trails carry the customer’s brand from consent to completion.
The mechanism is ordinary and documented: each of your customers is an organization under yours, each organization carries its own brand and email settings, and a customer without its own brand inherits your default. Web components, not iframes: override any control, style with standard CSS, and mit-licensed sdks on github and npm, so nothing about the experience is a black box. The full structure, and what to call it when you explain it to your own customers, is in multi-tenant white-label eSignature: branding at every layer.
The economics, illustrated
Illustrative, not a quote or a forecast. Assumes a platform with 200 customers, a signing add-on priced at $40 per customer per month, 10,000 envelopes a year in total, and the published Professional pack at $7,500 a year. Actual volume, attach rate, and pricing are yours to set and will differ.
The same envelopes on a per-seat vendor contract are a cost your customers pay to someone else. Price signing into your product and they become a revenue line. Model it on your own numbers in the ROI calculator, and see the pricing page for the packs the example uses.
Where an existing integration still wins
Some of your customers will keep their vendor, and should: an enterprise agreement already paid for, a contract lifecycle system built around it, a procurement team that has approved one name. A platform-owned offering does not need those customers to switch. It needs the rest of your base, the customers who would rather buy signing from you, to have the option. For an honest account of when the incumbents are the better fit, the comparison pages for DocuSign and Adobe Acrobat Sign say so.
Common questions
We already offer a DocuSign integration. Why would we add a Verdocs-powered offering?
Because they serve different customers. The integration serves customers who already pay DocuSign and want to use it from inside your product. A Verdocs-powered offering is a product you sell, under your brand and at your price, to customers who would rather buy signing from you. Keep the integration; add the offering.
Why an integration and an owned offering are different decisionsDoes Verdocs route between our existing provider and the Verdocs-powered offering?
No. Your product decides which option each customer has, the same way it handles any other connected service. Verdocs powers the offering that is yours and does not manage other vendors’ integrations.
Integrated versus embedded, in the decision guideCan each of our customers have their own branding, including the email sender?
Yes. Each of your customers is an organization under your account with its own brand: logo, colors, and email settings, including sending from that customer’s own verified domain. A customer without its own brand inherits your default. Signers see the institution they chose, not the platform and not Verdocs.
What each layer needs to carry its own brandHow do we bill our customers for signing?
However you choose: a separate add-on, inclusion in a premium tier, a per-envelope rate, or a bundled allowance. Verdocs bills you for envelopes and reports usage per customer organization so your billing system can pass it through. Verdocs does not bill your customers.
Four ways platforms package and price signingWhat does Verdocs charge us?
Pre-paid envelope packs with no per-seat fees, from $1,500 a year for 1,000 envelopes, with volume rates scaling to a published floor of $0.20 an envelope on enterprise agreements. Every plan includes the whole platform, white-labeling included.
See the pricing pageIs multi-tenant white-label the same as having many signers on one document?
No. Multi-tenant white-label is about brands: your platform’s, and each of your customers’. The number of people who sign a given document is routing, and Verdocs supports parallel and sequential signers regardless of how the document is branded.
Brand layers versus signer counts, explainedMore questions? The full FAQ lives in the developer docs, from API auth and webhooks to eIDAS signature levels.
See it in your customers’ brands.
Book a demo and we will walk through the layers with your product and one of your customers as the example. Or start for free and send a branded envelope from the sandbox today.