Processes · Modelling and automation

Measure where work stalls, then automate that step.

We model the real process from how the team works and the records that already exist. With the time each stage takes, we see where work piles up and automate where it pays off most.

01Process modelled with its exceptions
02Time per stage in view
03Automation where it pays off

Fields of application

Processes fail at the handoffs.

Each person usually does their part well. Work gets lost or sits waiting when it passes from one hand to another, and that leaves a trace in the dates.

01

Process modelling

With the people doing the work, we map stages, handoffs, rules and exceptions. The real process rarely matches the documented one.

02

Rules and exceptions

We also design the exceptions, such as missing documents or returned work. That is where processes usually break.

03

Automation

We automate the step that takes the most time with rules, integrations between systems or a web or desktop app. If what you use covers almost everything, nothing gets built.

04

Process analysis

With dates for each stage we calculate how long a case takes, where it waits and which different paths it follows. Work often waits where the team does not expect.

05

Targeted AI

Sorting requests or reading documents, with human review.

06

Permissions

Each person sees only what they should, and every change is recorded.

How we work on a process

Model, measure, and only then automate.

Automating a poorly understood process only makes the mistake faster. So we understand the timings before choosing what to automate.

01

Discovery

How work happens today: spreadsheets, email and systems

02

Model

Stages, handoffs, rules and exceptions

03

Measurement

Time per stage and where work piles up

04

Automation

Rules, integrations or custom software, with permissions

Simplified representation with simulated data. Tools and stages are defined for each process.

Typical processes

Where a process gets stuck, and what changes when it is fixed.

Five common processes. In each, the useful change comes from recording or automating one specific step.

Example processes

Monthly accounting close

  1. 01Documents
  2. 02Recording
  3. 03Review
  4. 04Filing
  5. 05Close
Where it gets stuck
Late documents, and nobody knows client by client what is missing.
What gets organised
Every stage has a recorded date, so you can see which clients delay the close and at which step. This is the Contabilidad San Vicente case.

Costs, infrastructure and maintenance

Before adding a tool, we review what you already pay for.

And once it is in place, it is clear who maintains it.

WHAT ALREADY EXISTS Spreadsheets Email Accounting system Cloud storage Licence DUPLICATE Per-user plan UNUSED Process ON WHAT EXISTS Maintenance AGREED BackupsMonitoringUpdatesSupport
  1. 01
    Inventory first

    We review systems and licences before recommending anything.

  2. 02
    Total cost

    We compare building and maintaining, not just building.

  3. 03
    Agreed maintenance

    Backups, updates and who responds when something breaks.

A practical question

Which stage is each task at, and who owns it?

If answering means checking spreadsheets or asking over chat, the process depends on people's memory.

A DECISION WE CAN REVIEW To do In progress Done WORKFLOW RECORD To do In progress Done TASKS PER STAGE · SIMULATED DATA
Conceptual scene · no client data or results

What your team can review

  1. 01

    The process as it happens today

    Stages, handoffs and where information gets lost.

  2. 02

    The agreed process and its tool

    Validated with the people who will do the work.

  3. 03

    A record to adjust with

    History and data to fix stages.

Common difficulties

What worked with three people stops working with ten.

Frequent symptoms when a team grows but keeps coordinating the same way.

  • 01

    Several versions of the same spreadsheet

  • 02

    Important email in the inbox of someone on holiday

  • 03

    At month end, people ask over chat what is missing

  • 04

    The process depends on one key person

  • 05

    Salaries in files the whole team can see

Before we talk

A useful starting point.

You do not need to arrive with a tool selected.

01

Which process is hardest to coordinate?

A monthly close, a procedure or client requests.

02

Where does the work live today?

Spreadsheets, email, systems or WhatsApp groups.

03

What needs restricted access?

Salaries, personal data or financial information.

A related caseContabilidad San VicenteAccounting and payroll with stages, owners and history in a dedicated system.

Let's talk

Tell us which process is hardest to coordinate.

We will tell you whether to organise the process, connect tools or build something of your own.

Let’s talk