A client comes back after your proposal with "can you do this for ₹35,000 instead of ₹50,000" and nothing else changes about what they are asking for. Most freelancers either cave immediately, because they are afraid of losing the project, or dig in and refuse, because they are afraid of being taken advantage of. Both reactions skip the actual negotiation.
Negotiating a freelance contract is not about holding your price or losing the client. It is about trading terms so that whatever changes, changes on both sides. Here is how to do that without either caving or blowing up the deal.
The rule that makes every negotiation easier: never give without getting
Every concession you make should come with a matching change somewhere else in the agreement. If a client wants a lower price, the scope shrinks to match it. If a client wants a faster timeline, the price goes up or the revision rounds go down. A concession given for free teaches the client that your first number was never your real number, which makes every future negotiation with them harder, not easier.
This is different from being rigid. You are not refusing to move. You are refusing to move on one thing while everything else stays fixed. State it plainly: "I can do ₹35,000 if we cut the scope to two logo concepts instead of three and one round of revisions instead of two." Now the client is negotiating a real trade-off, not just testing whether you will drop your price for nothing.
What to negotiate freely, and what to protect no matter what
Timeline, the exact number of deliverables, and how many revision rounds are included are all reasonable things to trade against price. These are the levers that genuinely change how much work a project involves, so moving them in exchange for a different number is a fair trade for both sides.
Payment terms, IP transfer conditions, and any kill fee for early termination are different. These are not scope, they are protection, and they should not move just because a client pushes on price. A client who specifically wants to weaken your payment terms, not just lower your fee, is often telling you something about how they intend to pay once the project starts. The guide on freelance client red flags to spot before you sign covers this exact pattern in more depth.
Handling the four most common pushback moments
Rate pushback ("can you do it cheaper") gets the scope trade above: name a specific reduction and hold your line on what that reduction actually removes. Do not simply lower the number and keep the scope the same, since that erodes your rate for every future project once word gets around, or once the same client remembers you moved once and expects you to move again.
Timeline pushback ("can you deliver faster") is a capacity question, not a willpower question. If a faster timeline is genuinely possible, it usually costs you evenings, weekends, or dropping other work, and that cost deserves a rush fee, typically 15 to 25% above your standard rate. If it is not actually possible without cutting corners, say so directly rather than agreeing and then delivering something weaker than what you would normally produce.
Scope pushback during negotiation ("can you also include X") before a contract is signed is easier to handle than scope creep after work has started, precisely because nothing is locked in yet. Price the addition and offer it as an option rather than folding it into the existing number silently. Once signed, any further additions should go through the change-order process rather than reopening the original negotiation. See the guide on handling scope creep without losing the client or margin for what happens once the contract is already in motion.
Payment-terms pushback ("can we do 100% on completion instead of an upfront amount") is the one worth being most firm about, especially with a new client where you have no track record together yet. An upfront payment is not a formality, it is the mechanism that filters out clients who were never serious, covered in the full breakdown in the guide on setting freelance payment terms in India. Reducing the upfront percentage is a reasonable trade for an established client with a proven payment history; removing it entirely for someone you have never worked with is a real risk, not a minor concession.
Knowing when to walk away from the negotiation entirely
Not every negotiation should end in an agreement. If a client keeps pushing after you have offered a clear, fair trade-off, repeatedly asking for the original price back with the reduced scope, or refuses every version of protective terms you propose, that pattern is the actual signal, not the specific ask. One round of pushback is normal business. Three rounds of the same pushback dressed differently is a preview of how this client will behave once the contract is signed and you have less leverage than you do right now.
Walking away from a negotiation that is not converging is not a loss. It frees up the time you would have spent managing a difficult client relationship for a project that was already showing warning signs before it even started.
Getting the negotiated terms into the actual contract
Whatever gets agreed in a negotiation conversation, whether over email, a call, or WhatsApp, needs to end up written into the contract itself before work begins. A verbal agreement about reduced scope or a rush fee that never makes it into the signed document is not protection, it is a memory both sides may recall differently later. See the full guide on writing a freelance contract that actually protects you for what else needs to be in that document beyond the negotiated terms. Rinto lets you fill in the final agreed scope and amount for a project contract and send it for e-signature in the browser, so whatever was actually negotiated becomes the version both sides sign, not a verbal understanding that drifts once the project is underway.
Frequently Asked Questions
How do I respond when a client asks for a lower price?
Offer a specific scope reduction that matches the lower price, rather than simply agreeing to the new number. Something like reducing the number of deliverables or revision rounds included. This makes the negotiation a real trade-off instead of teaching the client that your first quoted price was never firm, which makes every future negotiation with them, and with clients who hear about it, harder.
Which contract terms should never be negotiated away?
Payment terms (especially the upfront percentage for a new client), IP transfer conditions, and any kill fee for early termination are protection, not scope, and should not move just because a client pushes on price. Timeline, number of deliverables, and revision rounds are reasonable to trade, since they genuinely affect how much work the project involves.
Should I charge extra for a faster timeline?
Yes, if delivering faster is genuinely possible, it usually means giving up evenings, weekends, or other work, and that cost deserves a rush fee, commonly 15 to 25% above your standard rate. If a faster timeline is not actually achievable without cutting corners, say so directly instead of agreeing and then delivering weaker work than you normally would.
When should I walk away from a contract negotiation?
When a client keeps pushing after you have offered a clear, fair trade-off, repeatedly asking for your original price back with a reduced scope, or refuses every version of protective terms you propose across multiple rounds. One round of pushback is normal. Three rounds of the same pushback dressed differently previews how this client will behave once the contract is signed and you have less leverage than during negotiation.
Do negotiated changes need to go into the written contract?
Yes, always. Whatever gets agreed during a negotiation conversation, whether by email, call, or WhatsApp, should be written into the actual contract before work begins. A verbal understanding about reduced scope or a rush fee that never makes it into the signed document is not real protection, since both sides can recall it differently once the project is underway.