Contracts and signatures
Signing your side, the signature file rules, where the signed PDF ends up, and how to invalidate one.
Contracts are optional. The Include a contract toggle in the offer wizard is off on new offers.
A contract carries two signatures, yours and your client’s. Each one is drawn on a signature pad or uploaded as an image.
Signature states
State | Meaning |
|---|---|
Unsigned | Nobody has signed |
Signed by you | You signed, ready to send |
Signed by both | Your client accepted, the deal is on |
You sign first. The offer won’t send until you do.
Signing your side
Billow generates the contract from your template, filling in the account, project, and your standard terms. Edit & Sign Contract on the Contract step opens it.
The dialog puts the contract on the left and your signature on the right. The wording is editable, and the Load template dropdown above the editor pulls in a different template. Signing takes your full name, your company, your signature, and the consent line, then Sign Contract.
Your standard terms come from Contract templates, so most of this is pre-filled.
Your signature
Draw it with a mouse, a trackpad, or a finger. A clear button above the pad wipes it.
An upload replaces drawing. Drop a file onto the pad or use the upload button. The file has to be:
A PNG
On a transparent background
Under 1 MB
No bigger than 2000×1000 pixels
A file that breaks one of these rules is rejected, with a message naming the rule. Photos and flatbed scans fail the transparency rule: a solid background renders as a white block around the signature on the contract.
Your client’s signature
Your client signs on the offer page when they accept.
They enter their verification code, read the contract in full, and then sign it: full name, company, their own drawn or uploaded signature, and a consent line confirming the electronic signature is binding. The same file rules apply to their upload.
Billow renders the signed contract at that moment. Your name, company and signature sit on one side, theirs on the other, each with the date it was signed. Anything they declined is left out, and the fee in the contract is recalculated to match.
Where the signed contract ends up
The signed PDF is stored with the project and emailed to whoever signed it, attached alongside the accepted offer.
Your copy is the Contract button on the project overview. Once your client signs, it hands back the stored file, so it stays exactly as they saw it however your template, logo or details change later.
Their copy is the email. The offer page stops handing out documents the moment they sign, and tells them so.
Invalidating a contract
Invalidate unsigns the contract. It works while the project is Draft, Offer Pending or Rejected.
Invalidating:
Clears both signatures and their images
Deletes the stored PDFs
Invalidates the share link your client has
Releases the offer number
Pulls the project back to Draft
Sending again afterwards gives your client a new link, a new code, and a new offer number.
On a rejected offer, invalidating is the way to change the terms and send it again.
After the project is active
The contract is locked, and the Include a contract toggle greys out with “Can’t be changed once the project is active.”
