What automation costs in Switzerland
What automation costs before you build
What automation costs in Switzerland can be pinned down reliably at one point before the first build: a fixed-price package once you have a tangible case in writing. The Process Check that produces that case is free. Everything in between is a guide band. For owners, ops, and finance with one recurring office workflow, that is the figure you can take to a partner or board without guessing a twelve-day project.
This page is a poor fit if you want a day rate for «some AI», a workshop, or a quote to build a product. The packages cover one bounded workflow after the Check has named it. What happens in the half hour is in what the Process Check is. The offer in short form: Process Check.
- 30 minFree
Process Check online. The build afterwards stays a fixed price.
- BuildPackage
Small through Max as guide prices; size set in the Check.
- RunHosting
Guide CHF 50 to 150 per month, cancellable.
The Check: the half hour is free
The Process Check is free. It is not a deposit on a larger project. The build afterwards stays a fixed-price package, if you have a case and want it built.
You pick a slot, and the appointment is confirmed by email. The same path is book a Process Check.
Packages as guide prices
Implementation after the Check is a fixed price once the case is bounded. The sizes on the offer page are guide prices. You still buy a package, not a timesheet. The final size is the one named in the Check on your workflow.
| Package | Duration | Guide price |
|---|---|---|
| Small | 2 to 3 days | CHF 3’200 to 4’800 |
| Medium | 7 days | CHF 14’000 |
| Large | 10 days | CHF 20’000 |
| Max | from about 12 days | from CHF 25’000 |
Small is the guide for a narrow glue that is already repetitive: two stable exports into one known sheet, a reminder that opens a draft a person still sends. Few systems, few exceptions, one owner.
Medium is the guide when the path is still one workflow, but more than a paste: several sources, a review queue, rules you can list. Invoices from more than one portal, with a person confirming before anything is booked, often lands here once the path is clear. It can also be a harder Small, or it can fall apart into «not yet» if the exceptions are not listed. The half hour decides.
Large and Max are the guides when that same single workflow touches more systems, more permissions, and more written rules, and the build runs longer. They are not a bundle of five unrelated ideas. Five topics in one package means five half-results. The Check stays on one process. If the list is longer, you pick one and the rest wait. Buying a package with no case means guessing the scope. The guide table cannot see your portals, your logins, or the column that changes name every week.
What you pay monthly after it is live
Token cost sits with you: your model subscription or API on the account the firm already chose. We do not fold a vendor’s token price into the package, because that bill moves with how often the flow runs and which model you use.
Hosting, as a guide, is CHF 50 to 150 per month, and it can be cancelled. That is the running cost after the build. The final figure is in the Check, the same way the package size is. Treat the band as a planning number for a small workflow host.
Licences you already pay stay yours. Microsoft 365, bexio, Abacus, a CRM. A package does not replace those subscriptions.
Two scopes, so the bands mean something
These illustrations show the shape of a scope. The Check is what places your file in a band.
A Monday report from two stable exports, eight columns that have not moved in a month, one person who checks totals before send. That is the shape of Small: a few days, a start and an end you can say in one sentence, systems you can already log into.
Invoices from five portals, a Teams approval, and a match to a purchase order that lives in another tool, with a human confirm before bexio or Abacus gets a booking. That is a larger shape. More logins, a queue, rules about VAT and project codes when they are unclear. It may be a Medium or it may be the wrong workflow until the exceptions are written down. The guide price of a larger band exists so you do not budget a two-day paste job for a five-portal path.
The fixed price waits until after the case because those two Mondays are not the same purchase. A price picked from a menu before anyone has seen the file is a guess with a Swiss franc sign on it.
What stays outside the package
You are here for a number on one workflow. Closing, odd VAT positions, and the year-end stay with the trustee or the person who already signs them. A package can move a PDF from a portal into a review queue. Microsoft 365, bexio, Abacus, and the CRM stay subscriptions you already pay.
A product idea or an MVP sits outside this cluster. So does a training day for the team. The figure on this page is for a bounded build after the Check.
Walk away from a package, including ours, when the workflow has no owner, the columns change every week, or you hope the build will decide which process matters. Book the free Process Check if you want that answer. Do not pay for twelve days of implementation to find that out.
Book the half hour that sets the size
If you have one recurring workflow and you want the guide band replaced by a size for that workflow: pick a slot and bring the file or the path.
The offer, including how the packages are described on the live page: Process Check.
Written by
Aurum Avis Labs
Builds and ships at Aurum Avis Labs. Writes here about what we learn working with founders and SMEs in the DACH region.
Related Articles
You might also be interested in these articles