Have a website built — planable scope and acceptance.

A professional website that carries your offer and enquiries — without months of agency ping-pong. Visible scope and price, clear milestones, acceptance with criteria. Ideal when nobody in-house can own delivery and you still need control over the brief.

  • Scope in the dashboard
  • 50/50 payment
  • Checklist acceptance
Concrete example

Example scenario (anonymised)

A 12-person trades business wants to leave a 2014 one-pager. Goal: 2–4 qualified enquiries per month by service and region — not maximum clicks. In the briefing we lock 6 core pages, a form with required fields for job type and timing, and defer a customer portal to phase 2. Design and build run via dashboard milestones; acceptance against a checklist (mobile, form, legal pages, baseline performance). Final payment only after acceptance.

In practice projects rarely fail because of “pretty design” — they fail on unclear scope and missing acceptance. We therefore run delivery via dashboard and written criteria — freelance, no agency façade, with an honest no to scope that breaks timeline or enquiry quality.

This page’s job: Owns first-build purchase intent only: professional setup with scope and acceptance. Not relaunch, not B2B committee depth, not a lead guarantee.

Checklist

Checklist: before you commission a website

Use this list with any vendor — including us. Missing answers mean missing scope.

  1. 01

    Target enquiry

    What is a good lead (budget, region, urgency) — and what is not?

  2. 02

    Pages & features

    Written list including forms, languages, blog — MVP vs later.

  3. 03

    Content

    Who supplies copy/photos by when? What if content is late?

  4. 04

    Milestones & acceptance

    Which criteria end the project? How many review rounds are in scope?

  5. 05

    Payment

    Which rate when? Is the final rate tied to acceptance?

  6. 06

    Out of scope

    What is explicitly excluded (shop, app, ads, ranking #1)?

Problem & fit

Why “cheap build” becomes expensive

Cost of the status quo

Cheap builders and fuzzy freelancer projects create rework, hidden hours, and sites nobody accepts. The real cost sits in delayed enquiries, internal meetings, and a presence decision-makers do not trust.

What “done” looks likeA live company website with fixed scope, transparent pricing logic, and acceptance that truly ends the project.
When a professional build is worth it

When trust and enquiries matter more than the cheapest builder. Ideal when you want to buy capacity — but keep control of scope and acceptance.

Not for you if…

  • You only need a one-page calling card with no enquiry goal
  • You want pure hourly billing without milestones
  • You will not supply subject-matter content and expect magic copy
Differentiation & buying guide

Having a website built: how we differ — and what to watch.

First professional sites are often sold as “all inclusive”. In reality scope, acceptance, and limits are missing. We state before build what is in, what comes later — and what we will not do, with reasons.

How we differ on new builds

Briefing before pixels

Goals, pages, features, and pricing logic in the dashboard — before design rounds. No “we will start anyway” without scope.

MVP cut, not a wishlist

What carries go-live and enquiry quality comes first. Nice-to-haves are deferred or declined if they break the core.

Acceptance ends the project

Checklist and 50/50: final rate only after acceptance. Endless “one more small thing” is not the business model.

One delivery line

Concept, design, and build fit together — you are not negotiating between three vendors with gaps between them.

What to watch when having a website built

  • Fixed price without page/feature list and change rules
  • Unlimited revisions in the price — often unclear scope
  • “Done in two weeks” without content, hosting, and acceptance criteria
  • Builder price with custom-app and ranking-#1 promises
  • Only mockups; build and handoff unclear or outsourced without process
  • No payment tied to milestones/acceptance

Included vs. deliberately not (new build)

Typical clarity in the briefing — final per project:

  • We do / include

    Agreed page and feature scope with milestones and acceptance

  • We do / include

    Structure and design that carry the offer and next step

  • We do / include

    Declining scope that risks timeline or enquiry goals — with rationale

  • We do not / exclude

    Endless feature drops “on demand” without change control

  • We do not / exclude

    Guarantees for rankings, traffic, or lead volume

  • We do not / exclude

    Complex web-app logic hidden inside a website package

If you want a plannable start with honest scope: start the briefing. If you want maximum promises without limits, we are not the fit — better known early.

How delivery works

What you get, what you carry, how we finish.

Planable scope — not an open hours jar and not fake 48-hour promises.

/ 01

What goes live

A finished, operable site with core paths: offer, trust, contact/enquiry.

/ 02

Why it is planable

Questionnaire, pricing logic, and reviews in the dashboard — you see the plan before work scales.

/ 03

When value lands

Realistic milestones — not fake 48-hour marketing. Speed through clarity, not emptiness.

/ 04

What you carry

You prioritise content and approvals; we structure, design, and build in scope.

What changes

Practical outcomes for you.

01

One accountable partner

Concept, design, and build fit together — you are not negotiating between three vendors.

02

Transparent milestones

You know what ships in each phase and when feedback counts.

03

Tech with a future

A modern base that does not block SEO, performance, or later extensions.

In the package

Core delivery and what sits next to it.

01
Core

Predictable website build

IA, design, and build of core pages in the agreed scope.

02
Bonus

Structured briefing with pricing logic

Visible in the customer area before design rounds start.

03
Bonus

Review checklists instead of chat chaos

Feedback becomes decidable — OK or a concrete change.

04
Bonus

Acceptance and handover ZIP

The project ends with criteria and handoff — not “one more small thing”.

Typically included

  • Information architecture and page framework
  • Brand-aligned design system approach
  • Implemented site including core pages in scope
  • Acceptance and go-live support
Steps

From briefing to live site

01

Clarify goals

Enquiries, brand, content, deadlines — without this, design is guesswork.

02

Concept & design

Structure and look that buyers and search engines can understand.

03

Build & content

Implementation: responsive, fast, solid foundations.

04

Acceptance & go-live

Checklist, in-scope fixes, launch, and handoff.

FAQ

Objections, answered honestly.

How long does it take to have a website built?

Depends on scope and content supply. In the briefing we give a realistic timeline with milestones — no fake 48-hour promises.

Do we have to write all copy ourselves?

You know your offer best. We structure and sharpen; final subject-matter content comes from you or in collaboration.

What does it cost?

Depends on scope. See Pricing for orientation; the briefing makes the frame concrete and transparent.

What if scope grows?

It becomes visible — not silently absorbed. Extensions run as clear change, not a “quick extra round”.

What if we want new features during the build?

The change becomes visible: impact on time and price, approval in the dashboard — not silently absorbed. Acceptance stays fair.

Can we start with unfinished copy?

Yes, with placeholders and a supply plan. Go-live and acceptance depend on agreed criteria, not “copy eventually”.

Next step

Request a website project

Start the briefing in the customer area — next you see scope logic and next steps, not an empty promise.

Scope before buildNext step
Start briefing