Why I Started Saying No to Webflow Projects With More Than Three Decision-Makers in June 2026

Why Did I Start Turning Down Webflow Projects With Too Many Decision-Makers in June 2026?

In the last week of May 2026, I sent a polite no to a Webflow project that would have been the largest deal of my year. A B2B fintech company in Bengaluru wanted a homepage rebuild with seven internal stakeholders signing off on the design. The brief was clean. The budget was generous. The timeline was reasonable. I still said no, because past projects with that many cooks have taught me what the next four months would look like.

Three rounds of revisions per page. Two stakeholders who never join the calls and then send opinions in email after the fact. A pricing page that gets rewritten four times because Sales and Product disagree on the positioning. A homepage hero that stays in limbo for six weeks because the CEO wants something the CMO does not. The economics break before the project ships. According to the Harvard Business Review's 2025 study on B2B decision-making, projects with more than five stakeholders take 79 percent longer to complete and cost 41 percent more than equivalent projects with fewer stakeholders.

I started saying no to those projects in June 2026 because the math finally caught up with my emotional energy. This is a piece about why three is my limit, how I screen for it on the discovery call, and what I do when a referral I want to take on turns out to have too many people in the room.

What Is the Three Decision-Maker Rule and Why Did I Set It at Three?

The rule is simple. If more than three people at the client company need to sign off on creative direction, I do not take the project. Not for any price. The number is three because past projects taught me that two-person sign-off is fluid, three-person sign-off is doable, and four-person sign-off begins to compound badly. The compounding is what kills you.

According to the CEB Marketing Leadership Council research that Gartner now publishes annually, the average B2B buying decision involves 7.4 stakeholders. That is the buying side. The internal sign-off side, the people who must approve a creative deliverable, is usually smaller but follows similar dynamics. When that number is three or fewer, the project moves. When it is four or more, every creative decision becomes a committee vote.

Three is also a number I can hold in my head. I can know what each of three people cares about. I can write three discovery prompts. I can review feedback from three people in one sitting. Four breaks that. Four becomes a meeting with notes I have to keep refreshing because I cannot remember everyone's preferences.

How Do I Screen for This on the Discovery Call?

I ask one direct question on every discovery call. Who needs to approve the design before it ships? Not who is in the room today. Not who is the project lead. Who has the power to push back on a creative direction and require a revision? The answer to that question, in my experience, is almost always more than the founder expected before they thought about it.

The answers cluster into three patterns. Pattern one, the founder says one or two people, and that turns out to be accurate. Pattern two, the founder says three people, and that turns out to mean five in practice because two more get added during the project. Pattern three, the founder says five or more upfront, and I know the project will be miserable from day one. I take pattern one projects. I am cautious about pattern two. I decline pattern three.

For background on how the discovery call shapes the rest of the engagement, my earlier piece on why I limit every Webflow discovery call to 25 minutes covers the broader call structure. The decision-maker question is the single most important question I ask, and it has to come up early.

But What About Big Projects With Big Budgets That Need More People?

This is the fair objection. Some projects are genuinely large enough to need more stakeholders. A multi-page enterprise SaaS marketing site for a Fortune 500 company is not going to have one decision-maker. My answer is that I am not the right studio for those projects. I am a four-person studio in Bengaluru. The right shop for a 50-stakeholder enterprise build is a 30-person agency that knows how to staff that kind of structure.

The pricing also reflects this. A four-stakeholder project does not just cost more because there is more design work. It costs more because you have to staff a project manager whose entire job is to keep the stakeholders aligned. I do not have that role on my team. According to a Smart Insights agency staffing study from March 2026, agencies that successfully run multi-stakeholder projects allocate 18 to 22 percent of project hours to coordination overhead. I would rather give up the revenue than build that overhead into my studio.

For studios bigger than mine, the calculation is different. For a freelance Webflow practice, three is a reasonable ceiling.

How Do I Say No Without Burning the Referral Relationship?

The no is structured and short. I thank them for the referral. I lay out what I see in the project that does not match my studio's shape. I name the decision-maker count specifically, not as a personal preference but as a project risk for them as much as for me. I refer them to two other Webflow studios that handle larger stakeholder counts well. Then I close the door cleanly without leaving it ajar.

The referral move is the part that protects the relationship. If I leave a founder without a path forward, they remember the no. If I introduce them to a studio that can actually serve them, they remember the help. According to a Bain Customer Loyalty study from January 2026, B2B service providers who refer ill-fit work to better-fit providers see 31 percent higher referral rates from the same source over the following twelve months.

For studios that need a script for the no, the template I use is three sentences. Your project sounds important. The decision-maker structure you described would not be a fit for how my studio runs creative work. I would recommend you talk to studio X or studio Y, who handle this shape well.

How Do I Handle Projects That Sneak Past Three During the Engagement?

This is the more common situation. A project starts with two decision-makers, then expands to four three weeks in because the founder loops in the new VP of marketing. The right response is to name what just happened, not to pretend it did not. I send a single note to the client saying I have noticed the sign-off circle has grown, and here is what that means for timeline and budget.

The note has three options. One, we keep the original scope but extend the timeline by four to six weeks to accommodate the new feedback layer. Two, we narrow the scope so the new stakeholders weigh in on fewer creative deliverables. Three, we pause the project for two weeks to rebaseline the sign-off circle and confirm who is in and who is out.

Most clients pick option two. The narrowing forces the founder to have a conversation internally about who really needs to approve what. According to my own retainer notes across nine projects since 2024, this conversation reduced the working sign-off circle from five-plus back down to three in seven of nine cases.

How Do I Build the Three-Person Limit Into My Statement of Work?

Starting in June 2026, every Webflow SOW I send includes a stakeholder clause. The clause names the three people who will sign off on creative direction. Any addition to that list triggers either a timeline extension or a scope narrowing, mutually agreed in writing. The clause is in plain language, not in legalese, because the goal is alignment not enforcement.

The SOW also names a primary point of contact, who is the one person responsible for gathering feedback from the other two sign-off voices and consolidating it into a single response. I do not accept feedback from three voices independently. I accept consolidated feedback from one voice. This is the discipline that keeps the three-person rule from collapsing into nine voices in practice.

For background on how this fits into my broader retainer pricing, my notes on charging a discovery pack fee before quoting Webflow projects cover the upfront pricing motion that pairs with this clause.

What Has Happened to My Revenue Since I Started Saying No?

The honest answer is that revenue per project went up and total revenue stayed flat. I took three fewer projects in the past four months than I would have under the old approach. Each of the projects I did take paid 40 to 60 percent more than my old average. The reason is selection. The projects I now take are cleaner, ship faster, and deliver better outcomes, which lets me charge for the result rather than the hours.

I also have more energy at the end of each week. That is harder to measure than revenue, but it shows up in how creative my work is on the next project. According to a McKinsey Q1 2026 wellness report, knowledge workers who reported feeling drained at week end were 47 percent less likely to produce work they were proud of. I am not running a study on myself, but the pattern matches.

For background on how the financial side of the studio has evolved, my piece on raising my Webflow retainer floor to 50,000 rupees in June 2026 covers the floor-pricing decision that the three-person rule made possible.

How Should You Decide Whether to Set a Decision-Maker Limit This Week?

The exercise takes a single afternoon. Open the list of every project you completed in the past twelve months. For each project, write down two numbers. The number of stakeholders who actually approved creative work. The total billable hours the project took. Calculate the ratio. Then sort the list by ratio. The pattern will be obvious. The projects with more decision-makers consumed more hours per dollar of revenue.

Pick the smallest number of decision-makers that still includes at least 70 percent of your most enjoyable past projects. That is your limit. For me it was three. For another studio it might be two or four. The point is that the number is not abstract. It is empirical, based on what your past work has taught you. Then bake the limit into your discovery calls and your SOWs going forward. For broader background on how I run a sustainable freelance Webflow practice, my notes on why my Bengaluru studio bills in dollars now cover the adjacent pricing decision.

If you want help thinking through your own studio's decision-maker limit and how to enforce it without burning client relationships, I am happy to walk through it. Let's chat.