How to Turn Down Web Design Projects Without Burning Bridges or Losing Money

Not Every Project Is Your Project

A potential client emails you. They love your portfolio, they have budget, and they want to start next week. Then you read the brief: they need a custom WooCommerce store with 500 product variants, a membership portal, and integrations with three different shipping APIs. You build clean marketing sites on Squarespace and Webflow. This is not your project.

Every freelance web designer faces this moment. The money is right there, the client is ready, and saying no feels like throwing revenue away. But taking work outside your specialty is how you end up three months into a project that is over scope, over budget, and destroying your reputation.

I have been freelancing as a web designer for seven years. Roughly a third of the inquiries I get are for work I should not take: wrong platform, wrong scope, wrong complexity level for my skill set. Early on, I said yes to all of them and paid for it with stressful projects, thin margins, and clients who were never fully satisfied.

What changed my business was learning to turn down those projects in a way that kept the client relationship, protected my reputation, and often generated income from the referral itself.

Knowing When to Say No

The hardest part of turning down a project is admitting it is not right for you. Here are the situations where I have learned to say no instead of forcing a yes:

• Wrong platform. A client needs a WordPress site and you work exclusively in Webflow or Squarespace. Or they need a Shopify store and you have never touched Liquid templates. Each platform has its own templating language, plugin ecosystem, and deployment workflow. You cannot learn a new one on a client’s dime without the quality suffering.
• Wrong complexity. The project requires custom development (a booking system, a payment gateway integration, a client portal with role-based access), and your strength is design, layout, and front-end styling. Design and development are different disciplines. Pretending otherwise leads to scope creep and a product that half-works.
• Wrong scope. The client needs a 200-page enterprise site with a CMS, multilingual support, and accessibility compliance. You build 10- to 20-page marketing sites for local businesses. The project management demands alone would overwhelm a solo operation.
• Wrong industry knowledge. The client is in e-commerce, healthcare tech, or another vertical where you have no domain experience. A website for a medical device company has regulatory content requirements you have never navigated. The learning curve will eat your margin and delay delivery.

Saying no in these situations is not turning away revenue. It is protecting the revenue you already earn from your existing reputation.

Building a Network of Specialists You Trust

Turning down a project only works if you have somewhere to send the client. That means building a short list of specialists who handle the work you do not.

I keep a roster of about eight designers and developers, each covering a different gap in my own services. Here is what that list looks like:

WordPress developers

WordPress powers about 40% of the web, and a significant chunk of small business clients will specifically want it. If you do not build in WordPress, you need someone who does: ideally a developer who handles custom themes, plugin configuration, and WooCommerce.

Shopify and e-commerce specialists

E-commerce is its own world. Product catalogs, inventory management, checkout flows, shipping integrations: a Shopify specialist knows the platform’s limitations and best practices in a way that a general web designer never will. I refer all dedicated e-commerce builds to a Shopify developer whose work I have reviewed and whose clients I have spoken with. App developers handle similar tech stack mismatches by keeping a roster of specialists for platforms they do not work in.

Custom developers

When a project goes beyond what any website builder can handle (custom web applications, complex integrations, or database-driven features), it needs a developer, not a designer. I have two custom developers on my list: one who works in React and Node.js, and one who specializes in Python and Django. The distinction matters because the right developer depends on the project’s technical requirements.

Other designers with different specialties

Sometimes the project is a good design project, just not for your specific niche. I primarily design for service businesses: restaurants, professional firms, local shops. When a SaaS startup or a large nonprofit needs a designer, I refer them to peers who specialize in those spaces. Their portfolio speaks to that client in a way mine does not.

How to find these specialists

The best referral partners are people whose work you have actually seen in production. Not portfolio thumbnails, live sites you have clicked through, tested on mobile, and evaluated with a designer’s eye. Here is how I found mine:

• Through shared clients. When a client hires a developer to add custom functionality to a site I designed, I pay attention to that developer’s code quality and communication. If they are good, I add them to my list.
• Through online communities. Slack groups, Discord servers, and forums for web professionals are full of people showcasing their work. I have found three of my eight referral partners through communities where I could see their contributions over months before ever referring a client their way.
• Through reciprocal introductions. Two of my referral partners came from other designers who already had established networks. A Webflow designer I know introduced me to a WordPress developer she trusts, and vice versa.

Setting Up Referral Fee Arrangements

Referring a project does not have to mean giving up income entirely. When you send a qualified client (someone with a defined project, budget, and timeline) to another professional, that introduction has real value. A referral fee acknowledges that value.

How referral fees work in web design

In my experience and from conversations with other freelance designers, referral fee structures typically look like this:

1. Percentage of project value. The receiving designer or developer pays you a percentage of the total project fee, usually between 5% and 15%. On an $8,000 WordPress build you refer out, a 10% fee is $800 for making a phone call and sending an email. This is the most common structure among the designers I work with.
2. Flat referral fee. A fixed dollar amount per referral that converts, regardless of project size. This works well when you refer across a wide range of project sizes and do not want to negotiate a new percentage each time. A $500 flat fee per converted referral is common for mid-range web projects.

When to set up the arrangement

The time to discuss referral fees is before you send the first client, not after. I keep it simple:

“I get WordPress requests about once a month that are not in my wheelhouse. If I send qualified leads your way and they sign, I’d want a 10% referral fee on the project. Does that work?”

That one conversation takes five minutes and sets the terms for every referral going forward. If the other designer or developer says no, that is fine. You can still refer on goodwill alone, and many referral relationships work that way. But having the conversation upfront avoids the awkwardness of bringing up money after you have already sent someone a paying client.

What to agree on

• Fee amount or percentage. Be specific. Ambiguity creates tension.
• When payment happens. Most designers tie the referral fee to the receiving designer’s first payment from the client. That way nobody is paying out of pocket on a project that has not started.
• First project only. The standard arrangement covers only the initial project. If the referred designer builds an ongoing relationship with the client, that is their work paying off: the referral fee covers the introduction, not a perpetual commission.

Communicating the Referral So the Client Feels Taken Care Of

How you handle the transition makes or breaks the client’s experience. If you just say “I cannot do this, here is someone’s email,” the client feels abandoned. If you frame it right, they feel like you are going above and beyond.

Step 1: Be direct about what you do and what you do not do

Do not hedge or apologize. Confidence in your own scope of work builds trust:

“This project is really a custom Shopify build, and my specialty is Webflow marketing sites. I want to make sure you get someone who builds in Shopify every day and knows the platform inside out, because that is what this project needs.”

Notice what is happening here: you are not saying “I cannot do this.” You are saying “your project deserves a specialist.” That reframe makes the client feel like you are protecting the quality of their project, not passing them off.

Step 2: Recommend someone specific and explain why

A vague “you should find a Shopify developer” is not helpful. A specific recommendation shows the client you are solving their problem, not creating a new one:

“I work with a Shopify developer named Marcus who has built stores for about a dozen small product brands. His work is clean, he communicates well, and his clients consistently come back for updates. I think he would be a great fit for your project. Want me to make an introduction?”

Specificity matters. When you can describe the specialist’s relevant experience and vouch for their work quality, the client has a reason to trust your recommendation. For more on how to build these referral partnerships, this post on getting consistent referrals from other professionals covers the relationship-building side.

Step 3: Make a warm introduction, not a cold handoff

Do not just hand the client a name and email address. Set up a three-way introduction that gives both sides context:

“Marcus, meet Sarah. She runs a skincare brand and needs a Shopify store with about 40 products, subscription options, and a loyalty program integration. Sarah, Marcus has built several stores with similar scope and he is great at walking clients through the platform options. I will let you two take it from here, but feel free to loop me in if any questions come up.”

That introduction does four things: it gives the receiving designer enough context to prepare an informed response, it gives the client confidence that you have thought about the match, it signals that you are still available if needed, and it positions you as a connector rather than someone who just said no.

What to say when you do not have a specialist on your list

Occasionally you will get a request for something nobody on your roster handles. In that case, be honest about it:

“I do not have someone in my network for this specific type of project, but let me ask around and get back to you by tomorrow. I do not want to recommend someone I have not vetted.”

That response keeps you in the driver’s seat and gives you time to find the right person. It is also an opportunity to expand your own referral network for future requests.

Following Up After the Referral

Most freelancers make the introduction and then vanish. That is a missed opportunity. Following up after a referral protects your reputation, strengthens both relationships, and often leads to future work.

Check in with the client during the project

About two weeks after making the introduction, send the client a brief message:

“Hey Sarah, just wanted to check in, how are things going with Marcus on the Shopify build? Hope it is going smoothly. Let me know if you need anything on my end.”

This keeps you visible without being intrusive. If the project is going well, you get credit for a good recommendation. If something is off, the client has a safe person to tell, and you can intervene early before it becomes a disaster.

Check in with the receiving designer

Touch base with the person you referred the work to as well. Ask how the project is going, whether the client is a good fit, and whether they have any concerns. This signals that you care about the outcome, not just the referral fee. It also gives you real data about whether this person deserves future referrals.

What to do when the referral goes wrong

It will happen eventually. The designer you referred delivers late, the code is messy, or the client is unhappy with the design direction. How you handle this matters:

• Talk to the receiving designer first. Get their side of the story. Sometimes the client changed scope three times and the delays are not the designer’s fault. Sometimes the designer dropped the ball. Either way, you need the full picture before you respond to the client.
• Offer to help the client. If the project is salvageable and within your capability, offer to step in. If it is not, help them find a replacement. The point is to stay useful to the client, even when the referral did not work out perfectly.
• Update your referral list. One bad outcome does not necessarily mean cutting someone from your roster. But a pattern does. If a designer consistently underdelivers on referred work, stop sending them clients. Your reputation is worth more than any referral fee.

Following up also generates future work

Here is the part that most designers miss: the follow-up after a referral often leads to new work for you. When a client finishes a Shopify build with someone you referred, they might need landing pages, a brand refresh, or ongoing design support that fits squarely in your wheelhouse. You are already the person they trust for design advice. The project you turned down becomes the opening for the next project you take on. UX consultants see the same pattern: clients come back for the next engagement because the designer was honest about the first one.

5 Steps for Turning Down a Project Profitably

Here is the framework I follow every time a project lands in my inbox that is not the right fit. It takes about 30 minutes total and consistently generates goodwill, income, and future opportunities.

1. Evaluate the project honestly. Is this outside your platform expertise, your complexity level, or your niche? If the answer is yes to any of those, do not talk yourself into it.
2. Identify the right specialist from your roster. Match the project’s requirements (platform, scope, industry) to the person on your list who handles that type of work best.
3. Confirm referral terms with the specialist. If you have an existing arrangement, a quick heads-up is enough. If this is a new partner, have the fee conversation before making the introduction.
4. Make the introduction. Be direct with the client about why this person is a better fit, give a warm introduction with project context, and stay available for questions.
5. Follow up with both sides. Check in with the client two weeks after the introduction, and touch base with the specialist as the project progresses. Close the loop.

Common Mistakes When Turning Down Web Design Projects

I have made most of these. Here is what to avoid:

• Ghosting the client. Not responding to an inquiry because it is not your type of project is the worst option. Every unanswered email is a burned bridge. Even a quick response that says you are not the right fit and offers a name keeps the door open.
• Saying yes and figuring it out later. Taking a WordPress project when you have never built one, or accepting a custom development project when your skills stop at page builders, leads to late nights, scope explosions, and a client who tells everyone you were in over your head.
• Referring to someone you have not vetted. If you recommend a designer whose work you have not reviewed, you are gambling with your reputation. A bad referral reflects on you, not just the person who did the work.
• Never following up. Making the introduction and disappearing means you miss the chance to course-correct if something goes wrong, and you miss the chance to pick up future work from the same client.
• Waiting to discuss fees. Bringing up referral compensation after you have already sent someone a paying client is awkward for both sides. Set terms before the first referral, not after.

Getting Started: Your First Steps This Month

If you have been saying yes to everything or just saying no and moving on, here is what I would do in the next 30 days:

• Think about the last three projects you either struggled with or turned down flat. What type of work were they? WordPress, e-commerce, custom development? Those categories tell you exactly which specialists you need on your referral list.
• Find one designer or developer for each gap. Look at live sites they have built. Check their client reviews. Talk to them about their process. You do not need a full roster right away, start with the gap that comes up most often.
• Have the referral fee conversation. Keep it direct: “If I send you a qualified lead and they sign, I’d want a 10% referral fee. Does that work for you?” Most designers and developers will say yes, because a warm referral from a trusted peer is worth far more than 10% of the project.
• The next time a project comes in that is not your fit, refer it. Make the introduction, follow up two weeks later, and track the outcome.

Every project you turn down the right way becomes an investment in your reputation, your network, and your revenue. The freelance web designers who build sustainable businesses are not the ones who say yes to everything. They are the ones who know exactly what they do best and have trusted people to handle the rest.

If you want a structured way to manage referral agreements and track payments with the specialists in your network, take a look at how PureIntro works for tech and digital professionals.

This post reflects one professional’s experience and is for informational purposes only. It is not business, legal, financial, or professional advice. Results described are individual and not guaranteed. Referral fee arrangements may be subject to state and local regulations. Consult a qualified professional for guidance specific to your situation. PureIntro facilitates referral tracking and payment processing but does not guarantee payments between users or any particular business outcome.