Freelance contracts with e-signature

What a freelance contract is actually protecting

Not litigation. The overwhelming majority of freelance disputes never get near a court, because the amounts do not justify it. What a contract does is settle, in advance and in writing, the four things that later become arguments: what is in scope, what happens when the client wants more, when payment is due, and who owns the work.

That is a short document. A freelance contract that runs to twelve pages is usually a company template with the company removed, and it makes clients nervous for no gain. The useful version fits on two.

Templates you edit once and reuse

Flowzivo ships with contract types you can start from and lets you save your own as templates. The distinction matters: the second contract you send should take two minutes, because the thinking was done on the first one.

Client details, dates and amounts are filled from the client record rather than retyped, which removes the most common embarrassment in reused documents — the previous client's name still in paragraph four.

Signing in the browser, on a phone

Both parties sign by drawing on the document, in the browser, with a finger on a phone or a trackpad on a laptop. There is no account for the client to create and no application for them to install, which is the point: every barrier you put between a client and a signature is a delay you pay for.

The signed document keeps a record of when each signature was added. That audit trail is what makes an electronic signature worth more than a scanned photograph, and it is the part that email-a-PDF workflows never have.

Expiry, and knowing what is outstanding

A contract can carry an expiry date, and unsigned contracts show up as outstanding in your own list rather than disappearing into a sent-items folder. Work that has started without a signature is a specific, nameable risk, and the first step to managing it is being able to see it.

Flowzivo is not a legal service and none of this is legal advice. Electronic signature law differs by country and by the type of agreement, and for anything substantial you should check the rules that apply where you and your client are.

The four clauses worth arguing about

Scope is first, and it is the only one clients reliably read. Describe the deliverable in terms someone could check: three page designs, two rounds of revisions, source files on final payment. Vague scope is not generous, it is an invitation to a dispute you will lose because nothing was written down.

Payment terms are second. A due date, what happens when it passes, and — if you can get it — a deposit. Third is what happens when the client wants more than the scope: not a refusal, but a stated mechanism, usually a written change at an agreed rate.

Fourth is ownership of the work, which matters more than people expect. In many jurisdictions the creator holds copyright by default, and clients frequently assume the opposite. Saying explicitly that rights transfer on final payment protects both sides and gives you leverage that no reminder email can.

Keeping the signed version findable

A signed contract is only useful if you can produce it eighteen months later, in the week the argument happens. Contracts in Flowzivo sit against the client record rather than in a folder, so the path to it is the client's name rather than a memory of what you called the file.

Export the whole workspace periodically anyway. This is true of any tool and doubly true of documents you might one day need to hand to someone else.

Questions