Process workshop a written result that stays with you
We map how your processes actually run, not how the documentation says they should. You walk away with a process map, a list of automation candidates with the hours they would free up, a rollout order and a quote for the rollout. In writing, within 3 working days. EUR 3,500 net per week, from 1 to 7 weeks.
- EUR 3,500net per week of workshop. The number of weeks, from 1 to 7, follows the number of processes and departments, and we agree it before we start
- 3 working daysfrom the last session to the written report, put in business language rather than technical language
- 30 daysan action plan your own team can run without us, even if you never order a rollout
The problem
Why do processes run fine until somebody maps them?
The manager says the process runs fine. Then you ask the person who actually does it what they do in the morning before the real work starts, and you hear: 45 minutes pasting data out of emails into a spreadsheet. You ask what eats the most time and you hear: waiting for a colleague to come back from leave, because he is the only one who knows how to run the export. Several versions of the same file circulate around the company and nobody knows which one is right.
Documentation describes what should happen. The truth about a process sits with the people who run it, and usually nobody has asked them. That is why a conversation about automation so often starts with the name of a tool and ends with a rollout nobody opens a quarter later.
Part of that description is already a legal duty. Article 30 of the GDPR requires a record of processing activities with purposes, data categories, recipients and erasure deadlines, and the exemption for organisations under 250 people falls away as soon as the processing is not occasional. The catch is that the record describes what happens to personal data. It says nothing about who retypes an order from an email into a spreadsheet at 8:15, or how many times a day the same figure gets keyed in twice.
- You automate the loudest symptom instead of the most expensive process
- A tool bought to try out sits unused, because nobody agreed what it should do
- The rollout quote is a guess, because nobody counted the hours that could come off
- Process knowledge stays in one head, along with the risk of that person taking leave
Why the workshop comes first
What does a process map give you that a tool demo cannot?
Tools are cheap and quick to connect. The bottleneck is not technology. It is that nobody inside the company agrees on how the process actually runs: how many steps it has, how many times data gets keyed in by hand, where a case stops and waits for somebody to decide.
The workshop puts that on paper. We talk to the people who do the work, draw the flow step by step, and record three things at every step: how long it takes, how often it repeats, and what happens when it goes wrong. Only that kind of map lets you rank changes by impact instead of by who asked loudest.
Our rule is process first, tools second. So the workshop sometimes ends with the recommendation do not automate this, simplify the process first. That is a result too, and it is one you are paying for. We say it before we start, not in the report. Automating a mess gives you a faster mess.
The workshop is also the paid core of our AI consultancy work. If you are still choosing between a strategy firm, an independent consultant and a team that advises and then builds, that page sets the options side by side, including the cases where you do not need us.
The deliverable
What exactly lands on my desk at the end?
A map of the process as it runs today
The flow step by step, the way it really works: systems, people, decision points and every place where somebody retypes data by hand. The team looks at one diagram instead of four different mental pictures.
A diagram, not a deck: steps, systems, people, decision points
Automation candidates with the hours counted
Every item carries an estimate of the hours per week it would take off people, and the error risk that disappears with it. That number is what the return conversation is later built on.
Hours per week freed up, counted separately for each item
A rollout order, not a bag of ideas
Recommendations ranked by impact: time consumed, how often the step repeats, error risk. You know what you do first, what second, and what you never do at all.
Ranked on three criteria, with quick wins pulled out separately
A rollout quote based on scope
After the workshop we know how much work sits inside each recommendation, so the quote stops being a guess made before anyone saw the process. You get it split into stages, so you can start with one.
Quoted after the workshop, split into stages, not one number from thin air
Metrics and a 30 day action plan
What to measure daily, monthly and quarterly, with a proposed dashboard structure. The plan also lists the changes you can make tomorrow, without waiting for a formal rollout.
A metrics list plus the first improvements you can run without us
All of it in writing, and yours to keep
The report arrives 3 working days after the last session, in business language. It is yours and it stays with you, including when you order no rollout from us or from anybody else.
3 working days after the last session, a document with no strings
Proof
Did you start with a workshop yourselves?
We do not publish other people's numbers without the owner's permission, so we show our own. Two AI agents have been running in production inside our founders' companies since March 2026, and both started with the same step: taking the process apart before anyone touched a tool. Below is six months of measurement from one of those companies, together with what these numbers do NOT prove. They measure the effect of the whole rollout, not of the workshop alone.
Built for ourselves. These are not client deployments but implementations inside the founders' own companies. We say so plainly, because proof you cannot verify is not proof.
JustBottheir agentJustIdea Agency, a performance marketing agency of around 30 people
- 23
- people from the company work with the agent
- 38
- systems wired in permanently
- 112
- processes run without a human
- 475
- thousand lines of the agent’s code
An agent wired into Google Ads, Meta, the CRM, the task system, the SEO tool, Analytics, Search Console and the data warehouse. First commit 1 March 2026, today 23 people use it.
8 of 38 systems it works in
Google Ads
Meta Ads- HubSpot
- ActiveCollab
- Ahrefs
GA4
Search Console
BigQuery
- Before
- In the twelve months before launch the agency ran at a margin of minus 4.42 percent. Across a twenty-month window there was not a single run of three profitable months.
- After
- May, June and July 2026 are three profitable months in a row, the first such run in the whole window. Revenue barely moved, so the change sits on the cost of delivery, not on sales.
Margin up 5.55 percentage points year on year, with revenue up 1.5 percent
And in your company
What if we have nothing worth mapping?
Four sentences we hear most often in the consultation, and what we answer to each of them.
We already have our own automation ideas.
Good, the workshop tests them. Usually half of them are genuine priorities and the other half turn out to be the most visible symptom of something sitting one step earlier. If your list holds up, you get it back with the hours counted and a place in the order, so the rollout conversation stops being a matter of taste.
We cannot spend seven weeks sitting in workshops.
Seven weeks is the widest version, for a manufacturer with a process running from order to dispatch. One narrow topic takes a week. On your side it is two sessions of 60 to 90 minutes a week, and the rest of the work happens between sessions, on ours.
We are worried this ends with a presentation and nothing else.
That is why the workshop ends with a document rather than slides: the process map, the candidate list with hours to free up, the rollout order, the quote and a 30 day plan. You get it 3 working days after the last session and you can execute the recommendations yourselves or with anybody else.
What if you tell us there is nothing to automate?
We will say it if that is how it comes out, and it is a normal result of a workshop. Sometimes the answer is simplify the process first, cut two steps and one spreadsheet, then come back to tools. We say this before we start, so nobody buys a workshop assuming it has to end in a rollout.
- CRM
- HubSpot, Pipedrive, Salesforce, LiveSpace
- Invoicing and accounting
- Fakturownia, sevDesk, Xero, Comarch Optima
- Sales and stock
- BaseLinker, Allegro, Shopify, WooCommerce, PrestaShop
- Team tools
- Google Workspace, Microsoft 365, Slack, Notion, ClickUp, Jira, Asana
- Data and reporting
- BigQuery, Google Sheets, GA4, SQL databases
- Automation layer
- Make, n8n, Zapier, custom API integrations
What decides the number of weeks
The price is charged per week, so the scope of the workshop is also its quote. Three things set the number of weeks: how many processes we map, how many departments the process crosses, and how many systems the data lives in. We agree the scope in the free consultation, before anything is signed.
| Workshop scope | Weeks | When that is enough |
|---|---|---|
| One narrow process in one department | 1 week | you know what hurts; you need a map and a quote for one change |
| 2 to 3 processes in one department | 2 weeks | the department has a few repeatable tasks and one data source |
| A department from enquiry to closed case | 3 weeks | the process crosses several systems and several people |
| Two departments and the handovers between them | 4 weeks | most is lost at the seam, sales and operations for example |
| Sales, operations and finance together | 5 weeks | the same data gets keyed in several times, in several places |
| A manufacturer, from order to dispatch | 6 to 7 weeks | the process touches the warehouse, production and accounting |
Each week costs EUR 3,500 net, so you know the total the moment the scope is agreed. Most engagements land at 3 to 7 weeks. If it turns out along the way that fewer weeks are enough, we finish early and you pay for the weeks that happened.
How it runs
Five steps from the first call to the report
Every week looks similar. Two sessions of 60 to 90 minutes with the people who run the process, plus a short check with the decision maker. Between sessions we work on our own: drawing the map, counting task times, writing down the questions for the next session. At the end of every week you get one thing in writing rather than a promise: first the process list with times, then the map, then the priorities, and finally the quote and the plan.
Free consultation, 30 minutes
We agree how many processes to map and how many weeks that takes, which sets the price. You write directly to Paweł Pasterak, the founder, with no reception and no tickets.
Discovery
Conversations with the people who run the process day to day, not only with the management. What you do in the morning, what eats the most time, where mistakes happen. Output: a list of processes with estimated times.
Mapping
The process drawn step by step: systems, people, decision points, manual data entry, and the places where a case stops and waits for somebody to decide.
Prioritisation
A ranking by impact: time consumed, how often the step repeats, error risk. Plus an estimate of the work that comes off and the rollout time for every item.
Report and 30 day plan
The map, the automation candidates, the rollout order, the quote, the metrics and the action plan. In writing, 3 working days after the last session, in business language.
Before and after
How the automation conversation changes
Before
- 45 minutes of every morning goes on pasting data from emails into a spreadsheet
- Several versions of the same file circulate and nobody knows which one is current
- One person can run the export, so their leave stops the process
- The rollout conversation starts with a tool name and ends with a guessed number
After
- The process is drawn and the whole team looks at the same diagram
- You know how many hours a week each step eats and which one comes off first
- The rollout order is agreed, with a quote and metrics to measure against
- The tool conversation starts from scope, so the quote stops being a guess
You run the first improvements from the 30 day plan yourselves, right after the report. The first automation is usually live 14 days after the workshop, and a full rollout takes 2 to 4 weeks.
For the person signing this off
What you actually risk by ordering a workshop
You are signing off a workshop, not a rollout, and that is the whole difference in risk. You know the spend to the euro before it starts, because it follows from the number of weeks agreed in the consultation. The date is fixed too: the report lands 3 working days after the last session.
The second thing matters more in front of a board. You walk in with a document where every recommendation carries counted hours and an estimated rollout time. It holds up on its own, even if the company decides not to go further for now, and it does not depend on who tells the story better.
- Price known before the start: EUR 3,500 net per week, weeks agreed in the consultation
- The report is yours and stays with you, including when you order no rollout
- If the process needs simplifying rather than automating, we write that down plainly
- We deduct the cost of the workshop from the value of the rollout if you go ahead
What it costs
The price is published: EUR 3,500 net per week
The workshop costs EUR 3,500 net per week and runs from 1 to 7 weeks. Three things decide the number of weeks: how many processes we map, how many departments they cross, and how many systems their data lives in. We agree the scope in the free consultation, so you know the total before anything is signed. Most engagements land at 3 to 7 weeks, and one narrow topic takes a week.
Every week buys you something concrete in writing: the process list with times, the map, the priorities, and at the end the quote and the 30 day plan. We quote the rollout only after the workshop, because anything earlier would be guesswork. Running costs for tools and models you pay directly to the provider, with no margin from us. If you go ahead, we deduct the cost of the workshop from the value of the rollout.
Process workshop
EUR 3,500 net
per week, from 1 to 7 weeks
A self-contained piece of work. It ends with a document you can execute without us, and it commits you to nothing.
- A map of the process as it runs today, step by step
- Automation candidates with an estimate of the hours to free up
- Rollout order and a quote for the rollout
- Metrics and a 30 day action plan
- A written report in 3 working days, in business language
- The result stays with you, including when we do not go further
- Most popular
Workshop and rollout
Quoted after the workshop
we deduct the cost of the workshop from the value of the rollout
The option most companies choose. The workshop, then the recommendations built in the order the priorities produced.
- Everything in the workshop
- First automation usually live 14 days after the workshop
- Production rollout in 2 to 4 weeks
- Team training and exception handling
- Measurement after 30 and 90 days, on the metrics from the workshop
Workshop and AI agent
Quoted after the workshop
for companies that want to ask about data in a plain sentence
Everything in the rollout plus a company AI agent that answers from your own data rather than from the model's general knowledge.
- Everything in the rollout
- A company AI agent answering from company data in 5 to 10 seconds
- Access scope per system agreed before the rollout
- Agent in production in roughly 2 months
The result of the workshop is yours. The process map, the list of automation candidates, the rollout order, the quote and the 30 day plan stay with you in writing, including when you order no rollout from us or from anybody else. The workshop sometimes ends with the sentence do not automate this, simplify the process first, and we say that before we start rather than in the report.
Frequently asked questions
How much does the process workshop cost?
EUR 3,500 net per week. The workshop runs from 1 to 7 weeks, most often 3 to 7, and one narrow process takes a week. We agree the number of weeks in the free consultation, so you know the total before you sign anything. If it turns out along the way that fewer weeks are enough, we finish early and you pay for the weeks that happened.
What exactly do I get at the end of the workshop?
A map of the process as it runs today, a list of automation candidates with an estimate of the hours per week they would free up, a rollout order, a quote for the rollout, a list of metrics with a proposed dashboard, and a 30 day action plan. All of it in writing, 3 working days after the last session, in business language.
What if I decide against a rollout after the workshop?
You keep the whole report and you can execute the recommendations yourselves or with another partner. The result of the workshop is yours, with no obligation to work with us further. The workshop is a product in its own right, not a deposit against a rollout you have not ordered yet.
How much of my team's time does the workshop take?
Two sessions of 60 to 90 minutes a week with the people who run the process, plus a short check with the decision maker. The rest of the work happens between sessions, on our side. You need one person who can close a topic, access to information about the process, and permission to talk to the people doing the work.
What decides whether the workshop takes one week or seven?
The number of processes, the number of departments the process crosses, and the number of systems the data lives in. One narrow process in one department is a week. Two departments with handovers between them is usually four weeks. A manufacturing process from order to dispatch, touching the warehouse, production and accounting, is 6 to 7 weeks.
Is the workshop run online or on site?
Both work and you choose at the start. Online means recurring sessions, typically two or three a week, short and focused on one part of the process. The on site version earns its place where somebody has to watch the work on the shop floor or in the warehouse, because half the steps are written down nowhere.
Does the price of the workshop count towards the rollout?
Yes. If you decide on a rollout after the workshop, we deduct the cost of the workshop from the value of the project. We quote the rollout itself only after the workshop, once we know the scope, the number of systems and the state of the data. A quote made before anyone saw the process would be guesswork, and then a year of arguing about that guess.
What if we already have our own automation ideas?
The workshop tests them, and usually about half the list holds up. The rest turns out to be the most visible symptom of something sitting one step earlier in the process. You get your own ideas back with the hours counted and a place in the order, so the rollout conversation stops being a matter of taste.
Let us set the scope and the price of your workshop
The free consultation takes 30 minutes. You describe the process that eats the most time, and we tell you how many weeks it takes to map it and what you get at the end. You write directly to Pawel, with no reception and no tickets.
We run at most two rollouts at a time, so there are only as many workshop slots as we can genuinely staff. A workshop books your place in the queue.
Book a free consultationPS. If several versions of the same file circulate in your company and nobody knows which one is current, this is exactly the moment. For EUR 3,500 net per week you walk away with a process map, a rollout order and a quote in writing, and the document stays with you even if we never go further.