Documentation that knows when it's wrong.
Cicerone checks whether your written procedures still match your software, guides your people through the ones that do, and shows the evidence.
If you own the operations manual after an ERP, CRM, HRIS or finance-system change, you know the pattern. Buttons move. Labels are renamed. Access rules change. Screenshots go stale. Someone follows a step, it no longer works, and that is how you find out. Cicerone tells you first.
What it does for you
-
After a system change
Your core system was upgraded or replaced and the manual was written for the old one. Cicerone shows which lines no longer match, line by line, so you fix what is wrong instead of rewriting everything.
-
New joiners, guided at the point of work
People follow the checked procedure inside the application itself, one step at a time, instead of stopping work to search a document or ask a colleague the same question again.
-
No manual, or one nobody trusts
Cicerone writes the user manual from the application, with every procedure checked from the start, and brings an old manual up to date the same way.
-
Evidence your reviewers can check
Every finding comes with what Cicerone saw and why it decided, so IT, security and process reviewers can check its work rather than take its word.
Three offerings, one for each role
One for the person who owns the manual, one for the people who follow it, and one for the person who writes it. All three work from the same checked procedures.
-
For the manual’s owner
Cicerone | Owner Check the manual and keep it current
Point Cicerone at your manual and the application it describes. Back comes every line that no longer matches, with its line number and the evidence behind it. When the software moves, Owner proposes the correction; you approve it, and what passes is published to your people.
-
For the people who follow it
Cicerone | User Guide your people
Your people open the application and a small card names the next control and shows where it is: the exact step you checked and published. They click; the card moves on. It never clicks or types for them.
-
For the technical author
Cicerone | Author Write the manual from the app
Start with nothing but the application. Cicerone writes the user manual from it, every procedure checked from the first draft with the evidence behind each step, and brings an old manual up to date the same way.
Where it works
- Browser applications
Web-based business systems, in your people's own Chrome or Edge and their own signed-in session. - Windows desktop applications
Office, standard Windows programs and dialogs, and a web page that forms one step of a desktop task.
Not covered: Citrix or remote desktop, CAD, and drawing or diagram canvases. They show a picture of the software with no named controls, so there is nothing reliable to point at.
What it never does
- It never clicks, types, or bypasses a login or CAPTCHA. Cicerone points; a person acts.
- It never holds a password, credential or two-factor code.
- It never takes a production create, delete, submit, invite, publish, export or billing action. Sessions use a test environment with placeholder data.
- It never sends screen contents to an external service. Where your manual's text goes is on the data handling page.
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:
- Does the system run in a web browser, as a Windows desktop program, or through Citrix or a remote desktop?
- Is there a written manual, and in what format?
- 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.
Talk to us about the platform
Have a written manual and want to know where it stands? Book the audit. Looking at guided procedures for your people, a manual written from your application, or a Windows desktop application? Tell us which, and we will talk it through.
Request access (Tally, no name needed)
Answers are kept at the named provider or in our inbox, never in a system we build. Role is useful; name and company are not asked for.
Which would you use first?
One question, anonymous. It tells us which problem matters most to the people who read this page.