E-signatures for agencies: SOWs, change orders, and retainers signed the same week

Agencies lose money in a very specific place: the gap between the work being agreed and the work being signed. A client says go, the team starts, and three weeks later someone realises the SOW never came back — or worse, that the extra round of revisions everybody has been doing was never papered as a change order. The work happened. The document that would have paid for it didn't.

None of that is a client-relationship problem. It's a paperwork problem, and it's the cheapest thing an agency can fix.

The documents an agency actually runs on

Agency paper is repetitive by nature, which is exactly what makes it worth systematising:

• Master services agreements, signed once per client, that everything else hangs off.
• Statements of work — one per project, same structure, different scope and numbers.
• Change orders, the single most-skipped document in the business.
• Retainer agreements with a monthly fee, a term, and a notice period.
• Mutual NDAs at the pitch stage — see how to get an NDA signed online.
• Freelancer and subcontractor agreements on the supply side, plus IP assignment where you're delivering work you don't want to be arguing about later.
• Model, talent, and location releases for anything you shoot, which are covered as a document class in how to get a consent form signed online.

The mechanics of putting any of these out for signature are in how to send a document for electronic signature.

The change order is the document that pays for itself

Most agencies under-bill not because they price badly but because scope creeps in increments too small to justify a meeting. A fourth round of revisions. An extra deliverable "while you're in there." A launch date pulled forward. Each one feels too minor to raise, and collectively they are the difference between a profitable account and a break-even one.

The reason change orders get skipped is friction: nobody wants to draft a document to capture two hours of extra work. So remove the drafting. Keep a change order template with fields for the change, the added fee, and the revised date, and issuing one becomes a two-minute job you can do the same afternoon the request lands — while the client still remembers asking for it. A change order sent that day reads as professional. The same one sent at invoice time reads as a dispute.

Build the SOW once, then stop rebuilding it

Your SOW is the same document every time except the scope, the fee, and the dates. Build it once as a reusable template with the signature, date, and text fields already positioned and the signer roles defined. Each new project is then: pick the template, fill in the specifics, send.

That matters beyond the minutes saved. When sending is trivial, paper goes out before the work starts. When sending is a chore, the work starts first and the paper follows "once things settle down" — which is how agencies end up delivering unsigned scope. The workflow is in reusable templates for repeat documents.

Never make the client's legal team create an account

Your day-to-day contact rarely signs alone. They forward the SOW to a procurement lead, a finance director, or an in-house lawyer who has never heard of your agency's tools and has no interest in learning them. If that person hits a registration wall, your document stops moving and you will never be told why.

On Signed, every signer clicks the emailed link and signs in whatever browser they already have open, phone included — no account, no password, nothing to install, and no seat charged for signing. Only senders need seats. The full argument is in why your signers should never need an account.

Two or three approvers on the client side

Client-side approval chains are normal: your contact → their finance or procurement → your own signatory countersigning. Send that as a signing order and each person is emailed only when it's their turn, so nobody sits on a link they can't act on and you always know whose desk it's on. Where order doesn't matter — two co-equal parties on a partnership deal — everyone can sign at once instead. Both modes, plus per-signer fields so nobody signs on the wrong line, are in how to collect signatures from multiple people.

Reminders and expirations keep a start date real

Automatic reminders take the awkwardness out of chasing. The follow-up stops being an account manager deciding whether today is too pushy and becomes a neutral, scheduled nudge to whoever's turn it is. An expiration date turns "this quote holds through the 31st" from a sentence in a PDF into something the document enforces — useful when your pricing assumed a start date the client has now let slide by a month. Both are covered in how to chase unsigned documents.

The status dashboard — sent · viewed · signed · completed — also changes what a resourcing meeting sounds like. "Sent Tuesday, never opened" and "opened five times, still unsigned" are different situations: one is a wrong email address, the other is a client with a question they haven't asked yet.

The record you want when scope is disputed

Scope arguments don't happen at signing. They happen at month four, when someone says the deliverable list was different, or that the person who approved the change order wasn't authorised to.

Every completed document on Signed carries a tamper-evident Certificate of Completion: each signer's name and email, timestamps for every view and signature, and the IP address each action came from — sealed so later edits are detectable. That's a materially stronger record than a countersigned scan, which proves an image exists and nothing else (why print-scan-email costs more than it looks). Details in the audit trail explainer and Audit trail & certificate. Signatures are designed to satisfy the US ESIGN Act and UETA; background in are electronic signatures legally binding?. General information, not legal advice.

What Signed deliberately doesn't do

Worth knowing now rather than in week three:

• No CRM or project-tool connectors and no public API — documents don't auto-create from a deal or a project, and status doesn't sync back.
• No bulk send, so you can't blast a terms update to every client at once.
• No conditional logic — a document can't show or hide clauses based on an answer.
• No in-document payments, no SSO/SAML, no SMS or knowledge-based identity checks, no online notarization, and no EU qualified (eIDAS) signatures.

If your agency needs Salesforce-native sending or bulk campaigns, buy the platform that does that. If it needs a signed SOW before Monday, keep reading.

What it costs

Signed is $9.99 per seat per month, one plan, unlimited documents, month-to-month, with a 14-day free trial. A seat is a sender — five account managers cost five seats no matter how many clients sign, and clients never cost anything.

That shape matters for agencies specifically, because agency document volume is lumpy: three SOWs and six change orders in a busy month, two documents in a quiet one. A capped or per-envelope plan quietly teaches the team to ration paperwork, which is the exact behaviour that loses you the change-order revenue. The reasoning is in why unlimited documents matters.

For comparison, DocuSign's published pricing (docusign.com/pricing, checked June 2026 — verify it yourself; pricing changes and varies by country) listed Business Pro at $40 per seat per month on an annual commitment, and month-to-month at $65 per seat per month capped at 10 envelopes a month. Ten envelopes is one busy fortnight for a single account manager, and paying annually per seat to escape that cap is the annual-contract trap — a bad fit for a business whose headcount moves with the client roster. The side-by-side is on the DocuSign comparison page, the full breakdown on pricing, and seat mechanics in Billing & plans.

Start your free 14-day trial →