How I Built a Document Signing System Without DocuSign
DocuSign wanted $1,800/year for 10 employees to sign basic HR paperwork. I built the same thing on infrastructure I already pay for. Extra cost: zero.
By Mike Hodgen
Every company that sells document signing software prices it like you're a giant corporation with a legal team of 50. When I needed new hires at my DTC fashion brand in San Diego to sign basic onboarding paperwork — offer letters, handbook acknowledgments, direct deposit forms — DocuSign wanted $15 per person per month.
Ten employees. $1,800 a year. Just to put a signature on a digital document.
The thing is, what these platforms actually do under the hood is pretty simple. They show you a document, let you fill in some fields, capture your signature, lock the whole thing so nobody can change it, and store it. That's the product. The rest is bells and whistles that a team under 50 people will never use.
So I built my own. It runs on computer systems I was already paying for. Extra cost: zero.
What a Signing System Actually Needs to Do
Before I built anything, I wrote down what I actually needed. Not what DocuSign sells. What I needed.
It came down to eight things: upload a document template, mark where people need to sign or fill in information, create a unique link for each signer, show them the document with fillable fields in their web browser, capture their signature (drawn or typed), lock the finished document so nothing can be changed, save it with a record of who signed and when, and email copies to everyone.
That's the whole list.
You don't need fancy login systems. You don't need the ability to send documents to hundreds of people at once. And you don't need the legal complexity that these vendors try to scare you with. Electronic signatures have been legally binding in the US since the year 2000. The legal requirements boil down to: the person intended to sign, they agreed to do it electronically, and you have a record. A digital fingerprint of the document plus a log of who signed, when, and from where is more than enough for internal HR paperwork.
The Part That Almost Killed the Project
Here's what I didn't expect. The hardest part of the entire build wasn't the signing itself. It was making sure a signature field shows up in the right spot on the page.
Think of it like this. When you look at a document in your web browser, the computer measures everything starting from the top-left corner of the page, going down. But the underlying document format measures from the bottom-left corner, going up. These two systems are literally upside down from each other.
My first attempt, every signature block I placed near the bottom of a page showed up near the top in the final document. It was like looking in a mirror where up and down are flipped.
I went through three complete rebuilds before positions mapped correctly across different screen sizes — phones, tablets, laptops. What I thought would take two hours took fifteen. That's the kind of hidden complexity that makes people give up and pay for DocuSign.
The fix was storing every field position as a percentage of the page rather than a fixed measurement. So a signature block at "80% down the page and 10% from the left edge" renders correctly whether you're on an iPhone or a 27-inch monitor.
From Click to Locked Document
When a new hire clicks their signing link, here's what happens in plain English.
The system checks: Is this link still valid? Has this document already been signed? Is this the right person? If anything's wrong, they see a clear error message.
If everything checks out, the document appears in their browser with fillable fields right where they need to be. They type their name, check boxes, enter dates. For the signature itself, they can either draw it with their finger or mouse, or type their name and the system renders it in a handwriting-style font. Most people pick the typed option — fewer people abandon the process when they don't have to fumble with drawing on a trackpad.
When they hit submit, the system takes everything they entered and permanently bakes it into the document. This is the critical step. The finished document becomes like a photograph — you can look at it, but you can't reach in and change anything. Without this step, someone could open the file and edit what was written. With it, the signed document is locked.
The system also creates a digital fingerprint of the final document. If anyone ever questions whether a document was changed after signing, you can check that fingerprint. If it matches, the document is untouched.
The Results in My Business
For onboarding at my brand, new hires need to sign four documents. It used to involve printing, signing in person on day one, scanning, and filing. If someone started remotely, the whole thing stalled for days.
Now HR sets up each template once. For each new hire, the system creates one link that walks them through all four documents. Average time from "documents sent" to "all signed": under 2 hours. The old paper process could take a week of chasing.
I also built an automatic reminder system. If someone doesn't sign within 24 hours, they get a nudge. Another at 3 days. Another at 7 days marked urgent. This cut average signing time from 4.2 days to 1.1 days. Most people sign within an hour. The reminders catch the 20% who forget.
Should You Build or Buy?
Honest answer: not everyone should build this.
It makes sense when you have a small team, predictable documents, some technical ability (or someone like me to build it), and you're already running systems that can host it. My extra cost was 15-20 hours of focused work and zero in ongoing hosting.
It doesn't make sense when you need complex signing chains between multiple parties, you're in a heavily regulated industry, or your volume is high enough that DocuSign's per-unit cost actually becomes reasonable.
This is the kind of decision I help businesses make. Not just for document signing — for every tool in their stack. One custom system saves $500 a year. Build ten of them across your operations and you've eliminated $5,000+ in software fees while owning your entire workflow. At my brand, this approach contributed to a 38% increase in revenue per employee and a 42% reduction in manual operations time.
That's what working with a Chief AI Officer looks like in practice. Finding these opportunities and building tools that fit how your team actually works.
Thinking About AI for Your Business?
If this resonated, let's have a conversation. I do free 30-minute discovery calls where we look at your operations and identify where AI or custom tooling could actually move the needle. No slides, no pitch deck — just an honest look at what's worth building and what's worth buying.
Get AI insights for business leaders
Practical AI strategy from someone who built the systems — not just studied them. No spam, no fluff.
Ready to automate your growth?
Book a free 30-minute strategy call with Hodgen.AI.
Book a Strategy Call