The 3-Project Rule: Why I Turn Down Work (And You Should Too)

In logistics, I managed operations that served hundreds of clients simultaneously. Scale was the game. More routes, more vehicles, more shipments, more revenue. The business model rewarded volume.

When I started my creative studio, I applied the same thinking. Book as many projects as possible. Stack the schedule tight. Maximize billable hours. It's what "successful" service businesses do.

For about six months, I ran five to seven projects simultaneously. I was working constantly—early mornings, late nights, weekends. Revenue looked healthy on paper.

Then the cracks appeared.

Client calls started feeling like interruptions rather than collaborations. I'd lose track of where we were in each project's timeline. Details slipped through the cracks—small things at first, then bigger ones. I was delivering work on time, but I wasn't delivering my best work. I knew it. Some clients knew it too.

One day, I sent a client the wrong project files. Not a big mistake, quickly corrected. But it forced me to confront what I already knew: I was spread too thin to be proud of what I was producing.

I finished out those projects, took a breath, and rebuilt with a new constraint: three active projects maximum.

Three isn't a magic number. It emerged from experimentation.

Two projects wasn't enough. There's downtime in every project—waiting for client feedback, rendering overnight, shipping revisions. With only two projects, I'd have idle capacity that felt wasteful.

Four projects was too many. Inevitably, timelines would overlap in uncomfortable ways. I'd have two client calls on the same day with nothing prepared. The mental switching cost was too high.

Three projects is the maximum I can hold in working memory while staying fully present. I can track where each project stands, what's coming next, and what each client needs—without consulting my notes.

Your number might be different. But the principle is the same: identify the maximum you can handle while maintaining quality, then enforce that limit.

The effects of the 3-Project Rule rippled through everything:

• Client experience improved dramatically. I started responding to messages within hours, not days. I could prep properly for every call. I remembered details clients had mentioned weeks ago. They noticed.
• Work quality went up. Instead of racing to "good enough," I had time to push into "this is great." The videos got more thoughtful. The web projects got more refined. I started producing work I wanted to show off.
• My health recovered. I stopped working weekends. I stopped checking email at 11 PM. The constant low-grade anxiety of trying to keep too many plates spinning faded.
• Revenue stayed stable. This surprised me. I expected limiting projects to limit income. What actually happened: I started charging more per project (better work commands better rates), and I stopped giving discounts to fill the schedule (no longer needed).
• Referrals increased. Happy clients refer. Clients who feel like one of many don't. The 3-Project Rule turned every client into a potential advocate.

Having a rule is easy. Following it when a great opportunity appears is hard. Here's how I maintain discipline:

• I track projects visually. A simple board shows my three active slots. When they're full, they're full. The visual reminder prevents me from "just taking one more" when I'm feeling optimistic about my capacity.
• I quote realistic timelines. If a project can't start until next month because my slots are full, I say that upfront. Most clients would rather wait for quality than get squeezed into a rushed timeline.
• I maintain a waitlist. When I turn down work, I offer to add clients to a waitlist. Maybe half of them are still interested when a slot opens. The others weren't the right fit anyway.
• I refer trusted alternatives. When a project isn't right for me—wrong timing, wrong scope, wrong budget—I try to connect them with someone who's a better fit.
• I revisit quarterly. Sometimes market conditions change. Sometimes my capacity changes. Every quarter, I reassess whether three is still the right number. So far, it's held.

The 3-Project Rule is really about something bigger: deciding what kind of business you want to build.

Some businesses are built on volume. They systematize delivery, hire teams, create processes that allow serving many clients simultaneously. That's a valid model. It can be very successful. It requires different skills than doing the work yourself.

Other businesses are built on depth. They limit scope intentionally, invest heavily in each engagement, and compete on quality rather than quantity. This is the boutique model.

Most service providers start as boutiques but don't realize they're trying to operate like volume businesses. They take on too much work, deliver inconsistent quality, and burn out—all while making similar money to what they'd make with fewer, better projects.

The 3-Project Rule forced me to embrace the boutique model consciously. Every decision flows from that: pricing (premium), clients (selective), marketing (relationship-based), delivery (immersive).

In the past year, I've turned down roughly $60,000 in potential revenue by enforcing the 3-Project Rule. That sounds like a significant sacrifice.

But in the same period:

• • My average project value increased by 40%
• • Client satisfaction scores hit all-time highs
• • Referral rate doubled
• • I shipped SharedTask, continued development on MyAmbulex, and maintained creative work—without burning out

The math worked out. More importantly, I'm doing work I'm proud of, with clients I enjoy, at a pace I can sustain.

That's worth more than any amount of additional revenue.