You don't buy a platform and hope. You start with a free mapping session, validate one workflow in a paid pilot, then scale into an operating department. This page explains each step — and defines exactly what a "workflow" is, so you know what you're buying.
In a free 60-minute session we identify three candidate workflows, the data behind them, and whether Solace is a fit. You leave with the map whether or not you continue.
In a paid pilot we stand up your private tenant, connect your systems, deliver day-zero data, and activate one real workflow end-to-end — with evidence and one owned artifact.
Your department takes on more workflows over time. As a workflow proves out, the recurring reasoning is compiled into deterministic code you own, and cost per outcome falls.
A common question — here's exactly what's included in each.
If a chosen workflow can't be activated in the pilot, we tell you plainly and we don't advance it. Exact scope and any timing commitments are written into your pilot order.
Plans are priced by workflow (Foundation includes up to three; Department and Network include more). So a workflow needs a precise definition. Each one your department runs is specified by:
What starts it — a schedule, an event, an inbound message, or a manual kick-off.
The data and systems it reads from.
What it produces — a message, a record, a document, an action taken.
A stated band (e.g. per day / per week) so scope is bounded.
The platforms it touches, under delegated access.
Which steps run autonomously and which pause for a human.
What gets recorded to your audit trail.
The upkeep included as the workflow runs.
What's explicitly out of scope, so there's no ambiguity.