Personal

Why I Stopped Offering Free Discovery Calls for Small Webflow Projects in 2026

Written by
Pravin Kumar
Published on
Jun 13, 2026

Why Did I Even Offer Free Discovery Calls in the First Place?

For four years, I treated free discovery calls as the default first step with every Webflow prospect. The reasoning was familiar. Lower the friction. Show value upfront. Build trust before asking for money. Every agency growth book I read between 2020 and 2024 said the same thing. So when a founder pinged me through my contact form, I offered a free 30-minute call within the week. The call would often turn into 45 minutes. Sometimes 60. Then I would write a proposal. Half the time the lead would go cold.

Last quarter I tracked the hours. Across nineteen free discovery calls, I spent 14 hours on calls plus another 11 hours on follow-up proposals. Six of those nineteen converted to paid projects. That is a 31 percent conversion rate, which sounds reasonable, until you add up the total time spent on the thirteen that did not convert. That is unbillable time. This post walks through why I stopped, what I do instead, and what changed in my business.

What Was Actually Going Wrong With the Free Discovery Model?

Three things. The first was self-selection. Free attracts people who are not ready to spend. I would get on calls with founders who had not yet decided to build a website, were comparing me against four other freelancers, or wanted free strategic advice they had no intention of paying for. The free call was filtering wrong.

The second was preparation. Because the call was free, I treated it as low-stakes and showed up under-prepared. The founder also showed up under-prepared because they had nothing at risk. The result was a half-useful conversation that left both of us slightly disappointed. According to HubSpot's 2025 sales benchmark report, free consultations convert at less than half the rate of paid ones in services businesses, partly because of this preparation gap.

The third was the proposal cycle. After a free call, the prospect would ask for a written proposal. Writing a Webflow project proposal takes me about ninety minutes if I do it carefully. Doing that on thirteen losing leads cost me roughly twenty hours a quarter. That is two full days I was not getting paid for.

What Did I Replace Free Discovery With in Early 2026?

I shifted to a paid 25-minute Discovery Sprint costing 7,500 rupees, or about 90 dollars. The Discovery Sprint includes a 25-minute focused call with me, plus a one-page summary email afterward with my preliminary recommendation. The fee is refundable against any project we book together within thirty days, so for serious buyers it costs nothing.

The pivot was uncomfortable at first. I worried I would lose leads. The opposite happened. Total inbound volume dropped about thirty percent, but the conversion rate from inquiry to paid project climbed from 31 percent to 58 percent. Better still, every Discovery Sprint converted into either a project or a clean "not a fit" within a week. No more proposal black holes.

What About the Lost Leads Who Refused to Pay for Discovery?

About thirty percent of inquiries went cold the moment I mentioned the fee. That was the design. Those were exactly the leads I did not want. According to Blair Enns of Win Without Pitching, the willingness to pay for discovery is the single strongest predictor of project quality. My lived experience matches his thesis. The leads who agreed to pay turned into better clients.

The other useful effect: paid discovery filtered out price shoppers. A founder comparing five freelancers and looking for the cheapest will not pay for discovery with five of them. They pick one or two who feel most aligned. By charging, I made that selection happen earlier in the funnel, which saved me from being one of five quotes in a spreadsheet.

What Does the Money Math Actually Look Like After Six Months?

From January to June 2026, I ran 23 Discovery Sprints. Twenty-one of them converted to paid projects, two of which had their fees refunded as part of the project payment. So the direct revenue from Discovery Sprints was small, about 1.5 lakh rupees over six months. The real benefit was elsewhere.

The 21 projects that came out of those 23 sprints averaged 2.8 lakh rupees per project. That is 58.8 lakh rupees in project revenue from 23 paid discovery calls. Compare that to the previous year when I ran roughly twice as many free discovery calls and booked similar project count. The hours spent on discovery dropped from about fifty per quarter to under fifteen. According to my own time tracking in Toggl, the net hourly value of my time on inbound rose roughly three times.

How Do You Actually Sell a Paid Discovery Call to Prospects?

The first move is to position it as valuable, not as a barrier. My contact page now lists the Discovery Sprint as a productized offer with a clear scope: 25 minutes, one preliminary recommendation, one summary email, fee refundable against any project. The page does not apologize for the fee. It explains what they get for it.

The second move is to make booking frictionless. The fee is collected through Razorpay at checkout, and the Calendly slot opens immediately after payment. Friction on payment kills conversion. Friction on booking kills momentum. According to Calendly's own 2025 customer benchmark, integrating payment into the booking flow doubles completion rate compared to a two-step setup.

How Do You Handle the Awkwardness of Mentioning a Fee?

I do not mention it on the contact form itself, only on the discovery page they get directed to. The contact form is a low-friction first touch. The discovery page is where the qualification happens. By the time the prospect sees the fee, they have already self-selected as someone who wants to talk to me specifically.

I also wrote a short FAQ on the discovery page covering the obvious questions: why pay for discovery, what if the project does not happen, can I have a free initial chat first. The honest answers in plain language remove most of the awkwardness. About a quarter of prospects email me with one of those questions before booking, which is fine. It is a sign they are taking it seriously.

What Did I Change About My Own Behavior on Paid Calls?

Everything got tighter. I read the prospect's website before the call, took notes on what I would change, came with three specific questions, and arrived three minutes early. The call has a fixed agenda. The first five minutes are their context, the next ten are my questions, the next ten are my preliminary recommendation. We end at 25 minutes. Always.

The discipline I bring to a paid call is different from what I brought to free calls. The prospect senses it. They show up prepared too. The whole conversation moves at a higher altitude. Conversion follows from that.

How Do You Decide If This Model Is Right for Your Webflow Practice?

Run the numbers on your last twenty inquiries. Count the hours spent on calls and follow-up. Calculate your effective hourly rate on inbound time. If it is below 5,000 rupees an hour for an experienced Webflow freelancer, free discovery is hurting your business. The fix is not to work harder on calls. It is to charge for them.

For the specific format of my 25-minute paid call and what I cover in it, my piece on the 25-minute Webflow discovery call walks through the agenda. For the Bengaluru-specific pricing context and how I priced the sprint at 7,500 rupees, my breakdown of paid Webflow discovery calls in Bengaluru covers the regional pricing logic. For the variant where I require a refundable deposit instead of a fixed fee, my guide on the refundable discovery deposit model covers when each makes sense.

If you want to talk through whether this model fits your Webflow practice, reach out. I am happy to walk through it. Let's chat.

Get your website crafted professionally

Let's create a stunning website that drive great results for your business

Contact

Get in Touch

This form help clarify important questions in advance.
Please be as precise as possible as it will save our time.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.