Situations you will recognize.

These typical scenarios describe situations we encounter and how we handle them. They name no client. Their purpose is to help you place your own situation, not to impress you.

Submit your situation

typical scenario · digital identity

A civil registry that no longer depends on paper

The situation

A municipality issues certificates from paper registers, some of them damaged. Requests arrive at the counter, searching is manual, and duplicates are frequent.

What is blocking

No one knows how many records are actually usable. Every copy requires finding a register, then a page, then copying it out again.

What we do

Inventory of registers, prioritized by condition
Digitization and indexing checked by double entry
Single index linked to the person’s digital identity
Staff access by role, with a log of every consultation

What we measure

Time to issue a certificate
Share of records indexed and verified
Rate of duplicates detected

typical scenario · one-stop shop

A tax one-stop shop that never asks for the same document twice

The situation

A company files its returns, financial statements, and certificates with several administrations, each with its own form.

What is blocking

The same information is entered four times. An error in one blocks the others, and no one can see where.

What we do

Mapping of procedures and the documents actually required
Common company reference record, populated only once
Connectors between existing tools rather than a replacement
Tracking board shared between the user and the administration

What we measure

Number of entries per procedure
End-to-end processing time
Rate of incomplete files

typical scenario · cybersecurity & compliance

A software vendor facing a large customer’s security audit

The situation

A software vendor signs with a large organization. The contract requires a security questionnaire, a penetration test, and a path to ISO/IEC 27001.

What is blocking

The practices exist but are not written down. The questionnaire has several hundred questions, and the deadline is contractual.

What we do

Gap review against the required standard
Penetration test targeting the application and its hosting
Policies and records written from what is actually done
Team training (ISO/IEC 27001 Lead Implementer)

What we measure

Critical gaps closed before the deadline
Vulnerabilities fixed and retested
Questionnaire coverage by evidence

typical scenario · enterprise AI

AI agents in production, without losing control

The situation

A management team wants AI agents to triage incoming requests and prepare replies.

What is blocking

Trials work in demonstrations, but no one can explain a decision or stop it cleanly.

What we do

Written scope: what the agent can do, what it cannot do
Log of every decision and human approval at sensitive points
Bounded pilot with stop criteria set before starting
ISO/IEC 42001 standard as the governance framework

What we measure

Share of requests handled without rework
Response time
Contested decisions and reasons

typical scenario · expertise neutrality

An SME responding to a public tender

The situation

A technical SME spots a public tender in its field but has never responded to this type of contract.

What is blocking

The specifications are long, the criteria are weighted, and the technical proposal does not show what the company can really do.

What we do

Reading the criteria and their weighting
Comparison with similar public programs
Technical proposal structured around the available evidence
Neutral review before submission

What we measure

Administrative compliance of the file
Technical score achieved
Preparation time

Typical scenarios built from observed situations and public frameworks. Any resemblance to a specific organization reflects recurring problems, not a client case.

Does your situation look like one of these?

Book a demo Write to the team