Put an actual number on it: multiply the weeks you were delayed by what a normal week earns, then add the specific peak period you missed — for a seasonal business the second figure usually dwarfs the first. That number is the argument for a hard deadline on your next project, not for a bigger budget.
The moment it happens
The real business cost of a website delay becomes visible when the season is over. The site you commissioned in July for the wedding rush arrives in December. It works fine. It just arrives in the month when nobody’s buying.
The build price was ₹25,000. Whatever the wedding season normally earns you is a completely different order of number, and it isn’t recoverable next year — that’s a different year’s revenue, not this one’s, delayed.
Which businesses this hits hardest
Not every business is seasonal, and for some this cost is genuinely small. It’s largest when your revenue concentrates into windows:
- Wedding-linked trades — decorators, caterers, photographers, boutiques, banquet services. A concentrated season with firm dates.
- Festival retail — the weeks before Diwali carry a disproportionate share of the year.
- Education-linked services — coaching, uniforms, admission consultants, tied to admission cycles.
- Tax and compliance work — filing deadlines create the demand.
- Construction and interiors — post-monsoon activity.
- Tender-driven B2B — tenders have closing dates and a website requirement.
If your trade is on that list, a delay isn’t a delay. It’s a skipped year for that window.
Putting a number on it
Three components. Estimate each roughly rather than precisely — precision isn’t the point.
1. Ordinary weeks lost. How many weeks late was the site, and what does a normal week earn? Then apply an honest fraction — the website was never going to produce all of it. Even a conservative fraction of ten weeks is a real figure.
2. The peak window. Did a season pass? Estimate what those weeks normally earn against what they earned this year. This is usually the dominant number.
3. Specific lost moments. Count them if you can: corporate buyers who asked for a link, tenders you skipped for lack of a website field, marketplace or gateway applications you couldn’t complete. Each has a nameable value.
| Component | How to estimate | Typically |
|---|---|---|
| Ordinary weeks | Weeks late × weekly revenue × honest fraction | Moderate |
| Peak season missed | This year’s peak vs. a normal year’s | Often the largest |
| Named lost moments | Count them, value each | Variable, sometimes very large |
What the number should change
Not your budget. Your deadline discipline.
The single most useful conclusion from this arithmetic: a website that arrives before your season is worth much more than a better website that arrives after it. That reorders every decision in a project.
Which means:
- Buy earlier than feels necessary. If your season starts in September, commission in June, not August.
- Choose a smaller scope that lands on time over a larger scope that might not. Five good pages before the season beats twelve pages after.
- Make the date a term, not a hope. In writing, with a stated consequence — a partial refund, a discount, a hold on final payment.
- Send all content before the build starts. Content delay is the largest single cause of overrun, and it’s on your side.
- Pay against viewable stages, so a slip is visible in week two rather than week eight.
The order that protects a season
If you have a date that matters:
- Work backwards. Season start, minus two weeks of buffer, minus the build time. That’s your commissioning date.
- Tell the vendor the real date and why. A season with a fixed date is more persuasive than a general request for speed.
- Have content ready first. Text, photographs, logo, prices — before you pay the advance.
- Write the date and the consequence into the agreement.
- Ask for a staging link from day one, so you can see a slip early enough to act.
Being fair about it
Not all of a delay is the vendor’s. Content arriving in pieces over six weeks is the most common cause of overrun, and it’s the buyer’s side. So is approval waiting on a family member who’s travelling.
Which is the practical point. If a missed season costs you many times the build price, then getting your own content ready before the project starts is the highest-return hour you will spend on the whole thing.
What to do this week
- Identify your peak window and its dates.
- Estimate the three components and write down the total.
- Work backwards to your commissioning date for next season.
- Gather all content into one folder now, before you engage anyone.
- Put the date and a consequence in writing on your next project.
If you want it done the certain way
Tell us the date your season starts and we’ll tell you honestly whether it’s achievable and what scope fits — including when a smaller site that lands on time is the better call. The date goes in writing, and you get a staging link from the first build day so a slip is visible early. WhatsApp us; we reply in about five minutes between 9am and 7pm.
Related reading
- Add up everything: the true cost of failed attempts
- The hidden cost of a delayed website
- Diwali, wedding and tender season: when “someday” becomes “this week”
- A client asked for my website and I don’t have one
FAQ
How do I calculate what a website delay cost my business?
Multiply the weeks you were late by normal weekly revenue and apply an honest fraction, then add the value of any peak season that passed, plus specific lost moments like tenders skipped or corporate enquiries you couldn’t answer with a link.
Is it better to launch a smaller website on time or a bigger one late?
For a seasonal business, almost always on time. A site that arrives before your peak window earns for that window; a better site arriving afterwards earns for a period when demand is low.
How do I stop a website project from missing my season?
Work backwards from the season start with a two-week buffer, have all content ready before paying the advance, put the date and a consequence in writing, and ask for a staging link so slippage is visible in week two.
