E-signature and document workflow

What this actually solves

A deal is agreed on a call and then takes a week to sign. In that week the buyer's enthusiasm cools, a competitor gets another meeting, or a decision-maker goes on leave. The delay has nothing to do with the terms. It is that the document has to be produced by hand, printed, signed, photographed, sent as an image, and then chased twice — and each of those steps depends on a person remembering to do it. A deal that was already agreed can go cold while it waits in that gap.

HR has the same problem in a different shape. A new starter needs an offer letter, an NDA and a policy acknowledgement — three separate documents, three separate chases, all while the person is forming their first impression of how organised the company is. And then there is the question that exposes the whole thing months later, when somebody asks whether a particular contract was ever actually signed and finding out takes half a day of searching inboxes and shared drives.

The service exists to close all three gaps. Documents that fill themselves in, chase themselves politely, and then file themselves in one known place so the question of whether something was signed takes ten seconds to answer rather than an afternoon.

How the work runs

1. Inventory the documents that repeat. Which ones go out regularly, who sends them, who signs, in what order, and what happens to them today. The list is often shorter than expected — and the ones that go out rarely are usually not worth templating, which is a saving worth naming out loud. Half a day to a day.
2. Build the templates with merge fields. Every value that changes between sends - name, company, amount, dates — becomes a field that is populated automatically instead of typed. Signature and initial blocks are placed, date and checkbox fields added, and the signing order set. Legal wording is left untouched and any gaps are flagged for your lawyer rather than filled in. Two to five days.
3. Reminders and the failure cases. A reminder schedule per document type with wording that is polite and not pushy, plus an agreed expiry. Then the awkward cases are decided deliberately rather than discovered — the signer's email address is wrong, the signer forwards it to a colleague, the document expires unsigned, or somebody signs an old copy that was emailed separately. One to two days.
4. The after-signature automation. This is the part that changes daily life. The signed PDF is renamed to one fixed naming pattern, saved to exactly one folder, attached to the CRM deal or employee record, and the record's status advanced. One destination, one pattern, no exceptions — because the moment a document can end up in two places, the filing question returns. Two to four days.
5. Test with real documents, on a phone. Two or three genuine documents are sent through the whole route end to end, including a deliberate failure, and every one is opened on a phone before launch, because the working assumption is that the signer opens it on a phone. Then a one-page instruction sheet for your staff. One to two days.

What moves the price

The range is $400–$6,000, and three things decide where a project sits.

How many document types there are. Three templates plus one routing automation sits at the bottom of the range. Twenty-five documents across sales, HR and procurement, each with its own fields, signing order and destination, is a different project entirely.

How many systems the signed document has to touch. Saving to a folder is simple. Saving to a folder, attaching to a CRM record, moving that record to a new stage, notifying a channel and creating a task is a chain, and every link in it needs testing for what happens when one step fails halfway.

Whether documents go out in bulk. Sending one contract at a time is straightforward. Sending a policy update to two hundred employees, tracking who has signed and chasing only those who have not, needs a different setup and its own reporting.

What usually goes wrong

A previous client's name survives in the template. It sounds trivial and it is the most damaging error in this service, because someone else's name goes out on your document, in front of your own customer, in a moment that is supposed to demonstrate professionalism. It happens when a real value is typed into a template instead of a merge field, or when a template is built by copying a completed document. The defence is mechanical — before a template goes live, send yourself a test envelope and read the entire document on a phone, not a scan of the first page.

The workflow stops at the signature. The document is signed, an email lands in somebody's inbox, and that is where the automation ends. Three months later the original question — was this ever signed — is back, because the signed file is in a mailbox rather than in the place people look. A workflow is only finished when the file has renamed itself, arrived in exactly one folder, and updated the record it belongs to.

Two copies of the same document are in circulation. Somebody helpfully emails a PDF alongside the signing link, and the counterparty prints, signs and returns that one. Now the signed artefact is an image with no audit trail, it does not match the version in the system, and if it is ever disputed the trail is worthless. The workflow has to be the only route a document goes out by, and that rule belongs in the staff instruction sheet, not just in the configuration.