Chapter 4 of 5

Fix it with AI agents.

We rebuild one workflow at a time, inside the systems you already use, with the people who will run it. The person who approves always makes the final call.

Start with an auditNext: Work with us

Step 5: Fix what holds growth back. Then let AI speed up what is already clear.

Once we know where work waits, we fix that first. Then AI speeds up the work that is already clear. Your people keep the judgment and the relationships.

  1. Demand engineLeads wait days for a replyEvery lead followed up within minutes
  2. Relationship engineQuiet accounts noticed too lateOne customer-health view, with early alerts
  3. Operations engineThe same data typed in three placesOne data flow instead of retyping

How a build happens.

Each step depends on the one before, so we do them in order.

  1. Connect your systems

    Link every system the workflow touches, and find where the numbers don’t match.

  2. Agree what each number means

    Write down what “booked” or “won” means, and who decides.

  3. Keep it in your accounts

    Logins, passwords and records stay in your accounts, under your control.

  4. Run it with AI agents

    The AI agent prepares the work and a person approves it. Each week, a short report on what was learned.

  5. Hand it over

    The people who run the workflow helped shape it. They run it day to day; we step back to support.

How much the agent does

Agents earn trust one step at a time.

An AI agent gets more responsibility only after it has been right at the step below. Routine work moves on; unusual cases wait for a person.

  1. Level 1 of 5

    On request

    You ask. The agent reads and drafts. Nothing happens unless asked.

    Still with a personEvery action
  2. Level 2 of 5

    Daily checks

    The agent checks the work every day and flags what changed.

    Still with a personEvery change it flags
  3. Level 3 of 5

    Checked against your team

    On real cases, its drafts match what your people decide.

    Still with a personEvery decision, checked against its draft
  4. Level 4 of 5

    Approve in batches

    Routine work arrives ready, and the approver signs off on several at once.

    Still with a personA sign-off on each batch
  5. Level 5 of 5

    Runs on its own, within set limits

    Proven routine work runs by itself. Unusual cases, pricing and spend still go to a person.

    Still with a personUnusual cases, pricing and spend

The agent prepares. The approver decides.

An AI agent builds the quote from your pricing rules and the account history. Everything inside the rules goes straight through. The one line outside them waits for the person who approves, with the details already attached.

Illustration of a pricing approval. Not a client result.

Quote draftRenewal · prepared by agent
  1. Platform licence120 seats, three-year termList price
  2. OnboardingStandard scopeWithin the rules
  3. SupportPriority tierWithin the rules
  4. Multi-year discount18%Above the 12% limit

Waiting for the sales director to approve. Three lines done, one decision left.

Three rules that never change.

Scroll, and watch each one play out.

  1. Nothing is posted before a person decides

    The agent prepares the work and the evidence. Your team approves, corrects or holds it, and every action is logged with the person responsible.

  2. When unsure, it stops

    If the agent isn’t sure, it asks a person before changing your records.

  3. Money decisions stay with people

    Pricing and spending always need a person’s approval.

Your team owns everything we build.

Everything is written down and runs in your own accounts, so your team can use it, check it and build on it.

  • Rulebook

    A plain-English rulebook

    1. Rule 1Nothing is posted before a person decides.
    2. Rule 2When unsure, stop and ask a person.
    3. Rule 3Pricing and spending need a person’s approval.
  • Runbook

    Documentation and a runbook

    If the nightly sync fails

    1. Check the error log
    2. Re-run the sync
    3. Still failing? Tell the owner
  • Code

    The code, tested and documented

    • The agent’s instructions
    • Your rules, in one file
    • Tested on 12 of your real cases
    • A how-to guide for your team
  • History

    Project history and decisions

    1. Week 2Scope and result agreed
    2. Week 6Approval limit set with the director
    3. Week 12Handed over to your owner

Step 6: Make each fix easier than the last. Each sprint starts further ahead.

With the rules written down and an owner in place, every new workflow starts further ahead. Customers who adopt, stay and buy more become advocates who bring in the next ones.

  1. First sprintBuilds the first workflow
  2. Second sprintStarts from what is already in place
  3. Third sprintStarts from what is already in place
  • Already in place: the rules, the data, the owner
  • New work this sprint
Next chapter, 5 of 5Work with us.What to expect, from first call to handover, and who you’ll work with.Continue the story