Web Design Process: What Happens Step by Step

Ask three suppliers to explain how they build a website and you will get three diagrams. The boxes will differ, the arrows will differ, and none of it will tell you the thing you actually need to know: what you will be asked to decide, and when.

That gap matters more than it sounds. A website project is not really a production job. It is a sequence of decisions, what the site must produce, who it speaks to, what goes on which page, what gets cut, with build work attached to each one. When a project stalls, it is almost never because someone could not code the layout. It is because a decision was still open and nobody said so out loud.

So this guide walks the process from the client’s side of the table. Six phases, what closes each one, where the calendar actually goes, and what to expect once the site is live. The video below gives the quick overview if you want the shape before the detail.

PART 1 · DIAGNOSE

The Web Design Process Starts Before Any Design

IN BRIEFThe first phase produces no visible work, which is why it gets compressed. Discovery settles what one action the site must produce and who it must produce it from. Skip it and every later argument about layout becomes an argument about taste, the reason a website design project should open with a decision, not a mood board.

The useful discovery question is not “what pages do you want”. It is “what does a visitor do on this site that makes you money”. For most Malaysian service businesses the honest answer is a WhatsApp message or a phone call, not a purchase, and that single answer changes the layout of every page that follows.

Three things should be written down and agreed before any design work begins:

• The one primary action. Enquiry, booking, order, or quote request. If the list has four items, the site will convert none of them well.
• Who decides. One named person with final sign-off. Committees do not approve websites; they postpone them.
• What already works. Existing pages, rankings and enquiry sources you cannot afford to lose in the move.

That last point is where new builds quietly go wrong. A site that already earns organic traffic is carrying value that a fresh build discards by default. That is the same risk that makes deciding between a redesign and a rebuild a diagnosis rather than a preference.

BENCHMARK BRIEFING 1 OF 4

The Six Phases and the Decision Each One Closes

IN BRIEFEvery phase in a web design process has an owner, an output, and a decision it exists to close. Reading the table by the last column tells you where your own attention is genuinely needed, and where it is not.

Notice which phase closes no decision. Build is the only purely productive stage, and it is the shortest span in which a client can safely go quiet. Every other phase needs you awake.

PART 2 · DESIGN

How to Contract the Process Before It Starts

IN BRIEFThe shape of the contract decides how the process behaves under pressure. Fixed scope protects the price, phased engagement protects the outcome, and a monthly retainer protects nothing unless the deliverables are named, a distinction worth settling with IZI Digital Marketing before the first invoice.

One clause is worth more than the rest combined: what happens when you want something that was not in the brief. A supplier who has never written that clause down will improvise it in the middle of the project, usually badly.

BENCHMARK BRIEFING 2 OF 4

Where the Calendar Actually Goes in a Web Project

IN BRIEFProposals allocate time as though design and build dominate the schedule. In practice the content phase and the review loop absorb roughly half the elapsed calendar, and both sit almost entirely on the client’s side.

The pattern is consistent and slightly uncomfortable: the two phases that swell beyond plan are the two you own. A supplier can compress design and build with more hours. Nobody can write your service descriptions for you at three in the morning.

PART 3 · DEPLOY

The Review Loop That Decides Your Launch Date

IN BRIEFReview is where good projects go slow. The fix is procedural rather than technical, one consolidated list per round, two rounds agreed upfront, and one named approver. Check the result on a phone first, since a mobile-first layout is what most visitors will actually see.

Feedback arriving in dribs and drabs from four people is not four times as useful as one list. It is roughly four times as slow, because each fragment restarts a cycle of change, redeploy and re-check.

A review round that works looks like this:

1. Collect everything first. Everyone comments in one shared document over a fixed window, three working days is plenty.
2. Resolve contradictions internally. Two people wanting opposite things is your problem to settle, not the designer’s.
3. Separate faults from preferences. Broken forms and wrong prices are faults. Font size is a preference. Faults get fixed; preferences get budgeted.
4. Send one list, then stop. Additional items discovered afterwards go into round two, not into the current round.

Two rounds is the sensible default. The first catches real problems, the second confirms they were fixed. A third round almost always signals that a decision from an earlier phase was never actually closed.

Before you approve a launch, it is worth running a basic SEO audit checklist across the staging site. Page titles, headings, redirects from old URLs and working tracking are cheap to verify now and expensive to discover later. The phone check is not optional either, since Google’s own guidance is explicit that the mobile version of a page is what Search indexes and ranks.

BENCHMARK BRIEFING 3 OF 4

Five Causes of Overrun and Whose Court They Sit In

IN BRIEFWebsite projects overrun for a short list of repeatable reasons. Four of the five sit on the client’s side of the table, which is good news, the causes you control are the ones you can remove before the project starts.

The last row is the quiet one. Recovering a domain registered years ago by a former supplier can take weeks of email chasing, and it only surfaces on the day someone tries to point the domain at the new site.

PART 4 · DRIVE

What Happens in the First Month After Launch

IN BRIEFLaunch day is a milestone, not an ending. The first month settles indexing, catches the tracking that silently failed, and gives you the first honest read on whether the new site produces more enquiries than the old one.

Four things belong in the diary for the weeks after go-live:

• Check every form and tracking event yourself. Submit a real enquiry, click the WhatsApp button on a phone, confirm the notification arrives.
• Submit the sitemap and watch indexing. New URLs need to be found before they can rank.
• Compare enquiries, not visits. Traffic can dip while enquiries rise, and only one of those pays wages.
• Fix the small things fast. A typo on a service page is a five-minute job in week one and an embarrassment in month six.

Handover deserves the same attention. Domain, hosting, the content management login and the design files should all sit with you when the project closes. Confirm that in writing before you engage any website designer, not after.

BENCHMARK BRIEFING 4 OF 4

Why the Standard for a New Site Keeps Rising

IN BRIEFOfficial Malaysian statistics show e-commerce income by establishment climbing every year. More transaction value moving online is the reason a new build now has to end in a site that sells, not one that merely exists.

Growth has slowed but not reversed, and that shape is the point. Buying behaviour online is now normal rather than novel, so a new site is judged against what customers experience everywhere else, not against the site it replaced.

FAQ

Web Design Process: Common Questions

How long does the web design process take in Malaysia?

Plan for six to twelve weeks for a small business website. It depends far more on content readiness than on build speed, projects that stall almost always stall waiting for copy, photos and approvals. With the content written before the kick-off meeting, the quoted timeline usually holds.

What do I need to prepare before a web design project starts?

Prepare the words, the pictures and the logins. It depends on your setup, but at minimum that means draft copy for every page, real photos of your work or premises, and access to your domain, hosting and any existing analytics accounts. Missing logins cause more delay than missing designs.

How many revision rounds should a web design project include?

Two rounds is the sensible default for a small business site. It depends on how consolidated your feedback is, one list from one approver resolves faster than four opinions arriving separately. Agree the number in writing, because unlimited revisions almost always mean an undefined launch date.

Who writes the content for a new website?

You do, unless you pay someone specifically to do it. It depends on the scope you signed, most website quotes cover layout and build, not copywriting, and the assumption goes unnoticed until the design arrives full of dummy text. Settle this in the first conversation.

What should I receive at handover?

You should receive control, not just a live site. It depends on the contract, so check that domain registration, hosting account, content management login and design files all transfer to your name. Anything left in a supplier’s account is a dependency you did not agree to buy.

THE VERDICT

The Process Is a Decision Sequence, Not a Production Line

Every phase in a web design process exists to close a decision. Discovery decides what the site is for, content decides what it says, review decides what is good enough, and handover decides who owns the result. The build in the middle is the easy part.

So judge a proposal by the decisions it names, not the diagram it draws. If a supplier cannot tell you what you will be asked to approve and when, the schedule they quoted is a hope rather than a plan.