At a glance
- The problem
- Contracts went out as PDFs to be printed, signed, scanned and emailed back, and unsigned contracts held up project starts.
- Systems touched
- The firm's internal platform and its CRM.
- What we built
- Contract generation from the CRM deal record, in-browser signing backed by a tamper-evident audit trail, and tracked states with configurable reminders.
- What changed
- Clients sign from wherever they open the email, and the sales team can see when a contract has been sent but not opened.
Anonymised and illustrative. Client details are hidden and in some cases combined into a composite, and there are no outcome figures.
The Problem
A B2B services firm was closing every contract the slow way. The standard process was: draft the contract in Word, export to PDF, email it to the client, wait for them to print it, sign it, scan it back, and email the scan. Some clients did this within days. Others took much longer and needed reminder after reminder before the signed scan arrived, by which point the sales team had moved on to other deals and the chase had become low priority.
The cost was not the time per contract but the cumulative drag on the sales pipeline. Contracts sitting unsigned for weeks meant project starts were delayed, revenue recognition slipped, and occasionally a deal evaporated because the client had second thoughts during the lag. The firm’s operations director had started measuring “days from verbal yes to signed contract” and the number was consistently embarrassing.
The firm had considered DocuSign and the obvious alternatives. The cost-per-envelope model was uncomfortable at their volume, and more importantly, the contracts did not exist in isolation. They were the output of a sales process where the same client data, the same scope summary, and the same commercial terms had already been captured in the firm’s CRM. Generating the contract in one system, signing it in another, and then re-entering the signed state back into the CRM was duplicative work.
The Approach
We built a contract signing workflow as part of the firm’s existing internal platform rather than as a separate tool. A contract is generated from the CRM record (client details, scope, commercial terms) using a configurable template, so the legal language stays controlled while the commercial detail is pulled from the deal record automatically. The generated contract is sent through a signing flow that tracks viewed, opened, signed, and countersigned states, with reminders configurable per client or per contract type.
The legal weight of the signature was the bit that needed care. We used a recognised e-signature standard with cryptographic signing and a tamper-evident audit trail, so the signed contracts hold up legally in the jurisdictions the firm operates in. The audit trail captures every state change with timestamp and IP, and the final signed contract is stored with a hash that can be re-verified at any time to prove it has not been altered since signing.
The System We Built
A contract generation, signing, and tracking workflow integrated into the firm’s existing internal platform. Contract templates draw their variable fields from the CRM. Clients receive a link, view the contract, and sign in-browser with no login required; the firm sees the state change in real time. A reminder engine nudges clients on configurable cadences. The signed contracts are backed by a tamper-evident audit trail with cryptographic signing, and each one is archived against the original CRM deal record so the firm has a single timeline per client covering proposal, contract, and project start.
The Outcome
The print-sign-scan portion of the process is gone. A client can sign from wherever they open the email, with no printer and no scan, so the gap between a verbal yes and a signed contract no longer depends on whether someone has a printer to hand.
A subtler outcome: the sales team gained visibility they did not have before. When a contract has been sent but not opened after seventy-two hours, they see it, and that triggers a different kind of follow-up than the generic “have you signed yet” chase. The reminder is contextual rather than blind.
What We Learned
Building this into the firm’s existing platform rather than wiring up a third-party e-signature tool was the right call because the contract is one event in a longer relationship, and having it visible against the CRM record alongside the proposal, the signed state, the project, and the eventual invoice gave the firm a coherent view it would never have had with the contract living in another vendor’s system.
Stuck on PDF Print-Sign-Scan?
If your contracts are still moving by PDF and email and you have measured the lag, get in touch to talk through what an integrated signing workflow could look like for your sales process. The law firm client document portal case study covers similar access-and-audit territory, and the audit trail compliance implementation goes deeper on the verification side. Our contract management system page covers the system we built here. The case studies overview has the full portfolio.
Written by
Alex
CEO
I’m a software developer and CEO of Digital Royalty, helping growing teams scale their SaaS platforms without losing quality, visibility, or control. I focus on building structured, maintainable systems with clear processes, reporting, and accountability. With over a decade of experience across agency and in-house roles, I specialise in delivering long-term, scalable solutions that support complex, evolving products.