How We Estimate the Cost of Supporting Older Browsers
A working note on legacy browser support cost — what matters, what does not, and where these projects usually go sideways.
Most conversations about legacy browser support cost start with a tool comparison. They should start with the workflow. This post walks the order we actually use.
The problem underneath
Teams don't get legacy browser support cost wrong because they lack skill. They get it wrong because the decision gets made in a hurry, by whoever is closest to the ticket.
Nobody documents it. Six weeks later three people have three different mental models.
That gap costs more than the original choice ever did.
Two real shapes this takes
One common pattern we see: the product works and the process around it does not. Nothing in the code needs changing, but three people are doing manual repair work every day.
The other pattern is the reverse. Process is fine, the system cannot hold the shape the business now needs.
The fixes have almost nothing in common, so guessing is expensive.
Mistakes companies make
- Choosing tools before the workflow is written down.
- Scoping version one to cover every edge case.
- Leaving the work unowned, then blaming the tool.
- Skipping measurement, so nobody can prove it helped.
- Treating launch day as the end of the cost.
The first and the last are the expensive ones.
The engineering view
From inside the codebase, legacy browser support cost reduces to three questions. What happens when a step fails halfway. Who finds out. How you reverse it.
Design for partial failure before you need it. Step three fails after one and two already succeeded, and that is the case people skip.
Give retries a ceiling and some jitter. A retry storm is an outage you built yourself.
The sequence we use
- Map the workflow on one page, including the manual steps people are embarrassed about.
- Mark where money, time, or trust is being lost.
- Choose one of those, not three.
- Define what "better" means numerically before building.
- Ship a narrow version behind a flag.
- Compare a two-week window either side, then decide.
What good practice looks like here
- One owner, named, with time actually cleared.
- Limits enforced in code so a bad day cannot become a bad invoice.
- A short written record of why the choice was made.
- Alerts that a human reads, not a dashboard nobody opens.
- A scheduled review, because every decision here has a shelf life.
The trade-offs nobody puts in the proposal
Every option here buys you something and charges you elsewhere. Faster now often means a rewrite later, and that can still be the right call.
What matters is naming the bill in advance so it is a decision rather than a surprise.
Where the common advice is wrong
“Do it the way the big companies do.” Their constraint is coordination across many teams. Yours is probably two engineers and a deadline.
“Automate everything.” Automate the repeated, boring, high-volume part. Leave judgement to people.
“Wait until we have more data.” Ship something small and the data arrives.
Frequently asked questions
How long does legacy browser support cost take to get right?
A narrow first version is usually four to six weeks. Anything quoted at three months with nothing shippable in between is a risk, not a plan.
How do we know whether it worked?
Choose the number before you build — hours saved, error rate, response time, or conversion — then compare a two-week window either side.
How much should we budget?
Scope decides the number, but a focused first phase on work like this typically lands in the low five figures rather than a six-month programme.
What is the most common mistake with legacy browser support cost?
Scoping too wide. Covering every case in version one delays feedback and raises cost without a matching benefit.
When is the right time to revisit the decision?
When a second customer asks for something the first one never needed, or when volume changes by an order of magnitude.
Conclusion
The useful move on legacy browser support cost is almost always the smaller one. Ship a narrow slice a real user can touch this month, measure it, then decide what earns the next four weeks.
Everything gets easier once something is live.
Related reading and next steps
- AI audit — how we run this kind of work.
- growth analytics — where this often connects.
- More writing from the team.
Want a second opinion on legacy browser support cost for your setup? Book a 30-minute call. If it is not worth building, we will say so.
FAQ
Frequently asked questions
How long does legacy browser support cost take to get right?+
A narrow first version is usually four to six weeks. Anything quoted at three months with nothing shippable in between is a risk, not a plan.
How do we know whether it worked?+
Choose the number before you build — hours saved, error rate, response time, or conversion — then compare a two-week window either side.
How much should we budget?+
Scope decides the number, but a focused first phase on work like this typically lands in the low five figures rather than a six-month programme.
What is the most common mistake with legacy browser support cost?+
Scoping too wide. Covering every case in version one delays feedback and raises cost without a matching benefit.
When is the right time to revisit the decision?+
When a second customer asks for something the first one never needed, or when volume changes by an order of magnitude.
Building something similar?
Let's talk in 30 minutes.