DIAGNOSTIC · 2 WEEKS · FIXED FEE
An AI readiness assessment that shows exactly what to automate first.
A senior engineer reviews your team's workflows, identifies the highest-ROI automation candidates, and gives you a written roadmap with the strongest candidate designed in full. Two weeks. One flat fee. No surprises.
WHAT IT IS
A diagnostic, not a discovery process.
Traditional consulting "discovery" is a multi-week process of workshops, stakeholder interviews, and steering committee reviews that produces a slide deck. The deck recommends further discovery. Nothing ships. The bill arrives before the work begins.
The AI Workflow Audit is different. It's structured around a concrete deliverable: focused interviews, documented workflow mapping, and a written report delivered in 14 days. Every hour of engagement time is pointed at producing something useful, not billable conversation.
The output is concrete: a prioritized list of automation candidates with effort estimates (S/M/L), expected ROI ranges, dependency notes, and high-level architecture sketches for the top two or three candidates. The strongest of them goes further, to a storyboard and mockup detailed enough to build from. Something your team can act on immediately — whether that's internal implementation or a follow-on Sprint with me.
New to the category? Start with the AI workflow automation guide.
WHO IT'S FOR
Teams that want a plan before they commit budget.
Right fit if…
- You know AI should help but aren't sure where to start
- Your team has tried ChatGPT but nothing has shipped
- You want a senior outside opinion before committing to a build
- You're tired of consultancy decks that don't become code
Probably not a fit if…
- You already know exactly what to build (skip to Automation Sprint)
- You need someone to do the work for you ongoing (I hand off, I don't operate)
- You're looking for the cheapest possible option (this is premium boutique work)
- Nobody who runs the workflow can be freed for half a day (the design session needs them in the room)
WHAT'S INCLUDED
Seven concrete deliverables.
Stakeholder interviews
4–6 focused 45-minute calls with operators, leads, and decision-makers across the teams that do the most repetitive work.
Workflow mapping
Documented current-state diagrams of your top 5 workflows — inputs, outputs, steps, decision points, and where time actually goes.
Automation candidate list
Prioritized by ROI, with effort estimates (S/M/L), expected time saved per week, and dependency notes for each candidate.
Architecture sketches
High-level system diagrams for the top 2–3 automation candidates — data flow, integration points, LLM usage, and operational approach.
Design session and storyboard
Half a day with the people who run the workflow, worked through a fixed sequence of steps that ends in a design rather than a discussion. The storyboard is the artefact: frame by frame, what a person sees, what they do, what the system does, and what happens next. It reads as the scope for a build, whoever ends up doing the building.
Risk and governance notes
Data handling requirements, security considerations, vendor dependencies, and compliance flags relevant to each automation candidate.
Written report
A 15–25 page PDF covering findings, recommendations, and roadmap — written for both technical and business readers, not just the engineering team.
PROCESS
Two weeks, end to end.
Days 1–2
Kickoff & scope confirmation
Align on team access, workflow priorities, interview schedule, and who attends the design session. Those names are harder to gather at short notice than they look.
Days 3–7
Interviews & workflow mapping
Structured interviews across teams, live workflow observation where possible.
Days 8–11
Design session & candidate prioritization
The half-day session runs first and produces the storyboard for the strongest candidate. Scoring follows: each candidate rated by ROI, effort, and feasibility, with architecture sketches drafted for the ones that lead.
Days 12–14
Report writing & walkthrough call
Final written report, delivered ahead of a live walkthrough session with your team.
OUTCOME
You leave with a roadmap your CFO can read.
There are three routes out of the Audit. The first is internal: your own engineers take the prioritized list and build the top candidates, using the report as the map.
The second is a delivery engagement — an Automation Sprint on the highest-ROI candidate in the usual case, or an AI Knowledge Base where what the report surfaces is a retrieval problem rather than a process one. The Audit identifies the target, the engagement builds it. Two engagements, one clear through-line from diagnosis to production.
The third applies when the report surfaces a standing decision problem rather than a single workflow: what you need next is not a project but an owner. The storyboard holds across all three, because it is written in terms of what a person experiences and what the system does rather than who implements it — your engineers, a delivery engagement, or nobody yet. Whichever route you take, the report replaces the internal debate about "where do we even start with AI" with a concrete answer backed by evidence from your own workflows.
FAQ
Common questions.
What does it cost?
Flat fee, scoped per engagement. I'll quote it on the discovery call. No hourly billing, no scope creep.
What size of team is this for?
Best fit is 20–500 person companies. Smaller and the ROI on the audit alone may not justify it. Larger and you may need a deeper engagement.
Do you sign NDAs?
Yes, before any conversation involving your data or workflows.
What if you don't find anything worth automating?
Then I tell you. If your workflows genuinely don't have automation candidates, I'll say so in the report.
Can you do this remotely?
Yes. Engagements run fully remote, including the design session, which runs on a shared board with the same structure it has in a room. In person with cards and a wall works too. On-site possible in the DACH region for an additional fee.
Who needs to be in the design session?
The people who execute the work, not only the people who manage it, plus one person with the authority to decide — named at the start of the day rather than when a tie appears. Six to eight is a good size. Past ten it stops being a working session.
How much of my team's time does the audit take?
Four to six interviews of forty-five minutes, one half day for the design session, and the closing walkthrough call. That is the whole ask.
What languages?
English, Spanish and Italian. German via written report; verbal interviews in English.