Skip to content
Prompt Consulting
de

Services

You can stop after the map.

Some teams need one process fixed and no agents at all. The map says which, and stopping there costs you nothing further.

The three services

01

Operations map

Find where the hours go

Ten working days of interviews and system access, and a written map of every recurring workflow in the department with hours and cost against each one.

  • Interviews with the people doing the work, not only their managers
  • Every recurring workflow written down, start to finish
  • Hours and cost attached to each one
  • A build order, with the first agent named and scoped
What this looks like

02

Agent build

Put agents in production

We build the agents the map called for and deploy them on the software you already run. One agent per workflow, with an audit trail on every action.

  • Built on the software you already run
  • One agent per workflow, never one agent for everything
  • An audit trail on every action an agent takes
  • Deployed in your cloud account, or ours, your call
What this looks like

03

Team enablement

Hand it to your team

The prompts, guardrails and training that let your team change an agent's behaviour without calling us. Written into every build, not sold separately.

  • A prompt library your team edits, in files they can read
  • Guardrails that state what an agent may never do
  • Two workshops, recorded, for the people who run it
  • A named contact for the first ninety days
What this looks like

Process

Ten days to a decision. Ten weeks to a working agent.

The same four steps every time. The parts that change are which workflows we touch and how strict the review has to be.

  1. 01

    Interviews

    Days 1 to 4

    Days one to four are interviews. Six to ten conversations, forty minutes each, with read access to the systems the work passes through so we count volumes at the source.

    • Six to ten interviews, recorded with permission
    • Read access to the systems in scope
    • Volumes counted from the source
  2. 02

    The map

    Days 5 to 10

    Every recurring workflow written down with hours and cost against it, then ranked by hours returned against effort to build. The first agent gets specified tightly enough to quote. You read a document, not a deck.

    • One page per workflow
    • Hours and cost, with the method shown
    • A build order you can argue with
  3. 03

    Build and deploy

    6 to 10 weeks

    The first agent gets built on top of your existing systems, then runs in shadow mode until it clears the pass mark you agreed. Once it is live, whatever it cannot place lands in a human queue.

    • Shadow mode before go-live
    • A pass mark agreed in advance
    • Every action logged from the first run
  4. 04

    Handover

    90 days

    Prompts and rules go into your repository in files your team can read and change. Two recorded workshops, a named contact for ninety days, and a weekly thirty-minute review while the numbers settle.

    • Prompt library in your repository
    • Guardrails enforced in code
    • A named contact who answers the phone

Questions

What people ask on the first call.

Next step

Tell us what your team still does by hand.

Thirty minutes on a call. You describe the work that eats the week. We tell you whether an agent can take it and what building it would cost, including when the answer is that it cannot.

Book the scoping call
  • Built on your current stack
  • Nothing to migrate
  • Three clients at a time

Analytics and spam protection

We would like to count visits with Google Analytics, and to load Google's spam check on the contact form. Both load only if you accept. Either way we store one entry in your browser so this does not ask again, and the contact form works the same whichever you press.

What we collect, in full