New sellers say yes to almost everything. Established sellers say no to the right things. The ability to decline a project, a price, or a scope request without ending the relationship or damaging your reputation is one of the more practical skills on Fiverr — and one nobody explicitly teaches.
There are three situations where "no" is the right answer on Fiverr. Each has a different framing that keeps the buyer's experience positive while protecting your business.
When to say no versus when to find a way
Not every uncomfortable situation warrants a no. Before using any of the scripts below, a quick filter:
Say no when: the project is outside your niche in a way that would require significant learning time, the budget is so far below your minimum that accepting would build resentment into the delivery, or the scope is so unclear that misalignment is almost certain before you start.
Find a way when: the project is adjacent to your niche and learnable, the budget is slightly below but negotiable, or the scope is unclear but a clarifying conversation could resolve it. These situations are better handled with a question than a decline.
The distinction matters because "no" on Fiverr is visible in your response metrics only when you do not reply. Declining politely after a conversation does not hurt your response rate. Ignoring an inquiry does. Always reply, even when the reply is a decline.
Pattern 1: Declining an out-of-scope request
A buyer asks you to do something your gig does not cover. The most common version: a buyer of a basic package who asks for a significant scope expansion in the requirements or in a pre-order message.
The script:
"Thanks for reaching out with this — I can see what you're trying to accomplish. What you've described goes a bit beyond what my current gig covers: [specific element that's outside scope]. I have two options for you. I can deliver [what is in scope] as described, which would cover [specific deliverables]. Or if you'd prefer the fuller scope, I can put together a custom offer for the complete project — usually around [ballpark price]. Which direction works better for you?"
What this does: it acknowledges the request without agreeing to it, states the scope boundary specifically rather than vaguely, and offers two paths forward that both lead to an order. Most buyers choose one of the two options. Some choose neither, which means the order was not going to work regardless.
The key is specificity. "That's outside my scope" is a dead end. "That falls outside what my gig covers, but here is exactly what I can do and here is what a custom project would look like" is a conversation.
Pattern 2: Declining a low-budget inquiry
A buyer's budget is significantly below your rates. This is particularly common with buyers who message before ordering asking whether you can do the project for less.
The script:
"Thanks for the message. My rates for this type of project start at [your price] because [one specific reason — delivery time, scope, expertise requirement]. I understand that may not fit every budget, and I hope you find a seller who's the right fit at your price point. If your budget changes, I'd be glad to work together."
What this does: it closes the negotiation without being dismissive, gives a specific reason rather than just restating the price, and leaves the door open without encouraging extended back-and-forth. The closing line is important — it signals that you are not offended, which occasionally brings buyers back when their budget adjusts.
What this does not do: apologise for your pricing, explain that you are "worth it," or offer a discount. None of those work. A seller who apologises for their pricing trains buyers to push on pricing every time.
One caveat: if a buyer is slightly below your rate and the project is genuinely appealing, there is nothing wrong with offering a modest scope adjustment that brings the project to their budget rather than discounting the full scope. "For that budget I could do [adjusted scope] — would that work?" is different from "okay I'll give you a discount."
Pattern 3: Declining a project that is not the right fit
Sometimes a project is technically within your niche and within a reasonable budget but is still wrong: the buyer is communicating in a way that signals difficult expectations, the brief is unclear in ways that suggest a mismatch, or the project type has historically produced your worst outcomes.
This is the hardest "no" to justify because there is no obvious reason. The right answer here is a light decline that does not require explanation.
The script:
"Thanks for reaching out. After reviewing your brief, I don't think I'm the right fit for this particular project — I wouldn't want to take it on without being confident I could deliver exactly what you need. I hope you find a seller who's a stronger match for this one."
No explanation. No apology. No offer of an alternative unless you genuinely have one. A brief, professional decline that respects both your time and theirs.
The instinct against this script is the fear that buyers will be offended. Some will be mildly surprised. But buyers who receive a polite, honest decline almost never leave negative feedback about it — they move on. Buyers who receive a yes from a seller who was not the right fit and then receive a disappointing delivery are the ones who leave bad reviews.
The response rate protection
All three patterns above assume you reply. Not replying is what damages your response rate and leaves buyers with a worse experience than any polite decline would.
Every first message deserves a reply within 24 hours — even when the reply is "this is not the right fit for me." The reply protects your response rate metric, maintains your professional reputation, and occasionally converts into a future order when the buyer's situation changes.
The Fiverr inbox guide covers the full response management system including quick replies that make maintaining high response rates sustainable even during busy periods. The handling difficult buyers guide covers what to do when buyers push back on a no you have already given.