Work piles up between systems
People move information from inboxes to documents, ERP, CRM, and spreadsheets. The process takes hours and creates room for missed details.
For owner-led European companies · typically 30–250 people
Punch above
your headcount.
We turn a valuable, repeatable process into a governed AI workflow—built in your cloud accounts on European infrastructure you control, with people in the loop where judgment matters.
A short fit call. If the work is a match, the next step is a free diagnostic.
Example workflow · technical quoteUnder your rules
Business inputQuote requestSpecs · drawings · customer context
Workflow runtimePrepare the workRead · check · draft · return
Shared rules · control planeYour context and boundaries guide every run.
What it can accessWhich model to useWhen a person reviews
Useful outputDraft quote + open questionsSource information stays traceable
Business decisionEngineer reviewsAdjusts and sends
✓People stay accountable. Automate the repeatable work; keep judgment where it belongs.
Workflow 1Workflow 2Workflow 3
Illustrative specialist-manufacturing example. Other workflows use the same shared rules, with their own access, checks, and approval points.
A well-chosen workflow can help your team:
01Take on more work
02Keep know-how in reach
03Get quotes and replies out sooner
Why now
Business is accelerating. Your operating systems need to keep pace.
AI can process information at machine speed. The advantage comes from systems that turn it into dependable work, shaped by your context and controls.
Important know-how sits with a few people
Quotes, exceptions, and customer decisions rely on experience that is difficult to find, share, and apply consistently.
AI tools don’t add up to an operating capability
AI in separate products brings separate context and instructions. Passing work between them can add calls, delay, and cost without creating one dependable process. A well-designed workflow uses only the context and tools the job needs, with clear permissions and checks.
Provider dependence can become a continuity risk
If a critical workflow depends on one model or cloud provider, a change in its terms, access, or location could disrupt the work.
We build the system in cloud accounts your company controls. We test model changes against the workflow before they go live.
The work, made concrete
From scattered information to work your team can use.
A first workflow takes a specific, repeatable process and turns its inputs into a checked result. These are examples, not client case studies.
RevenueSpecialist manufacturing
Technical enquiries into draft quotes
Read specifications and drawings, check feasibility and pricing rules, prepare a draft, and list unanswered questions.
An engineer reviews and sends.
OperationsManufacturing · logistics
See the impact of an order change
Check a requested change against inventory, supplier commitments, production or delivery capacity, and customer terms. Surface conflicts and prepare options for the team.
People approve changes to commitments.
ResilienceManufacturing · infrastructure · services
Turn a disruption into a response plan
When a supplier, site, or service is disrupted, assemble affected orders, customers, dependencies, and relevant obligations. Prepare a prioritized response for review.
People decide what to communicate and what action to take.
Agree the measure first
Before building, we set a baseline and acceptance tests with you. Depending on the workflow, we might measure time per case, correction rate, turnaround, or backlog. At handover, we review the result against the agreed measures.
How it works
Models need a system to do useful work.
For each workflow, we define its business context, what data and tools it can access, where information is processed, and when a person must review an action.
Shared rules govern the workflow. The workflow runtime carries out one defined process within them.
Control plane · shared rulesSet by your business
Company contextGoals, terms, policies
Data accessWhat this workflow can see
Model choiceWhich model handles each task
Review pointsWhen a person approves
Activity recordWhat ran and who approved
Change testsHow replacements are checked
↓ governs each workflow ↓
Workflow runtime · one processRuns in your cloud accounts
Receive input
Follow steps
Use approved tools
Check result
Act or ask
Human review: approve the actions that need judgment; return failed checks and exceptions to a person.
01 workflow proves the setup02 · 03 · more workflows reuse shared rules, each with their own controls
A clear first step
One workflow, built to become a capability.
Start with a useful process. Establish the shared context and controls it needs. Decide what to expand after you see it working.
First workflow · 30 days
A working system in your cloud accounts, built around your process.
We agree the workflow, systems, measures, and acceptance tests before the build. At handover, your team has the code, configuration, and operating guide.
€19,500 + VAT · fixed price
- Shared company context and workflow rules
- One workflow in production
- Agreed data access, processing location, and human review
- European provider by default
- Model-change test and documentation
- EU-only processing available by choice
50% at signing; 50% when the agreed acceptance tests pass. If a test fails, we fix it and retest.
After handover, choose how to grow.
Run it with your team €0 / month to us
Your IT contact or a freelancer runs it using your access, the source code, and the operating guide.
Have us run it €2,000 / month + VAT
Monitoring and support for the workflows we built, in your cloud accounts. +€500/month + VAT per further workflow; three-month minimum, then monthly notice.
Add another workflow From €15,000 + VAT
Fixed scope and price, quoted for each workflow on the shared rules already in place.
The free diagnostic, in practical termsA 90-minute session, followed by a two-page write-up within a week: three ranked workflow candidates, the recommended first workflow scoped for the 30-day build, and how it will use systems and be tested. Yours to keep, whether or not you proceed.
The system stays yours.
Your infrastructureIt runs in your cloud accounts. Admin access stays with your company from day one.
Your systemSource code, configuration, and operating guide are handed over at the end of the build.
Your choicesChoose models and hosting; test model changes before they go live. EU-only processing is available by choice.
Choose the right first process
Start where good people spend too much time moving information.
A strong first workflow repeats often, pulls information from different places, and has a result the business can measure. You don’t need an in-house AI team. You do need someone who knows the process and can help define what good looks like.
It happens every week
Invoices, enquiries, reporting, document checks, or another process your team handles again and again.
Information is spread around
The work crosses email, documents, and business systems. People spend time finding, copying, checking, and re-entering it.
You can see the cost
Time, delays, backlog, rework, or missed opportunities make this process worth improving—and give us a way to measure progress.
A strong fit
An owner, CEO, or managing director at an owner-led European company—typically 30–250 people—can name the process and bring its owner into the work. Your team keeps responsibility for business decisions; we design, build, and hand over the workflow.
Outside this offer
A general-purpose chatbot, a strategy deck without implementation, or unchecked AI decisions about consequential business matters.
Ivan Sanz
Built by an operator
From hardware to software, I build for resilience and control.
My work spans the infrastructure behind modern business: hardware and supply chains, data centers, global networks, and software that coordinates work. At Fastly, I led network strategy and capacity across more than 150 Tb/s, focusing on resilience, failover, and vendor diversity. Through Listo Digital, I advised carriers, infrastructure operators, and investors on network and data-center strategy, satellite infrastructure, market entry, and technical due diligence across North America, South America, Europe, Africa, Asia, and Australia. I’ve also built software and operating processes for businesses I run.
I studied political science at UC Berkeley and earned an Executive MBA in finance and strategy. That mix shapes how I see AI: its value depends on infrastructure, ownership, regulation, capital, and geopolitics. Berlin Operators helps European companies put AI to work while keeping control over how it runs and how they adapt.
Questions, answered
Before you start.
A workflow is only useful if the business can trust it, operate it, and change it.
What happens on the first call?
We talk through what runs slowly, where information gets stuck, and whether the process fits a first workflow. If it does, we offer a free diagnostic. If it doesn’t, we’ll tell you.
Do you need our data or system access before we sign?
No. The diagnostic uses conversation only. Files, credentials, exports, and system access come after a contract and data-processing agreement.
How do you handle data access, processing location, and security?
Before the build, we agree what data and systems the workflow can access, which model handles each task, where information is processed, and where human review is required. The system runs in cloud accounts your company controls, with a European provider by default. EU-only processing can be specified and checked for the full deployment path.
Can we change models or providers later?
Model routes are configurable. A replacement is tested against the agreed workflow checks before going live. Moving hosting providers or infrastructure is a planned migration, not an instant switch.
What if the workflow doesn’t pass the acceptance tests?
If a test fails, we fix the workflow and run the agreed tests again. The second 50% is due when those acceptance tests pass.
What does ongoing operation involve?
Someone needs to handle access, updates, monitoring, recovery, and model changes. Your team can do that with the handover materials, or you can choose the monthly run service.
Start with the bottleneck
What work would give your team room to move?
Talk it through in 20 minutes. If there’s a fit, the diagnostic maps the right first workflow and how we’ll measure it.