Documents and e-signature
DocuSign API consultant: agreements sent, signed and filed without chasing
SBD builds DocuSign eSignature integrations for teams of 1 to 1,000 people: envelopes created from your CRM or app, status tracked through Connect webhooks, and signed documents filed and recorded automatically. Workflow automation builds start at $1,000, with the fixed price set after a $500 Automation Audit that is credited to the build.
- Tool
- docusign.com
- Usually paired with
- HubSpot, Google Drive, Slack, Pipedrive
- Timeline
- Most builds live in 2 to 8 weeks
- Owned by
- You, with accounts, credentials and code in your name.
What we build on DocuSign
- Generate agreements from CRM data and send for signature
- Move deals forward when documents are signed
- File signed copies where finance and ops can find them
- Chase unsigned documents automatically
What we sync
Workflows we are asked for
- DocuSign envelope from a HubSpot deal
- Signed contract to project kickoff
- DocuSign status to Slack
- Unsigned document reminders
Tools DocuSign usually needs to talk to
-

DocuSign and HubSpot
The CRM and marketing platform most B2B teams of 10 to 1,000 run on.
-
DocuSign and Google Drive
Google Workspace file storage, Docs and Slides.
-

DocuSign and Slack
Team chat, and usually the place where alerts get read.
-

DocuSign and Pipedrive
A sales-first CRM for small teams, with a straightforward API.
What a DocuSign developer from SBD builds
Staff can already send an envelope from the DocuSign web app, so the value of an integration lies elsewhere.
It is everything around it: filling the document from the CRM or quote so nobody retypes figures, sending it to the right signers in the right order, knowing the moment it is signed, and then doing the next thing, such as creating the customer, provisioning the service, filing the PDF and telling finance.
Typical builds: quote or proposal to envelope from a CRM or internal tool; onboarding packs sent automatically when a new hire or customer is approved; Connect events that move a deal, open a project or trigger an invoice when an envelope completes; and archiving of completed envelopes and certificates to your document store with a record in your database.
We have not published a case study built on DocuSign, so we will not point you to one.
When DocuSign is the right choice, and when it is not
A good fit
DocuSign suits organisations that already standardise on it, or whose customers and counterparties expect it, and that need a mature API, a webhook service with long retries and options for organisation-wide configuration. Its developer platform is strict about how you use the API, which is a good thing once you design for it.
We will recommend something else when
- Volume is a few documents a month and nothing downstream needs to happen automatically; the web app alone is enough.
- The documents are internal acknowledgements that a form with a checkbox and an audit log would cover.
- You want to embed signing in a product you sell to others; DocuSign says embedded integrations need ISV partner licensing, which changes the commercial picture.
- Your CRM's native DocuSign integration already does the full job.
DocuSign API limits, polling rules and Connect
DocuSign enforces an hourly request limit per account, shared by every integration on it and shown in the X-RateLimit-Limit response header, with usage refreshed on the hour. There is also a burst limit at account level of 200 calls per 30 seconds in the developer environment and 500 in production, and limits on GET and PUT requests per envelope per hour. DocuSign advises using five API calls or fewer to create or update an envelope.
Polling is restricted. An app may make one status request per envelope every 15 minutes; DocuSign recommends polling at 20-minute intervals if you must, and says breaches are flagged and can fail go-live review. The better route is Connect, its webhook service. From the developer docs in October 2026:
- Configuration levelsaccount, recipient, envelope and organisation-level Connect configurations, sending XML or JSON.
- Retriesafter 5, 10, 20 and 40 minutes, 1 hour, 2 hours and 1 day, then once a day for 15 days.
- API limitsConnect messages do not count against your request limits.
- SigningHMAC-SHA256, with up to 100 keys and one X-Docusign-Signature header per key.
- Document limitsuploads of the same document are capped at 70 in progress, and combined-PDF downloads at 3 in progress within an hour.
JWT service auth, consent and the go-live review
Most of our integrations are service integrations: nobody is sitting at a screen when an envelope is sent
DocuSign's JWT Grant is designed for that. The integration impersonates a specific user, such as an HR or contracts mailbox, after that user or an administrator grants consent. Access tokens last one hour and no refresh token is issued, so the integration signs a new JWT each time. Because impersonation is a high level of trust, DocuSign advises using an authorisation code flow instead where impersonation is not needed, and we follow that advice.
Before production, the integration key must be promoted from a developer account to a paid production account through the go-live process
Requirements include meeting the API resource limits and using OAuth 2.0. The key is copied across, but secrets and redirect URIs are not, so they must be configured again in production. Manual reviews are typically completed within 24 to 48 hours. We build against the limits from the start so review is a formality, and we plan production configuration as a release step.
How we design envelopes that stay within the rules
- 01
DocuSign's guidance is to use five API calls or fewer to create or update an envelope, so we design for that from the start.
Templates hold the fixed wording and signer roles, and the integration supplies recipients and field values in as few calls as possible, sending at creation where the process allows rather than creating a draft and updating it piece by piece.
- 02
Values come from the system of record and are validated before the envelope exists: the price on a quote, the start date on an offer, the legal entity on a contract. If a value fails validation the workflow stops and asks a person, rather than sending a document that will need to be voided. Every envelope ID is stored against the source record, so Connect events can be matched without searching.
- 03
Completed documents are downloaded once, after the completion event, and filed with the certificate, keeping well inside the per-document download limits.
How hiring a DocuSign consultant from SBD works
- Step 1$500Automation AuditCredited to the build
- Step 2from$1,000Workflow automationFixed after the audit
- Step 3from$3,000Internal toolsFixed after the audit
- Step 4from$50Care planA month, after sixty days of hypercare
Every engagement starts with an Automation Audit at $500, credited in full to your build. For DocuSign we map each agreement type from draft to filed, count the manual steps and rekeying, and check your account's API access and any existing integrations against the polling and request rules. You get a ranked list of builds, each with a fixed price.
Workflow automation builds start at $1,000, internal tools at $3,000 and multi-module systems at $5,000. Work runs in two-week sprints with sixty days of hypercare, and care plans start at $50 a month. Your DocuSign subscription is paid by you to DocuSign.
What you own when the build is finished
Everything below is in your name when the build ends.
- The DocuSign account, integration key, RSA key pair, Connect configuration and HMAC keys are in your name, with private keys in your secret store.
- You receive a runbook covering consent, key rotation, each Connect event and what it triggers, and the steps to reconcile envelopes after a receiver outage.
- Templates are documented with their fields and where each value comes from, so your team can change wording without breaking the integration.
DocuSign at enterprise scale
Larger organisations run DocuSign across sales, HR, procurement and legal, often with several accounts under one organisation and a mix of native CRM integrations and custom ones. The constraints that bite are shared: one hourly API limit per account, strict polling rules, and a security team that wants to know who can impersonate whom.
Impersonation and consent
We use JWT Grant only where no user is present, impersonate a dedicated service user rather than a person, and document who granted consent and how to revoke it.
Shared API limits
Every integration on an account shares the hourly limit. We inventory them, remove polling in favour of Connect and keep each envelope within a handful of calls.
Organisation-wide events
Organisation-level Connect configurations can notify one listener for all accounts. We use that where a central team owns the integration, with HMAC on every message.
Receiver resilience
Connect keeps retrying for more than two weeks. Receivers verify, store and acknowledge quickly, and process from a queue, with a reconciliation job for anything missed.
Go-live and change control
We build in the developer environment, pass go-live review, and treat production secrets and redirect URIs as a documented release step.
Records and retention
Completed documents and certificates are filed to your document store with a database record, under a retention rule your legal team sets.
Engagements we take on
Already on DocuSign, integration failing review or hitting limits
An older integration polls every envelope and is flagged or throttled. We replace polling with Connect, cut calls per envelope and take it through review.
Already on DocuSign, signed documents stuck in inboxes
Completed agreements are downloaded by hand. We file them automatically with metadata and start the next step in the CRM or project tool.
Already on DocuSign, contracts retyped from the CRM
Sales copies figures into templates. We fill envelopes from the CRM or quote record with validation, so a wrong price cannot reach a signer.
Already on DocuSign, impersonation nobody can explain
Integrations act as named staff with broad consent. We move them to a service user, narrow consent and document the model for your security team.
Read next
Sources
- DocuSign, eSignature API rules and resource limits (hourly, burst, per-envelope and polling limits, document limits), checked 29 October 2026
- DocuSign, Connect overview (configuration levels, retries, limits), checked 29 October 2026
- DocuSign, HMAC security for Connect, checked 29 October 2026
- DocuSign, JWT Grant authentication (impersonation, consent, token lifetime), checked 29 October 2026
- DocuSign, Go-Live (production account, requirements, classifications, review time), checked 29 October 2026
Standards on every build
Validation, retries, reconciliation, audit logs and alerts come as standard, with credentials and accounts in your name. Read the integration standards
What people ask about DocuSign
Can the contract be built from CRM fields?
Yes. Template fields are filled from the deal, the contact and the company, and the signed PDF is stored against the record.
Start with the one DocuSign workflow your team still runs by hand
Bring it to a discovery call. You leave with a yes or no on fit, an outline of the build and what we would do first.
Book the call












