Not every project that lands in your inbox is a good fit. Some pay too little. Some have red flags all over them. And some are perfectly fine projects that just don't align with what you're doing right now.
Saying no is hard. Especially when you're freelancing and some part of your brain is always whispering "but what if work dries up?" I get it. But taking on the wrong project costs you more than turning it down ever will. Bad-fit projects drain your energy, eat into time you could spend on better work, and sometimes damage client relationships that started fine but soured because the fit was off from the start.
The trick is declining in a way that's professional, kind, and keeps the door open for future work. Here are five scripts for the most common situations.
Why You Should Get Comfortable Saying No
Every yes to the wrong project is a no to something better. That's not motivational poster talk. It's math. If you're buried in a $500 project that's eating 20 hours of your week, you literally can't say yes when a $3,000 project shows up on Thursday.
Freelancers who grow their income consistently aren't the ones who say yes to everything. They're the ones who get selective. They protect their time. And they decline gracefully enough that the people they turn down still think well of them.
The emails below are designed to do exactly that.
Script 1: When the Budget Is Too Low
This is the most common reason you'll decline work. The client seems great, the project sounds interesting, but the budget is nowhere near your rates.
Subject line: Re: [Project Name] - Availability
Hi [Name],
>
Thanks so much for thinking of me for this project. I appreciate you reaching out, and it sounds like an interesting one.
>
After looking at the scope, I don't think I'd be able to do it justice at the budget range you mentioned. My rates for this type of work start at [your rate], and I want to be upfront about that rather than try to squeeze it into a number that wouldn't let me deliver my best work.
>
If the budget has some flexibility, I'd love to chat about what we could make work. If not, no hard feelings at all. I'd be happy to point you toward a couple of other freelancers who might be a great fit.
>
Either way, thanks for reaching out. I hope we get to work together on something in the future.
>
Best,
[Your Name]
This works because you're not insulting their budget. You're framing it as a quality issue. You can't do your best work at that number, and you'd rather be honest than deliver something mediocre.
The offer to recommend someone else is a nice touch. It leaves them with a positive impression and shows you're thinking about their needs, not just your own.
Script 2: When You're Fully Booked
Sometimes the project is perfect but you genuinely don't have bandwidth. This one's actually the easiest to write because it's flattering to both sides.
Subject line: Re: [Project Name] - Timing
Hi [Name],
>
This project sounds right up my alley, and I wish I had the bandwidth to take it on. Unfortunately, I'm fully committed through [date/timeframe] and wouldn't be able to give it the attention it deserves.
>
If your timeline has some flexibility, I'd love to circle back around [specific date] when things open up. If you need to move forward sooner, I completely understand.
>
Would it help if I sent over a couple of names of people who do similar work? Happy to make an introduction.
>
Thanks for thinking of me,
[Your Name]
Be specific about when you might be available again. "I'm busy" is vague and forgettable. "I'm booked through mid-April" gives them something concrete to work with. Some clients will wait for the right freelancer.
Script 3: When the Project Has Red Flags
Maybe the client wants "just a quick thing" that's clearly 40 hours of work. Maybe they've mentioned they've been through three freelancers already. Maybe something about the communication just feels off.
You don't need to explain the red flags. You just need to decline cleanly.
Subject line: Re: [Project Name]
Hi [Name],
>
Thanks for the detailed overview of what you're looking for. I've given it some thought, and I don't think I'm the right fit for this particular project. I want to make sure you find someone whose skills and working style align really well with what you need.
>
I appreciate you considering me, and I wish you the best with the project.
>
Best,
[Your Name]
Notice what this email doesn't do. It doesn't explain why. It doesn't list the red flags. It doesn't try to fix the client's approach. It just declines politely and moves on.
You don't owe anyone a detailed explanation for why you're not taking their project. A clean, professional no is enough.
Script 4: When the Project Isn't in Your Wheelhouse
Getting asked to do work outside your specialty is actually a compliment. It means someone thinks you're capable of more than your core offering. But taking work you're not great at usually ends badly for everyone.
Subject line: Re: [Project Name] - Quick Thought
Hi [Name],
>
I'm flattered you thought of me for this! After reviewing the project details, I think this falls a bit outside my core expertise. I focus mainly on [your specialty], and I think you'd get better results from someone who specializes in [what the project actually needs].
>
If you'd like, I can ask around in my network and see if anyone comes to mind who'd be a strong fit.
>
And if you ever need help with [your specialty] down the road, I'd love to chat.
>
Thanks,
[Your Name]
This is a great relationship-building email. You're being honest about your limits, offering to help them find the right person, and planting a seed for future work in your actual specialty.
Script 5: When You've Started Talking but Realize It's Not Right
This is the awkward one. You've had a call. Maybe exchanged several emails. Perhaps you even talked pricing. But somewhere in the process, you've realized this isn't going to work.
Subject line: Following up on our conversation
Hi [Name],
>
I've been thinking about our conversation regarding [project], and I want to be straightforward with you. After reflecting on the scope and my current commitments, I've realized I wouldn't be able to give this project the level of attention it needs. I'd rather tell you that now than get halfway through and not deliver my best.
>
I really enjoyed our conversation, and I think the project you're building is [genuine compliment]. I just want to make sure you have someone who can be fully dedicated to it.
>
I hope this doesn't cause any inconvenience, and I'm happy to help with the transition to another freelancer if that would be useful.
>
Warm regards,
[Your Name]
The key here is speed. The further along you are in a conversation, the faster you need to pull the plug once you've decided. Waiting makes it worse. Every additional email exchange makes the eventual no feel more like a rejection.
How to Keep Track of Projects You've Declined
Here's something most freelancers don't do but should: keep a simple record of projects you turn down. Just a quick note with the client name, project type, why you said no, and whether you'd be open to working with them in the future.
This is useful for a few reasons. You'll start to notice patterns. Maybe you're turning down a lot of projects in a certain niche, which tells you something about your positioning. Maybe you're saying no to budget issues more than anything, which might mean your marketing is attracting the wrong tier of client.
If you're tracking your email outreach with a tool like Pynglo, you can see whether the clients you declined ever come back and reach out again. Some of my best client relationships started with a no that turned into a yes six months later.
Tips for Declining Without Burning Bridges
Respond quickly. The longer you take to say no, the more inconvenient it is for the client. They need to find someone else, and every day you sit on it is a day they're waiting.
Be warm but direct. Don't bury the no in five paragraphs of hedging. Get to it within the first few sentences.
Never ghost. This is the worst thing you can do. Even a one-line "I'm not able to take this on right now" is infinitely better than disappearing. Ghosting damages your reputation, and freelance communities talk.
Offer alternatives when you can. Recommending another freelancer costs you nothing and helps everyone. The client gets a lead. The other freelancer gets a potential project. And you look generous and well-connected.
Don't over-explain. You don't need to justify your no with a detailed list of reasons. A brief, professional explanation is enough. The more you explain, the more it sounds like you're looking for permission to say no.
The Long Game
Declining well is a skill that pays off over years, not days. The client you turn down politely today might come back with a bigger budget next quarter. They might recommend you to a colleague. They might remember how professional you were and reach out when they have a project that actually fits.
Every no is a chance to leave a good impression. Treat it that way.
Your inbox is your business. Being thoughtful about what you let in, and how you handle what you turn away, is one of the most important skills you can develop as a freelancer.