From first call to live in twelve weeks.

Around twelve weeks from the first call to a branch that is already booking work. We build in stages, so you see progress every week rather than waiting for a single reveal at the end. Simpler builds can move faster; we tell you the realistic date on the first call.

Less than most owners expect. A focused discovery session up front, then short weekly check-ins to review progress and sign off each stage. We write the copy and run the build; you steer and approve. The point of the branch is to take work off your desk, and that starts during the project.

Because you review the design and copy before code, most changes happen while they are cheap to make. Larger scope changes are quoted clearly before we proceed, so nothing lands as a surprise on the invoice.

No. The design is bespoke art direction built to your brand, server-rendered for speed and search. A site that looks like everyone else's cannot pass the three-second test that justifies your price.

We run it. The AI workforce goes live connected to your tools, and we monitor, report, and refine the site and the staff behind it. Copy, layout, and the AI keep sharpening while you get on with the work, so the value compounds instead of fading.

Builds start from £3,500 for the Autonomous Storefront, £6,000 for the Operational Hub, and £10,000 for the Bespoke Transformation, each followed by a managed AI workforce retainer from about £400 to £1,500 a month depending on the tier. Prefer the workforce on its own, plugged into a site you already have? A standalone AI employee runs from about £3,000 to set up plus about £700 a month. Every build is scoped and quoted in writing before work starts. The full breakdown, in your local currency, is on the pricing page.

At three fixed points, and the check is yours at each. Before it handles a live enquiry you approve the scripts and the escalation rules it must work inside. Day to day, a named owner on your team picks up whatever it escalates. Each month we put a written report in front of you covering what it handled and what it passed to a person, and the scripts are corrected from what that shows.

Each build ships with an audit trail, so any enquiry can be opened and read back in full. You can see what came in, what the employee replied, which approved script it was working inside, and the point at which it handed the matter to a person. The monthly report summarises the same record, and the underlying trail stays there for your own inspection.

We handle this as an operating procedure, agreed with you before launch. The employee works only inside scripts you have approved, so what it can say is bounded from the start, and anything sensitive goes to a named person on your team for sign-off before it reaches your client. Where we run a system on your behalf, you remain the data controller and we act as your processor under a data processing agreement. A mistake surfaces in the audit trail, we correct the script, and you re-approve it before it runs again.

A named person on your team, chosen during scoping and written into the build. That person sets what the employee may decide alone and what it must escalate, and every escalation it raises lands with them. We stay accountable for the employee itself, including how it runs and how it is corrected, so your owner directs the work while we keep the worker in good order.

Against two fixed checkpoints and one running record. At week six there is a written adoption check that asks whether the workflow you hired the employee for has actually changed. Ninety-day usage telemetry then shows whether your team is genuinely using it. In between, the monthly report tells you what the employee handled and what it passed to a person.

The week-six adoption check exists for exactly that. It is a written checkpoint that asks whether the workflow has changed, and if your team will not use what we built, the walk-away clause applies and we stop. The ninety-day usage telemetry backs it, so the answer rests on what the telemetry shows. Resistance is usually a sign the employee was scoped to a job nobody owned, which is why each one is given a named owner at the outset. What the working relationship looks like beyond the twelve weeks is set out in working with AI employees.