How Vertical SaaS Platforms Monetize eSignature as Their Own SKU
Verdocs Team
A vertical SaaS platform can relate to eSignature in two ways. It can connect its customers to a signing vendor they pay separately, or it can sell signing itself, as a SKU on its own price list, powered by infrastructure it licenses. The first is a convenience. The second is a product, and it carries revenue, margin, and a customer relationship the first never will.
This post is about the second: what "partner-centric" means when a vendor actually operates that way, the four ways platforms package signing, an illustrative example with every assumption stated, and what the model requires from the infrastructure underneath.
Connecting is not selling
When your product connects a customer's DocuSign or Adobe Acrobat Sign account, the customer is that vendor's customer for signing. The vendor sets the price, sends the invoice, answers the support ticket, and books the revenue. Your platform contributes an integration and receives, at best, a referral fee and a checkbox on a feature list.
When your product sells signing, the customer is your customer for signing. You set the price, send the invoice, answer the ticket, and book the revenue. The infrastructure vendor bills you for what you use, the way a payment processor bills a platform that has built payments into its product.
Both can exist in one product, and for most platforms they should, because they serve different customers: an existing integration and an owned offering are not the same decision. The rest of this post is about the owned offering.
What "partner-centric" means, operationally
A partner-centric eSignature vendor is one whose business is selling through platforms rather than to their end users, and whose product and pricing are built for that. In practice the roles divide like this:
| Responsibility | Infrastructure vendor (Verdocs) | Platform (you) |
|---|---|---|
| Signing workflow: envelopes, templates, signing, identity, certificates, audit trails | Provides | Configures and embeds |
| Legal validity and compliance program | Maintains | Inherits, and adds any vertical obligations |
| Product name, positioning, place in plans | Owns | |
| Price to the end customer | Sets | |
| Contract and invoice with the end customer | Holds | |
| First-line support | Supports the platform | Supports its customers |
| Per-customer usage data | Reports | Bills against |
| Branding the signer sees | Renders what is configured | Configures per customer |
Two consequences follow. The vendor never appears on your customer's invoice or in your customer's inbox. And the vendor's revenue grows only when yours does, which is what "we sell through you, not around you" means on a balance sheet.
Verdocs works this way: platforms buy envelopes in pre-paid packs with no per-seat fees, every customer is an organization under the platform's account with its own brand, and usage is reported per organization for pass-through billing. Verdocs does not bill your customers and does not provide a billing engine; your billing system does that, with the usage data to do it.
Four ways to package signing
None of these is right in general. Each fits a price list and a customer base.
1. A separate add-on. Signing is a line item a customer turns on, priced per month or per year. Simplest to explain and to attribute revenue to. It fits platforms whose customers vary widely in whether they sign anything, so a flat inclusion would overcharge some and undercharge others. Risk: an add-on must be sold, and features that must be sold get lower attach than features that are present.
2. Inclusion in a premium tier. Signing is one of the reasons to move from Standard to Professional. No separate SKU; the revenue shows up as tier mix and as a lower discount at renewal. Fits platforms whose premium tier needs a tangible, demonstrable reason to exist. Risk: heavy signers in the premium tier consume envelopes without paying for them directly, so the tier price has to carry an assumed volume.
3. Usage-based pricing. Customers pay per envelope, or per envelope above an allowance. Aligns cost and revenue perfectly and is the natural fit where document volume is the customer's core activity (a lender's closings, an agency's policies). Risk: usage pricing is harder to forecast for both sides and needs metering you trust.
4. A bundled allowance. Every plan includes a number of envelopes; more are available in blocks. A hybrid of the second and third that lets you say "signing included" while charging the heaviest users. Fits platforms where most customers sign a little and a few sign a lot.
Platforms often combine two: an allowance in every tier, plus a per-envelope rate above it, or an add-on for small plans and inclusion in the top tier. Whichever you choose, the underlying cost should be usage-based on your side so that margin holds at every mix; a per-seat cost cannot be packaged any of these four ways without either overcharging or losing money.
An illustrative example, with the assumptions on the table
This example is illustrative. It is not a customer result, a forecast, or a quote. Change any assumption and the outcome changes.
Assumptions:
- A lending platform with 200 customer institutions.
- Signing sold as a separate add-on at $40 per institution per month, taken by every institution (a 100 percent attach rate, which is unrealistic and chosen only to keep the arithmetic legible; halve it and halve the revenue line).
- 10,000 envelopes a year across all institutions, or about four per institution per month.
- Envelope cost at the published Verdocs Professional pack: 10,000 envelopes for $7,500 a year ($0.75 an envelope). Identity add-ons (KBA, ID scan, SMS) excluded; add them per use where the documents require them.
- No allocation of your support, engineering, or sales cost, which is real and yours to estimate.
| Line | Amount | Basis |
|---|---|---|
| Add-on revenue | $96,000 | 200 x $40 x 12 |
| Envelope cost | $7,500 | published pack |
| Gross margin on the feature | $88,500 | before your own operating costs |
| Effective cost per envelope | $0.75 | published pack rate |
| Effective revenue per envelope | $9.60 | $96,000 / 10,000 |
The point is not the specific numbers, which depend entirely on what you charge and how much your customers sign. The point is the shape: envelope cost is a small, usage-based number, and the revenue is a product price you set. The ROI calculator models the same shape on your own inputs, and the pricing page carries the packs.
Now the alternative for the same platform: 200 institutions each holding a per-seat contract with a signing vendor, at that vendor's list price, with the platform earning nothing and fielding questions about a bill it does not control. The cost saving to the institutions of buying signing from the platform instead can be considerable, and the comparison pages carry a labeled illustrative range for DocuSign and others. But the saving is the supporting argument. The lead is the $96,000 that is now on your price list.
What the model requires from the infrastructure
Packaging is your decision. Whether it can be executed at a margin depends on five things about the provider, and they are worth checking before the pricing meeting.
Usage-based cost to you. Envelope or transaction pricing, not seats. Your cost must scale with your customers' activity, which is what you can pass through, rather than with your headcount or theirs.
Per-customer metering. Every packaging option above except pure tier inclusion needs to know which customer sent which envelope. The provider has to model your customers as distinct organizations and report usage for each. In Verdocs, customers are child organizations under your parent organization, and the usage endpoint returns daily and monthly usage per organization for pass-through billing.
Tenant-level branding. A SKU you sell has to look like your customer's product to your customer's signers, or you are reselling a vendor's experience. That means each customer's logo, colors, and email sender, not one logo for the platform. Multi-tenant white-label eSignature: branding at every layer covers what that requires.
No feature ladder. If white-label, API access, or webhooks sit on the provider's top tier, your cost floor is that tier and your smallest customers are unprofitable. Every Verdocs plan is the whole platform.
Permission to resell. Confirm it in writing. Some vendor programs are built for it; others license signing for a company's own use and treat resale as a separate agreement with separate economics.
What you take on
Selling a product means owning it. Three obligations come with the revenue.
Support. Your customers call you, and your team needs enough of the product to answer first-line questions before escalating. Component-based infrastructure that renders in your product helps here, because your support team can see what the customer sees.
Compliance roles in regulated verticals. A platform that white-labels and resells software can acquire regulatory duties the vendor cannot take on for it. The clearest documented case is tax software, where the IRS treats resellers as intermediate service providers; who is responsible when eSignature is embedded in tax software works through it. Lending, insurance, and healthcare each have their own version of the question. Price the SKU after you know the answer for your vertical.
Pricing discipline. The margin in the example is wide because envelope cost is low relative to a software price. That margin is an invitation to underprice, and a signing add-on priced at cost plus a little is a support obligation without a business. Price it as the product it is.
Common mistakes
Treating the integration as the product. Connecting a vendor earns a checkbox. Only an owned offering earns revenue.
Buying per-seat infrastructure and trying to resell it. The cost scales on the wrong axis and the margin disappears as customers add staff.
Skipping tenant branding to launch faster. The first customer to see a vendor's name, or the platform's name, on an email to its own client will ask why, and the answer costs more than doing it first.
Leading with the saving. Your customers care that signing is in the product they already use and carries their brand. Your board cares that it is a SKU. The saving supports both stories and leads neither.
Frequently asked questions
Does Verdocs provide billing for our customers? No. Verdocs bills you for envelope packs and reports usage per customer organization. Your billing system charges your customers according to whatever packaging you choose.
Can we set any price we want? Yes. The price your customers pay for signing is yours to set, in any of the packaging forms above or a combination.
What happens if a customer sends far more envelopes than we planned for? Your envelope cost rises at the pack rate for the volume, and volume rates scale down to a published floor of $0.20 an envelope on enterprise agreements. Whether the customer pays more depends on your packaging; usage-based and allowance models pass it through, a flat inclusion does not.
Is this the same as a referral or reseller partner program? No. Referral and reseller programs pay a commission on the vendor's sale to your customer, under the vendor's brand. Selling signing as your own SKU means the sale is yours and the vendor is your supplier. Verdocs also runs a partner program for consultancies and integrators; it is a different relationship.
Where to go next
The combined offering, with the layer structure and the coexistence with existing integrations, is summarized on the white-label eSignature page. To model the example on your own volume and prices, use the ROI calculator. To see a branded envelope from your sandbox before any conversation, start for free.
