Free · 60 s Free AI-readiness audit See your site the way ChatGPT does.
Personal reply within one business day.

Engine room · 30-day sprint

AI Agents & Automation Sprint

In 30 days I take one to three workflows your senior people repeat every week and turn them into AI agents that research, draft and route the work, with a human approving anything that matters.

from €7,500 · $8,300 30 days

Typical project €7.5k–15k. Fixed price per sprint.

Proof on file

CLIENT · NAME CHANGED

€100

hard monthly AI budget breaker

Corvane Legal’s engine runs on its own every few minutes, sends a daily approval digest, and stops spending at a hard monthly cap the firm sets.

observed 2026-10-05 · engine config default

03 Fit

Who this is for, and who it isn't.

Built for you if

  • Senior people in your firm spend hours each week researching, drafting, searching and chasing.
  • Leads wait hours, or until tomorrow, for a first reply.
  • Answers to staff questions exist somewhere in old emails, drives and manuals, and nobody can find them.
  • Onboarding a new client takes weeks of questionnaires and reminder emails.

Not for you if

  • You want a chatbot on your homepage for its own sake.
  • The decision legally requires a professional. Agents draft; a qualified person decides, always.
  • There’s no settled process yet. Automating chaos produces faster chaos, so we’d map it first.
  • You need a two-step Zapier automation. Do that yourself and keep the money.

04 The problem

Your best people are doing your most repetitive work.

Look at a week in a senior person’s calendar: researching a lead before the call, answering the same client question again, digging through drives for a document someone wrote two years ago, chasing a client for onboarding details. None of it needs their judgement until the very last step.

That is exactly the shape of work agents are good at: gather, draft, check, route. It’s also why searches for “AI agents for business” grew +210% year on year (Truelogic/DataForSEO, June 2026).

The risk is the opposite failure: an agent that sends, spends or promises something without a person. Every workflow I build has a gate where a human approves, a budget it can’t exceed, and a log of everything it did.

Signs you need this

  • Leads wait until tomorrow for a reply, and some don’t wait.
  • Only one person really knows where anything is.
  • Onboarding a new client takes weeks of emails and reminders.
  • You tried a chatbot once and it made things up.
  • Monthly reports are copy-pasted together by hand.
  • Partners approve things by forwarding emails to each other.

Not sure which workflow to automate first?

Book 20 minutes and bring your busiest week. You leave knowing which workflow I’d start with, whether or not we work together.

06 Where I suggest starting

Three workflows worth building first.

Your sprint can be any workflow the audit ranks highest. These three are where I suggest starting, because the hours are obvious and the risk is easy to gate.

Onboarding

AI client onboarding

A guided, autosaving intake that collects everything a new client engagement needs, lets clients pre-fill it from their own website or documents, and hands your team a complete, structured brief.

  • Autosaves at every step, so nothing is lost
  • Client documents uploaded in the same flow
  • Structured output your team or tools can use
  • Reminders sent for you, approved by you

Speed to lead

Lead pre-briefs and reply drafts

Every new enquiry researched before you open it: who they are, what they need, whether they fit, and a drafted reply for you to edit and send.

  • Research from public sources, cited
  • Fit score against criteria you set
  • Draft reply in your voice, never sent automatically
  • Also: inbox-to-draft, reporting, approval digests

07 What you get

Deliverables, tagged by the layer they fix.

Every workflow goes into production on your accounts, not a demo on mine.

  • Workflow audit

    Your repetitive work mapped and ranked by hours saved, risk and data access, before anything is built.

    Layer: Engine room
  • One to three production workflows

    Running on live work by day 30, chosen by you from the audit.

    Layer: Engine room
  • Human approval gates

    Anything that sends, spends, publishes or promises waits for a named person.

    Layer: Engine room
  • Spend caps

    A hard monthly budget per workflow. When it’s reached, the agent stops; it doesn’t overspend.

    Layer: Engine room
  • Logs of every run

    Input, output, cost and who approved, kept where you can search them.

    Layer: Engine room
  • Tests on real examples

    Automated tests against captured real cases, so a model update can’t quietly change behaviour.

    Layer: Engine room
  • Optional MCP access

    Internal data exposed to your team’s AI assistants through scoped, logged tools.

    Layer: Found
  • Runbook and handover

    How each workflow works, what to do when it fails, and how to switch it off.

    Layer: All layers

08 How it runs

Thirty days, from audit to running on live work.

Fixed price, fixed timeline. You choose what gets built and where the human gates sit; the agents never get to decide that.

Agents at work Human gate: nothing moves on until a person approves

  1. Step 1: Days 1–5

    Workflow audit

    Interviews and a look at the real inboxes, drives and tools. Each candidate workflow scored on hours saved, risk and data access.

    • agent://researcher
    • agent://architect

    Human gate You choose which workflows get built.

  2. Step 2: Days 6–10

    Design

    For each workflow: triggers, data sources, the agent’s job, what it is never allowed to do, where the human gate sits, and its budget cap.

    • agent://architect

    Human gate You approve the design and the “never allowed” list.

  3. Step 3: Days 11–22

    Build and test

    Built on your accounts and tested against real captured examples. A working demo every week.

    • agent://builder
    • agent://tester
  4. Step 4: Days 23–27

    Pilot

    Running on live work with every output approved by your team. Prompts tuned on their feedback.

    • agent://watcher

    Human gate Your team approves every output during the pilot.

  5. Step 5: Days 28–30

    Handover

    Runbook, recorded walkthrough and an access review.

    Human gate You decide which gates stay manual for good.

09 Proof

Agents with limits, already running in production.

The pattern is the same everywhere: agents do the work, a person approves what matters, and a budget guard stops anything from running away.

CLIENT · NAME CHANGED

5 min heartbeat

Corvane Legal: digest + research agent

A daily approval digest with one-click links, an inbound-email research agent that turns names into drafted articles, 649 automated tests and a €100 monthly breaker.

  • Agents
  • Approval digest
~€33/mo✓ AI spend (throttled to 15 rewrites/day) observed 2026-10-05 · configured throttle
649✓ automated tests observed 2026-10-05 · test suite count
4✓ AI providers (Claude, GPT, Gemini, Grok) observed 2026-10-05 · codebase

And Cuckoo, my own distribution engine in pilot: agents draft a week of posts, clients approve each one from a phone.

10 Price

What moves the price, and what it costs to run.

Starts at €7,500 · $8,300 per sprint; most land at €7.5k–15k. Fixed price per sprint.

Costs more when

  • Workflows that touch many systems.
  • Sensitive data that needs stricter access control and audit trails.
  • A third workflow in the same sprint.
  • A custom interface instead of email, Slack or Teams.

Costs less when

  • Data already in one place (Google Workspace, Microsoft 365 or a CRM).
  • Approvals by email or chat rather than a new app.
  • One workflow done properly first.
  • A named person on your side with time for the pilot.

Monthly running costs

Paid by you, directly to each provider, in your own accounts. I add no markup and no hosting fee.

WhatHow it worksPaid to
AI model usageBilled by the provider in your account, capped per workflow by a hard monthly budget.Anthropic / OpenAI
Hosting and schedulesCloudflare Workers, queues and cron. Small volumes fit Cloudflare’s free plan; Workers Paid is budgeted when volume or CPU needs it.Cloudflare
Your existing toolsAgents work inside the email, drive and CRM you already pay for. No new subscriptions unless we agree one.Nobody new

Every workflow has a written “never allowed” list and a spend cap. Both are in the runbook, and only you can change them.

11 Handover

What you own when we're done.

  • Code, prompts and tests your GitHub organisation
  • Workers, queues, databases and secrets your Cloudflare account
  • AI provider accounts and API keys in your name
  • Logs of every run your database
  • Runbook and “never allowed” list docs/ in your repo
  • Recorded walkthrough shared drive

No licence fees to me, no lock-in, no proprietary platform. If I disappeared tomorrow, any competent developer could pick it up from the runbook.

12 Questions

Straight answers to fair questions.

Is our data used to train AI models?

The workflows run through the providers’ business APIs under your own accounts, where your settings decide how data is used. The major providers’ API terms don’t train on business data by default; I’ll show you where to check and set it.

How is this different from Zapier, Make or n8n?

Those tools move data between apps by fixed rules, and they’re great at it. An agent reads, judges and drafts. I use both: deterministic steps wherever rules are enough, and a model only where judgement is needed. If a Zapier zap solves it, I’ll tell you.

What happens when an agent gets something wrong?

It hits a gate before it can matter: a person approves anything that leaves the building. Every run is logged, so mistakes are visible and traceable, and the tests built from real examples catch regressions before they reach your team.

What exactly is an internal knowledge agent?

A private assistant your staff can ask questions in plain language, answered from your own documents, manuals, contracts and past emails, with the source linked under every answer. Access follows your existing permissions. Optionally, your team’s AI assistants can query it through MCP.

Does it work with Microsoft 365, Google Workspace or our CRM?

Usually, yes, through their official APIs. The workflow audit checks access in week one, before anything is promised.

What happens after the 30 days?

You run the workflows yourself with the runbook, start a second sprint, or keep me on through the AI Department for monitoring, tuning and new requests.

Rather talk it through first?

20 minutes with me, not a sales rep. You leave with a clear next step — whether or not we work together.