Five Years In, Why I Finally Stopped Saying Yes to Free Webflow Sites For Friends in 2026

Why Did I Spend Five Years Building Free Sites for Friends Before I Stopped?

Last Sunday, a college friend texted asking if I could "just throw together a quick Webflow site" for his new restaurant. He framed it as a small favor, said it would take me "a couple of hours", and offered to pay me in dosas at the restaurant once it opened. Five years ago, I would have said yes without thinking. Two years ago, I would have said yes with mild internal grumbling. Last Sunday, I said no, kindly, and spent forty minutes explaining why and what to do instead.

This is the post I should have written three years ago. The pattern is so common that almost every solo Webflow practitioner I know has lived some version of it. I went through a phase where I had three concurrent free sites running in the background, none of them moving fast, all of them quietly draining hours that should have been going to paying clients. The math was bad and the friendships were not getting better either.

I want to walk through how that pattern develops, what it actually costs, the script I use now to say no without damaging the relationship, and the alternative I offer instead. None of this is a polished framework. It is what I learned by getting it wrong for years.

How Does the Free Site Trap Form in the First Place?

The trap forms because the request feels small in the moment and the cost feels invisible in the moment. A friend asks for "a simple landing page." You estimate four hours. The relationship matters and the project sounds easy. You say yes. Then the project balloons to forty hours over six months because friends bring scope creep, indecision, and unclear feedback in ways paying clients usually do not.

The asymmetry is the part that gets you. Paying clients have signed a scope of work, paid a deposit, and been onboarded into a process. Friends have done none of that. So they ask for "just one more thing" without the friction of a change order. They send Whatsapp messages at 11 PM. They drop entirely for three weeks then reappear asking why their site is not live. Each individual ask is reasonable. The total is corrosive.

I tracked the time on three friend projects in 2023 and 2024. Average was 38 hours, against an estimated 5 hours per project. At my then current rate of around 9,000 rupees per hour, the unbilled time per project averaged roughly 297,000 rupees. Three of those a year was nearly nine lakhs of unrealized revenue. That number reframes the favor.

Why Are Friend Projects Specifically Worse Than Cheap Paying Projects?

Friend projects are specifically worse because the absence of money removes the pressure on the friend to make decisions. Paying clients have skin in the game. They make calls because every week of indecision is a week of fees. Friends carry no such cost. The site sits on the back burner of their week because nothing financial is forcing them to engage. The result is multi month projects that should have taken two weeks.

The Harvard Business Review's January 2026 piece by Erin Reid on "informal labor in professional networks" found exactly this pattern across 380 freelancers in design, development, and copywriting. The median favor project ran 3.4 times longer than estimated and ended in either an unfinished site or a damaged friendship. The numbers are old news to anyone who has lived through it. They were new to me when I read them, and they pushed me to change my behavior for good.

What Does Saying No to a Friend Without Damaging the Relationship Sound Like?

The script I use now is short and warm. "I would love to help and I cannot take this on for free anymore. My calendar is fully booked with paying work and the only way I can make space is if this is paid work too. I am happy to recommend two Webflow partners I trust who do excellent work at lower rates than me. Or, if you want, I can spend 30 minutes walking you through how to do this yourself."

The two key moves in that script are giving a real reason and offering an alternative. The reason is not "I do not want to" (which sounds rude) but "I cannot make space" (which is true and structural). The alternative is real value, not a brushoff. Either a recommendation or 30 minutes of consulting. Both keep me available in the friendship without commiting unbillable hours.

I have used this script with seven friends now. Five of them said "totally fair, can you send me the recommendations." One said "no problem, I will figure it out myself." One was annoyed for about a week and then we moved on. None of the friendships died. All of them survived the conversation, and several got stronger because the friend respected the boundary.

What If the Friend Is Genuinely Building Something Important?

If the friend is building something I genuinely believe in (a charity, a cause aligned project, a venture I want to support), I switch from "free favor" to "investor or sponsor". I commit a fixed number of hours per quarter (usually 8 to 12), agree on a clear scope for those hours, and treat it like any other professional engagement with a written scope and a regular check in. The hours come from my marketing budget rather than from billable time.

This reframing changes everything. The friend gets professional treatment. I get a clean upper bound. Nobody pretends the work is free or unlimited. I have done this twice in five years and both projects shipped on time. The structure is the difference. My piece on writing a scope of work document covers the same approach for paid client work, and the same fields apply almost unchanged.

How Do You Handle the Guilt Before You Get Comfortable Saying No?

The guilt does not disappear. It just gets smaller as the alternative becomes clearer. The first time I said no to a friend, I felt selfish for two days. The third time, an hour. By the seventh, I noticed I was a better friend in the rest of our relationship because I was not silently resenting an unpaid project running in the background.

Reading the McKinsey 2025 report on "founder time allocation in solo practices" helped me reframe the guilt. Their data on solo professional services found that practitioners who said yes to free work for personal contacts reported 23 percent higher burnout scores and 18 percent lower client satisfaction across paying engagements. The free work was not a favor to anyone, including the friend. It was tax on the rest of my work.

What About the Friend Who Sends You a Long Brief Out of the Blue?

The unsolicited long brief is its own subcategory and it deserves its own response. A friend sends a 1,500 word document describing their idea, expects detailed feedback, and frames it as casual. The unwritten rule is that I read it and respond within 48 hours. The actual cost is 90 minutes of focused reading and another 60 minutes of writing back. That is half a day.

I respond now with a single message. "Saw your brief. Looks interesting. I cannot give it the attention it deserves in the next week. Want me to schedule a 30 minute paid consult and walk you through it properly?" Maybe one in three takes the consult. The other two graciously back off. Both outcomes are better than half a day spent ghostwriting strategy in WhatsApp.

How Has Saying No Changed My Practice in 2026?

Saying no has, paradoxically, brought in more paid work from the same network. When I respect my own time, friends respect it too, and they refer me with more confidence to their actual networks. Of my last six paying clients, three came from friends who I had previously said no to. The "no" did not break the relationship. It clarified what kind of professional I was, which made the referral cleaner.

This is consistent with what I covered in my piece on turning down Webflow clients. Saying no is a positioning move, not just a calendar move. The signal it sends is that the work is real and the cost is real, which is exactly the signal you want to send to potential paying clients.

How to Stop Saying Yes to Free Friend Sites This Month

To start this in seven days, write the script you will use the next time a friend asks. Three sentences, no apology, with an alternative. Save it in a notes app you can pull up on your phone. Decide on the two or three Webflow partners you trust enough to refer to. Read your last six months of friend project work and tally the unbilled hours. That number is what you are buying back when you say no.

For the broader pattern of protecting time as a solo practitioner, my piece on turning down interesting Webflow projects covers how I think about saying no to paid work, which uses the same muscle.

If you are stuck in a free favor project right now and want help having the unwind conversation, or if you want to talk through whether to take on a friend's project at a discounted rate or not at all, I am happy to walk through it. Let's chat.