Geist builds a living model of your company: its processes, sites, suppliers and teams, connected to your systems and to what happens in the world. When something changes, you see what it touches and what to do about it.
Example scenarios on a fictional company network. A delayed feeder vessel with bearings for Kassel Pump Plant leads to a proposal to pull bearings from Lyon DC. The inbound logistics team transfers 2,400 bearings, and line 2 keeps running. A critical gateway advisory leads to a patch window and a temporary route for order intake. Possible approval bypasses in Brno lead to holding 14 purchase orders for second approvals. A power price spike leads to moving heat treatment to night shifts. Each proposal becomes a ServiceNow incident that the responsible team works and resolves; write-back covers ServiceNow incidents only and is in beta.
An illustrative workflow, not a customer case study. Start with a signal, examine the process and choose a response. Your team connects the steps, using the sources you have configured.
A port disruption appears near a supply route. In Horizon, inspect the signal alongside your sites and routes, then check which suppliers need attention.
Horizon · WatchpointsOpen the receiving model in Blueprint. Ask Wisp to draft an exception path for delayed deliveries. In Review mode, inspect the proposed batch before accepting it.
Blueprint · AI draftWith a relevant event log, compare process variants and waiting times. Use the evidence to decide whether the receiving process needs a different approval or handoff.
Blueprint · AnalysisReview a proposal in Wisp with its evidence. Apply the agreed change in Blueprint or Horizon, then watch for new signals. Actions in external systems depend on the connector and permissions you have configured.
Wisp · InboxWisp builds the model group by group and highlights each group on the canvas. Everything from one request arrives as one batch, which you keep or undo.
How Blueprint worksConnected feeds send events all day. Wisp checks each one against your sites, suppliers and open orders, and the ones that matter arrive as proposals with the evidence attached. You decide which proposals to act on.
Meet WispDescribe the dashboard you need, and Wisp builds it from your event log: key figures, cycle times, bottlenecks. Explain this chart then puts a chart into words and lists the evidence.
How analytics worksProcess models and business data come in, agents build documents with the models you choose, and approved changes go back out.
Ask Wisp for a board deck, an audit report or a cost model. Agents work from your process models, event logs, files and research, then build native PowerPoint, Word and Excel files in your own company templates.
Use the providers your company already trusts. Pick a model for each tier and Geist routes every task to the right one.
Solution pages and articles on the processes we hear about most.
Pick the process that costs you the most time or risk. We run it through Geist with you, on your data, and you leave with five results you can act on.
What to bringAn event log export (CSV or XES) gets you all five. Process documents or an existing BPMN file work too. No data yet? We start from demo data.
Why we built Geist.
Process diagrams, system records and improvement decisions often live apart. We are building Geist to bring them into the same working context, so teams can trace a proposed change back to the evidence behind it.
Meet the company →
