← Back to blog

How to Get a Client to Sign a Contract

Some clients push back on formal agreements. How to address their concerns, what a minimal contract most will accept looks like, and when to walk away.

The client is enthusiastic. The project is interesting. And then you send the contract and they say “do we really need all this?” or “we don’t usually do contracts with our freelancers” or simply go quiet for a few days. This happens often enough that it’s worth having a position on it before you’re in the middle of it.

A client who won’t sign a contract isn’t necessarily a bad client. But getting a freelance client to sign a contract, and understanding what to do when they resist, is one of the more useful skills you can have. A client who won’t sign has told you exactly where you stand if something goes wrong.

Why Clients Resist Contracts

The resistance usually comes from one of three places. First, genuine informality: some clients, particularly small businesses and individuals, simply haven’t worked this way before and find formal agreements uncomfortable or unnecessary. They’ve hired people on a handshake before and it worked out fine.

Second, institutional inertia: larger organizations often have their own contracts and assume you’ll sign theirs. Sending your contract can create friction because it requires someone on their side to actually read it. This isn’t usually resistance to contracts as a concept — it’s resistance to the administrative overhead of dealing with a new document.

Third, and least common but worth recognizing: some clients resist contracts precisely because a contract would limit what they can do. A client who’s hoping to renegotiate scope, delay payment, or dispute deliverables after the fact has reasons to prefer ambiguity. Their resistance tells you something about their intentions, even if they’d never articulate it that way.

How to Respond to “We Don’t Usually Do Contracts”

The effective response to this is normalizing rather than negotiating. “I work with a contract on all my projects — it protects both of us and keeps everything clear.” That’s it. You’re not explaining yourself. You’re stating how you work.

If the client asks what you need the contract to cover, the answer is: scope, payment terms, and who owns the work. Those are the three things that cause the most problems when they’re not documented. Most clients who were resistant to a formal contract will accept a short document that covers just those elements, framed as a project confirmation rather than a legal agreement.

Framing matters. “I’ll send over the contract” can feel bureaucratic to a small client. “I’ll send over our project confirmation — it’s just a one-pager that outlines what we’ve agreed” often meets less resistance. The document is the same. The framing changes how it’s received.

The Minimal Contract Most Clients Will Accept

If a client is genuinely resistant to a formal agreement, there’s a version of a contract that most will sign: short, plain language, and limited to the essentials. Two pages at most. Written in plain sentences, not legal boilerplate.

It needs to cover:

What you’re delivering. Specific deliverables, formats, quantities, revision limit. Not “design services.” The actual thing.

What they’re paying and when. Total amount, deposit required before work starts, final payment due date. If there’s a late payment clause, one sentence: “Late payments accrue interest at 2% per month.”

Who owns the work. One sentence: “Copyright in the work transfers to the client upon receipt of full payment.” Or, if you’re licensing: “The client receives a non-exclusive license to use the work for commercial purposes. Copyright remains with the freelancer.”

What happens if either party cancels. One sentence on the kill fee or what’s owed for work completed.

That’s a functional contract. Four sections, possibly two pages, written so a non-lawyer can read it in five minutes. Clients who resist a ten-page services agreement rarely resist this. For a full picture of what a complete contract should contain when you have the space for it, see what to include in a freelance contract.

Using Email Confirmation as a Fallback

If a client won’t sign even a minimal document, a detailed email confirmation is better than nothing. Send an email summarizing the agreed scope, the fee, the payment terms, and the timeline. Ask the client to reply confirming the details. Their reply is a written record of the agreement even without a formal signature.

This is less protection than a signed contract. There’s no kill fee clause, no IP ownership clause, nothing about late payments. But it establishes that a scope and a price were agreed, which is the most common point of dispute, and it creates a paper trail that didn’t exist before.

Use this as a last resort, not a first option. And when you do, know that you’re accepting more risk than a signed contract would carry.

Many larger clients will send you their own contract rather than signing yours. This is common and not inherently problematic, but their contract is written to serve their interests, not yours.

Review it carefully before signing. The clauses to look at first: IP ownership (often automatic assignment of all work product), payment terms (often net-45 or net-60, sometimes contingent on their client’s payment), confidentiality (often broad enough to prevent portfolio display), and limitation of liability (often waived for you but not for them). These are negotiating points, not fixed terms. See what the standard clauses in a client-drafted contract mean before you sign anything that transfers copyright or limits your recourse.

Making It Easy to Sign

Friction is the enemy of getting documents signed. A PDF you’ve emailed that requires printing, signing, scanning, and returning will sit in someone’s inbox for days. An electronic signature link takes 30 seconds.

DocuSign, HelloSign, PandaDoc, and similar tools generate signing links that work on any device. Most have free tiers that cover a few documents per month. If you’re sending contracts regularly, the paid plans are worth the cost, both for the ease of signature collection and for the timestamped records they create.

Send the signing link as soon as the project terms are agreed. Don’t wait for the client to ask. “I’ll send over the project confirmation for your signature — you should receive a link in the next few minutes” creates the expectation that signing is the next step, not an optional one.

When to Walk Away

A client who refuses any form of written agreement after you’ve offered a minimal two-page document, a plain English confirmation, and an electronic signing link is telling you something. Not necessarily that they’re dishonest — possibly that they’re very small, informal, and genuinely don’t operate this way. But you’ve done what you can, and the risk of proceeding is now yours to evaluate clearly.

The calculation is: how much is this project worth, and what’s the maximum you could lose if nothing is documented and something goes wrong? If the project is small and the client seems legitimate, proceeding without a contract is a risk you might choose to take. If the project is substantial, involves transferring significant work before payment, or comes with any other flags, the absence of a contract is a reason not to start.

A client’s refusal to sign a contract doesn’t mean they’ll behave badly. It means you have no written recourse if they do. Factor that into the decision, not just the appeal of the project. If you do proceed without a signed document, protecting yourself when freelancing without a contract covers the minimum documentation that still gives you some standing.

Ready to get paid without the paperwork?

One verified identity. Proposals, invoices, and payouts — with a real person beside you.