Your clicks become a process diagram.

Process documentation describes HOW work gets done across people, systems, and decisions — the end-to-end flow including handoffs, branching, and exceptions. An SOP is a focused subset: a step-by-step procedure for one specific recurring task within the larger process. A new-hire onboarding *process* might include 5 SOPs (account provisioning, equipment ordering, training, etc.) plus the connective tissue between them. InstaGuide handles both: capture an SOP-level walkthrough and the Visual Process Flow shows where it sits in the larger process map.

Visio and Lucidchart make you draw the process by hand — boxes, arrows, swimlanes — which means the diagram is decoupled from the actual work happening in your apps. InstaGuide generates the Visual Process Flow diagram from the clicks you actually performed, so the diagram is always accurate to the underlying workflow. When the process changes, you re-capture (not re-draw), and the diagram updates automatically.

Yes — this is one of InstaGuide's strongest use cases. The Desktop App captures clicks across any native application (Mac and Windows), and the Chrome extension captures any browser-based app. AI-detected app changes group steps by domain in the Visual Process Flow so cross-app workflows visually break out by tool, making handoffs explicit. Most competitor tools only capture browser flows, leaving the desktop steps undocumented.

Three things make in-sync documentation realistic: (1) Edit step text inline — no need to re-export to a Doc. (2) Re-capture a single step that changed without redoing the whole process. (3) The Guide Change Audit Log tracks every edit with timestamp and actor (Pro+), so process owners can be held accountable for reviews. Without these, documentation goes stale within months. With them, teams keep processes accurate quarterly.

Yes — included in both PDF and HTML exports. The diagram renders with domain-grouped columns, color-coded event nodes, and app-change indicators. PDF auto-switches to landscape orientation when the diagram is wide. HTML exports include an interactive flowchart that consumers can click through to jump to the corresponding step.

Yes. Organization plans support Project folders + custom roles (Admin, Editor, Viewer, or any custom role with granular permissions per project). Share specific guides with view-only access for stakeholders, edit access for process owners. Audit log records who changed what. Enterprise plans separate Builder seats (people who create) from Viewer seats (people who consume) so onboarding 100 viewers doesn't cost 100× the bill.

Yes — see our Scenarios page for real captured examples covering Google Workspace, Microsoft 365, Slack, Salesforce, Jira, and Notion workflows. Each is a complete process walkthrough you can use as a reference or starting point for your own.