Direct answer

Skip the paperwork if they insist. Do not skip the protection.

Plenty of good clients hate formal contracts, and plenty of bad situations started with one anyway. What protects you is not the document, it is four specific things being settled in writing before work starts. Here is what those four things are, the single email that settles all of them, and the staged start that caps what a no-contract job can cost you.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 19, 2026. The delivery record quoted below is real and public, re-checked against the live service on publication day.

What a contract actually does

Strip the legal furniture away and a contract does four jobs. It fixes the scope, so done has a definition. It fixes the price, so the invoice is not a negotiation. It fixes the acceptance test, so there is a moment the client says the work counts. And it fixes the payment terms, so everyone knows what lands when. A formal agreement is one way to do those four jobs. It is not the only way, and a job where all four are settled in plain writing is safer than a job with a signed template nobody read.

The one-email agreement

Send one short email before anything starts, and get a yes back. It carries: the scope in three or four lines, the total price and the deposit that starts the work, how delivery happens (one record link where each step lands and can be checked), how acceptance works (the client accepts or flags the delivery on the record), when the balance is due (on acceptance), and the start date (when the deposit lands). A reply of yes, go ahead makes that email the written agreement for the job. It takes four minutes, it does not feel like lawyering, and it quietly performs all four jobs above.

Why the record matters more without a contract

With no formal document, the delivery record is your shared fact base, the thing both sides point at when memories diverge. Build it like this one is built:

A delivery record both sides can check

That record was filed by an independent studio for its own delivery, and anyone can recompute it and read its stated gaps. When your job's scope email points at a record kept to that standard, the no-contract job stops depending on who remembers the call correctly.

Start staged, not exposed

However friendly the client, a no-contract job starts small: a first stage priced so a walk-away costs you days, not weeks, behind a deposit, with the final files held until the balance lands. If stage one runs clean, the stages can grow. This is not distrust; it is sizing the risk to the paper that actually exists, which in this case is one email and a delivery record.

Red flags that end the conversation

Some refusals are information. A client who will not put the scope and price in a single email is not avoiding paperwork, they are keeping the exit foggy. A client who refuses any deposit while demanding an urgent start wants you financing their deadline. A client who wants the source files before the first payment wants the work with no trail at all. Any one of these, on a no-contract job, is the answer to whether you should start: shrink to a small paid first step, or decline and keep the slot.

What this page does not settle

Some work, some industries, and some places legally require formal contracts, and whether a short written agreement binds in a dispute varies by jurisdiction. This page is general information, not legal advice. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the work was correct, and Zambo never holds your money or the client's.

Frequently asked questions

My client wants to start work without a contract. How do I protect myself?

Settle the four things a contract exists to settle, in writing, before work starts: the scope, the price, the acceptance test, and the payment terms. One short email can carry all four, with the deposit that starts the work, delivery on a checkable record, acceptance on that record, and the balance due on acceptance; a yes in reply makes it the job's written agreement. Then start staged: a small first stage behind the deposit, final files held until the balance lands, stages growing only as trust is earned. If the client will not put even that in writing, treat the refusal as the answer and shrink the job to a small paid first step or decline it.

What is the minimum I need in writing?

Four lines are the floor. Scope: what will be delivered, in plain words. Price: the total, the deposit, and when the balance is due. Acceptance: how the client confirms the work counts, ideally by accepting it on the delivery record. Start: the date work begins, tied to the deposit landing. Dates on all of it. Below that floor you do not have a light agreement, you have a misunderstanding scheduled for the delivery day, and every later argument about scope, price, or payment will be settled by whoever remembers the conversation most confidently.

How do I raise it without scaring the client off?

Frame it as your standard setup, because it should be. A working form: I keep this light, no formal contract needed. Before I start I send one email with the scope, the price, and the dates, and I deliver on one link where you can check every step and accept it there. Just reply yes and we are booked in. Most clients relax at that message, because the same writing that protects you protects them: the price cannot drift upward, and the delivery is checkable instead of promised. The clients it scares off are the ones the writing existed for.

What if they will not put anything in writing at all?

Then you have learned the most important fact about the job before spending an hour on it. A client who refuses an email, refuses a deposit, and wants an urgent start is asking you to carry every risk the writing would have shared. Offer the smallest paid first step that proves the relationship, priced so a walk-away costs you almost nothing, delivered on a record. If that is refused too, decline politely and keep the slot for a client who will sign an email. Jobs that begin in fog end in the fog, with you holding the unpaid invoice.

How do I protect myself on every no-contract job?

Make the light setup your default rather than a per-client decision. Run the work through Zambo, so the scope email points at a handover link where every step lands with its own verifiable receipt and the client accepts the delivery on the record itself, which is the acceptance test your one email promised. For $0.99, run the next job on that footing, with the record building from the first step: https://zambo.dev/day-pass/ A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month or $290 a year, and $19 a month for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related