Freelance Design Process: From First Call to Delivery

How to run a freelance design project in phases, from the first call to delivery, and the process mistakes that cost freelancers the most money.

info Quick Definition
A freelance design process is the sequence of phases an independent designer uses with a client: discover the problem, propose scope and price, sign a contract, collect a deposit, design, deliver, and close. Its purpose is to keep scope from growing unchecked and to leave a written agreement at each phase.

What is the freelance process, and why does it matter?

A freelance project looks like a team project, but with less safety net. There is no manager filtering changes, no procurement team negotiating the contract, and no colleague doing the final review. Anything decided without writing it down gets lost, and anything not agreed at the start becomes an argument at the end.

There is no formal standard for this process. Zoom structures a proposal in seven parts and Efdot Studio describes five stages, from inquiry to presentation: the names change, but the order is similar.

Why does this matter for a junior designer?

Because freelancing is one of the most common ways to start, and process mistakes are the ones that cost the most. A junior who works without a contract, accepts unlimited revisions, or delivers files before payment learns those lessons at their own expense. Knowing the sequence avoids almost all of those traps.

The process also gives you a shared language with the client. Talking about scope, review rounds, and dependencies makes the conversation professional without sounding distrustful.

How does discovery work?

Discovery is the first conversation that defines the problem before you propose anything. Zoom, in its guide to design proposals, lists what to clarify:

  • Target audience. Who will use what you design.
  • Prior work. What was tried before and what did or did not work.
  • Success at three months. What has to happen for the client to feel the project was worth it.
  • Assets and constraints. Brand, content, technology, deadlines, or rules that already exist.
  • Budget and approval. A rough range and who signs off.

If the client cannot answer these questions, the project is not ready for a proposal yet. That is also information, and it is worth saying so.

How do you write the proposal?

Zoom suggests a structure: discovery, executive summary, scope, process, timeline, pricing, and close. The close restates payment terms, includes one testimonial or portfolio sample, and offers a single next step instead of several options.

Three concrete recommendations from the same source:

  • Group costs by deliverable (for example logo, brand guidelines, and file preparation), so the client sees what each amount buys.
  • Name what is out of scope, such as social media templates or packaging design, so the client does not assume it is included.
  • Cap revisions and leave time for them. Zoom suggests, for example, two rounds per deliverable with extra rounds at a separate fee, plus buffer time in the schedule, because clients rarely respond the same day.

The proposal should be specific. Zoom warns that a generic proposal, recycling the same paragraphs for every client, signals little effort to understand the client’s brand.

What should the contract include?

A Dribbble guide on freelance graphic design contracts recommends covering five points:

  • Scope and deliverables. The services, the start date, an estimated timeline, deliverables with their file formats, and a clause for anything outside the original scope.
  • Revisions. How many rounds the scope includes and what each extra round costs.
  • Payments. Whether there is a deposit, how many payment milestones exist, and what late fees apply.
  • Termination. What happens if either party cancels, who owns the work done so far, and whether cancellation fees apply.
  • Ownership of the final work. Whether the client gets exclusive rights and when: the guide recommends it happen once you have been paid.

A contract does not replace professional advice. If the project is large or the client asks for unusual clauses, have someone with legal experience review it, and laws on freelance contracts vary by country.

How do deposits and payments work?

Some studios take a deposit when the proposal is accepted and deliver final files only once the final invoice is paid. Efdot Studio, for example, describes an initial fee that is typically 50% of the total. It is an individual practice, not a rule, but it shows the principle: work the client has not paid for is not delivered.

Before setting a percentage, review how much time and prior work you are putting into the project. A small deposit on a long project means funding it with your own money. For structuring that calculation, budget management offers a frame.

When should you NOT take the project?

  • When the client wants only production and does not want to discuss discovery. Zoom puts discovery before scope: without a defined problem, scope is hard to close.
  • When scope and budget are already fixed by a framework contract you cannot change.
  • When the client refuses to agree scope in writing. UXmatters reminds us that the client must review and approve scope before work begins; without that approval, any later dispute has no reference point.

To estimate effort before you propose, the article on estimating design work offers a framework that also works for freelance.

Example

Illustrative example: an independent designer is asked to redesign a clinic’s website.

  • Discovery: two meetings. It becomes clear that success means more appointment requests from mobile over three months, that a booking system cannot be changed, and that the clinic manager gives final approval.
  • Proposal: three priced deliverables: a quick study with five patients, a booking prototype, and the website design. Out of scope: content, photography, and development.
  • Contract: two review rounds per deliverable, with a third round at an additional charge.
  • Deposit and delivery: a deposit is collected on acceptance. Final files are delivered after the final invoice is paid.

The project was not the biggest of the year, but there were no scope arguments at the end, which is where problems usually show up.

If you want to see how freelance work combines with AI tools, the article on freelancing with AI covers pricing by scope versus by time.

Common mistakes

  • Starting work without a signed contract or a deposit.
  • Writing vague scope that drifts into unpaid changes.
  • Reusing one client’s proposal for another without adapting it.
  • Leaving no margin in the timeline for review rounds.
  • Not flagging client dependencies, such as content or approvals.
  • Delivering final files before the invoice is paid.

Sources

Frequently asked questions

What phases does a freelance design project have?
One possible sequence is discovery, proposal, contract, deposit, design, delivery, and close. There is no formal standard, but the practical guides that describe the process follow a similar order.
What should a design proposal include?
Discovery, an executive summary, scope, process, timeline, pricing, and a close with proof, terms, and one next step. Zoom recommends grouping prices by deliverable and naming what is out of scope.
What should you clarify during discovery?
The target audience, what prior work succeeded or failed, what success looks like three months out, brand assets and constraints, the budget range, and who approves. Without these answers, the proposal will be generic.
What does a design contract usually include?
According to a Dribbble guide: scope and deliverables, included review rounds and the fee for extra ones, a payment schedule, what happens if either party cancels, and when ownership of the final work transfers, which the guide ties to payment.
Is there a usual deposit in freelance projects?
Efdot Studio, a design studio, collects an initial fee that is typically 50% of the total once the proposal is accepted, and sends the final files only after the final invoice is paid. It is an individual practice, not an industry standard.