Client feedback delays and how they should affect pricing

Nineteen days of "I'll look at it this weekend"

I delivered staging for a small business site on a Thursday afternoon. The owner replied within the hour: "Looks great, I'll go through it properly this weekend." I had blocked the following Monday and Tuesday for revisions, because that was the plan we had agreed, and I turned down a two-day fix job that a past client had sent my way, because I did not want to juggle it alongside the revision round.

The weekend passed. Monday passed. I sent a friendly nudge on Wednesday and got a thumbs-up emoji back. The next real message arrived nineteen days after staging went up. It had forty-odd comments from three different people, two of whom I had never heard of, and a line at the bottom saying they had promised a supplier the site would be live by the end of the following week.

I did it. I pushed another client's work into three evenings, rebuilt two sections the owner's business partner disliked, and launched on the date. The project was fixed price, so the invoice did not change. On paper it went fine. In practice I had turned away paid work so a slot could sit empty, and then paid for the client's delay with my evenings.

They are a cost.

That was the project where I stopped treating feedback delays as weather. They are a cost. Like any cost, they either go into the price and the paperwork, or they come out of your pocket quietly.

Photograph

Hourly billing does not make waiting free

The usual advice is "bill hourly and the problem goes away". It goes away less than people think. Hourly billing stops the meter while you wait, which sounds fair, but the days you were holding cannot be sold to someone else at short notice. Nobody books a freelancer for "maybe Monday, maybe in three weeks".

Then there is the restart. When feedback finally lands after a long gap, you have to reload the project: reread your own notes, check that staging still builds, work out which of three people's comments actually wins. On hourly work that time is billable if you are disciplined about logging it. Most people are not. "Remembering what I did" rarely makes it onto an invoice.

Fixed price is worse. With no pause terms, every week the client spends deciding is a week you are financing. Fixed price versus hourly covers which model suits which kind of project. The point here is narrower: whichever model you pick, the cost of waiting has to be written down somewhere before kickoff, or you will end up arguing about it from memory when everyone is already tense.

What that ghost month actually cost

I went back and put rough numbers on it afterwards. These are my planning numbers, not industry averages. My internal day rate is €560, which is eight hours at the €70 an hour I get from my freelance hourly rate math. The fixed fee for the whole site was €4,000.

• Two reserved revision days sat empty: 2 × €560 = €1,120. The referral job I turned down would have filled exactly those days.
• One day of restart once feedback arrived (rereading, re-testing, merging conflicting comments): 1 × €560 = €560.
• Three evenings of about three hours each to protect the other client's deadline: 9 × €70 = €630.

That is €2,310 of cost on a €4,000 project, more than half the fee, and none of it was visible on any invoice. The client did not know. They were not being malicious. Their week got busy, then a business partner got involved, and nobody had told them that silence had a price.

What would have helped was not a stern email. It was three sentences in the estimate. A pause clause would have moved the delivery date one-for-one with their delay. A rush clause at twenty-five percent of remaining fees, with €1,600 still to invoice, would have made compressing the schedule cost them €400. Faced with that choice, I suspect they would have moved the date by a week, which is all I needed.

Wording I now put in every estimate

Adjust the numbers to your own work. The exact day counts matter less than the fact that they exist in writing before anyone is annoyed. This is planning wording for an estimate, not legal advice about contracts.

Feedback window: "Assumes consolidated feedback within three business days per milestone. Later feedback moves the delivery date by the same number of days."

Pause: "If the project waits more than five business days for client input, the project clock pauses and restarts when feedback arrives."

Holding the slot: "After ten business days of waiting, reserved time is billed at fifty percent of the day rate, unless we agree in writing to release the slot and rebook."

Revision rounds: "Two consolidated revision rounds per milestone are included. Further rounds are billed at the hourly rate." When the extra round turns into new features, that is a different conversation, and how to raise a change order covers it.

Rush: "If the client compresses the remaining schedule after a client-side delay, a rush fee of twenty-five percent of remaining fees applies. Without rush, the date moves."

One approver: "The estimate assumes one named person gives final feedback. Review by several people without a named decision-maker is billed as extra coordination time."

Assets first: "Work on a milestone starts when copy, logos, access and any required legal text are delivered. Missing assets count as waiting on the client."

None of these are aggressive. Most clients read them, nod, and never trigger them. Their real job is to make the conversation on day six boring.

Committees are where the real delay lives

My nineteen days were mostly a committee problem disguised as a busy owner. One person approved the plan. Three people reviewed the result. Whenever a client says "I'll just run it past a couple of people", I now ask who those people are and whether any of them can overrule the brief.

If the answer is vague, I price it. Either the client names a single approver, or the estimate carries a coordination line for the extra review. On a recent quote that was fifteen percent on top of the build fee, and the client chose to name one approver instead. That choice alone saved more time than the fifteen percent would have paid for.

Time zones stretch this further. An approver eight hours away reads your Friday afternoon delivery on their Monday morning, and nobody was slow for that to happen. So my feedback windows are written in calendar days when the approver sits in another zone, which saves us arguing later about whose business days count. If you work with people far away regularly, timezone collaboration without chaos has more on planning around that gap.

The email on day six

The pause clause is useless if you never mention it. On the day the feedback window runs out, I send something like this:

"Milestone B has been waiting on feedback since the 4th. Per the estimate, the delivery date now moves to the 21st. If the original date still matters, I can hold it with the rush terms, or we can release this week's slot and rebook. Which works better for you?"

It takes two minutes. It is polite. It also turns silence into a decision the client makes, rather than a cost I absorb. Regular, short updates like an end-of-day status note help here too, because a client who already sees "waiting on your copy for the pricing section" every evening is rarely surprised when the date moves.

If a client is slow on every single milestone, chasing becomes real work. I put communication time into the retainer or the estimate for those clients, rather than pretending reminders are free.

When a client is just always slow

Some clients will blow through every window you write. They are not bad people. Some businesses simply decide slowly. For those, the fix is the price, not more reminders: a higher fixed fee with a wider schedule, an hourly arrangement with a monthly minimum that pays for the time I keep for them, or a retainer with a stated review window on their side as well as a response window on mine.

The one arrangement I will not repeat is the fixed fee, tight date, no pause terms setup that I ran on that site. Buffer helps, and how much buffer a freelancer needs goes into sizing it, but buffer is for ordinary wobble. Nineteen days of silence followed by a hard launch date is not wobble. It is a business decision the client made, and the paperwork should let them pay for it.

A short checklist before the quote goes out

1. Feedback window per milestone, in business or calendar days
2. The day the project clock pauses
3. The rule for holding or releasing reserved time
4. Included revision rounds and the rate beyond them
5. Rush fee if they compress after their own delay
6. One named approver, or a coordination line
7. Asset list as the start gate

If a line is missing, I add it or I widen the price. Feedback delays are not a moral failing on the client's side, and they do not need to become resentment on mine. They are a known risk, as predictable as legacy code, and the freelancers who stay calm about them are the ones who priced them before the project started.