Context
The owner of an online store selling workwear for construction and utility crews. Six years on a single platform (an old version of OpenCart, customized by a previous developer who’s no longer on the project). The team: the owner, a manager, and an accountant. The developer — an external freelancer who maintains the site for about $400/mo. Revenue is steady, but flat for two years.
The pain
Every new idea the owner has (integration with the courier service, a mobile layout, a new payment method) turns into the same dialogue: the freelancer says “that’s hard on this version, we’d have to rewrite the whole module, ~$2K and 3 weeks.” And so it goes — every time. The owner suspects that part of “it’s hard” is either genuine, or a convenient excuse. Meanwhile, new IT companies show up offering “a full redesign on a modern platform for $15–25K.” The owner doesn’t know whether that’s the right investment, or whether his site still has years of life left in it.
Approach
Five days. Day 1 — a conversation with the owner about the business: where we actually lose customers, which features get requested most, how much a manager’s hour of manual data re-entry costs. Day 2 — a technical review of the site: the platform’s age, security risks, how hard it is to make changes, and how easy it would be to “exit” the system down the line. Day 3 — a comparison of two scenarios with real numbers: A) “rebuild everything on a modern platform” ($20K + 4 months), B) “targeted improvements on the current one” ($5K + 2 months). For each — a realistic 3-year ROI estimate. Day 4 — a deeper conversation with the owner: we go through both scenarios and look each risk in the eye. Day 5 — the final document + a 30-minute conversation.
Result
The owner chose option B — targeted improvements on the current platform. Because: 1) the business is stable, not explosive, so a full rewrite wouldn’t pay back within 3 years; 2) the current platform has another 2–3 years of life in it given minimal updates; 3) the main pain points are solved by 4 specific improvements (~$5K), not a total reinvention. The owner saved about $15K he’d been ready to spend. And, more importantly, he saved 4 months of attention that would have gone into the rewrite project — and instead was able to return to business priorities (a new sales channel, B2B clients).
What it taught
“Rebuild everything from scratch” is almost always more expensive and slower than it looks at the outset. It’s sometimes necessary (~20% of cases), but mostly it’s the sale of a service, not the optimal decision for the business. A 5-day independent look draws that line clearly, without emotion.
This is an illustrative composite pattern from 8 years of work in IT — not a specific client. AG is in a validation phase.