Can we keep DocuSign as the signature engine and use Strkr for the CRM and contract workflow?
Yes. Strkr integrates with DocuSign through the standard webhook spec with HMAC signing. The rep writes the quote in Strkr, converts to order form, routes through internal approval, and clicks send to DocuSign for the final signature flow. The signed contract and certificate of completion flow back to the customer record on Strkr. For teams on DocuSign Enterprise with a branded signer experience the enterprise clients expect this is the common path. The DocuSign subscription stays.
What is the compliance posture of Strkr native signature versus DocuSign?
Strkr native signature meets ESIGN Act and UETA requirements for enforceability in the United States. For international signers Strkr supports eIDAS Advanced Electronic Signatures (AES). For eIDAS Qualified Electronic Signatures (QES), which some EU jurisdictions require for specific contract types, teams typically integrate with DocuSign or Adobe Sign through the webhook spec. Strkr is HIPAA compliant with a BAA available on request, GDPR and CCPA compliant today, and SOC 2 Type II is in progress with a target of 2026-Q4.
How does the native signature flow handle signer verification and audit trail?
The signer receives an email with a hosted browser signing view. Signer verification options include email token (default), SMS text verification, and knowledge-based authentication for high-value contracts. The audit trail captures the IP address, the device fingerprint, the signing timestamp, and the full page view history. The certificate of completion generates on signature with a tamper-evident hash. The audit trail archives to the customer record with 90-day default retention tunable per tenant.
Can we migrate existing DocuSign contracts into Strkr?
Yes. The DocuSign export brings in the full signed contract library (executed PDFs, certificates of completion, signer metadata, document history). Strkr import maps the contracts to the customer records and extracts the structured terms (contract term, renewal date, auto-renew clause, pricing, obligations) using AI with human review on the first batch. Teams typically run a staged migration: new contracts route through Strkr immediately, existing DocuSign contracts stay in DocuSign through their current term, and the DocuSign subscription closes at renewal.
What does Strkr cost compared to DocuSign plus a general CRM?
Strkr prices flat per seat at 29 on Starter, 59 on Pro, and 119 on Scale per user per month, with a 14-day trial. Contract workflow and native e-signature are included. A 40-rep team on Pro runs 28,320 per year. DocuSign Business for a 40-rep team runs 42,000 to 78,000 per year depending on envelope quota, and the general CRM runs 23,000 to 125,000 per year depending on choice and edition. The combined savings land between 55,000 and 180,000 per year for most 40-rep teams.
How does Strkr handle the CLM features (approval routing, renewal reminders, obligation tracking)?
Approval routing tunes by dollar threshold, contract type, and discount envelope through the admin console. Renewal reminders fire at 120, 90, and 30 days before renewal date with the AI-drafted outreach ready to send. Obligation tracking extracts the key commitments (SLAs, delivery milestones, custom work, data residency, support tier) from the signed contract and surfaces them on the customer record for customer success. For teams with heavy CLM requirements (highly regulated industries, complex multi-party contracts) Strkr can integrate with Ironclad, Agiloft, or Icertis via the webhook spec.