12 Questions to Ask Before You Hire a Web Design Company

Choosing who builds your website is mostly a question of trust, and quotes rarely tell you much. Two proposals with similar prices can mean very different things once the work starts. The questions below are the ones that surface those differences early, while you can still walk away. This guide groups them by what they protect: ownership, scope, timeline, what happens after launch, evidence of past work, and the real shape of the cost. It ends with a table of all twelve questions, what a good answer sounds like, what a warning sounds like, and the mistakes that make a project go wrong.

Ownership: the four questions that matter most

This is where the worst surprises live, and it is the easiest section to skip because everyone is being friendly at the start of a project.

• Will the domain be registered in my name? It should be. If the agency registers it under their own account, you are dependent on them to keep it.
• Who controls the hosting account? You should have your own login, or at minimum the right to be given one on request.
• Do I own the finished site, including the files? Get this in writing, along with what happens if you part ways.
• Can the site be moved to another host? Some setups are portable. Some are not. Better to know now.

A straightforward supplier answers all four without hesitation.

Scope: what is actually included

Most disagreements later are really disagreements about scope now. Ask specifically:

• How many pages does the quote cover, and what does an extra page cost?
• Who writes the text — you, or them? This is the single most common gap.
• Are photos included, or do you supply them? Are stock images licensed?
• How many rounds of revisions, and what counts as a revision?
• Is the site set up so search engines can index it properly?

The most expensive version of this gap shows up when "the text" turns out to mean twelve pages of marketing copy nobody has actually written yet. Ask to see a page-by-page content plan before signing, not after the first invoice arrives and the project stalls waiting on words that were never budgeted for.

What a complete quote lists

A quote you can compare against another one itemises what is in and what is out. For a small business site, the list usually looks like this:

Our guide to website costs in Malaysia puts numbers against each row, and what to prepare before a website project lists what the supplier will need from you.

Timeline: how long, and what will delay it

Ask for a realistic timeline and, more usefully, ask what typically causes delays. An honest answer is almost always "waiting for content from the client" — which tells you the project depends on your input as much as theirs. If a supplier promises a fast turnaround without mentioning what they need from you, that estimate is unlikely to hold. Our guide to how long a website project takes gives typical durations by site size.

As a rough scale: a five-page site usually takes two to four weeks once content is ready, while a ten-page site with a booking system or online store often runs eight to twelve weeks. The gap between that estimate and the calendar weeks a project actually takes is almost always the client side — text arriving in batches, photos needing a re-shoot, or an approval sitting unread in someone's inbox for a week. Ask how the supplier handles a stalled handoff; a fixed check-in date that keeps nudging the project along is a better sign than an open-ended "whenever you're ready."

After launch: the question most people forget

A website is not finished when it goes live. Ask what happens next:

• Who updates text and images later — and at what cost?
• Who is responsible if the site goes down?
• Are backups taken, how often, and has a restore ever been tested?
• Is there a support arrangement, and what response can you expect?

A site nobody maintains quietly degrades: contact details go stale, plugins age, and a small problem becomes an outage. A supplier who can describe their last outage, and how quickly they noticed it, is worth more trust than one who claims it never happens. Our guide on why a website needs ongoing maintenance covers what proper upkeep looks like month to month.

Evidence: ask to see the work, not the portfolio

Portfolios show the best day of a project. More useful questions: can I see a site you built two years ago that is still running? Can I speak to that client? Does the site load quickly on a phone right now? Open one of their live sites on your own phone while you are in the meeting — that single test tells you more than a slide deck.

When you do get a past client on the phone, ask about the two years after launch rather than the launch itself: did anything break, how fast was it fixed, and would they hire the same supplier again today. A supplier confident in their own aftercare will usually offer this call before you think to ask for it.

Cost: understand the shape, not just the number

Ask what is one-off and what recurs. A website has a build cost, then ongoing costs for the domain and hosting that continue regardless of who built it. Ask what happens at renewal, and whether ongoing maintenance is billed hourly, monthly, or not offered at all. A cheap build with no maintenance path can cost more over three years than a well-scoped one.

A worked comparison makes this concrete. A five-page site built for around RM4,800 with no maintenance plan, left to accumulate small breakages and stale content, often needs several thousand ringgit of emergency fixes and an eventual partial rebuild within three years. The same site on a RM150/month care plan costs roughly RM5,400 over the same three years, but stays updated, backed up and monitored the whole time. The cheaper quote on day one is not automatically the cheaper total by year three.

The twelve questions, with good and warning answers

Common mistakes when choosing a supplier

• Comparing quotes by the total alone. Two numbers that look the same can cover different page counts, revisions and ownership terms.
• Accepting verbal reassurance on ownership. Get it in the proposal or contract.
• Assuming the text is included. The most common cause of a stalled project.
• Judging on the portfolio. Ask for the old sites and the clients.
• Ignoring what happens after launch. The site that nobody maintains is the next recovery exercise.
• Letting the agency own the accounts. See who owns your website for what to check.
• Choosing the cheapest build without a maintenance path. Three years of hourly fixes cost more than a care plan.
• Not testing a live site on your phone. It takes ten seconds and tells you how their work actually performs.

Where Gotka Technologies fits

Gotka Technologies has provided hosting and digital services in Malaysia since 2004, and we are happy to answer every question above directly. Web design covers the design and build, with packages from a five-page Starter site at RM5,300 and the full list of inclusions and add-ons on the package builder; the site is hosted on our own cloud hosting from RM17.80/month on LiteSpeed servers with free SSL and daily backups, and domains from RM10/year are registered in your name. After launch, a care plan from RM150/month covers updates and monitoring.

If you already have a site with another provider and want to move it, migration is free and our team handles the transfer.

Key terms used in this guide

• Registrant: the person or company recorded as the legal owner of a domain name.
• Scope: the written list of what a project includes and excludes.
• Revision round: one batch of feedback and the changes made in response; the definition varies by supplier.
• Copywriting: writing the text for the site's pages, usually quoted per page when not supplied by the client.
• Portable site: a site built on standard software that any hosting provider can run.
• Handover: the delivery of files, logins and documentation when the project ends.
• Care plan: a monthly arrangement covering updates, backups, monitoring and small edits.
• Recurring cost: what the site costs each year to keep online, regardless of who built it: domain, hosting, maintenance.
• Total cost of ownership: the build cost plus every renewal, fix and maintenance fee over the years the site stays in use, not just the initial quote.
• Stalled handoff: a project delay caused by the client side — missing text, unreviewed drafts, or an approval nobody has signed off.