In mid-October, at a company trading industrial equipment, a marketing coordinator handed a change request to the technical lead: swap the homepage banner for the autumn trade fair and add one entry point for a new product line, live by Wednesday. The lead passed it to a front-end developer hired two weeks earlier. After two days inside the project, the reply came back in one line — this system is not built in VUE, and I cannot touch it. The job posting said “familiar with VUE”, the candidate was hired against exactly that line, yet the old system sat there, immovable.
Knowing VUE does not mean being able to take over every legacy system
Ask in an interview whether someone knows VUE and the answer is nearly always yes; a live sample page usually looks clean. The trouble starts after the first day. A company website and its admin panel often have not been touched for years, and the way they were built belongs to an earlier generation than what junior developers train on. Faced with an unfamiliar structure, a capable hire may not even see where to begin. That is not a failure of the person; it is a recruitment that never verified what, besides VUE, the old system actually demands. For the owner, the money is spent and the backlog does not move.
Backlog grows: the redesign queue keeps getting longer
When the developer cannot make changes, requests do not disappear — they pile up. The autumn banner waits, then a Double-Eleven campaign page, a registration form for the annual dinner, refreshed case studies. The owner asks for progress and hears “still working on it”. A familiar picture emerges: the ad account keeps spending every day, visitors land on last season’s campaign, the product range has turned over twice, and the website still sells discontinued models. Lead quality drops, conversion falls, and at month-end the marketing coordinator cannot explain why, so budget gets added instead of redirected.
Caught between two choices: rebuild or endure
After two months of deadlock, two roads usually appear. One is a full rebuild, quoted anywhere from tens of thousands of yuan upward, hard to approve in the current budget. The other is ad-hoc outside help billed per change, with every newcomer relearning the system from scratch, so fixing one banner costs what building a section would. In practice many businesses take a third road: do nothing, and let the website run with stale information. All three are expensive, and they share one starting point — nobody established, when the system was taken over, whether it could be maintained at all, and by whom.
Staff leave, and hiring costs repeat
Developers who cannot take over the legacy system rarely stay past three months. For the company, that means recruitment fees, probation salaries and the lead’s mentoring time all sink, before the cycle restarts: new posting, new interviews, fresh disappointment. A retail chain once tallied it up: three front-end hires in one year, and the accumulated cost of recruitment and missteps would have paid for a professional team to refurbish the old system with money left over. Turnover itself is normal; what hurts is that every departure snags on the same spot — nobody can explain the system’s foundations, so every newcomer hits the same wall.
Broken handover: the code exists, but nobody can explain it
There is a quieter version of this problem. The original web company has gone quiet, the previous employee has returned their laptop, and server credentials sit in a spreadsheet. All the files are there, yet not one document explains how the system is deployed, what was changed and when, or who touched it last. A new hire looking at that pile of files is looking into a black box. What holds real value is not the code alone but the story around it — its history, its decisions, its weak spots. Once that thread is cut, even a strong engineer can only probe blindly, and every wrong probe shows up on the live site.
Before taking over, clear away three layers of ground
Most of this is avoidable, provided the groundwork happens before recruiting and handover. The first layer is technical: which generation of technology the system uses, whether anyone maintains it, what incidents it has had — have someone experienced review it before defining the role. The second is documentation and handover records: the original contract, source delivery, account ownership, past changes; complete whatever can be completed before memories and people fade. The third is the maintenance path: keep someone in-house or outsource the care, with a monthly budget and agreed response times written into the arrangement. With all three layers clear, the job posting is written accurately and a new hire can actually land.
A company website is a long run, not a one-off purchase. Familiarity with VUE only opens the door; whether the legacy system can be carried depends on how clearly its foundations were mapped, how honestly the handover was done, and who is responsible for its care. Xi’an Zunyun Technology has focused since 2015 on one-stop internet solutions for enterprises — website development, APP development, mini-program development, VUE front-end work, PHP back-end development, API integration and secondary development — and routinely maintains, refurbishes and redesigns legacy systems. If your business is stuck with an immovable old system, a broken handover or mis-aimed hiring, contact us first for an assessment, then decide whether to hire, rebuild or outsource.