Skip to content

Pricing

How engagements are shaped.

We do not publish package prices, because the same headline service can mean a two-week build or a two-quarter programme. These three levels describe the kind of work involved; the number comes after a short conversation.

  • AI Discovery

    Turn a rough idea into a defined problem and a practical direction.

    Who it's for

    Teams who can feel that something should improve but want it specified before committing budget to a build.

    Typical scope

    • The problem, written down with its business context
    • An honest read on where AI and automation help here
    • A recommended direction and an outline scope
    • A written summary you can act on with or without us
  • AI Build

    Most common

    Design and deliver a defined website, agent, automation or data solution.

    Who it's for

    Teams who already know what needs to exist — a site, an assistant, a WhatsApp flow, an automation or a data product.

    Typical scope

    • The build itself: website, web app, agent or automation
    • Content structure, data model and the integrations around it
    • Testing, deployment and analytics
    • Documentation and a proper handover
  • Custom AI Solution

    For work that spans several systems, datasets and workflows.

    Who it's for

    Teams with a bespoke product, a data platform, or an operational problem that touches many tools at once.

    Typical scope

    • A custom AI or data application
    • Integration across your existing systems and APIs
    • Data pipelines and modelling
    • Continued iteration once it is live

We don't publish fixed prices because scope, integrations and ongoing support vary substantially between projects. You get a written quote before any work starts.

How engagements work

  • Discovery & Consultation

    A short conversation that turns a rough idea into a defined problem, scope and success measure.

    • Problem definition
    • Workflow review
    • Feasibility
    • Recommended approach
  • Custom Project Scope

    An agreed build with a fixed scope, visible milestones and a delivery plan.

    • Solution design
    • Implementation
    • Integrations
    • Handover
  • Ongoing Improvement & Support

    Monitoring, tuning and new workflows once the system is live.

    • Monitoring
    • Model & prompt tuning
    • New workflows
    • Support

How a number is reached

From your problem to a written estimate

Diagram: an engagement moves from problem to scope, a written estimate, a staged build and ongoing support.
  1. Problem

    You describe the situation in plain language.

  2. Scope

    We agree what is in, what is out and what can wait.

  3. Estimate

    A written range with the assumptions behind it.

  4. Build

    Delivered in reviewable stages, not one silent handover.

  5. Support

    Agreed support once it is running in the business.

Not sure which level fits?

Describe what you're trying to build and we'll tell you which one applies.

Start a Project