Your first agentic workflow · Claude Code · Claude Cowork
AI that works — not just answers.
An agentic workflow is a digital caseworker for one clearly scoped process: it works inside your systems by fixed rules, and your people keep the sign-off. We build your first one — with a real process from your day-to-day, in two weeks.
Take tenders: answering one costs your experts two or three days of digging today. The agent delivers the draft, your experts review and decide. Before and after get measured — you get proven numbers instead of an estimate.
2 weeks
1 process
12+
EU
What this looks like in practice
The idea isn't missing. Production is.
Processes, not demos. Your process isn't listed? That's exactly what the first call is for.
Three days of digging before quality even starts
The agent drafts the tender response from past bids and product docs. Your expert reviews and decides instead of assembling.
Four weeks of panic before every audit
Agents generate and version evidence continuously from your systems. We automated DORA inventory maintenance at a bank on this principle.
The same copy-paste ritual every month
The agent gathers from the source systems and builds the draft. Your people review instead of copying.
The release depends on the one person who knows the ritual
Agents draft changelogs, release notes and migration checks — cross-checked, repeatable, no more evening job.
At 3 a.m. the diagnosis starts from zero
The agent gathers logs, metrics and recent changes and files a first hypothesis with the alert.
Weeks of mechanical work across dozens of repos
Upgrades and API migrations roll out across the whole estate, each change verified by its own checks.
Why this is different
Not a consultant's deck. A process that runs.
I'm building exactly this right now inside a BaFin-regulated bank: model gateway, guardrails, skill library — for developers and business teams alike.
Built, not recommended
I don't hand over a concept for self-assembly. I work in the same repository as your team — the workflow runs against real cases before I leave.
Everything as a Skill
Every solved process becomes a documented building block in your own library. The second process is faster than the first, because nothing starts from zero.
Data protection and approval from day one
GDPR-compliant model access in the EU (AWS Bedrock, Google Vertex AI), no training on your data. Built with your DPO and CISO, not around them.
The layer underneath the AI
Sandboxes, permission boundaries, controlled network access, complete logs. This protective layer decides whether the security review says yes.
How we work together
Two weeks to a number you can prove
If week 1 shows the process isn't worth automating, you'll hear that — and we pick a better one.
Pick & map the process
In the room: process owners, the business side, engineering
We start with the process, not the tool — and make its current cost measurable.
- ▸Process interviews with the people who run it daily
- ▸Candidate scoring by effort, frequency and risk
- ▸Baseline measurement: cycle time, error rate, cost
- ▸Clear split: what the agent does, what humans decide
- ▸Permissions and approvals clarified up front
Outcome: One selected process with a measured baseline.
Build & secure the workflow
In the room: engineering, security & data protection
The workflow is built on your real data and systems, with your security team's rules.
- ▸Connected to Jira, GitLab, databases, line-of-business systems
- ▸Fixed rules: what the agent may do, where humans sign off
- ▸Isolated sandbox instead of full access
- ▸Logging and cost control from day one
- ▸Tested against real cases
Outcome: The workflow runs — with an after-value to hold against week 1.
Hand over & make it stick
In the room: your team, your future champions
The engagement ends with your team driving.
- ▸Handover: your team drives, I watch
- ▸The process becomes a building block in your library
- ▸Non-developers work with it too: Claude Cowork, same guardrails
- ▸Playbook for the next process
- ▸4 weeks of async support
Outcome: Your team builds the next process without me.
Why it survives the security review
Built for the security review
A workflow that can't be approved never ships. This is what the setup looks like:
Model access through the EU
Access to frontier models via AWS Bedrock or Google Vertex AI. Data kept in the EU, zero retention, no training on your data.
Isolated sandboxes
Agents run in disposable containers with tightly scoped access.
Fixed rules instead of trust
Allowlists, checkpoints and approval gates define deterministically what agents may do. Role-based access for humans and agents.
Traceable for your auditors
Every action logged. Dashboards for usage, quality and cost, on open standards.
>_ Designed so your CISO and DPO say yes — documented so your auditors do too.
Engagement models
Workflow Sprint
Fixed scope, fixed outcome: one real process, proven against real cases.
- ✓Process selection with a measured baseline
- ✓One agentic workflow on your systems
- ✓Before/after numbers for your leadership
- ✓Approval package: architecture, data flows, permissions, audit concept
- ✓4 weeks of async support
For: one team with one process that hurts
Process Program
Several processes of one team, plus the platform and library behind them.
- ✓3–5 processes as agentic workflows
- ✓GDPR-compliant platform per the reference architecture
- ✓Your skill library, versioned, owned by you
- ✓Cost architecture: the right model per task, budgets per team
- ✓Enablement along the way — developers and business users alike
For: teams of 5–15, incl. platform & security
Embedded Partner
A standing partnership that keeps turning processes into workflows.
- ✓Quarterly process delivery with your teams
- ✓Skill library governance and curation
- ✓Champions program & internal enablement
- ✓Adoption, quality and cost reporting to leadership
For: organisations scaling beyond the first team
Solo professional or small team? Ask for the compact one-day intensive — one small process plus a secure single-seat setup.
Next step
Bring your hardest process
30 minutes, one real process that hurts. I'll show you what it looks like as a secured workflow — with the rules your security team will demand. If I can't, you've lost half an hour, not a budget.