Skip to content

How we work

Four ways to work with us.

The right structure depends on how well defined the work is. What does not change is that scope goes in writing first, and you own what you pay for.

Discuss an EngagementRead the FAQ
Engagement models

Pick the shape that fits the problem.

Fixed-scope project

A defined deliverable with an agreed scope, staged timeline and a fixed price. Best when what needs building is well understood before work starts.

Suits

  • A new website or rebuild with clear requirements
  • A security assessment against a defined system
  • A discrete integration or migration

Staged delivery

The work is split into stages that are scoped, priced and approved one at a time. Each stage ends with something usable, and direction can change between them without renegotiating everything.

Suits

  • Platforms where later requirements depend on earlier findings
  • Budgets released in tranches
  • Projects where the shape is clear but the detail is not

Ongoing retainer

A recurring arrangement covering maintenance, monitoring, security updates and a block of improvement time each month. Cancellable, with your infrastructure remaining in your own accounts.

Suits

  • Live sites that need to stay current and monitored
  • Teams without in-house engineering capacity
  • Businesses wanting continuous small improvements rather than periodic rebuilds

Consulting and review

Short, focused engagements: a technical review of an existing system, a second opinion on an architecture, or an assessment of a proposal from another supplier.

Suits

  • Deciding whether to build, buy or rebuild
  • Due diligence on an existing codebase
  • Getting an independent read before committing budget
Principles

The parts that do not vary.

These apply whichever model an engagement uses.

  • Scope in writing before work starts

    Every engagement begins with a written scope covering what is included, what is explicitly not, and what happens if requirements change. Surprises belong in the proposal, not the invoice.

  • You own everything

    Code, domains, hosting and analytics are yours, set up in your accounts or transferred at handover. Leaving should always be possible; we would rather you stay because the work is good.

  • No estimates presented as certainties

    Timelines are given as stages with dependencies made explicit. Where something genuinely cannot be estimated until earlier work is done, we say that rather than inventing a date.

  • Findings reported honestly

    If a rebuild is not warranted, or a feature will not earn its cost, we say so. Recommending unnecessary work is a short-term trade against a long-term relationship.

What about price?

Quoted per engagement, not from a rate card.

Published price tiers tend to be either meaningless or misleading, because the same brief can differ several-fold in real effort depending on integrations, content readiness and how much of the existing system has to be untangled first. What we can commit to is how the number is arrived at:

  • A written scope before any figure is discussed
  • Stage-by-stage breakdown, so you can see what each part costs
  • Explicit exclusions, so nothing arrives later as an extra
  • A stated process for handling changes in scope mid-project
  • No charge for the initial scoping conversation
  • No obligation attached to receiving a proposal

Describe the work and we will propose a structure.

Tell us what needs building or securing, and what your constraints are. We will come back with an approach and an honest view of what it involves.

Start a ConversationExplore Services