Client SolutionsCustom Apps & SolutionsAutomations
Replaced their e-signature service with one they own, and gave it the thing SignWell could not do
They were paying SignWell per signature to send the same referral agreements to the same agents, month after month. I built the replacement. The agreement comes from their own Google Docs, is signed on their own page, is filed as a PDF in their own Drive, and their CRM is told the moment it is done. Then the part no e-signature service can do at any price: an agent who refers repeatedly signs one standing agreement, and every deal after that produces a finished contract automatically, without waiting on anyone to sign.
Opens in a new tab. Click through it like a visitor would, nothing is a screenshot.
The problem
Every referral agreement went out through an e-signature service that charged by the signature, and the bill grew with the business rather than with the value of the signing. Worse, most of the agreements were not new relationships. The same agents took referrals over and over, and each one meant another set of links, another round of chasing, and another fee to sign a document that said what the last one said. The two people who appear on every single agreement, the referring agent and his managing broker, were signing their own name several times a week as a formality. And because the contracts lived inside somebody else's product, the finished files, the templates and the record of who signed what were all somewhere the business did not control.
What shipped
- SignWell replaced outright, and the per-signature bill with it, by a system running on a $5 a month plan with the database on a free tier
- The capability no e-signature service sells: repeat agents sign one standing agreement, and their later deals produce a finished PDF with no link and no waiting
- The two people on every agreement stopped signing their own name several times a week, because their signatures are placed automatically
- A standing agreement expires unless both the agent and their broker confirm it every ninety days, so nothing signs itself indefinitely
- Templates, signed PDFs and the record of who signed what all sit in the client's own Google Drive and their own Cloudflare account
- An office console for finding, cancelling and archiving agreements, so a wrong contract is a thirty second fix by the person who spotted it rather than a message to me
- 294 tests, and the whole thing handed over to the client's GitHub organisation with a deploy runbook and an in-app manual
Building the contract only at the end sounds like a detail and it is the reason the system is simple enough to trust. The obvious approach is to keep a draft document and patch each signature in as it arrives, and it goes wrong in the ways you would expect: a signer drops out and you have a half-signed artifact, someone signs twice, a retry produces two documents, and every path through the code has to know how to repair a partially built file. Holding nothing but signatures until the last one lands means there is a single place a contract is ever created and a single thing that can go wrong there. The ninety-day check-in got the same treatment from the other direction. A standing agreement is a real convenience and also a real risk, because it is permission that keeps working after everyone has forgotten agreeing to it. Making it expire by default, and requiring both the agent and their broker to actively confirm, means the quiet failure mode is a paused agreement rather than a contract nobody remembers authorising. A broker who covers several agents is asked once per round, because a system that emails a busy person five identical questions gets ignored, and an ignored check-in is the same as no check-in at all. The last decision was about ownership, and it is the one that mattered most to the client. Everything runs in accounts they hold: their Cloudflare, their database, their Google Drive, their GitHub. The handover was a runbook, a data export and a documentation site built into the app itself, so the thing does not depend on me being reachable.
Next.js on Cloudflare Workers through OpenNext. Google Docs and Drive through a service account: the templates are real Google Docs, so the finished contract keeps the formatting the client designed rather than an approximation of it, and the agreement is exported, placeholders filled, and rendered into a sandboxed frame for the signer to read. In-flight sessions live in Redis, deliberately temporary, because a session that has served its purpose should not linger. Object storage holds two separate things in two separate buckets: the public signature images the finished PDF references, and a private, append-only record of every step for the paper trail. A scheduled job sweeps every five minutes for the things that need chasing. There is a passcode-gated admin screen for finding and cancelling a contract by its deal reference, with the passcode compared server-side and the login rate-limited. The documentation lives inside the app on its own passcode-gated route, rendered from the repository's own markdown with diagrams, so it cannot drift away from the code the way a separate wiki does. 294 tests across 41 files.
Want one built for you?
Get on a call with me and let's talk it through.