| Price | CHF 2'490 · 2,600 € | SAITS price list · as of 09.2026, net, plus VAT |
| With a first workflow | CHF 4'900 · 5,200 € | SAITS price list · as of 09.2026, net, plus VAT |
| Result | Scored use cases and a phased implementation roadmap | SAITS |
| Requirement | Access to the people who run the processes today | SAITS |
01 What the analysis is for
It answers one question: which recurring process in your company is worth automating first — and which is not.
02 What happens before: the free conversation
Every booking starts with a conversation, in the chat or with the team, where we take a rough record of your processes; if nothing is worth doing we say so there and the analysis does not happen.
03 Step 1: record the processes
We talk to the people who do the work today, not only to management.
04 Step 2: record the systems
We look at which systems are in use, where the data sits and which interfaces already exist.
05 Step 3: collect use cases
Every process where time disappears into coordination rather than the core business is noted as a use case.
06 Step 4: score the use cases
Each use case gets four values: hours bound, effort to build, risk, and dependency on other work.
07 Step 5: prioritise
The scoring produces an order — the first use case is the one with the most hours at the smallest effort.
08 Step 6: write the implementation plan
The plan says, per phase, what gets built, what it requires, who takes part and when it goes into production.
09 What you get at the end
A document with the scored use cases, the order and the phased plan — and a meeting where we go through it with you. How it is built is below.
10 What the analysis is not
Not a quote and not a commitment: the plan belongs to you, even if you build nothing with us afterwards.
11 How long it takes
The duration depends on the number of departments and on how quickly the conversations can be scheduled. A firm figure is not yet settled and will be added here once it is evidenced.
12 What we need from you
Time with two to four people from day-to-day operations, a look at the system landscape, and real example documents.
13 The step up to CHF 4'900
Booking the analysis together with the first workflow gets the first use case built straight away; which one it is follows from the analysis.
14 If you build nothing afterwards
The plan still belongs to you, and you can implement it with anyone.
What is in the implementation plan
The plan is a document in four parts.
Part 1 — The record Who was interviewed, which departments took part, which systems are in use and where the data sits today.
Part 2 — The scored use cases Four figures per use case: how much time it binds today, how much effort building it would take, what risk it carries and what it depends on.
Part 3 — The order Which use case comes first and why. At the front is what binds the most hours at the smallest effort.
Part 4 — The phases Four figures per phase: which use case gets built, over what period, what has to be in place and who from your side takes part.
We go through the plan with you in a meeting. After that it belongs to you.
If you want to know which process is number one in your company, the analysis is the way to find out.
See also: How a first workflow goes live in four weeks · What a workflow costs and what it saves