
Self-Hosted E-Signature for One 4 The Books
One Platform, Every Client, No Limitations
Context
One 4 The Books runs the back-office operations for a growing roster of home-services contractors — roofing crews, gutter installers, exterior remodelers — stitching together Airtable, Make.com, and whatever CRM each client already runs.
Almost every one of those workflows ends the same way: a customer or a subcontractor has to sign something, and that signature is what turns the work into a contract. Each client business handled that step through its own e-signature subscription.
Why Per-Client E-Signature Subscriptions Don't Scale
Across the portfolio, client businesses were spread across different e-signature vendors — SignWell, DocuSign, Adobe Sign, and Zoho Sign — each billed the same way this category always prices itself: one paid account per client, a seat limit, a capped number of documents, then an overage fee once a client actually used the product. Different logos, same structure.
Added up across every client running one of these subscriptions, the combined bill ran past $500 a month — and the money didn't even buy freedom from the limitations. Every account still capped how many people could send a document and how many could go out before the next charge kicked in, regardless of which vendor's name was on the invoice.
The Solution: One Self-Hosted Documenso Instance
BSB Tech Hub replaced that entire stack of vendors with a single self-hosted deployment of Documenso — an open-source, API-first e-signature platform — on DigitalOcean. Every client business keeps its own account, its own templates, its own signers, exactly as before.
What disappears is the subscription itself: one instance now does the job that used to require a separate paid account, on a separate platform, for every client on the roster. It's the same logic behind any custom software decision — build the thing once, own it outright, and let it cover the next client for free instead of paying a fifth vendor for a sixth account.
Open Source Means No Feature Limits
Self-hosting bought more than a lower bill. Documenso ships its full source code under an open license, so when One 4 The Books wanted outgoing signing emails to carry a branded sender name — the kind of feature a SaaS vendor sells as an Enterprise upgrade — the answer wasn't a support ticket or a pricier plan.
BSB Tech Hub forked the platform, patched the code that controls how a sender's name is composed, and rebuilt the image from source. A feature that would have meant negotiating a bigger subscription became a small, one-time change to infrastructure BSB Tech Hub already owned.
How It Works
The instance runs on DigitalOcean App Platform behind a managed PostgreSQL database and object storage for signed documents and templates, all under a custom Docker image built from Documenso's own source.
Every e-signature platform in this category works the same way underneath — create a template, map the signer fields, send, listen for a webhook — so migrating each client off whichever vendor they'd been using meant rebuilding that one mapping once, not re-architecting the automation itself. The Make.com and Airtable workflows each client already relied on kept working; only the endpoint and the account underneath them changed. When a document goes out for signature and comes back signed, a webhook fires straight into the client's existing Airtable base, and the signed PDF lands where the team already looks for it.
What Self-Hosting Actually Protects
Moving off a SaaS vendor doesn't mean giving up what makes a signature legally defensible. The same ESIGN Act and UETA requirements apply either way — intent to sign, consent to sign electronically, attribution to the right signer, and a tamper-evident audit trail with timestamps and signer identity — and Documenso produces all of it natively. What changes is who owns the infrastructure underneath that audit trail, and whether every client business has to pay for their own copy of it.
Key Outcomes
- Combined per-client subscriptions eliminated — replaced by one self-hosted platform
- No seat limits and no per-document caps, at any volume
- Fully open source — patchable to match a client's exact workflow or branding
- ESIGN Act / UETA-compliant audit trail preserved
- Onboarding another client requires no new subscription
- No vendor lock-in — the code and the data are owned outright
Business Impact
Consolidating onto one self-hosted instance turned off the subscription stack entirely. Instead of every client business paying its own way into the same seat limits and document caps, the whole portfolio now runs on one platform with none of those restrictions — and adding the next client costs nothing beyond what's already running.
Own the Infrastructure, Not the Subscription
This project is a clean example of what a custom-built system can do that a stack of per-client subscriptions never will: remove the limitations entirely, not just discount them.
Systems Involved
Documenso
DigitalOcean App Platform
PostgreSQL
DigitalOcean Spaces
Docker
Airtable
Make.com
Still Paying Per Client for the Same Software?
If your business runs the same subscription once for every client, we can design and build the self-hosted platform that replaces all of them with one.