Feature · Esignature

Esignature on every deal, powered by DocuSign and PandaDoc.

Strkr does not try to replace DocuSign or PandaDoc. Strkr connects to them. Connect your existing account (or sign up fresh), send signature requests from the deal record, watch the completed PDF and the status events flow back automatically, and let Flows advance the pipeline the instant the last signer completes. The signature system of record stays with the provider. The deal system of record stays with Strkr.

Start free trial See pricing
How esignature works in Strkr

Your DocuSign or PandaDoc account, wired into the deal.

Esignature inside Strkr is not a separate product the CRM ships. It is a native integration pattern. You bring the DocuSign or PandaDoc account your legal team already approved (or sign up fresh if you do not have one yet), connect it to your Strkr tenant from Admin, and the connection unlocks signature workflows across every object that cares about contracts. Deals, renewal opportunities, HR records, partner agreements, custom objects. The user never leaves Strkr to fire an envelope, and the signed PDF comes back automatically with its event stream wired into the pipeline. For the signer, the experience is still DocuSign or PandaDoc, which is what your legal team already approved. For the rep, the experience is one click from the deal record. For RevOps, the experience is a reliable completion event that fires a Flow, not a Slack ping to chase a signed PDF.

Connect once

OAuth to DocuSign or PandaDoc from Admin.

Open Admin, Integrations, pick DocuSign or PandaDoc, click Connect, complete the OAuth consent flow, and the integration is live for the tenant. Multiple accounts per tenant are supported if different brands or regions sign under different provider accounts. No per-rep provisioning required.

Send from the deal

Signature request from the contract record.

Open the deal, pick the contract document, click Send for Signature, choose the provider, pick the signers from the opportunity contacts, and submit. The envelope is created in DocuSign or PandaDoc under your account, and the deal picks up a Pending Signature status without a separate app to open.

Status flows back

Viewed, signed, completed, declined events.

Every status transition on the envelope fires a webhook back into Strkr. The deal timeline logs the event, the pipeline stage advances or waits based on the Flow you configured, and the signed PDF plus the provider audit record land on the deal attachments the instant the last signer completes.

Signed PDF on the deal

Completed document attached automatically.

The provider stores the authoritative original and the certificate of completion. Strkr pulls a copy of the signed PDF and the certificate onto the deal record so your reps and CSMs see the executed contract on the opportunity instead of hunting through a separate signature inbox for it.

Deal auto-advance

Closed Won the moment the last signer signs.

Build a Flow that listens for the signature.completed event on an envelope tied to a deal and moves the deal to Closed Won, updates the renewal date, fires the implementation handoff, and notifies the delivery lead. The pipeline advance happens in the same minute the signer taps submit.

No separate signature inbox

Reps work out of Strkr, not out of DocuSign.

Pending signatures across the whole tenant surface inside Strkr as a list view scoped to the user. Reps nudge the slow signer with a one-click resend, legal sees the envelope status alongside the deal, and nobody logs into the provider admin console to run the day.

What the integration actually does

DocuSign and PandaDoc, wired to the Strkr object model.

A good integration does more than open a webhook endpoint. The Strkr integrations with DocuSign and PandaDoc map provider concepts (envelopes, documents, recipients, templates, tabs, status events) onto the Strkr object model (deals, contracts, contacts, Flows, custom fields) so the handoff is bidirectional and the data stays consistent. The result is that firing an envelope from Strkr looks the same whether the provider underneath is DocuSign or PandaDoc, and swapping one for the other does not require rebuilding your workflows.

Field prefill

Signer name, email, company, address.

When the envelope is created, Strkr prefills the standard provider recipient fields (name, email, title, company, address) from the opportunity, account, and contact records. The signer confirms rather than retypes. Fewer errors, faster signatures, no "the address on the contract is wrong" cleanup.

Template picker

DocuSign and PandaDoc templates, discoverable in Strkr.

Templates created in your provider account appear in the Send for Signature picker inside Strkr. Pick an MSA, Order Form, or renewal addendum template, map the provider roles to Strkr contacts, send. The template library stays owned by legal in the provider, surfaced to reps in Strkr.

Role mapping

Customer Signer, Internal Countersigner, Observer.

Provider template roles are mapped to Strkr relationship fields the first time a template is used. The next time a rep sends that template, Strkr already knows that Customer Signer equals opportunity.primary_contact and Internal Countersigner equals opportunity.owner.manager. No role-picker guessing per envelope.

Attachments from the deal

Pull the proposal PDF into the envelope.

The quoted proposal, the engineering appendix, the custom SLA. Any document already attached to the deal can be added to the signature envelope in one click. The signer sees one combined packet. No "please find attached the four PDFs that make up this contract" email thread.

Status back to Strkr

envelope.sent, viewed, signed, completed, declined.

Every provider webhook event lands as a Strkr event on the deal timeline. envelope.sent, envelope.viewed, envelope.signed (per signer), envelope.completed, envelope.declined, envelope.voided. Each event carries the envelope ID, signer identity, and timestamp. Flows subscribe to any event.

Signed artifact sync

Completed PDF and certificate pulled on completion.

When envelope.completed fires, Strkr pulls the final signed PDF and the provider certificate of completion onto the deal attachments. The provider remains the authoritative source. Strkr holds a convenience copy so reps and CSMs do not need provider logins to read the executed contract.

Decline + void handling

Rejections flow back as events, not surprises.

If a signer declines or an owner voids the envelope, the deal picks up the status change with the reason text attached. Flows subscribed to envelope.declined can roll the deal back to Negotiation, notify the AE, drop a task on the CSM, or kick off a legal review. Nothing silent.

Reminders handled by provider

Nudges fire from DocuSign or PandaDoc.

Reminder cadence is configured in the provider template or at send time. The provider sends the reminders from its own sending domain. The reminders show up as reminder.sent events in Strkr so the deal timeline logs the chase without the rep typing "just circling back on the contract" ever again.

Flows + esignature

Signature events as triggers for the whole motion.

The highest-leverage part of the DocuSign and PandaDoc integrations is not the ability to send an envelope. It is the ability to react to signature events the moment they happen. Every envelope event is available as a trigger inside Strkr Flows. That turns the signed PDF into the match that lights the rest of the revenue motion: Closed Won, renewal date seeded, delivery handoff, finance notification, customer success onboarding. One signer taps submit and the next ten things happen automatically. No rep touching a stage picker. No "I will update the CRM once I get back to my desk" delay.

envelope.completed

Move the deal to Closed Won automatically.

Flow listens for envelope.completed on a signature envelope tied to a deal. Actions: move stage to Closed Won, set close_date to today, update contract_start_date and renewal_date from the contract metadata, notify #sales-wins with the amount, fire the delivery handoff flow. One signer, five actions, no admin.

envelope.declined

Roll back to Negotiation, surface the reason.

If a signer declines, Flow rolls the deal back to the previous stage, attaches the decline reason to a new activity, drops a high-priority task on the AE, and notifies the deal manager. The deal stops being a Pending Signature zombie that sits in the pipeline forecast until someone notices.

envelope.viewed

First-view alert for enterprise deals.

On an enterprise opportunity above a threshold amount, Flow fires on envelope.viewed to notify the AE and the deal manager the moment the economic buyer opens the envelope. Hot moment. Rep is on the phone inside five minutes offering to walk through any questions.

Reminder flow

Custom follow-up when the signer stalls.

If envelope.sent has fired but envelope.signed has not fired after 72 hours, Flow drops a task on the AE with a personalized follow-up script, posts a nudge in Slack, and optionally fires the provider resend endpoint for a native reminder. Three nudges stacked, zero admin keystrokes.

Renewal auto-renew

Signed renewal advances the account health card.

On envelope.completed for a renewal envelope, Flow extends the account contract_end_date by the term, updates the account health field, closes out the renewal opportunity, and emails the CSM with the new end date. The renewal motion closes itself inside Strkr with no manual data entry.

HR onboarding

Offer-letter signed fires the onboarding chain.

When a new hire signs the offer envelope in DocuSign or PandaDoc, Flow creates the hire record in Strkr, provisions the delivery project, assigns the onboarding checklist to the hiring manager, and emails IT the account-creation task. One envelope, one Flow, five teams in motion.

DocuSign and PandaDoc capabilities on offer

The signing surface the providers already ship.

Because Strkr runs the signing experience through DocuSign or PandaDoc, Strkr customers inherit the full feature surface the providers already ship. Sequential signing, parallel signing, in-person signing, bulk send, mobile signing, white-label branding, qualified identity checks for regulated transactions in Europe. None of that is a feature Strkr builds. All of it is a feature Strkr customers get the moment the OAuth connection is in place. The integration framing matters: your legal team already approved DocuSign or PandaDoc, which means the signing capability is already approved for your contracts. Strkr just wires it to the deal.

Signing routes

Sequential, parallel, hybrid, routed on provider.

DocuSign and PandaDoc both support sequential (signer 1 before signer 2), parallel (all at once), and hybrid grouped routing. Configure the route in the provider template once; every envelope Strkr fires inherits the route. The route also surfaces in the Strkr envelope view so reps can see where the envelope is stuck.

Countersign

Your side signs after the customer.

Set the customer as signer 1 and your rep or VP as the internal countersigner (signer 2). The envelope locks after the customer signs and routes to the countersigner. Fully supported in both DocuSign and PandaDoc. Strkr maps the countersigner slot to opportunity.owner or a named internal role.

Mobile signing

Signers never need a desktop.

DocuSign and PandaDoc both ship responsive signing experiences that work on iOS Safari, Android Chrome, and every modern mobile browser. Signers tap, draw, confirm, submit. The signed PDF and the certificate come back to Strkr the same way regardless of what device the signer used.

Bulk send

One template, hundreds of personalized envelopes.

Fire a renewal addendum to 200 customers at once using the provider bulk-send feature with a CSV of recipients. Strkr maps each envelope back to its matching account or opportunity so the status rollup lives on the Strkr pipeline, not in a separate provider dashboard.

In-person signing

Hand the laptop over at the dinner meeting.

Both providers support an in-person signing mode where both parties sign from the same device during a face-to-face meeting. Common for enterprise closes, QBR handshakes, and partner agreements. Strkr fires the envelope in in-person mode when the deal has an in-person signing field set.

Reminder cadence

Provider-managed nudges on a schedule.

Configure 2, 3, or 7 day reminder cadences in the provider template with custom message copy and a hard cutoff. The provider handles the sending and the per-signer suppression once they sign. Strkr receives the reminder.sent events for the deal activity timeline.

White-label branding

Your logo, your reply-to, your legal footer.

Both DocuSign and PandaDoc support tenant-level branding on the signing experience and the notification emails: logo, primary color, sending domain, legal footer. Configured once in the provider, inherited by every envelope Strkr fires. Signers see your brand, not the provider brand.

Qualified signatures (EU)

eIDAS AdES and QES through the provider.

For regulated transactions in EU member states that require an Advanced or Qualified Electronic Signature under eIDAS, both DocuSign and PandaDoc partner with Qualified Trust Service Providers to deliver the higher tiers. Flip the envelope mode in the provider template; Strkr fires it the same way.

Signer delegation

Named signer forwards to the right person.

When the named signer forwards the envelope to a colleague with signing authority, both providers log the forward event and route the envelope. Strkr receives the recipient.delegated event so the deal timeline records the forward and the rep sees the real signer on the record.

How Strkr compares

The esignature line item on your renewal.

Buyers evaluating CRM esignature usually run a four-way comparison: DocuSign standalone, PandaDoc standalone, Dropbox Sign standalone, Adobe Acrobat Sign standalone, versus one of the CRMs that bundles its own signature product. Strkr is positioned differently. Strkr does not try to replace DocuSign or PandaDoc. Strkr connects to them. The question is not "whose signature product is better" but "which CRM lets me run my existing provider contract inside the sales workflow with the least glue code." On that framing, Strkr is designed to win because the integrations are first-class native code shipped by Strkr, not a third-party marketplace listing.

vs DocuSign standalone

Same signature product, wired to the deal.

DocuSign standalone is the industry gold standard and your legal team almost certainly already approves it. The gap it leaves is CRM integration. Strkr closes that gap: your DocuSign account powers the signing, your Strkr deal record holds the metadata, status events wire the two together without a middleware vendor between them.

vs PandaDoc standalone

Same signature product, bundled with the pipeline.

PandaDoc standalone ships signing plus a proposal builder. The gap it leaves is pipeline context. Strkr closes that gap: PandaDoc envelopes fire from the deal record, status events advance the pipeline stage, and the signed PDF lands on the opportunity so your CSM reads the executed contract from the account record.

vs Dropbox Sign

Not a native integration today.

Dropbox Sign (formerly HelloSign) is a capable signature product. Strkr does not ship a first-class integration for it today. Teams on Dropbox Sign typically route envelopes manually or via middleware, which loses the status event stream and the Flow trigger. DocuSign or PandaDoc is the recommended path when a Strkr-wired signature workflow matters.

vs Adobe Acrobat Sign

Not a native integration today.

Adobe Acrobat Sign is a capable signature product bundled with Adobe Creative Cloud for many organizations. Strkr does not ship a first-class integration for it today. The DocuSign or PandaDoc path is where the native Flow triggers and bidirectional sync live, so teams on Adobe Sign typically add a DocuSign or PandaDoc seat for the Strkr workflow.

vs HubSpot + DocuSign

Capable, pipeline-locked, no multi-provider.

HubSpot plus the DocuSign connector works and most teams can live with it. The constraints are the HubSpot pipeline model (fewer custom objects, fewer field types) and the single-provider assumption. Strkr lets you connect DocuSign and PandaDoc side by side and route specific envelopes to the right provider.

vs Salesforce + DocuSign

Capable, expensive, requires an admin.

Salesforce plus the DocuSign connector is powerful and widely deployed in large organizations. It also runs well into five figures per year between Salesforce licenses, DocuSign licenses, and the certified admin who maintains the integration. Strkr collapses the stack and keeps the integrations one-click without a dedicated admin.

Keep your legal posture

Signature compliance stays with the provider.

US ESIGN, UETA, EU eIDAS, UK Electronic Communications Act, SOC 2 Type II signing posture. All of that lives with DocuSign and PandaDoc as the signature system of record. Strkr is not a signature compliance surface and does not try to be. Keep the compliance posture your legal team already signed off on.

What legally compliant means in practice

Where the legal record of signature lives.

The regulatory frameworks for electronic signatures (US ESIGN Act, UETA across 49 US states plus DC, EU eIDAS Regulation 910/2014, the UK Electronic Communications Act 2000) all point to the same reality: a valid electronic signature requires intent, consent, attribution, record integrity, and an auditable trail of the signing events. In the Strkr pattern, every one of those requirements is satisfied by the provider underneath. DocuSign and PandaDoc are the compliance surface. Strkr is the orchestration surface. That split is intentional and matches the way most legal teams already think about signature compliance: the signature system of record is a dedicated signature product; the CRM is the system of record for the deal that sits around it.

US ESIGN + UETA

Provider-managed, federally and state-level.

DocuSign and PandaDoc both ship signing flows designed to satisfy US ESIGN Act (federal) and UETA (state law, 49 US states plus DC) by default: intent capture, consent screen, attribution to signer, record integrity hash. The signed PDF and certificate stored in the provider is the admissible legal artifact.

EU eIDAS awareness

Simple, Advanced, Qualified tiers via provider.

Both providers support Simple Electronic Signature by default and offer Advanced (AdES) and Qualified (QES) tiers through partner Qualified Trust Service Providers for regulated EU transactions. The tier is configured in the provider template per envelope. Strkr fires the envelope at whichever tier the template is set to.

UK compliance

Electronic Communications Act 2000, provider-side.

The UK post-Brexit regime kept eIDAS awareness and layered its own Electronic Communications Act. DocuSign and PandaDoc envelopes signed in the UK carry the same evidentiary weight they do in the EU for English, Welsh, Scottish, and Northern Irish commercial agreements. Compliance posture inherited from the provider.

Audit trail stays with provider

Certificate of completion is the legal record.

Every envelope signed through DocuSign or PandaDoc produces a certificate of completion with signer IP, device, timestamps, event history, and a document hash. The certificate is retained by the provider as the authoritative legal artifact. Strkr pulls a copy onto the deal for convenience, not for compliance.

Record retention

Provider sets the retention terms.

DocuSign and PandaDoc each offer long-term retention of signed envelopes and certificates under their enterprise plans. Review the retention terms with your account on the provider side. Strkr does not override provider retention and does not try to be the long-term record store for signed artifacts.

Consent capture

E-sign disclosure baked into provider flow.

Before the first signature screen, DocuSign and PandaDoc both present the signer with the ESIGN consent disclosure. The consent event is captured on the certificate with timestamp and IP. This is a hard ESIGN requirement that most in-house signature flows forget. The provider ships it by default.

How teams actually run it

Three signature flows in production today.

New business

MSA plus Order Form fired through DocuSign.

The AE sends the MSA plus Order Form envelope from the opportunity record using a DocuSign template. Signer 1 is the customer procurement contact, signer 2 is the customer signatory, signer 3 is the internal VP of Sales as the countersigner. On envelope.completed, Flow moves the deal to Closed Won and fires the implementation handoff.

Renewals at scale

PandaDoc bulk send to 200 renewing accounts.

Finance exports the renewing accounts to a CSV, uploads to PandaDoc bulk send against a renewal addendum template, and fires 200 personalized envelopes in one action. Each envelope maps back to its Strkr renewal opportunity. On envelope.completed, Flow extends the contract_end_date and updates the account health card.

HR onboarding

Offer letter and I-9 bundled in one envelope.

A new hire receives one DocuSign envelope with offer letter, employment agreement, I-9 upload prompt, direct deposit form, and benefits acknowledgement. Signer fields prefilled from the HR record. On envelope.completed, Flow creates the hire record in Strkr, provisions the project, and notifies IT to provision the account.

DocuSign and PandaDoc, wired into every deal.

Connect your existing DocuSign or PandaDoc account in Admin, map a template to your opportunity contacts, and send the first signature envelope from a Strkr deal record this afternoon. The signed PDF, the status events, and the Flow triggers come back to the pipeline automatically.

Start free trial See pricing
Common questions

What buyers ask about this feature.

Does Strkr ship its own esignature product?

No. Strkr does not ship a native esignature product. E-signature inside Strkr is delivered via first-class native integrations with DocuSign and PandaDoc. Customers connect their existing DocuSign or PandaDoc account (or sign up fresh), send signature envelopes from the deal record, and the signed PDF plus the status events flow back automatically. The signature system of record stays with the provider. The deal and contract metadata system of record stays with Strkr. This split matches the way most legal teams already think about signature compliance.

Which esignature providers does Strkr integrate with?

DocuSign and PandaDoc are the two first-class native integrations today. Both ship with OAuth connection from Admin, template picker and role mapping, field prefill from the opportunity, status webhooks that fire Flow triggers, and automatic sync of the signed PDF and certificate back onto the deal record. Dropbox Sign and Adobe Acrobat Sign do not have native integrations today; teams on those products typically add a DocuSign or PandaDoc seat for the Strkr workflow or route envelopes through a middleware layer.

Is the audit trail stored in Strkr or in DocuSign and PandaDoc?

The authoritative legal audit trail (certificate of completion with signer IP, device, timestamps, consent record, document hash, event history) is stored by the signature provider as the system of record for the signature. DocuSign and PandaDoc both retain the certificate under their enterprise retention terms. Strkr pulls a convenience copy of the signed PDF and the certificate onto the deal attachments so your reps and CSMs can see the executed contract from the opportunity, but the admissible legal artifact lives with the provider.

Can Flows react to signature events from DocuSign and PandaDoc?

Yes. Every provider webhook event (envelope.sent, envelope.viewed, envelope.signed per signer, envelope.completed, envelope.declined, envelope.voided, recipient.delegated, reminder.sent) is available as a trigger inside Strkr Flows. The most common pattern is a Flow listening for envelope.completed to move the deal to Closed Won, update the renewal date, and fire the delivery handoff. Teams also use envelope.declined to roll the deal back to Negotiation and envelope.viewed to alert the AE the moment an enterprise buyer opens the envelope.

Does my legal team need to re-approve the signature flow?

No new compliance review is required for the signature itself because the signature product is still DocuSign or PandaDoc, whichever one your legal team already approved. The signing experience, the consent capture, the certificate of completion, and the US ESIGN plus UETA plus eIDAS compliance posture are all delivered by the provider exactly as your legal team evaluated them. The Strkr side is an orchestration integration that fires envelopes and syncs status; the signature compliance surface is unchanged.

What if a signer needs an EU Qualified Electronic Signature?

Qualified Electronic Signatures (QES) for regulated EU transactions are delivered by DocuSign and PandaDoc through their partner Qualified Trust Service Providers. Flip the envelope mode in the provider template to the QES tier for that specific transaction. Strkr fires the envelope the same way regardless of the tier. The identity verification step and the qualified certificate issuance happen on the provider side; the deal record in Strkr records the completed envelope the same way it would for a Simple Electronic Signature envelope.

Related features

Pair this with...

Contract Management Workflow Automation Flows Document Automation Customization

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing