Should You Turn Down a Website Project When You’re Already Booked Out?

You’ve spent months trying to get enough work. Now you’ve got three websites underway, revisions waiting, emails to answer and a client who suddenly needs something fixed before Friday. Then another enquiry arrives. It’s a good business, the project suits you, the budget looks reasonable — and your first thought is: “There is absolutely no way I can fit this in.” Saying no might well be the right call. It just shouldn’t be the automatic one.

Before you decline a good project, it’s worth understanding exactly why you can’t take it — and what alternatives actually exist. Sometimes the answer is still no. Sometimes the honest answer is “not this month”, or “not at this price”, or “not the whole thing”. Those are very different conversations, and they lead to very different outcomes for your business.

This article walks through six options, a simple way to decide between them, and the numbers you need to check before you say yes to anything.

Being Booked Out Isn’t Always the Same as Being at Capacity

There’s a real difference between a studio operating at maximum sustainable capacity and a studio with a clogged calendar. Both feel identical from the inside. They need completely different solutions.

Have an honest look at where the week actually goes. A lot of designers discover their diary is full of:

• Small fixes squeezed in between real work
• Unstructured revision rounds that never formally end
• Chasing content, logos and login details
• Administration, quoting and invoicing
• Maintenance jobs that were never properly priced
• Client meetings that could have been an email
• Work outside your strongest skills, taking twice as long as it should
• Projects that were scoped loosely and have quietly expanded

Understanding the bottleneck changes the solution. If the problem is production hours, extra production help is the fix. If the problem is scope creep and admin, hiring or outsourcing will simply give you a more expensive version of the same mess.

If this pattern feels familiar, our companion article on handling overflow without hiring looks at the capacity question in more detail.

First Question: Is This Actually a Project You Want?

Being busy has one genuine advantage — it gives you permission to be selective. Use it before you start rearranging your calendar.

Ask yourself:

• Is the project profitable enough to justify the disruption?
• Is it the kind of work you want more of?
• Does the client seem organised and realistic?
• Is the timeframe they’re asking for sensible?
• Does it sit comfortably inside your skills?
• Could it lead to useful ongoing work?
• Is it strategically valuable — a sector, a portfolio piece, a referral source?
• Are there warning signs already showing up in the first few emails?

If the job is poorly priced, badly defined, outside your expertise or already showing red flags, no amount of clever workload management will rescue it. Saying no may be the most profitable and professional decision you make that month.

Option 1: Turn It Down

Declining is a legitimate business decision, not a failure. It’s usually the right one when:

• The budget is unrealistic for what’s being asked
• The deadline can’t be met without damaging other work
• The project is a poor fit for how you work
• The scope includes things you can’t confidently deliver
• The client is already difficult and the project hasn’t even started
• Taking it would compromise the clients you already have

How you decline matters more than the decision itself. Be prompt, be clear, and be kind about it. A quick, respectful no is far better for your reputation than a slow maybe followed by silence.

Where it feels appropriate, point them somewhere useful rather than leaving them stuck. “I’m not the right fit for this one, but here’s someone I’d trust with it” is a much stronger ending than “sorry, I’m too busy” — and people remember it.

Option 2: Offer a Later Start Date

Not every client needs their website immediately. Plenty of enquiries arrive with a vague timeframe attached simply because nobody asked.

So instead of “I can’t do it”, the conversation can be: “My next production opening is in four weeks. If that works for you, I’d be happy to discuss the project.”

That single sentence does a few useful things:

• Protects the work you’ve already committed to
• Keeps a project you actually want
• Sets realistic expectations from the very first conversation
• Signals that your time is planned rather than improvised

One caution: a permanently growing waiting list isn’t a growth strategy. It looks like success and often functions as a slow leak — clients drift off, momentum is lost, and you spend energy managing a queue instead of delivering work. A short, honest lead time is healthy. A four-month backlog usually means something else needs adjusting.

Option 3: Review the Price Before You Review the Calendar

If you are constantly booked out, pricing deserves a look. Not for this one client — for your general offer.

To be clear: this isn’t about inflating a quote because a particular customer seems well-funded or in a hurry. That’s opportunistic and it damages trust. It’s about noticing a pattern. If demand consistently outstrips the hours you have, your standard pricing may no longer reflect the workload, the responsibility or the value of the finished work.

Pricing your general offer more accurately can:

• Improve revenue per project instead of per hour worked
• Make room for better-fit work by naturally filtering the rest
• Fund outside production help when you need it
• Create breathing space to give existing clients better service

Option 4: Refer the Project

If the job is decent but you genuinely don’t want it — or can’t fit it — referring the client to a provider you trust is often the best outcome for everyone.

A good referral:

• Helps the client get their website sorted
• Protects goodwill you’ve already built
• Strengthens your professional relationships
• Can create opportunities for reciprocal referrals

Some referral arrangements include an agreed reward or commission. Plenty of others simply run on reciprocal goodwill between people who respect each other’s work. Neither is more correct — just be clear about which one you’re in before you send the introduction.

Referral suits you best when you don’t want to manage the website project at all. You hand it over, you stay out of the delivery, and you’re not carrying any responsibility for the outcome.

Option 5: Collaborate

You don’t have to deliver every part of a project to be part of it. Splitting the work by strength is often the most enjoyable option, and clients rarely mind — they care about the result.

A common split looks like this. You handle:

• Creative direction
• Branding and visual identity
• Page concepts and layout thinking
• The client relationship and approvals

And another specialist handles:

• WordPress or Wix production
• Responsive implementation across devices
• Forms, integrations and email notifications
• Technical setup, hosting and domains
• Testing and launch

Both professionals stay visible, both work in their strongest area, and the project moves considerably faster than it would if either of you tried to do all of it.

Our article on white-label web design covers how these working relationships are usually structured, including where collaboration differs from staying entirely behind the scenes.

Option 6: Keep the Client and Use an Overflow or White-Label Partner

If you want to keep the project and the client relationship but simply don’t have production capacity, another website studio can do agreed work behind you.

Arrangements vary, and it’s worth choosing deliberately:

• The partner communicates only with you, never the client
• The partner works completely behind your brand
• The partner joins meetings as part of your extended team
• You supply finished design and content, and the partner builds it
• The partner handles one troublesome technical component rather than the whole project

This only works with trust and structure. Agree the scope in writing, agree who speaks to the client, agree what happens when revisions go beyond the original brief, and agree the commercial terms before anyone opens a code editor. Vague arrangements are where these partnerships come unstuck — not lack of skill.

The Numbers Still Have to Work

Outsourcing a project purely to keep revenue on the books makes no sense if there’s no worthwhile margin left at the end of it. Before you accept, work through the actual figures.

• What the client will pay
• What the production partner will charge
• Your own project-management and communication time
• Revision risk, and who absorbs it
• Content work — writing, editing, image preparation
• Software, licensing or plugin costs where relevant
• Payment processing and other direct project costs
• The longer-term value of the client relationship and any ongoing work

The question then becomes simple: does that remaining amount fairly compensate you for winning the work, managing the client, providing creative direction, handling revisions, carrying the risk and standing behind the finished website? Sometimes yes, comfortably. Sometimes it’s obviously not worth it, and that’s a useful thing to discover before you commit.

Revenue is not profit. A busy year with thin margins is exhausting and fragile.

Beware of Saying Yes and Then Doing Everything Yourself Anyway

This is the most common way overflow arrangements fail, and it has nothing to do with the partner.

A designer accepts the project on the basis that the build will be outsourced. Then, quietly, they:

• Rewrite all the copy because it wasn’t quite right
• Resize and re-export every image themselves
• Fix small details rather than raising them
• Rebuild parts they had already delegated
• Attend every conversation, just in case
• Make endless “quick” changes at 9pm

Four weeks later the project is delivered, the invoice from the partner arrives, and no capacity was created at all.

Decide deliberately what stays on your desk and what genuinely leaves it. Write it down if you have to. The discipline is the whole point — otherwise you’ve added a cost without removing any work.

A Simple Decision Test

When the next enquiry lands and your diary is already full, run it through this:

Turn it down

If the project is a poor fit, badly priced, unrealistic or risky.

Delay it

If it’s a good project and the client is genuinely happy to wait.

Reprice your general offer

If excessive demand is a consistent pattern rather than a one-off busy week.

Refer it

If you want the client looked after but don’t want to manage the website work.

Collaborate

If you want to contribute your specialist skills but not deliver the whole project.

White-label or overflow it

If you want to retain the client and the project while moving agreed production work off your desk.

What Happens When This Becomes a Regular Problem?

One busy month isn’t a business model issue. It’s just a busy month, and every studio has them.

But if good projects are regularly being declined because one person can’t physically deliver them, the business has reached a decision point. Continuing exactly as you are means capping your income at the number of hours you can personally work — and quietly handing good clients to competitors.

Some practical next steps might include:

• Higher, more accurate pricing
• Better systems and templates so each project takes less effort
• Tighter project scopes with clear revision limits
• Improved content collection so projects stop stalling
• Regular freelancers for specific tasks
• A trusted overflow or white-label partner for production
• Eventually, hiring

These aren’t mutually exclusive, and the right combination can change as a studio grows. Some designers may eventually employ staff, while others deliberately remain small and use freelancers or trusted partners to add capacity when they need it.

Frequently Asked Questions