Measure the bottleneck first.

It is a paid measurement engagement for one bottleneck. We define the workflow boundary, KPI, current performance, exception types, problem cost, systems, and access needs, then hand you a fixed Launch scope. You keep the pack either way. If the same workflow proceeds to Launch with Svolta, the Launch price already includes that scoping work.

Workflow Scoping includes the process boundary, normal and exception paths, primary KPI, measurement window and method, current-state evidence, problem-cost assumptions, system and access needs, human approvals, and a fixed Launch scope. It is a decision-ready pack, not a maturity scorecard.

Workflow Scoping measures the current KPI and sets a conservative minimum before Launch. We do not apply another client's percentage to your operation. The production workflow handles the repeat path; your team keeps exceptions, approvals, and judgment calls.

If you have a senior technical team with real delivery and production-support capacity, build it. You have the domain knowledge and records; Svolta brings workflow measurement, integrations, exception design, quality checks, and production operation. Workflow Scoping is useful either way because it gives either team the same boundary to build against.

Unusual integration or security constraints, a non-standard deployment pattern, or more than one workflow launched in parallel can make an engagement custom. Workflow Scoping makes those constraints explicit before Launch is priced. New workflows, features, or integrations after acceptance are separately scoped rather than absorbed into Maintenance.

Book the free 30-minute fit call first. Bring one workflow, its weekly volume, the systems it touches, and the person accountable for the result. We tell you whether it is measurable and whether Workflow Scoping is worth running. If the fit is wrong, we say so.

Every Launch is accepted against the KPI, measurement method, quality checks, access, data, and decision obligations agreed from Workflow Scoping. Any Capacity Guarantee is conditional on those signed terms; the proposal, not a general website claim, is the authority. You keep the Baseline Pack whether or not you proceed to Launch.

Yes. Workflow Scoping is a standalone engagement and the Baseline Pack is yours to keep. You can use it with your own team, another vendor, or no one. If the same workflow proceeds with Svolta, the Launch total includes all scoping expenses for that workflow.

Workflow Scoping is usually 1 to 2 weeks. Launch timing depends on the integrations, data, exception path, and acceptance scope defined in that Baseline Pack. The target is the first measured improvement 14 to 30 days after the production thin slice goes live, not a blanket promise that every complete Launch ships in 14 days.

Workflow Scoping exists to define one workflow, its evidence method, integrations, exceptions, and acceptance boundary before a build commitment. Workflow Launch is then offered at a fixed price against that scope, so your team can evaluate a named deliverable and number instead of an open-ended day rate.

Workflow Scoping and Launch are fixed-scope engagements, not seat licences. AI Accelerator is a monthly support engagement for the accepted production boundary; notice, included usage, and support terms are written into the agreement. New features and material changes are separately scoped. You own the pack and accepted build deliverables under the signed terms; Run is ongoing production value, not a data or code lock-in.

The Consultation is a 30-minute fit check around one workflow. Workflow Scoping is the paid evidence engagement: we document the current state, agree the KPI and measurement method, map systems and exceptions, and return a fixed Launch scope. The Baseline Pack is a deliverable you keep; the Consultation is not a substitute for that fieldwork.