Dupey ConsultingPROJECT / AUTOMATION
DocuSign Automation
DOCUMENT WORKFLOW AUTOMATION
Contracts and forms were still created, sent, and filed by hand. Built a DocuSign pipeline so the standard path runs itself and only exceptions need a person.
- Project type
- Document workflow automation
- Role
- Process automation consultant
- Systems
- Python · DocuSign API
- Status
- Internal system
THE STARTING POINT
Generate, send, then file - by hand.
Advisors assembled documents from templates, entered recipients in DocuSign themselves, and filed the signed copies. At volume that meant preparing PDFs, watching envelopes, and putting finished files in the right folders - one document at a time.
THE FLOW
Clean data in. A filed envelope out.
A Python application takes prepared client records, populates the matching PDF, sends a DocuSign envelope with signature fields placed on the page, and files the completed document after the household signs.
- 01Client dataIncoming records cleaned so a form can be filled
- 02PDFThe matching document type, populated
- 03DocuSignEnvelope with signature, name, and date fields
- 04SignatureSent to the client household
- 05FilingCompleted documents into named folders
WHAT I BUILT
The API was not the hard part.
Most of the work was making the incoming data clean enough to drop onto a form. Then a custom Python application populated about twenty PDF types, placed DocuSign fields by page coordinates, sent household envelopes, and filed what came back.
PYTHON · DOCUSIGN API · PDF
PREPARE
- Incoming client data cleaned and standardized
- About twenty PDF types populated and labeled
SEND
- Signature, name, and date fields placed by page coordinates
- Envelopes packaged and sent to each client household
COMPLETE
- Completion watched through the DocuSign API
- Signed documents filed in clearly named folders
WORKFLOW LOGIC
A document is only as good as the record behind it.
Some of the PDFs had more than two hundred fields. The pipeline still has to pick the right template, place the tabs, route the household, and surface envelopes that expire or get voided instead of failing quietly.
- 01
Clean
Incoming data standardized before anything is generated.
- 02
Select
The right document from about twenty PDF types.
- 03
Place
Signature, name, and date fields at page coordinates.
- 04
Route
Packaged as a household envelope, including more than one signer.
- 05
Watch
Completion, expirations, and voids logged so people only handle exceptions.
WHERE IT LANDED
The standard path now generates, sends, and files without someone assembling each envelope. Exceptions surface instead of failing quietly.
I designed and built the pipeline. It runs as an internal system.
MORE WORK
01SYSTEMS
WhatConverts → Salesforce
Paid leads were sitting in one tool while sales waited on manual CRM entry. Built a pipeline so new leads land in Salesforce in seconds, ready to call.
VIEW PROJECT →02PRODUCT
Freelance CRM
A simple CRM I built for my own consulting work - clients, leads, opportunities, tasks, time, and invoices in one place, without fighting Salesforce-scale software.
VIEW PROJECT →
