Improve your website or rebuild it? Start with what is failing.

A new design is a proposal, not a diagnosis

Your website feels dated, the sales team dislikes sending its link, and updating a service takes several messages to a developer. A rebuild may help. It may also replace working parts while leaving the original problem untouched. Before commissioning one, separate what visitors cannot understand, what the website cannot do, and what your team cannot maintain. These are different problems, and they do not always require the same intervention.

Write down the job the website must perform

For a Saudi engineering supplier, the useful job might be helping a procurement manager identify the right service, confirm coverage and send a sufficiently detailed request. For an established store, it might be making product selection and purchase more understandable. Start with one primary journey rather than a list of visual preferences. Describe who starts it, what they need to learn, which action matters and what counts as a functioning result. Include Arabic and English where both are genuinely needed.

Collect evidence in four places

Review content, customer tasks, maintenance and technical constraints separately. On content, check whether services, delivery areas and exclusions are accurate in both languages. For customer tasks, try the main route on a phone and a keyboard, including an invalid entry or unavailable item. For maintenance, ask an actual staff member to change a service description. For technical constraints, record what prevents a necessary change: inaccessible accounts, an unsupported dependency, restricted platform features or undocumented custom code.

Keep a short evidence sheet: the observed issue, where it occurs, who it affects, and how you would confirm a repair. “The site needs a modern look” is a preference. “The Arabic service page describes an offer we no longer deliver” is a concrete problem.

Choose the smallest change that addresses the cause

Targeted improvement fits when the foundation is workable and the problems are specific: unclear content, a broken contact route, inconsistent navigation or a difficult template. A partial rebuild fits when one section or journey needs different behaviour but the rest remains useful. A full rebuild becomes more reasonable when several essential requirements are blocked by the existing foundation, or maintaining it creates repeated, documented obstacles.

Imagine a fictional industrial maintenance company in Dammam. Its site looks old, but the main complaints are vague service descriptions and enquiries missing equipment details. Those observations support a content and enquiry project first. If investigation also shows that nobody can access the source or safely update the application, replacing the foundation may join the scope. The additional evidence changes the decision.

Compare the work behind each option

Ask for a short assessment that sets out what can be retained, what must change, what remains uncertain and the consequences of each option. Include the practical work: content rewriting, bilingual review, account recovery, old address mapping, integrations, staff training and ongoing maintenance. A rebuild proposal that mentions only design and page count leaves important work undefined.

Also decide what must survive the transition. Existing service addresses, useful articles, enquiry destinations and search visibility deserve explicit treatment. Keep a record of the current state so the team can distinguish a migration problem from an older issue. Do not assume every old page deserves to remain, but give each meaningful address a deliberate destination.

Make the decision testable

Agree on delivery checks before development begins. A member of staff can update the agreed content. The required service information is available in each language. Important old links reach relevant new pages. A test enquiry follows the agreed route. These checks establish whether the work was delivered; increased sales would require separate evidence over time.

Bring your current website, the three most persistent problems and the person who maintains it to the first conversation. Discuss a scoped website review with Sabbk. The useful outcome is a justified next step, whether that is a repair, a focused rebuild or a replacement.