CLM, e-signature and doc gen - all on Salesforce.

Yes. Templates, signer routing, audit history, executed PDFs and admin configuration all live inside your Salesforce org. There is no third-party server, middleware or separate signer database. Every contract attaches to the Salesforce record it belongs to.

Yes. The WYSIWYG editor handles formatting, merge tokens, sub-templates, conditional clauses, repeating tables and signer routing without code. Admins build templates the same way they'd build a Word document - just with live Salesforce data flowing through.

Merge tokens look like {Contact.FirstName} or {Opportunity.Amount | currency}. They reference any Salesforce field on any object in scope. The editor color-codes them by source: lavender for Signer 1, peach for Signer 2 (more colors for additional signers), and sky-blue for system-merged record data. Misrouted fields are visible at a glance, so authors can't accidentally ship a contract that asks the wrong person for the wrong information.

Sub-templates are reusable contract fragments - DPAs, exhibits, indemnity clauses, SLAs, regional schedules. You build them once, then reference them from any parent template, optionally with conditions. For example: include the EU DPA only when Account.Region = 'EU'. When the sub-template changes, every parent inherits the update on the next merge.

Yes. Drop in any PDF, drag signature, initial, date, text or checkbox fields onto each page, assign them to specific signers, and send. The same routing, authentication and audit-trail features apply - you don't need to rebuild it as a template first.

Point Doc Studio at any Salesforce report, list view or Apex query. Pick a template. Doc Studio runs asynchronously on platform-native batch infrastructure, generating and (optionally) sending one document per row. Sub-templates and conditional clauses evaluate per row, so every output is bespoke even though the job runs in bulk. There are no per-envelope fees and no rate limits - bulk send 100 contracts or 100,000.

Yes. Doc Studio supports any number of signers per document, with sequential, parallel or hybrid routing. Each signer can have a different authentication method (SMS, email, KBA, geo-fence) and a different field assignment. You can even add or remove signers mid-flight.

Yes. Doc Studio produces eIDAS- and ESIGN Act-compliant signatures. Every executed PDF is sealed with a tamper-evident hash and accompanied by a full audit certificate listing every signer event, IP, timestamp, authentication method and (optionally) GPS coordinate.

Every signer event, status change, version, redline, approval and clause edit writes back to Salesforce - typically into a custom Contract object's field history and a related Audit Event object. That means your audit story lives in the same database as your contract data, queryable with standard Salesforce reports, accessible to your existing security model, and inheritable by any downstream system that already integrates with Salesforce.

Yes. Doc Studio fires standard platform events - ContractDrafted, ContractSent, ContractSigned, RenewalApproaching - that you can hook into Salesforce Approval Processes, Flow, Process Builder or Apex. Route contracts above $250K to the CFO, escalate stalled negotiations after 14 days, push signed contracts to your ERP - all without leaving the platform.

Absolutely. Time-to-sign by template, redline cycles by counterparty, upcoming renewals by quarter, blocked approvals by stakeholder - every metric is a Salesforce report away. No BI tool, no data warehouse, no exports.

Key dates and clauses (renewal date, notice period, indemnity caps, exclusivity windows) are captured as structured Salesforce fields during template authoring. Schedule a Salesforce Flow to fire 90 days before any renewal - auto-generate the renewal contract, route to the relationship owner, escalate to legal if untouched after 30 days. Renewals never come as a surprise.

They don't need one. Counterparties redline, review and sign via secure email links - no account creation, no app install, no license. The submission still writes back to Salesforce, fully audited.

Yes. Built on Salesforce's platform-native batch infrastructure with asynchronous processing, retry logic and live progress monitoring. Customers regularly bulk-merge 5,000 to 50,000 contracts in a single job, and run continuous renewal pipelines without throttling.