abi. Clone Guide
This is the guide shown inside the app, published unchanged. It is generated from the app's own Help text, so when that changes, this page changes with it. It describes what the product does and, deliberately, what it does not.
abi. Clone builds a working model of how your organisation actually runs: every department, role and system, and the processes running between them. It is free to build by hand and it stays yours. Everything else in the platform reads from it.
The four ways things get onto the map
You can use one or all four. Each stamps where it came from, so every node on the map can be traced back to a source.
- By hand. Add a department, role, system, process, external party or AI agent yourself. Free, unlimited, no AI involved
- Interviews. Send someone a private link to a conversation with the intake agent, by text or by voice. It follows the workarounds rather than a questionnaire
- Documents. Upload SOPs, playbooks and checklists. Uploading is free; reading one into the map is a model call, so it is part of Pro and Max
- abi. Capture. An extension that records which systems somebody moves between while they work. See the Capture guide
Map, List and Intake
- Map is the 3D model. Layers show and hide people, processes, systems and external parties; filters highlight without hiding. Names can be switched off entirely
- List is the same data as a table, with the same curation actions, for when you want to work through it rather than look at it
- Intake is where interviews, documents and capture codes live, plus the Evidence list showing what each source actually contributed
Confirm, flag, broken
Anything the AI inferred is marked as inferred until a person says otherwise. Every node can be confirmed, flagged for a second look, or marked broken.
- Unaccounted software is the filter worth running first: systems somebody mentioned that are not in your official inventory
- A flagged node stays on the map. Flagging records a disagreement rather than deleting a fact
- Where two sources disagree, both are kept and the conflict is shown
Your own map, client maps and proposals
A free consultant account gets its own business map plus five client maps, as lifetime slots.
- A slot is spent when a map is created, permanently. Archiving or deleting a client map does not free one, so there is no need to tidy up
- Your own business map does not count against the five
- A proposal map is built from assumptions rather than interviews, and says so on every screen: every node is a question to confirm in discovery
- Once a client map holds real work its identity is locked, so a map cannot quietly become a different client's
Sharing what you have built
- Present hides the chrome and orbits the map, department by department
- A share link gives a read-only view. Names can be hidden on it, which is the usual choice for a client's own map
- Proposal turns ranked quick wins into a priced case for change, each line traceable to who said it