Map three workflows. Prove one. Grow from there.
You don't buy a platform and hope. You start with a scoping conversation, validate one workflow in a paid $2,500 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.
Three steps, in order.
Map
In a scoping conversation we identify three candidate workflows, the data behind them, and whether Solace is a fit. That conversation is not a free service tier.
Prove
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.
Grow
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.
Conversation vs. paid pilot.
A common question — here's exactly what's included in each.
Scoping conversation
- Discuss your goals and current stack
- Identify three preliminary workflow candidates
- Review the data sources we'd draw on
- An honest recommendation on whether Solace fits
- You keep the 3-workflow map either way
Technology Department Pilot
- Validate the workflow specification
- Configure your private tenant
- Connect your systems
- Deliver day-zero data
- Activate one workflow, live
- Produce the evidence trail
- Build one artifact you own
- Deliver a 90-day roadmap
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.
What one "workflow" means.
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.