12 Questions to Ask Before Hiring a Web Designer (2026)

This is the single most important question on the list. Every designer has a portfolio, but what matters is whether that portfolio includes work that's relevant to your industry, your audience, and your goals.

Why it matters: A designer who builds stunning fashion e-commerce sites might struggle with a corporate B2B website. The visual language, user expectations, and conversion paths are completely different. You want proof that they understand your type of business, not just that they can make things look pretty.

What a good answer looks like:

• They show you two or three live websites in your industry (or a closely related one)
• They explain the business goals behind each design, not just the aesthetics
• They share measurable results: increased enquiries, improved conversion rates, faster load times
• They can articulate why they made specific design decisions

Red flags: They only show mockups or screenshots (not live sites). Their portfolio has five identical-looking templates with different logos slapped on. They deflect with "we can do any style" without showing proof. If they can't demonstrate relevant experience, you're paying them to learn on your dime.

Take this seriously. Browse their portfolio sites on your phone. Check how fast they load. Click around and see if the navigation makes sense. A designer's best work is their portfolio; if that doesn't impress you, the work they do for you won't either.

A web design project has dozens of moving parts: discovery, wireframing, visual design, content creation, development, testing, and launch. If the designer can't explain their process clearly, they probably don't have one.

Why it matters: A structured process means fewer surprises. You'll know what's happening at each stage, when you need to provide input, and what milestones to expect. Designers who "wing it" tend to produce inconsistent results and miss deadlines.

What a good answer looks like:

• A clear, step-by-step breakdown: discovery call, project brief, wireframes, design mockups, development, content integration, testing, launch
• Defined approval points where you review and sign off before moving to the next stage
• A communication plan: how often you'll get updates, what tool they use (email, Slack, project management software)
• Contingency for scope changes: what happens if you want to add a feature mid-project

Red flags: Vague answers like "we'll figure it out as we go" or "it depends on the project." No mention of wireframes or prototypes (they're jumping straight to code). No approval checkpoints, which means you won't see the design until it's already built. If they can't explain their process in five minutes, they don't have a reliable one.

This question catches a lot of agencies off guard, and the answer reveals more than you'd expect.

Why it matters: Many agencies use a bait-and-switch model. A senior designer or the agency founder handles the sales pitch, then hands your project off to a junior developer or an outsourced freelancer. There's nothing inherently wrong with delegation, but you deserve to know who is actually doing the work.

What a good answer looks like:

• They tell you exactly who will handle design, development, and project management
• You can see those people's portfolios or profiles
• They explain the team structure: who you'll communicate with, who makes design decisions, who writes the code
• For smaller agencies or freelancers, they're upfront about doing everything themselves (which can actually be an advantage for consistency)

Red flags: "Our team will handle it" with no specifics. The person you're talking to won't be involved after the contract is signed. They outsource to developers in a different timezone with no overlap with your working hours. You discover post-signing that the "senior designer" on your project has six months of experience.

At TerrisDigital, the person you speak to is the person who designs your website. We believe that direct communication between the client and the designer eliminates the "telephone game" that ruins so many projects.

Web design pricing in Singapore varies wildly, from $500 to $50,000+. The number itself isn't the problem. The problem is when you don't know what that number actually covers.

Why it matters: Hidden costs are the number one source of frustration in web design projects. You agree to $3,000 for a website, then discover that copywriting is extra, stock photos are extra, the contact form plugin is extra, SSL is extra, and "SEO optimisation" is a $1,500 add-on. Suddenly your $3,000 website costs $6,000. For a full breakdown of what drives costs, see our guide on website costs in Singapore.

What a good answer looks like:

• A detailed scope document or proposal that lists everything included: number of pages, design revisions, copywriting (or not), image sourcing, SEO setup, mobile responsiveness, browser testing, training
• Clear pricing for common add-ons: additional pages, e-commerce functionality, custom animations, multilingual support
• Transparency about ongoing costs: hosting, domain renewal, SSL certificate, maintenance, plugin licences
• Written confirmation that the quoted price is the total price (assuming no scope changes from your side)

Red flags: A one-line quote with no breakdown. "We'll sort out the details later." Reluctance to put the scope in writing. Phrases like "starting from" without clarifying what determines the final price. If they can't tell you what's included before you pay, they'll definitely surprise you after.

Revisions are where most client-designer relationships get tested. Without a clear revision policy, you're setting yourself up for conflict.

Why it matters: "Unlimited revisions" sounds generous, but it usually means one of two things: the designer underpriced the project and will start pushing back after the third round, or they'll rush through changes to minimize their losses. Either way, the quality suffers. On the other hand, a designer who caps revisions at one round is essentially saying "take it or leave it."

What a good answer looks like:

• A defined number of revision rounds (two to three is standard for each project phase)
• Clear definition of what counts as a "revision" versus a "new request" or scope change
• A process for collecting and consolidating feedback (so you don't waste a round on miscommunication)
• Pricing for additional revisions beyond the included rounds
• Approval sign-off at the end of each phase, so approved work doesn't get revisited later

Red flags: "Unlimited revisions" with no caveats (it's a marketing line, not a policy). No written revision policy at all. They get defensive when you ask about this. There's no process for submitting feedback, leading to back-and-forth emails where changes get lost.

The best revision processes we've seen (and the one we use) involve structured feedback rounds with a clear brief template. We ask clients to compile all feedback into a single document per round, which reduces misunderstandings and keeps the project moving efficiently.

In 2026, this should be a given. But you'd be surprised how many designers still treat mobile responsiveness as an afterthought, and performance as someone else's problem.

Why it matters: Over 70% of web traffic in Singapore comes from mobile devices. If your website doesn't work flawlessly on phones, you're losing the majority of your potential customers before they even read your first headline. Speed matters too: Google uses Core Web Vitals as a ranking factor, and users abandon sites that take more than three seconds to load.

What a good answer looks like:

• They design mobile-first, not desktop-first with a responsive afterthought
• They can show you their existing sites' mobile performance scores (PageSpeed Insights, Lighthouse)
• They mention specific performance practices: image optimisation (WebP/AVIF), lazy loading, code minification, efficient caching
• They test on real devices, not just browser simulators
• They have performance targets: Largest Contentful Paint under 2.5 seconds, Cumulative Layout Shift under 0.1

Red flags: "Yes, it will be responsive" with no detail on how. Their own website scores below 50 on PageSpeed Insights. They've never heard of Core Web Vitals. They use heavy page builders that bloat every page with unnecessary code. If their own site is slow, yours will be too.

Here's a quick test: run the designer's own website through Google PageSpeed Insights. If they can't get their own site to perform well, they won't get yours to perform well either.

This is one of the most misunderstood areas in web design. Almost every designer claims their websites are "SEO-friendly." But what does that actually mean?

Why it matters: A beautiful website that nobody can find on Google is an expensive brochure. SEO isn't something you bolt on after launch; the technical foundations need to be baked into the design and development from day one. Poor site architecture, missing meta tags, slow load times, and broken internal linking can take months to fix after the fact.

What a good answer looks like:

• Technical SEO: clean URL structure, XML sitemap, robots.txt, canonical tags, proper heading hierarchy (H1 to H6), schema markup (LocalBusiness, FAQ, Service)
• On-page SEO: unique title tags and meta descriptions for every page, optimised image alt text, internal linking strategy
• Performance SEO: fast load times, mobile-first design, Core Web Vitals compliance
• Content SEO: keyword research for your target pages, content structure recommendations, blog capability for ongoing content marketing

Red flags: "We build SEO-friendly websites" with zero specifics. SEO is listed as a separate add-on at a premium price. They don't mention technical SEO at all (meta tags, schema, site structure). They promise "first page of Google" without doing any keyword research. Real SEO is systematic and measurable; vague promises are a warning sign.

At minimum, your web designer should deliver a site with proper technical SEO foundations. If they can also help with keyword strategy and content planning, that's a major bonus. If they can't explain the difference between technical SEO and content SEO, look elsewhere.

The technology behind your website affects everything: how easy it is to update, how fast it loads, how secure it is, and how much it costs to maintain. This isn't a decision to leave entirely to the designer.

Why it matters: Some designers default to whatever platform they're most comfortable with, regardless of whether it's the best fit for your needs. A five-page corporate site doesn't need the complexity of a full WordPress installation with 20 plugins. An e-commerce store with 500 products probably shouldn't be built on a basic website builder.

What a good answer looks like:

• They recommend a platform based on your specific needs (content volume, update frequency, e-commerce requirements, budget, team capability)
• They explain the trade-offs: WordPress offers flexibility but requires maintenance and security updates. Shopify handles e-commerce well but limits customisation. Static site generators (like Astro) deliver blazing speed but need a developer for changes
• They consider your team's technical ability: who will manage the site day-to-day?
• They discuss scalability: will this platform grow with your business?

Red flags: "We only build on [single platform]" with no rationale. They recommend an obscure or proprietary CMS that locks you into their services. They push an enterprise solution for a simple brochure site (over-engineering to inflate the price). They can't explain why their recommended platform is the right choice for your situation.

The right platform depends entirely on your business. A restaurant needs something different from a law firm, which needs something different from an online retailer. Any designer who gives the same answer to every client isn't thinking about your needs.

This question has saved business owners thousands of dollars and countless headaches. Do not skip it.

Why it matters: Some designers retain ownership of the code, the design files, or even the domain name. This means if you ever want to switch providers, you're starting from scratch, or worse, paying a "release fee" to get access to your own website. It's more common than you'd think, especially with agencies that bundle hosting into their packages.

What a good answer looks like:

• Full ownership of all code, design files, and content transfers to you upon final payment
• You own (or can easily transfer) the domain name, registered under your name or your company's name
• You have full admin access to the hosting account, CMS, and any third-party services (Google Analytics, Search Console, etc.)
• Design source files (Figma, Sketch, PSD) are included in the deliverables
• No lock-in clauses that penalise you for leaving

Red flags: The domain is registered under the designer's name or company. You don't get admin access to your own hosting. The contract includes a "proprietary platform" that only they can maintain. There's a fee to "export" or "release" your website. They avoid answering the ownership question directly.

Get this in writing before you sign anything. A legitimate designer will have no problem confirming full ownership transfer. If they hesitate or add conditions, that's your cue to walk away.

Your website doesn't stop needing attention the moment it goes live. In fact, launch day is when the real work begins.

Why it matters: Software updates, security patches, content changes, bug fixes, performance monitoring, and backup management are ongoing needs. If your designer disappears after launch, you're left managing a technical asset with no support. For a detailed breakdown of post-launch costs, see our guide on website maintenance costs in Singapore.

What a good answer looks like:

• A defined warranty period (30 to 90 days) for fixing bugs and issues discovered after launch
• Training for you and your team: how to update content, add pages, manage forms, and check analytics
• A clear maintenance plan (monthly or quarterly) with defined scope and pricing
• Backup and security monitoring included or available as a service
• Response time commitments: how quickly they'll address urgent issues

Red flags: "We don't offer maintenance" (so who fixes things when they break?). Post-launch support is priced at a steep hourly rate with no retainer option. No training provided; you're expected to figure out the CMS yourself. No mention of security updates or backups. The designer goes radio silent after the final payment.

A good designer builds a website that's easy to maintain. A great designer also helps you maintain it. Make sure you understand the ongoing relationship before you commit to the initial build.

Every business owner wants their website "ASAP." Every experienced designer knows that rushing a website leads to cutting corners. The honest conversation about timeline happens here.

Why it matters: A realistic timeline sets proper expectations and prevents frustration on both sides. More importantly, understanding what could cause delays helps you do your part to keep the project on track. For context on how long projects typically take, read our guide on how long it takes to build a website in Singapore.

What a good answer looks like:

• A specific timeline (e.g., "six to eight weeks from signed contract to launch") with milestones for each phase
• Clarity on what they need from you and when: content, images, brand assets, feedback on designs
• Honest acknowledgement that client delays (late feedback, missing content) push the timeline back
• Buffer time built into the schedule for unexpected issues
• A defined process for handling timeline changes if scope increases

Red flags: "We can have it done in a week" for a custom multi-page website (they're using a template and calling it custom). No milestones or checkpoints. They blame previous clients for delays without explaining how they mitigate that. The timeline is vague: "a few weeks" or "it depends." If they can't give you a concrete timeline, they either don't have a process or they're juggling too many projects.

For most custom business websites in Singapore, expect four to eight weeks from kickoff to launch. That includes discovery, design, development, content integration, and testing. Anything significantly faster usually means shortcuts. Anything significantly longer usually means poor project management.

Portfolios show you the finished product. References tell you what it was actually like to work with the designer.

Why it matters: A beautiful website doesn't tell you whether the designer communicated well, met deadlines, handled feedback gracefully, or was easy to reach when problems arose. Past clients can tell you all of this, and their honesty is usually refreshing.

What a good answer looks like:

• They provide two or three references without hesitation
• References are from recent projects (within the past 12 months), not from five years ago
• They have published testimonials or case studies on their website with real names and companies
• They're listed on review platforms (Google Business Profile, Clutch, or similar) with verified reviews
• They offer to connect you directly with past clients for a brief conversation

Red flags: "We don't share client information" (a convenient excuse). All testimonials are anonymous or use first names only. They have no online reviews anywhere. References are all from projects completed more than two years ago. They get defensive when you ask, which suggests they know what past clients might say.

When you do speak with references, ask these three things: Was the project delivered on time? Were there any surprise costs? Would you hire them again? Those three answers will tell you almost everything you need to know.

Don't just read this list and nod along. Actually use it. Here's how to get the most out of these questions to ask a web design agency:

• Ask all 12 questions to every designer you're considering. Comparing answers side by side reveals differences that aren't obvious from portfolios alone
• Get answers in writing. Verbal promises mean nothing when there's a dispute three months later. Ask them to include key points in the contract or proposal
• Pay attention to how they answer, not just what they answer. A designer who is confident, specific, and transparent is almost always a better choice than one who is vague, defensive, or evasive
• Don't choose the cheapest option by default. The cheapest quote usually becomes the most expensive project when you factor in revisions, delays, and eventually hiring someone else to fix it
• Trust your gut. If something feels off during the sales process, it will feel worse during the project. Communication issues don't improve after the contract is signed

For a deeper guide on evaluating agencies, read our post on how to choose a web design agency in Singapore.

How many web designers should I compare before hiring one?

Three to five is the sweet spot. Fewer than three doesn't give you enough data to compare. More than five leads to decision paralysis and wastes everyone's time. Focus on designers who have relevant experience in your industry and can articulate their process clearly.

Should I always go with the designer who has the best portfolio?

Not necessarily. Portfolio quality matters, but communication, process, and reliability are equally important. A designer with a slightly less flashy portfolio but excellent project management will almost always deliver a better outcome than a creative genius who misses every deadline.

Is it better to hire a freelancer or an agency in Singapore?

Both can deliver excellent work. Freelancers often offer more personalised attention and lower overhead costs. Agencies offer broader skill sets and backup capacity if someone is unavailable. The right choice depends on your project size, budget, and how much direct involvement you want with the person doing the work.

What should I prepare before contacting a web designer?

At minimum, have a rough idea of your budget range, your timeline, and what you want the website to achieve (generate leads, sell products, build credibility). If you want to go further, write a website brief that outlines your goals, target audience, competitor examples, and must-have features. The more prepared you are, the more accurate the quotes you'll receive.

What if the designer can't answer some of these questions?

That's useful information in itself. If a designer can't explain their process, their pricing structure, or their revision policy, it usually means they haven't formalised these things. That doesn't automatically disqualify them, but it increases your risk. For business-critical projects, choose someone who has clear, documented answers to all 12 questions.

How much should a web designer cost in Singapore?

A custom business website in Singapore typically ranges from $2,000 to $15,000, depending on complexity, number of pages, and features like e-commerce or custom functionality. Template-based sites can start from $500 to $1,500. Be wary of quotes that are dramatically lower than average; they often come with hidden costs or compromised quality. Read our full breakdown on website costs in Singapore.