Oxford Crown
Live in 14 days, then 28 days of optimisation

Seven steps. You know what exists at the end of each one.

Nothing is built until you have signed off the map, and nothing is called finished until it has been proven against your real systems in the live path. Here is who does what, and what you are holding when each step closes.

Start with step oneSee the seven steps

14days

From onboarding to a system running in the live path, not a demonstration of one.

28days

Of optimisation after go live, included, running alongside the money back guarantee.

2hours

Roughly what the first week asks of you in total. After that you are reviewing, not working.

At a glance

The whole delivery, on one page.

Every step has an owner and an artefact. If a step has not produced its artefact, it is not finished, whatever the calendar says.

StepWhenWhat you doWhat exists at the end
01 Discovery and AlignmentDay 1Bring the person who owns the process now, and whatever numbers you already have on it.A written scope, one named success measure, and the list of access we need.
02 Workflow MappingDays 2 to 3Read the map and sign it off, or tell us where it is wrong. Nothing is built until you do.A signed workflow map and a written acceptance test.
03 System IntegrationDays 3 to 6Grant access on your own accounts, so ownership never leaves your side of the table.A working connection to every system in scope, on accounts you hold.
04 Prompt Architecture and TrainingDays 5 to 9Hand over the templates, the price list and the awkward cases you would give a new starter.A trained system, with a written record of what it may and may not do.
05 Testing and RefinementDays 9 to 12Review a sample and tell us what a good answer looks like in your business.A test log against the acceptance test, with every failure closed out.
06 Launch and OptimiseDays 13 to 14, then 28 daysWatch the first day with us and tell us what to tighten.A live system, the documentation, and the 28 day guarantee running.
07 Growth and SupportOngoing, optionalDecide whether you want the plan at all. It is never a condition of the build.A monthly report, and a system that keeps up with the business around it.

The process

Step by step, with the split of work made explicit.

Most delivery goes wrong at the handover points, so this page names them. What our team does, what you do, and what is produced.

  1. 01

    Discovery and Alignment

    Day 1

    We start with an onboarding call. We confirm the scope of the project, agree what success looks like in numbers, list the tools you will need access to, and collect the credentials required to build. You leave the call knowing exactly what is being built and when it lands.

    What our team does

    Run the onboarding call, ask what the process costs you today, and write the scope down.

    What you do

    Bring the person who owns the process now, and whatever numbers you already have on it.

    What exists at the end

    A written scope, one named success measure, and the list of access we need.

    Your first live version is delivered within 14 days.

  2. 02

    Workflow Mapping

    Days 2 to 3

    We map the process as it runs today, then as it will run once automated. That map covers the tools you already use, the data that moves between them, the decisions the system is allowed to make on its own, and the points where a human stays in the loop.

    What our team does

    Map the process as it runs today and as it will run automated, including which decisions the system may take on its own.

    What you do

    Read the map and sign it off, or tell us where it is wrong. Nothing is built until you do.

    What exists at the end

    A signed workflow map and a written acceptance test.

    Nothing is built until you have signed off the map.

  3. 03

    System Integration

    Days 3 to 6

    We connect your tools and stand up the infrastructure behind the agent. Accounts are authenticated, interfaces are wired, and where a system has no interface to connect to, we bridge it another way rather than telling you it cannot be done.

    What our team does

    Authenticate the accounts, wire the interfaces, and bridge anything that has no interface to connect to.

    What you do

    Grant access on your own accounts, so ownership never leaves your side of the table.

    What exists at the end

    A working connection to every system in scope, on accounts you hold.

    Built on your accounts, under your ownership, from day one.

  4. 04

    Prompt Architecture and Training

    Days 5 to 9

    We teach the system to behave the way your business does. Its role, its tone, what it is allowed to say, what it must escalate, and how it handles the awkward cases. Where you operate in more than one market, that is designed in from the start rather than bolted on afterwards.

    What our team does

    Teach the system your role, your tone, its limits and its escalation rules, from your own documents.

    What you do

    Hand over the templates, the price list and the awkward cases you would give a new starter.

    What exists at the end

    A trained system, with a written record of what it may and may not do.

    Trained on your documents, your templates and your tone of voice.

  5. 05

    Testing and Refinement

    Days 9 to 12

    Before anything goes near a customer, we run it end to end against the real systems, not a simulation. We test the failure cases as hard as the happy path, review the outputs line by line, and fix what the testing exposes.

    What our team does

    Run it end to end against your real systems, test the failure cases as hard as the happy path, and review the output line by line.

    What you do

    Review a sample and tell us what a good answer looks like in your business.

    What exists at the end

    A test log against the acceptance test, with every failure closed out.

    Nothing is called finished until it has been proven in the live path.

  6. 06

    Launch and Optimise

    Days 13 to 14, then 28 days

    Your system goes live within 14 days of onboarding. You then enter a 28 day optimisation window where we tune the responses, tighten the edge cases and extend what the system handles, at no additional cost.

    What our team does

    Move it into the live path behind an explicit switch, then tune it while you watch it work.

    What you do

    Watch the first day with us and tell us what to tighten.

    What exists at the end

    A live system, the documentation, and the 28 day guarantee running.

    28 days of refinement included, plus the money back guarantee.

  7. 07

    Growth and Support

    Ongoing, optional

    Once the first system is producing consistent value, you can move onto an optional monthly plan covering monitoring, updates, new agent builds and continuous improvement as the business changes around it.

    What our team does

    Monitor, fix, update as your tools change, and report monthly on what the agents handled.

    What you do

    Decide whether you want the plan at all. It is never a condition of the build.

    What exists at the end

    A monthly report, and a system that keeps up with the business around it.

    Optional, cancellable, and never a condition of the build.

Twenty things we can build for you

AI ReceptionistsLead Response AgentsAutomated Sales SystemsProposal GeneratorsInvoice Data ExtractionLegacy System BridgesPrivate On-Premise AIBooking and Diary AgentsReactivation CampaignsCustomer Research EnginesQuotation PlatformsReporting PipelinesDocument ProcessingInternal Knowledge AssistantsOnboarding AutomationReconciliation EnginesEnquiry Triage SystemsFollow-up SequencersContract Review ToolingOperations Dashboards

The two lists that matter

What we ask of you, and what we will not do to your business.

A build stalls for one of two reasons: access that never arrived, or a system that was switched live before it was ready. Both are handled by naming them up front.

What we need from you

  • One person who owns the process today and can answer questions about it
  • Access granted on your own accounts, so ownership never leaves you
  • The documents the system should learn from, including your templates and price list
  • Around fifty real examples where documents are involved, including the messy ones
  • Sign off on the workflow map, which is the gate the build waits behind
  • One hour on the first day, and roughly one more across the rest of week one

What we will not do

  • Put a system in front of your customers before it has been proven in the live path
  • Call something finished when it has been built but not tested end to end
  • Turn on full automation where you asked for a draft and an approval step
  • Hold your systems on our platform, or anywhere you cannot take them back
  • Quote an hours saved figure we cannot trace back to a source
  • Start building from a map you have not signed

Our guarantee

We prove Return on Investment

Every build carries a 28 day, no questions asked money back guarantee, starting the day your first system goes live. Inside that window we show you the time the system has actually taken off your team, measured against what the process cost before. If the return is not there, we refund you in full and decommission the system.

28days

We prove Return on Investment, or you do not pay.

  • Live in 14 Days
  • 28 Day Money Back Guarantee
  • You Own Everything We Build

Questions

What clients ask about delivery.

These are the questions that come up between the first call and the signed scope.

What do you actually need from us in the first week?

About two hours in total. One hour on the onboarding call, thirty minutes to read and sign off the workflow map, and thirty minutes to hand over the documents and grant access on your own accounts. After that you are reviewing rather than working.

Is fourteen days realistic, or is that a marketing number?

It is the number we hold ourselves to and it is written into the scope. The two things that push it out are access that has not been granted and a map that has not been signed off, both of which sit on your side. We tell you on day one which of those we are waiting on.

What if we do not agree with the workflow map?

Then nothing is built. The map exists precisely so that disagreement happens on day two rather than day twelve. We redraw it and you sign the version you agree with. The build only starts from a signed map.

Do you work with our IT team?

Where you have one, yes, and they usually want to know three things: where the data goes, what access we hold and how it is revoked. We answer those in writing before integration starts. Where data cannot leave your building, we build so that it does not have to.

What happens after the 28 day optimisation window?

The system keeps running and it is yours. You can take the optional monthly plan for monitoring, fixes and new builds, or take the documentation and run it yourself. Nothing stops working if you decline the plan.

How do you handle a system that fails halfway through a run?

Every build ships with a ledger of what it has already processed, so a rerun never duplicates work, and a rollback plan for anything it wrote. Failures alert rather than pass silently, and each run reports what it did, what it skipped and why.

Day one is a call. Day fourteen is a system running in your business.

A private discovery call, with a fixed written quotation after it whether or not you go ahead. Leadership holding postgraduate degrees from the University of Manchester and the University of Oxford.

Book a discovery callSee what it costs

London, UK. Delivering across the Gulf. Live in 14 days, with a 28 day money back guarantee.