How it runs

What happens, week by week.

An automation project is judged by how much of your time it demands. Here is the real calendar for a first flow, and who needs to be available when.

A first flow, from kick-off to production

These durations are those observed on a single flow, with one or two systems to connect.

  1. Weeks 1 to 3

    Assessment

    We follow your real documents across a sample, record the exceptions and how often they occur, and check what your systems actually allow. Your commitment: half a day a week from the person who knows the process. Output: a report stating what can be automated, at what cost, and what cannot.

  2. Weeks 4 to 6

    Configuration

    Matching rules, extraction of the useful data, sign-off queue and thresholds. We work on a copy of your documents and do not touch your production. Your commitment: two one-hour sessions to settle the rules.

  3. Weeks 7 and 8

    Parallel run

    The flow runs alongside your usual handling. Your team carries on as before and compares. This is the stage that lets you say no at no cost: nothing is in production yet.

  4. Week 9

    Decision and switch-over

    We compare the results against the acceptance criteria written in week 3. If they hold, we switch over. If not, we adjust or we stop, and the assessment report stays with you.

  5. Months 2 to 3

    Review after real use

    A month of real use surfaces exceptions no sample contained. That review is planned and included in the go-live, not billed as an extra.

Why the parallel run is not negotiable

Switching straight over means discovering the exceptions in production, on real files with real deadlines. That is where most bad memories of automation come from.

The two weeks of parallel running cost your team time, and it is the only point in the project where we genuinely ask for it. In exchange, the switch-over rests on observed numbers rather than on a demo.

If the criteria are not met, stopping is a normal outcome. It is provided for in the contract and triggers no go-live invoice.

What is included, what is not

TopicIncludedOut of scope by default
DocumentsNative PDFs, office formats, scans with OCRHandwriting, forms completed by hand
ConnectorsThe systems listed in the contractInterface development on the third-party vendor's side
Sign-offSign-off queue and operations logDelegated signature, payment authority
AvailabilityMonitoring during business hours24/7 on-call, contractual uptime commitment
Historical backlogNoMigrating an existing archive is quoted separately

Request an assessment

Describe a process, we will scope it

Tell us which flow costs you the most time, which software it touches, and how many files go through each month. We reply within two working days, in English, French or German.

  • Swiss engineering
  • Reply within two working days

Email Dossivio

Describe the flow that costs you the most time and we will tell you whether it is worth automating.

Email Dossivio