Does Salesforce Have Built-in E-Signature? What Ships, What Doesn’t, What It Costs

Updated 30 September 2026

Does Salesforce have built-in e-signature? For sales documents, no. Sales Cloud, Service Cloud and CPQ do not include a way to send a proposal, quote or contract to a customer for a legally recognised electronic signature. Signing in Salesforce always comes from an app installed on top of the platform, and the choice of app decides what the signature costs, where the signed PDF ends up, and whether your reps ever have to leave the record to get it.

This guide explains what Salesforce does and does not ship with, why the platform has never added e-signature of its own, the four ways teams add it, and what each route costs for a Salesforce team in 2026.

What Salesforce gives you out of the box

It helps to separate three things that often get lumped together as “e-signature in Salesforce”.

• Quote Templates. Sales Cloud can render a PDF quote from the Quote object using standard layouts. The PDF can be emailed from the record, and it can include a printed signature line, but nothing on the platform lets the customer sign it electronically or returns a signed copy to the Opportunity.
• Field Service signature capture. The Field Service mobile app lets a technician collect a drawn signature on a service report at the end of an appointment. It is designed for confirming work was done on site, not for sending a contract to a buyer, and it has none of the identity, audit trail or sequential signing features a sales agreement needs.
• Salesforce Contracts and Revenue Cloud. These manage contract records, clauses and obligations inside Salesforce. When it comes to the signature itself, they hand off to an integrated partner such as DocuSign or Adobe Acrobat Sign rather than signing natively.

The pattern is consistent: Salesforce owns the data and the workflow, and leaves document generation and signing to its ecosystem. That is the same reason there is no built-in proposal builder. Our guide to Salesforce document generation covers the generation side of that gap in detail.

Why Salesforce has never added native e-signature

E-signature is a regulated, jurisdiction-specific product. A signature that stands up in a UK or EU dispute needs to meet eIDAS; in the United States it needs to satisfy the ESIGN Act and UETA; and in every case the provider has to keep tamper-evident audit trails, certificates and identity evidence for years. Salesforce’s strategy has been to certify partners for that work through the AppExchange security review rather than to build and maintain a signing service across every market it sells in. DocuSign has been one of the most installed apps on AppExchange for over a decade, which tells you how settled that arrangement is.

The practical consequence for a revenue team is that “Salesforce e-signature” is a buying decision, not a setting. You will be choosing an app, a plan and a licence model, and the differences between them are larger than they look.

The four ways to add e-signature to Salesforce

1. A document and signing app that works inside Salesforce

Apps in this category run inside the Lightning record page and combine document generation, engagement tracking and e-signature in one workflow. The rep opens the Opportunity, generates the proposal or contract from a template, sends it, and the signed PDF, status and timestamps write back to the record without a separate connector. SalesSign is built this way: the builder and the signing ceremony are part of the same app, Salesforce login is used throughout, and signing is included on every plan rather than licensed separately. This is the route for teams that want proposals and signatures to be one motion.

2. A dedicated e-signature vendor with a Salesforce connector

DocuSign eSignature for Salesforce and Adobe Acrobat Sign for Salesforce are the established options. Both are strong signing products with mature Salesforce apps, but the connector is a second product with its own licence and its own plan requirement, documents are still generated somewhere else (or with a separately licensed generation add-on), and pricing is per envelope allowance. Our DocuSign Salesforce integration guide walks through the setup and the plan tiers involved.

3. A low-cost signing tool that includes Salesforce on a mid tier

Dropbox Sign includes its Salesforce integration from the Standard plan, and SignNow lists Salesforce with its usage-priced Site License. These are good-value choices for teams that only need signatures on fixed PDFs and are happy to build the document in Word or Google Docs first. They do not generate the document from Salesforce data, and engagement tracking is limited to “viewed” and “signed”. See how Dropbox Sign works inside Salesforce, including its template and text-tag rules.

4. Build it yourself with Flow and a signing API

Every major signing vendor exposes an API, and a Salesforce developer can call it from Flow or Apex, then poll or receive webhooks for completion. This gives you complete control over the user experience, but you own the integration forever: API plans start at hundreds of dollars a month, every vendor change is your problem, and you still need a way to produce the document in the first place. It is the right answer for a handful of very large teams and the wrong one for almost everyone else.

What e-signature in Salesforce costs in 2026

Two things stand out. First, only two of the six options generate the document from Salesforce data at all, and only one does so inside the record without a second application. Second, the “free” signature in a bundled suite is rarely free for a Salesforce team: the Salesforce plan tier, the connector and the envelope allowance are where the cost lives. For a ten-user team, the difference between the cheapest and dearest route above is several thousand pounds a year before anyone sends a document.

What to check before you choose

1. Where does the signed PDF land? It should attach to the Opportunity, Account or Contract automatically, with the signing status and timestamps on fields you can report on and build Flows from. If the audit trail only lives in the vendor’s portal, your CRM is not the source of truth.
2. Does the rep leave Salesforce? Every tab switch is a place a deal stalls. Apps that work inside Salesforce keep the whole motion on the record; connectors open a second product.
3. Is the document generated from the record? If prices are retyped into a Word template, they will drift from the Opportunity Products. Merge fields and locked pricing tables prevent it.
4. What does the buyer see? Test the signing ceremony on a phone. Sequential and parallel signing, a branded experience and a clear audit certificate all matter to the person on the other side.
5. What is the all-in seat price? Add the plan tier, the connector, any generation add-on and the envelope overage together. Compare it with your realistic envelope volume, not the vendor’s headline.
6. Is the signature legally binding where you sell? All of the vendors above meet eIDAS and ESIGN for standard commercial agreements. Read our plain-English guide to whether e-signatures are legally binding for the exceptions.