Straight answers before you start a website project.

We begin with understanding your business, target audience, objectives and existing digital presence. We then define the website strategy, information architecture, page structure, content requirements and SEO direction before moving into visual design and development.

The typical process is:

Discovery → Strategy → Information Architecture → Content → Design → Development → SEO & Technical Setup → Testing → Launch

The exact process can vary depending on the size and complexity of the project, but we don't start by blindly designing pages. We first work out what the website needs to accomplish and why.

See how we work →

We first need to understand what you're trying to achieve.

We'll discuss your business, current website, target audience, competitors, goals and any problems with your existing website. If you already have a website, we may also review its structure, content, SEO and overall user experience.

If the project looks like a good fit, we'll define the scope, deliverables, timeline and investment before development begins.

There is no pressure to start simply because you contacted us. The objective of the initial conversation is to determine whether we can genuinely add value.

Start a project →

You don't need to manage the project day-to-day.

We handle the strategy, architecture, design, development and technical implementation. However, your involvement is important at specific stages — particularly when we need business information, content, approvals, technical access or decisions that only you can make.

The ideal relationship is simple:

You provide the business knowledge. We handle the digital execution.

A responsive client can significantly reduce project delays.

There is no meaningful single number because a five-page business website and a large SEO-driven website are completely different projects.

A straightforward business website may take a few weeks, while a larger website involving extensive content, custom functionality, integrations, migration or complex SEO architecture can take considerably longer.

Before starting, we'll provide a realistic project timeline based on the agreed scope.

The timeline also depends on how quickly we receive content, feedback, approvals and access to required third-party services.

Typically, we need:

• Business and company information
• Logo and brand assets
• Existing website access, if applicable
• Domain and hosting access where required
• Relevant photographs, videos and other media
• Product or service information
• Existing marketing material
• Contact and business details
• Access to relevant analytics or search platforms, where required
• Any existing SEO information or keyword research
• Clear information about your target customers and business objectives

You don't necessarily need to have everything perfectly prepared before contacting us. Part of our job is identifying what is missing and helping structure the information.

We don't treat a website as an endless cycle of random changes.

Design and content are reviewed at defined stages. We collect feedback, make the agreed revisions and move the project forward once that stage is approved.

This keeps the project controlled and prevents a situation where a website continuously moves backwards and forwards because decisions are never finalised.

Feedback should ideally be consolidated rather than sent as dozens of individual changes from different people.

Changes are normal. Uncontrolled scope changes are not.

If you request additional pages, functionality, integrations, content work, SEO work or other requirements outside the agreed scope, we'll identify the change and explain its impact on cost and timeline before proceeding.

Small adjustments may be absorbed where practical. Significant additions will be treated as additional scope and approved separately.

This protects both sides and keeps the original project from becoming an open-ended engagement.

There is no sensible universal price for a professional website.

A website's cost depends on its size, complexity, functionality, content requirements, design requirements, integrations, SEO requirements and the amount of strategic work involved.

A website designed primarily to establish an online presence is very different from a website expected to generate leads, rank for competitive searches, support multiple services or serve as a long-term digital acquisition channel.

We price projects according to what needs to be built — not simply by multiplying the number of pages by a fixed page rate.

Discuss your project →

The major factors include:

• Number and complexity of pages
• Custom design requirements
• Website architecture
• Content requirements
• SEO strategy and implementation
• Custom functionality
• Forms and integrations
• Third-party APIs and services
• CMS requirements
• E-commerce functionality
• Migration from an existing website
• Technical complexity
• Performance and optimisation requirements
• Research and strategic consulting involved

Two websites with the same number of pages can therefore have very different project costs.

Payment terms are defined in the project proposal before work begins.

For most projects, an initial advance is required to reserve the project and begin strategy, design and development. The remaining payment is linked to agreed project milestones or completion.

The exact payment schedule depends on the size and nature of the project and will always be clearly documented before the project starts.

Work does not begin on the basis of a verbal commitment alone.

Not automatically.

Website development, hosting, domain registration, maintenance, premium software, third-party APIs, email services and ongoing SEO are separate costs unless specifically included in the proposal.

We'll clearly identify which costs are:

One-time project costs

and which are

recurring or third-party costs.

This means you know what you're actually paying for instead of discovering recurring costs after the website has been launched.

A website project involves real work from the moment it begins — including strategy, research, architecture, design, development and technical setup.

If a project is cancelled after work has started, the cancellation is handled according to the agreed proposal and payment terms.

Work already completed or committed third-party expenses remain payable.

Refund eligibility depends on the stage of the project and the terms agreed before commencement.

Payments covering work that has already been completed are generally not refundable. Similarly, payments made to third-party services, software providers, hosting companies, domain registrars or other vendors may not be recoverable.

If a project is cancelled before significant work begins, any applicable refund will be determined according to the agreed terms.

The important point is that the refund and cancellation terms are established before the project starts, rather than negotiated after a disagreement occurs.

Completed work remains subject to the agreed payment and project terms.

Depending on the circumstances, this may include strategy documents, research, information architecture, content structures, designs, code, configurations or other project assets already produced.

Unpaid work is not automatically transferred to the client simply because a project has been cancelled.

If ownership or transfer of completed project assets is required, the applicable terms will be determined by the project agreement.

We don't start with:

“Which template should we use?”

We start with:

“What does this website need to achieve?”

We look at the business, target audience, competition, search demand, existing digital presence, user journeys, conversion opportunities and the information the customer needs before making a decision.

From there, we develop the website structure and content architecture.

The objective is to make every important page have a reason to exist.

See our work →

Design is only one part of the job.

A visually impressive website that cannot be found in search, communicates poorly, loads slowly or fails to generate enquiries isn't necessarily a successful website.

Where appropriate, we consider:

• Information architecture
• Search intent
• SEO
• Content structure
• User experience
• Conversion paths
• Calls to action
• Technical performance
• Schema and structured data
• Internal linking
• URL architecture
• Mobile experience
• Analytics and measurement

The level of involvement depends on the project scope, but the objective remains the same: build a website that works as a business asset, not merely as an online brochure.

We think beyond the launch date.

A website should provide a foundation that allows you to add new services, publish new content, target additional search queries, create landing pages, improve conversion paths and expand the business without rebuilding the entire website every few months.

That means paying attention to the underlying architecture — including URLs, navigation, content hierarchy, internal linking, technical SEO, performance, structured data and CMS structure.

The launch is not the finish line.

It's the point from which the website starts doing its real work.

Read the blog →