Ask almost any freelance designer about their worst client experience and the story usually involves one of three things: work that was delivered in full and never paid for, a project that expanded so far beyond the original brief that it stopped being worth finishing, or a contractor arrangement that felt fine until the moment it did not.
What connects almost every version of those stories is the same thing. The designer did not have adequate protection in place before the work started. Not because they did not know it mattered, but because the conversation about protection happens after the problem, not before.
Before you send a proposal or deliver anything, take ten minutes to confirm the business on the other side is what it says it is.
A professional website and a business email feel like sufficient evidence. For most clients they are. For the ones who are not, discovering the problem after you have delivered work is significantly more expensive than a quick check beforehand.
Many US businesses operate with an Employer Identification Number, particularly companies, partnerships, and employers. If a client says they have one, verifying that it actually matches the business they claim to represent is a sensible due diligence step. A business lookup system makes this straightforward. If the details do not match or the client cannot provide one when asked, that is worth knowing before you start.
For UK and European clients, Companies House is the equivalent check. Confirm the company is actively registered, that the person you are dealing with has a legitimate role, and that the details match what you have been told.
A few practical signals are worth watching regardless of where the client is based. Reluctance to sign a contract, insistence on paying only on final delivery with no deposit, or a business address that does not check out are all worth taking seriously before you commit.
Designers often use contracts that are too short, too vague, or borrowed from a template that was not written for their situation. The document feels like protection. When something goes wrong, it frequently is not.
Payment terms need to be specific. Not just the total but the deposit before work begins, any milestone payments, the exact due date for the final payment, and what happens if it is late. A contract that says "payment within 30 days" without specifying what triggers that period will be read differently by every client who signs it.
Revision limits are where vague language causes the most ongoing pain. "Reasonable revisions" means something different to everyone. Three rounds of minor changes and two rounds of structural revisions is specific. "Until the client is happy" is not a revision limit. It is an open commitment.
Intellectual property is the section most designers handle incorrectly. In most jurisdictions the creator retains copyright unless the contract explicitly transfers it. Designers regularly sign away full IP ownership as standard without realising they could have kept it or charged more for the transfer. Know what you are giving away before you agree to it.
Kill fees belong in every project contract. A project that gets cancelled after significant work has been completed costs real time and income. A clause specifying that a percentage of the total is owed if the client cancels after a certain stage is standard in professional creative work and should be in yours.
Studios that bring in other designers, developers, or photographers on a project basis often do so without thinking carefully about how those arrangements are structured legally.
Calling someone a contractor does not make them one. The actual nature of the working relationship is what matters. A person who works regularly for your studio, follows your internal processes, uses your equipment, and operates day to day under your direction will look like an employee to most legal frameworks regardless of what their contract says. That classification has implications for tax, for the rights that person may be entitled to, and for your obligations as the business engaging them.
Consider a small studio that brought in the same illustrator for eighteen months across multiple projects. The work was always described as freelance. But the illustrator worked exclusively for the studio during that period, attended client calls, used the studio's project management systems, and was expected to be available during set hours. When the relationship ended, the question of employment status became complicated in ways nobody had anticipated when the first project started. The studio had no documentation that clearly established the freelance nature of the arrangement, and the working reality pointed in a different direction entirely.
If your studio is growing to the point where people are working for you regularly, understanding your obligations as an employer before a situation arises is considerably less disruptive than addressing it after.
Most designers do not become good at contracts because they enjoy paperwork. They become good at them because at some point they lost money, spent weeks chasing an invoice, or found themselves in a disagreement over work that everyone thought had already been settled.
A solid contract does not guarantee a project will go smoothly. What it does is make the difficult conversations significantly easier when they happen, because there is something concrete to refer back to rather than competing memories of what was agreed.
The verification steps, the payment terms, the revision limits, the IP clauses. None of them take long to get right at the start. All of them matter considerably more than they seem to before something goes wrong.
Until next time, Be creative! - Pix'sTory