How pricing works

How pricing works: clear scope first, then a clear quote.

Website development cost depends on the work behind the interface: templates, commerce rules, integrations, content and testing. A scoped review helps separate essential work from optional additions before a written quote. Assumptions, exclusions and proposed changes should be visible, so the agreed scope explains what the quote covers.

  • Scope before commitment
  • Visible assumptions
  • Written options
Illustrative cost levers: scope, integrations, custom features, design and timeline. No price is implied.

What affects cost

What the build needs to do matters more than its label.

  • Scope and templates

    A page count does not tell the whole story. Several pages may share one template, while a single product configurator can contain many states.

    What makes it smaller: Reusable layouts and a clear content model.

    What makes it bigger: Distinct templates, permissions and interaction states.

  • Platform and architecture

    A theme and a separate storefront carry different responsibilities. The publishing workflow and maintenance capacity should inform that choice.

    What makes it smaller: A supported platform that already meets the workflow.

    What makes it bigger: Separate application, CMS and commerce boundaries.

  • Custom commerce features

    Quotation, subscriptions, personalisation and bundles change more than a product page. Each needs a defined relationship with cart, checkout and order handling.

    What makes it smaller: A narrow rule with established platform support.

    What makes it bigger: Interacting rules, exceptions and custom admin controls.

  • Integrations

    Payments, couriers, CRM and inventory services have their own APIs and failure modes. Mapping ownership and retry behaviour is part of the scope.

    What makes it smaller: A documented connection with a clear data owner.

    What makes it bigger: Multiple systems, reconciliation and background processing.

  • Design inputs

    Provided designs still need responsive and interaction decisions. Where design is also needed, the review and approval work belongs in the scope.

    What makes it smaller: Approved layouts with mobile and error states.

    What makes it bigger: Discovery, interface design and repeated revisions.

  • Content and migration

    Moving content can involve structure, relationships and redirects. Product variants and historical data need particular care before a migration approach is selected.

    What makes it smaller: Prepared content in a consistent format.

    What makes it bigger: Cleanup, transformation and legacy URL mapping.

  • Performance and SEO

    The target journeys and measurement method need to be agreed. Existing infrastructure and third-party scripts can affect what an implementation can change.

    What makes it smaller: A focused issue with reproducible evidence.

    What makes it bigger: Cross-platform investigation and broader remediation.

  • Timeline and urgency

    Scheduling constraints affect sequencing and the options available. An urgent request still needs review; a deadline does not remove technical dependencies.

    What makes it smaller: Flexible sequencing and prompt decisions.

    What makes it bigger: Coordinated releases and unresolved external dependencies.

  • Testing and handover

    Browser checks, commerce flows and deployment preparation take deliberate work. The quote should say which critical paths and ownership tasks are included.

    What makes it smaller: Clearly bounded flows and available test access.

    What makes it bigger: Many roles, devices, integrations and operational scenarios.

  • Continuing support

    Launch preparation and ongoing ownership are different activities. Any monitoring, maintenance or enhancement work needs an explicit scope rather than an assumption.

    What makes it smaller: A defined handover with known responsibilities.

    What makes it bigger: Continuing operational involvement and evolving features.

Typical project types

Different boundaries, different work.

Audit or targeted fix

Usually includes: Reproduce the issue, review the affected path and define the next change.

Gets bigger with: Intermittent behaviour, missing access or unclear causes.

Explore the service

Site or theme build

Usually includes: Templates, content structure and responsive implementation in WordPress or Shopify.

Gets bigger with: Unprepared content, custom interactions and migration.

Explore the service

Custom store or commerce logic

Usually includes: Product and buying journeys with agreed custom behaviour.

Gets bigger with: Subscriptions, complex offers and separate storefront responsibilities.

Explore the service

Plugin or integration

Usually includes: A focused connection or capability with validation and failure handling.

Gets bigger with: Multiple systems, custom administration and data reconciliation.

Explore the service

Ongoing support and ownership

Usually includes: An agreed boundary for maintaining and improving an existing system.

Gets bigger with: More platforms, release coordination and additional operational responsibility.

Explore the service

How a quote is prepared

Make the assumptions visible before agreeing the work.

  1. Brief or free audit

    Share the current constraint, intended outcome and existing platform.

  2. Review and questions

    Clarify dependencies, access, content and important edge cases.

  3. Scope with options

    Separate essential work, optional additions and unresolved assumptions.

  4. Written quote

    Record the proposed work, exclusions and the basis for approving changes.

  5. Kickoff and milestones

    Confirm the delivery checkpoints and responsibilities before work begins; specific arrangements need owner approval.

What is usually separate

These draft categories need confirmation in the actual proposal. A listed item is a question to resolve, not an additional charge being imposed here.

  • Hosting and domain registration
  • Premium plugin and app licences
  • Third-party service charges
  • Content creation and licensed assets
  • Ongoing maintenance after launch

Ways to work together

Project review

Investigate the constraint before choosing an implementation.

Build

Deliver a defined CMS, commerce or integration scope.

Ongoing ownership

Agree who maintains and develops the system after handover.

Try the scope guide

Explore dependencies and prepare a clearer brief. This tool estimates scope, not a commercial figure.

Use this tool in your browser.

Questions before a quote

Do you offer fixed prices?

A defined scope can support a written project quote. The engagement models and any published ranges still need owner confirmation; this page does not publish a universal package.

Explore the scope first
What do you need to give me a quote?

The business goal, platform, important journeys and existing constraints are a useful starting point. Designs, content, integration documentation and access requirements help distinguish known work from questions that need investigation.

Start with a review
Can you work with a small budget?

A focused improvement may be more appropriate than rebuilding everything. Describe the constraint and priorities so the options can be discussed; this is not a promise that every request can fit a particular budget.

Discuss the priorities
What if my scope changes?

A new requirement should be compared with the agreed work before implementation. Its effect on effort, dependencies and delivery planning should be written down and approved rather than assumed.

Read the quote process
Are there hidden costs?

The proposal should identify what is included and what is separate. Hosting, licences and service charges need to be checked explicitly; the draft exclusions below are a discussion guide rather than contractual terms.

Review separate items
Do I own the code?

Ownership and licence terms belong in the project agreement. The handover should distinguish custom work, platform licences and third-party dependencies, alongside deployment access and continuing responsibilities.

Read about review and ownership
What happens after launch?

A handover should explain the release and the responsibilities that continue afterward. Maintenance, monitoring and future changes need an agreed scope; no ongoing service or payment term is implied here.

Explore the service areas
Can I start with a free audit?

Yes, the audit page offers a written review and recommendations without an obligation to commission development. It can help identify the next question before a larger scope is discussed.

Request a free audit

Start with the question that needs answering.

A review or a brief can help define the next step.

Get a free auditStart a project