Internal test
If the experiment is simple enough, your team can run it internally.
AI Workflow Workshop · €1,000
Bring one real workflow case. Leave with one experiment worth testing.
Most teams have AI tools now, but the work itself has not really changed. In this workshop, your team brings one anonymized workflow case. I review how the work happens today, prepare an AI-assisted version, and help you decide whether this workflow is worth changing before you spend weeks building, buying, or debating.
You leave with one concrete experiment, the expected business impact, the human controls needed, and a recommendation to test, diagnose, sprint, or stop.
No sticky notes. No AI training. No generic use-case backlog. One real case, one prepared review, one practical next step.
€1,000 · 90 minutes online · 2 to 4 people · One workflow · One anonymized case · AI Workflow Review Pack
The workshop at a glance
- Price
- €1,000
- Format
- 90 minutes online
- Participants
- 2 to 4 people
- Scope
- One workflow
- Case
- One anonymized case
- Output
- AI Workflow Review Pack
Who this is for
This is for B2B SaaS teams that feel AI pressure, but need a concrete place to start.
Good fit
- You have one recurring piece of work that feels slow, inconsistent, risky, or too manual.
- AI keeps coming up as a possible answer, but the team has not agreed where it should fit.
- The work crosses people, tools, or handoffs.
- You can share one redacted or representative example.
- You want a grounded experiment, not a generic use-case list.
Not a good fit
- You want a broad AI inspiration session.
- You want training for a large group.
- You want a list of 30 AI ideas.
- You expect a finished automation in 90 minutes.
- You cannot share even a redacted or representative case.
How it works
1. Send one anonymized case
Before the session, your team shares one recent example of work you want to improve. It can be redacted, anonymized, or synthetic-but-representative. Examples: support ticket, customer handoff, invoice exception, account review, sales note, onboarding notes, internal report, product feedback batch, QBR prep case.
2. I prepare the review
I reconstruct how the work appears to happen today, prepare an AI-assisted version, and identify likely failure points, missing context, and control needs.
3. We compare current work with the AI-assisted version
In the session, we review the current workflow, correct the replay with the people who know the work, and judge what the AI-assisted version gets right or wrong.
4. We design the control model
We define what AI can suggest, what humans must approve, what the system must log, and what should never be automated.
5. We choose the experiment
We leave with one controlled experiment the team can test internally, continue into a diagnostic, or move into a sprint.
What you get
You receive an AI Workflow Review Pack your team can use as a decision artifact.
- Case inspected.
- Current workflow replay.
- AI-assisted attempt.
- What improved.
- What failed or felt risky.
- Human control model.
- Expected business impact.
- Concrete experiment recommendation.
- Verdict: test, diagnose, sprint, or stop.
The workshop does not promise ROI in 90 minutes. It identifies whether the workflow is worth changing, what impact the team should expect, and what needs to be tested before bigger investment.
What the session decides
The session is not about admiring AI output. It is about deciding whether changing this workflow is worth it.
- Where AI could reduce effort, cycle time, rework, or manual preparation.
- Where AI could improve consistency, quality, or prioritization.
- Where AI needs better context, sources, or system boundaries.
- What humans must still approve.
- What should never be automated.
- What expected business impact would make the experiment worth testing.
- Whether the next step is an internal test, diagnostic, sprint, or stop.
What to bring
Bring one real or representative case from a workflow your team wants to improve.
- A support ticket that took too long to triage.
- A customer handoff with missing context.
- An account review that required too much manual prep.
- An invoice exception that moved between too many people.
- A sales note that needed better qualification and follow-up.
- A product feedback batch that was hard to synthesize.
- An internal report that required too much copy-paste work.
Please anonymize, redact, or replace sensitive details before sharing. The workshop does not require confidential customer names, credentials, personal data, or production access.
Price and format
€1,000 for one AI Workflow Workshop. Includes:
- One intake case.
- Luis's private preparation.
- 90-minute online review session.
- AI Workflow Review Pack.
- One practical experiment recommendation.
The workshop is designed to answer whether this workflow deserves more investment before the company spends weeks building, buying, or debating. It is not a full implementation project.
Where it can lead
Diagnostic
If the opportunity is promising but the risks, owners, data needs, or implementation path are unclear, the next step is the AI Workflow Diagnostic.
Sprint
If the experiment is clear and the team wants hands-on help, the next step is the Operator / Advisory Sprint.
Stop
If AI adds noise, risk, or complexity, the recommendation can be to leave the workflow alone for now.
A few things people ask
Is this an AI training session?
No. It is built around one real workflow case and one practical experiment decision.
Do we need to give you access to our systems?
No. The workshop uses one anonymized, redacted, or representative case. No production access is required.
What if the AI output is not good?
That can still be valuable. The point is to see what AI can safely help with, where it fails, and what human controls the workflow would need.
Can more than four people join?
The session works best with 2 to 4 people who know the workflow and can make or influence the next decision. Larger groups usually dilute the review.
Can we review multiple workflows?
Not in one workshop. The format is intentionally focused on one workflow case. If there are several possible workflows, the diagnostic is a better fit.
Will you build the automation in the workshop?
No. The workshop defines the experiment. If you want help designing, prototyping, testing, or operationalizing it, that can continue in a diagnostic or sprint.
Start with the workshop if you are not yet sure which workflow is worth changing.
If the workflow opportunity is already clear, consider the diagnostic. If the experiment is already chosen, look at the sprint.
Want to review one workflow from your team?
Bring one anonymized case. I will prepare an AI workflow review, then we will decide what worked, where it failed, what humans must control, and what experiment is safe enough to test.
€1,000 · 90 minutes online · One real case · One practical experiment