Approach and limits

Instructions checked against the application, not against each other.

Documentation tools compare documents with documents. Cicerone compares your instructions with the software they describe, and shows its evidence.

Cicerone points. A person acts.

Everywhere it works, Cicerone shows which control a step refers to and a person does the clicking. It never clicks, types, or bypasses a login or CAPTCHA; it never holds a password; and it never sends screen contents to an external service. Your own person performs each step in their own session, in a test environment with placeholder data.

This is a deliberate design, not a missing feature. An operations manual is where mistakes become expensive. The safest tool is one that cannot act on your behalf, and the most useful one is the one that can show you why it said what it said.

Why we refuse to guess

Before settling on this approach we tested an AI vision model as the way to find controls on screen. It was right 20 times out of 24. The four times it was wrong, it was exactly as confident as when it was right. No threshold separates the two. In a back-office process, a tool that is confidently wrong one time in six is not a productivity tool.

So when Cicerone is not sure, it says so. It offers the most likely candidates rather than one answer, and any step it cannot check safely is reported as not checked. A blank is more useful to you than a confident mistake. Agents will get better at acting; someone still has to certify that the instruction was right in the first place. That is the layer Cicerone builds.

A procedure you own

Every procedure Cicerone checks, guides or writes is held as a portable navigation script: a plain file, readable by people, that names each control by what a person sees on the screen. Hidden technical selectors are treated as hints, never as the truth about which control is meant. The same script is checked and kept current by Owner, guided by User and written by Author, and it is yours, not locked inside a vendor's tour builder.

Limits, by design

We would rather you read this list here than discover it in a session.

Start here

Check my manual

A 90-minute documentation audit. One manual in; a findings report, line by line, that you can forward out. Three design-partner audits are free before anyone is charged.

It starts with a 20-minute call. The 90-minute session is arranged after it, once we have converted your manual's file format ourselves. Three questions decide whether the session is worth your time:

  1. Does the system run in a web browser, as a Windows desktop program, or through Citrix or a remote desktop?
  2. Is there a written manual, and in what format?
  3. Is there a test environment with placeholder data?

Book a 90-minute audit Email instead

You will hear back from Akinwande Cole personally within one working day, with a time or a reasoned no.