Skip to content
How it works

From a real job.
To your team’s system.

We review a recent workflow, agree the first version and put a working build in your team’s hands. Scope, responsibilities and support are decided together.

Tell us where you’re starting ↗
  1. 01

    Look at a recent job.

    We can start with a recent job, an idea for an AI tool, or a gap in your current software. Show the steps and the moments that need a person’s judgement.

  2. 02

    Agree what we’re building.

    We agree what the first version should do, who uses it, what data it needs and how it fits your current tools. Cost, schedule and responsibilities follow that scope.

  3. 03

    Let your team try it.

    A working version gives the team something to try. We review the normal workflow, the exceptions and what happens when information is missing.

  4. 04

    Get ready to use it.

    Before the workspace becomes part of the working day, we agree access, data preparation, team guidance, hosting and ongoing care.

Questions before a build

Understand the commitment.

A custom workspace has to fit the people using it and the tools around it. These are part of the conversation from the start.

How much does a build cost?

We work through the workflow and the tools involved, then propose a price for an agreed first version. The proposal should make the build cost, any ongoing care and third-party charges clear before you commit.

How long will it take?

The schedule depends on the first version we agree to build and what it relies on. We identify review points, client responsibilities and external dependencies in the proposal.

Can we keep our current tools?

We assess what to keep, connect or replace. A connection depends on the tool’s available access and the data involved. We check that before committing to it.

What about our data and team training?

We agree the data to move, who prepares it and how we check the import. We also agree how your team will learn the workflow and what guidance they receive at handover.

What if the workflow changes later?

We discuss the change, the impact on the existing workspace and whether it belongs in ongoing care or a separate piece of work.

YOUR NEXT BUILD

Show us where the work gets stuck.

A recent example is enough to start. We can work out the shape of the build together.

Prepare a brief