Skip to content

Workflow automation

Approvals, handovers and reminders that move between people and systems on their own, built to fail loudly, not silently.

What this usually looks like before we start.

  • Zaps and scripts nobody remembers building.
  • Approvals stuck in someone's inbox while the customer waits.
  • Automations that stopped working weeks ago, and nobody noticed.

What we build.

  1. The sequence people actually follow

    We map the real workflow, including the steps that never made it into the process document, before proposing anything.

  2. A named owner at every decision

    The decisions stay with the people who own them. The fetching, copying and chasing between decisions stops.

  3. AI inside the tools you already use

    AI added to your CRM, ERP, email, WhatsApp, Slack or accounting software, with no new platform for your team to adopt.

  4. Exceptions that do not stop the line

    The odd case is routed to a person rather than jamming the queue behind it.

Purchase approval

  1. RaisedSite office
  2. CostedEstimating
  3. ApprovedFinance
  4. OrderedPurchasing
  5. ReceivedStores
  • The sequence people actually follow

    We map the real workflow, including the steps that never made it into the process document, before proposing anything.

    Purchase approval

    1. RaisedSite office
    2. CostedEstimating
    3. ApprovedFinance
    4. OrderedPurchasing
    5. ReceivedStores
  • A named owner at every decision

    The decisions stay with the people who own them. The fetching, copying and chasing between decisions stops.

    Order sync

    Your ERP→Integration→The far end
    • Far end unavailableQueued, 3 retries
    • Partial writeRolled back
    • End of dayReconciled
  • AI inside the tools you already use

    AI added to your CRM, ERP, email, WhatsApp, Slack or accounting software, with no new platform for your team to adopt.

    WhatsApp · customer enquiry

    Can I move my Thursday booking to Friday morning?

    Yes. Friday has 9:30 or 11:00 free. Moving it is free up to 24 hours before.Source: booking policy, section 2

    11:00 please. Also, can I get a refund on the last one?

    Rebooked for Friday 11:00. Refund request handed to the support lead, with the full history.

  • Exceptions that do not stop the line

    The odd case is routed to a person rather than jamming the queue behind it.

    Stock against job JC-0219

    • Kraft liner 120g4,280 kgReserved 1,200
    • Fluting 110g2,940 kgReserved 860
    • Job JC-02193-ply, 12,000On the corrugator

How we work on it

  1. 01Describe the approval that always gets stuck.
  2. 02The real sequence mapped, with the undocumented steps in it.
  3. 03Handoffs removed one at a time, so nobody changes everything at once.
  4. 04Live, measured in days-to-decision rather than in steps automated.
  5. 05We run it and adjust it as the workflow changes.
How we work

Field services

A field service business books in minutes, not days.

Booking confirmations went from two days to under five minutes, with no double-bookings since launch.

An automated booking and confirmation workflow synchronised across every staff calendar, removing double-bookings entirely.

Read the case study
Close-up of a receptionist's hand on a mouse at a polished desk, with a keyboard and a monitor showing a scheduling screen beside it.

Tell us which approval always gets stuck.

Tell us what's hard to run, or what you need built. On the call we work out what's really going on, show where AI fits and where it doesn't, and you leave knowing the next step.

We reply within one business day. If we are not the right fit, we will tell you.