Question 1

Do you build the site as well, or only design it?

Accepted Answer

Both are available, but they are deliberately separate services. Design ends with a Figma file, a design system and specs; our web development service takes that into Next.js, React and a typed back end. Plenty of clients hand our design file to their own developers, which is exactly why the handover is documented rather than a set of flat images.

Question 2

Who owns the design files?

Accepted Answer

You do, on final payment. You get the working Figma file with editable components and tokens, not a flattened export, plus source assets and any licensed fonts or images identified so you can renew them. Nothing is held back to keep you dependent on us.

Question 3

When is a template or theme good enough, and when do we need custom design?

Accepted Answer

A well-chosen theme is a sensible choice if your content is standard, your brand is still forming and speed matters more than differentiation. Custom design earns its cost when you have a specific conversion path, an unusual catalogue or service structure, several languages, or brand recognition you cannot afford to look generic against. We tell you which situation you are in before quoting.

Question 4

What drives the cost of a web design project?

Accepted Answer

The number of unique templates, not the number of pages. Twenty pages built from five templates costs far less than eight pages that each need their own layout. Additional drivers are the number of languages, whether a design system has to be created from scratch or extended, and how many rounds of stakeholder review the process needs to absorb.

Question 5

How long does the design phase take?

Accepted Answer

A corporate site typically takes three to five weeks from kickoff to handover, a focused landing page around one to two weeks, and an e-commerce design longer because category, product, cart and checkout screens each carry many states. Feedback speed on your side is usually the biggest variable in the schedule.

Question 6

What do you need from us to start?

Accepted Answer

Your goals and target audience, any brand assets you already have — logo, fonts, colour, photography — plus access to analytics if the site exists, and one named decision maker who can approve. Real content, even in draft form, is the single most valuable thing you can supply, because designing around placeholder text hides problems that surface at launch.

Question 7

How many rounds of revisions are included?

Accepted Answer

We work in structured review rounds — usually two per stage — rather than open-ended tweaking, and each stage is signed off before the next begins. That keeps changes cheap: a structural change during wireframes costs an hour, the same change after visual design costs days. Requests outside the agreed scope are quoted separately before any work starts.

Question 8

Do you design mobile-first?

Accepted Answer

Yes, and not as a slogan. The majority of traffic on the sites we work on arrives from mobile, often on mid-range Android hardware over a mobile connection, so we design the narrow layout first and treat the desktop version as the expansion. Tap target sizes, thumb reach, form length and image weight are decided at that width.

Question 9

What accessibility level do you design to?

Accepted Answer

We design to WCAG 2.2 AA as the working target: colour contrast for text and interface elements, visible focus states, a logical heading structure, labelled form fields and layouts that survive 200% zoom. Full conformance depends on the build and on your ongoing content, so we hand over the rules and check the implemented pages rather than claim a certificate.

Question 10

Can you design Arabic or other right-to-left interfaces?

Accepted Answer

Yes. RTL is a layout and typography problem, not a translation problem: navigation, icons, form alignment, charts and numerals all need deliberate mirroring, and Arabic type needs its own size and line-height scale to sit correctly next to Latin text. We design the LTR and RTL versions as one system so a single build serves both.

Question 11

We already have a site — can you redesign without losing our search traffic?

Accepted Answer

Yes, and it needs planning rather than good intentions. We keep the existing URL structure where it earns traffic, map redirects for anything that must change, and preserve the pages and headings that already rank while improving their layout. Search implications are reviewed during information architecture, which is the stage where a redesign usually loses rankings.

Question 12

Will a heavier design slow the site down?

Accepted Answer

It can, which is why we set a performance budget during design instead of arguing about it after launch. Full-screen video, carousels, multiple font weights and large decorative imagery are the usual culprits, and we either justify their cost in load time or replace them. Core Web Vitals are treated as a design constraint alongside brand and layout.

How can we help?

Web Design
FAQ

Helpful
information

Getting Started

Timeline

Pricing

Support

Still have questions?

Web DesignFAQ

Helpfulinformation