The deal runs in Salesforce. The paperwork should too.

Most engagements run six to eight weeks across four phases — discovery and field mapping, template and logic build, integration and eSignature, then centralization and handover. The variable is how many document types and approval paths need mapping; a single proposal template on Opportunities sits at the short end, while multiple document types across CPQ and legal review sit at the long end.

Yes. PandaDoc for Salesforce creates documents from Salesforce CPQ Quote records, either as a generated PDF or as an editable document whose pricing table is filled from the quote lines, and it keeps quote status and document status in step. We connect it so quotes generate with live pricing and push straight into a signature-ready document without manual re-entry. PandaDoc also sells its own CPQ for Salesforce as a paid add-on for teams that do not run Salesforce CPQ; we scope that separately.

The Salesforce package runs on Professional, Enterprise, Unlimited and Developer editions, and the integration is available on PandaDoc's Business and Enterprise annual plans. The part that catches teams out is two-way sync: writing status and field values back to Salesforce needs API access, which means Enterprise edition or Professional with the API add-on. On Professional without API access you can still generate documents from Salesforce, but nothing syncs back. We confirm both edition and plan in discovery so the write-back you are counting on is actually available.

Configuration covers everything the standard package supports through settings: token and field mapping, pricing tables from Products, Quote lines or CPQ, conditional content, approval routing, and status and field write-back. Automating creation and sending on a stage change is low-code work in Salesforce Flow Builder using PandaDoc's actions. Custom development starts when a document needs data from several related records merged through a custom JSON builder, when it must generate from an object the package has no relationship to, or when a completed contract has to create an invoice or ERP record. We put every requirement on one side of that line during discovery.

Yes. PandaDoc's electronic signatures are built to comply with the US ESIGN Act and UETA and with the EU's eIDAS regulation, and every completed document carries a digital certificate and an audit trail recording signer identity, timestamps and IP address. That is what makes the signature enforceable; what we add is the routing and record-keeping in Salesforce so the signed document and its evidence are filed against the deal, not in someone's inbox.

Yes, with the right plan and configuration. PandaDoc holds SOC 2 Type II certification, supports GDPR requirements, and offers HIPAA-compliant features with a Business Associate Agreement for eligible enterprise customers. Compliance is then a matter of implementation: which fields are allowed into a template, who can approve and send, how signed documents are stored, and what Salesforce sharing rules govern access. We configure those controls to match your compliance requirements rather than the platform defaults.

It depends on what is already in the org and what the document has to do. PandaDoc combines generation, approval, eSignature and status sync in one package, which suits sales teams that want the whole quote-to-signature loop in a single tool. Conga Composer is the stronger choice when documents are complex, heavily formatted merges across many related objects, and it pairs with a separate signature tool. DocuSign is a signature and agreement platform first, and the right answer when generation already exists and only the signing step needs fixing. We implement all three, so the recommendation follows your document mix, not our preference — see our Conga Composer and DocuSign pages for how each is delivered.