How do I push back on vague scopes and rates as a freelance UX designer?

[Jason97]

I've been freelancing as a UX designer for about a year, and while I'm getting consistent project offers, I'm realizing I'm consistently undercharging and agreeing to vague scopes that lead to endless revision cycles, hurting my profitability and work-life balance. I know I need to get better at freelance contract negotiation, but I feel unprepared and anxious about pushing back on client requests, especially with larger agencies that have their own standard agreements. For experienced freelancers, what are the non-negotiable clauses you always include in your contracts, and how do you confidently navigate conversations about rates, kill fees, and defining what constitutes a "revision" versus a new scope of work? I'm also curious about your process for handling clients who resist signing a formal contract and prefer to work on a handshake agreement.

[Jerry.L]

Non-negotiables I always include in contracts:
- Scope of Work with clearly defined deliverables and acceptance criteria, plus a realistic timeline with milestones.
- Payment terms: upfront or milestone-based deposits, scheduled payments tied to deliverables, and late-fee language.
- Change orders: any addition or change requires a written Change Order, with new price and timeline.
- Intellectual property: who owns the final deliverables, licenses to use, and what the freelancer retains (source files, templates, methods) for portfolio use.
- Confidentiality and data security basics relevant to your work.
- Termination and wind-down: what happens if either side ends early, final deliverables, and how billing stops.
- Revisions policy: specify how many rounds are included and how additional revisions are billed.
- Warranties, liability cap, and indemnification: keep things sane legally.
- Portfolio rights: explicit permission to show work in your portfolio and case studies.
- Governing law and dispute resolution, and who may assign the contract.

Kill fees and handling termination: a practical, common approach is a termination clause that can be activated if the client ends the project without cause. For example, a termination fee of 10–25% of the remaining project budget or a pro‑rated cost to date plus a small completion fee helps cover the time you’ve already invested. If you’re new to this, start with 10% and adjust as you gain leverage.

[JeffreyP]

A practical way to distinguish revision from new scope:
- Revision: changes to the agreed deliverables that fall within the original scope (e.g., color tweaks, layout tweaks, copy edits). Include up to a set number of rounds (often 2) in the base fee.
- New scope: any addition of features, screens, integrations, or substantial changes that would require more time and resources and an updated SOW.
- Process: require a written Change Order that specifies the new scope, new pricing, and any timeline shifts. This keeps you from drifting into “we’ll do one more thing” territory.
Example language: “Any changes to the Deliverables described in Exhibit A shall be made only by a written Change Order signed by both parties; cost and schedule impact to be agreed in writing.”

[Jonathan.S]

Negotiation mindset and tactics:
- Anchor high and present 2–3 options (A, B, C) with different scopes and price points so the client can choose rather than you ceding ground on the first offer.
- Frame price around value and risk avoided (e.g., faster delivery, cleaner specs, fewer revisions).
- Use a calm, collaborative tone: “I want this to be a great partner relationship, here’s what I can commit to and what would require more budget.”
- Don’t bargain on the fly; have a prepared rate card and a few standard clauses you’re comfortable with.
- If a client pushes back on rates, propose a scope adjustment rather than lowering price; or offer a phased approach (core MVP now, enhancements later).
- Keep a written trail (email confirmations or a simple SOW) to avoid disputes later.

[John_J]

Handling agencies and formal contracts:
- Large agencies often want to keep their own MSA. You can still protect yourself by proposing a separate SOW that sits under their MSA. Use a concise engagement letter or two-page SOW that defines scope, deliverables, milestones, and payment terms.
- Ask for the MSA to apply to master terms but keep your high‑risk terms in the SOW (IP, liability cap, termination, change orders).
- If they resist, offer a minimal form contract with essential elements and a link to their MSA for reference, plus a calendar invite for a kickoff meeting.
- Don’t sign anything you haven’t read; if they pressure you, ask to bring in a lawyer or a freelancer-friendly contract attorney for a quick review.

[MichaelFL]

Handshake agreements and how to handle them:
- Handshake agreements are risky; explain that a short written Letter of Engagement or a one-page contract protects both sides while keeping negotiations efficient.
- A two-page engagement letter can cover scope, milestones, payments, and a few critical terms; add a simple “work-for-hire” note and IP rights language.
- Use digital signatures (DocuSign, HelloSign) to speed things up and reduce friction. If they truly won’t sign, propose a limited scope trial contract with explicit termination terms and a plan to formalize later.
- In all cases, preserve a clean audit trail (emails confirming scope, price, schedule) in case of disagreement later.

[Justin.S]

Practical starter clauses you can adapt:
- Change Order: Any change to the scope requires a written Change Order with new deliverables, price, and timeline.
- Revision cap: Up to 2 rounds of revisions included in the base price; additional revisions billed at $/hour or at a higher per‑item rate.
- Kill fee: If client terminates the project after kickoff, you’re compensated for work completed plus a small termination fee (e.g., 10–25% of remaining fees) to cover sunk time.
- IP and portfolio use: Final deliverables provided; you retain rights to describe the work and showcase it in your portfolio unless the client prohibits it; client gets perpetual, non-exclusive license to use the deliverables for their business needs.
- Acceptance criteria: A fixed process where deliverables must pass a defined set of criteria before final payment; include a sign-off mechanism.
- Payment terms: 30 days net; late fees; deposit up-front; milestone-based payments.
- Confidentiality: basic NDA terms as needed for the project.
- Liability cap: set a reasonable cap (e.g., a multiple of the project’s fees) to avoid unlimited liability.

[Luke_R]

Not legal advice here, but a practical reminder to bring a lawyer into the loop if you’re negotiating complex terms or high-risk engagements. Start with a lean contract and escalate to full MSAs as you grow. If you want, I can sketch a one-page engagement letter tailored to your typical client type and pricing.