Hourly, Project or Value: Which Pricing Model to Use

For local business websites the answer is fixed-price packages, with value used to set the number rather than to bill against it. Hourly actively works against you at this ticket size, and true value-based pricing needs a measurement you will never get from a bakery.

That is not what the published guidance says, and the reason is that all of it is written for agencies charging $150 an hour on $30,000 projects. The models do not scale down cleanly, and the failure modes are different at the bottom of the market.

The standard objection to hourly is that it penalises efficiency, and that is true. At this ticket size there are two worse problems.

The client can do the arithmetic, and the arithmetic looks bad. Quote ₹1,500 an hour to a shop owner and they will multiply by what they imagine the job takes. They are picturing a few days of typing. You are describing twenty hours of work and they have already decided that ₹30,000 for that is too much — not because the number is wrong, but because they can now see a number they think they can judge.

It caps you at your speed. The whole reason a first website is worth ₹30,000 to a hardware supplier is that it is the first time they are findable, not that it took twenty hours. Bill by the hour and you have priced against your own efficiency in a market where the buyer's value has nothing to do with your effort.

Hourly has exactly one good use here, and it is the hybrid one: a flat fee for the defined build, with anything outside the scope billed hourly at a stated rate. That splits the risk sensibly and gives you something to point at when the requests start.

Value-based pricing means charging against the business impact of the work. The reported income gap is real and large — freelancers pricing this way report roughly $96,000 against $58,000 for hourly billers — and it is genuinely the right model when impact can be measured.

The condition is the problem. Value pricing needs a defined, measurable outcome: a conversion rate, a pipeline number, a revenue line the work moves. A bakery cannot tell you how many cake orders it lost last year, because the entire point is that those enquiries never arrived. Nobody is going to attribute anything to you afterwards either.

So pure value pricing is unavailable. What you can take from it is the input rather than the mechanism: ask what one customer is worth to them over a year, and use that to choose your number. That is value-informed pricing, and it is the single most useful habit in this business — it is just not a billing model.

Fixed price moves the risk onto you, and that risk is entirely about scope. It is manageable with three things, none of which are complicated.

Write down what is included as a count. Number of pages, number of photo rounds, number of revision rounds. Not "a professional website" — five pages, two revision rounds, photos supplied by you.

Name what happens outside it, in advance. "Anything beyond that is quoted separately" is enough. The word "separately" said before the project starts is worth more than any argument after it.

Put the content deadline in writing. The overwhelming reason these projects run long is that the business has not sent its photos and text. That is not your delay, and it needs to be on paper before it happens, or the project stays open for four months and your fixed price becomes an hourly rate you would never have accepted.

Once the model is fixed price, the remaining decision is how many prices to present, and the answer is three rather than one.

A single quote is a yes-or-no question, and the easiest answer to a yes-or-no question is no. Three options change what is being decided — the prospect moves from whether to buy to which one to buy, and most of them land in the middle, which is where you wanted them.

The options have to be genuinely different deliverables rather than the same site with features withheld. A one-page presence, a standard five-to-eight page site, and a full build with a catalogue or registration are three real answers to three different situations. Padding a middle tier to make the top one look reasonable is obvious to buyers and it costs you the trust the mockup and the walk-in earned.

Name them for what they do, not Silver and Gold. "Presence", "Standard" and "Catalogue" tell a hardware supplier which one is theirs without you explaining anything.

None of the three is the important decision. The important one is whether there is a monthly attached to the build at all.

Twenty fixed-price builds a year is a business that resets to zero every January and depends on you finding twenty more strangers. Twenty care plans at ₹2,000 a month is ₹4.8 lakh of revenue that arrives whether or not you sold anything in a given week, from clients who already trust you.

So the pricing model question is mostly settled — fixed price, value-informed, scope written down — and the energy is better spent on making sure every fixed-price build has a monthly next to it from the first conversation.