Skip to content
Prompt Consulting
de

Operations map in 10 working days

Your team's marketing work, done by agents you own.

Ten working days to map where the week goes, then six to ten weeks to put agents in production on the software you already run. What you get is something your team uses on Monday, and prompts your own people can edit.

  • Built on your current stack
  • Nothing to migrate
  • Three clients at a time

Month-end close

Example run

running
  1. Pull both ledgers2,418 lines
  2. Match on amount and date2,390 matched
  3. Re-check near misses22 resolved
  4. File exceptions for review6 for a human

Every action logged. Nothing posted without a name against it.

Agents run inside the tools you already pay for

SlackHubSpotSalesforceNotionGoogle WorkspaceMicrosoft 365QuickBooksAirtableJiraXero

The difference

One automation is not a system.

Most AI work stops at a single task. Someone wires a summariser into one inbox, the demo lands well, and the department still runs the way it did the week before.

We take the whole path instead. Intake, decision, handoff, reporting. That is the gap between a team that saves twenty minutes a day and a team that stops doing the work.

  • Slack
  • HubSpot
  • Email
  • Notion
  • Sheets
  • QuickBooks

Agent layer

Runs on your systems, logs every action

  • Work done
  • Audit trail
  • Weekly report

How we work

Ten days to the map. Nothing to migrate.

Every number here is a term of the engagement. You can hold us to all three on day one.

  • 10

    working days from kickoff to the written map

  • 3

    clients we run at one time, by design

  • 0

    systems you have to migrate off to start

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.

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

What the work looks like

Finance close, CRM hygiene, inbox triage.

Three engagements we are set up to run. We have no client numbers to show yet, so each card names the symptom, what gets built, and the measure we would agree with you up front.

Finance operations

What you have
Three people reconcile the same two ledgers every month-end, and the close slips whenever one of them is on holiday.
What gets built
An agent that pulls both ledgers, matches on amount and date, re-checks the near misses, and files only the exceptions for a human to decide.
How we would measure it
Hours spent on close, counted the month before and the month after.

Revenue operations

What you have
The CRM runs a week behind reality, so pipeline review starts with twenty minutes of cleanup and ends with a forecast nobody believes.
What gets built
An agent that reads call recordings and mail threads, updates the records, and flags the deals that have gone quiet before the review, not during it.
How we would measure it
Time from a call ending to the record being correct.

Client service

What you have
Every request arrives as an email and gets triaged by whoever is free, which means priority depends on who opened the inbox.
What gets built
An intake agent that classifies each request, routes it, drafts the first reply, and escalates anything it cannot place with a reason attached.
How we would measure it
First response time, and the share of requests that never need a person.

About

A small firm, on purpose.

Prompt Consulting takes three clients at a time. Three is the number at which the person who writes your map is still the person who ships your agents.

The work is deliberately unglamorous. Read the systems, count the hours, build the boring thing that removes them, then hand it over properly so it survives us leaving.

Thilo Krause, founder of Prompt Consulting

Thilo KrauseFounder

Writes the maps, ships the builds, and answers the phone during the ninety days. Prompt Consulting is operated by dionics media UG (haftungsbeschränkt) in Burgdorf, Germany.

  • Three clients at a time

    Enough attention that we learn your stack as well as your team knows it, and few enough engagements that yours never waits behind another.

  • The advisor builds it

    No handoff from a consultant to a delivery team who were not in the interviews. The person who wrote the map writes the agents.

  • Ninety days of support, written in

    Ninety days of support is in the build price. We are around while your team learns to change things without asking.

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.

  • Built on your current stack
  • Nothing to migrate
  • Three clients at a time

Analytics

We would like to count visits with Google Analytics, which loads only if you accept. Either way we store one entry in your browser so this does not ask again. Nothing else is written to your device.

What we collect, in full