Solution

Too much still happens by hand.

We map the routine work between your tools, automate what repeats, and keep a person on every decision that needs judgement.

The problem

What usually goes wrong

Every enquiry is retyped, forwarded and followed up by hand. The work is predictable, and still eats hours every week.

You may recognise

  • Copy-paste between the site, email and the CRM
  • Follow-ups forgotten
  • Weekly reports built by hand

Why it happens

How it gets this way

  • Tools bought one at a time

    Each solves its own problem. None was chosen to talk to the others, so people carry the data between them.

  • The process lives in someone’s head

    Steps that are never written down cannot be delegated, let alone automated.

  • Exceptions block everything

    When a process can’t handle the unusual case, the whole thing stays manual.

Often overlooked

Automate the routine, not the judgement.

The best candidates are repetitive, rule-based and frequent: copying an enquiry into the CRM, sending the confirmation, preparing the weekly report. Decisions about money, risk or a customer’s exception still go to a person, with the context already gathered.

Every automation also needs an owner, a log and an off switch. Without them it fails silently.

Before you decide

Five questions to answer before anyone builds

A page of notes is enough. It is also the brief.

  1. Which tasks are done the same way every week?

    List them with how often they happen and roughly how long they take.

  2. Where is the same information typed twice?

    Each retyping is a place for errors, and a candidate for a connection.

  3. Where do handoffs stall?

    A form that waits for someone to forward it; a follow-up that depends on memory.

  4. Which steps need judgement?

    Mark them. They stay with a person; the rest can be prepared for them.

  5. Do your tools offer an API or an export?

    It decides what can be connected directly, and what needs a workaround.

The system

How the pieces connect

  1. Receive

    Forms, calls and bookings arrive in one format.

  2. Route

    To the right tool and person.

  3. Act

    Follow-ups, updates, reports.

  4. Hand off

    Anything unclear to a person, with context.

  5. Log

    Every run, readable.

In this offer

What is included, and what is not

Included

  • The workflow written down step by step, and the code that runs it
  • A log of every run your team can read
  • A notification or a review queue for the exceptions
  • A switch that stops any automated step without stopping the site
  • Handover notes your developers can maintain

Not included

  • Steps that send, pay or delete on their own in a first version: they wait for a person
  • Replacing an ERP or running a data platform: we build the smaller connections around them
  • A track record: we have not shipped an automation for a client yet, so a first project is a small pilot with a fixed scope

Status

What runs today, and what waits for access

Live means it runs now. Integration-ready means the code, the data model and the tests exist and it starts once your account or a platform approval is connected. Planned means not running yet: designed, or built and tested but not yet connected to a live endpoint.

Integration-ready 2

1

Evidence

What you can check today

The routine behind this site’s own forms runs this way. The AI step is a Lab design, and labelled as one.

  • Running on this site

    The enquiry pipeline behind these forms

    Every submission is checked on the server, given a score with readable reasons and delivered to one destination, with a spam trap and no retyping.

  • Lab, not client work

    Lead intake with an AI step

    A design where an AI step sorts free-text requests, and anything below a confidence line goes to a person.

Two ways forward

Map it first, then automate what repeats

Talk about your project

Describe the routine in a few lines, in a short enquiry. We reply in writing with how we would map it, what could be automated and what stays with a person.

Map our manual process

Fit

When to call us, and when not to

Worth a conversation if

  • A routine you can describe step by step

Probably not if

  • A process that changes every week

FAQ

Questions people ask about this

All questions

Do you build AI agents?

Yes, inside systems with clear limits. The AI receptionist answers calls from information you approve, review replies and content are drafted for a person to approve, and in automation a language model handles the steps that need judgement while a person reviews what it is unsure about.

None of it has run for a client yet, and we say so. A first project is a small pilot with a fixed scope.

Who owns the code and designs?

You do, once the project is paid for, as the contract sets out. Open-source libraries keep their own licences, which we list at handover.

Which routine eats your week?

Tell us what you need and by when. We read every enquiry and reply in writing, with questions, a next step, or a plain no if we’re the wrong studio.