How is a demonstration different from a VSA Fast Pilot?

A demonstration shows possible VSA behaviour on a limited example. Fast Pilot validates one agreed process, one data source and measurable success criteria in Shadow Mode with human approval.

When is a production VSA Instance launched?

A VSA Instance is launched after the pilot confirms value, operating boundaries, approved knowledge sources, integrations, human responsibility and the required support scope.

What does VSA Care include?

VSA Care covers maintenance, monitoring, updates, backups, diagnostics, availability control, incident handling and agreed development of the active instance.

What happens to data when the service ends?

Access to the instance is disabled and export, retention or deletion is handled according to the agreement, the defined retention period and applicable law. Client data is not moved into another client’s knowledge base.

Controlled deployment

Prove value first. Launch a managed production instance only when the numbers support it.

The client does not buy the VSA source code. The service provides access to a dedicated instance, VSA Connect, Dashboard and agreed modules for the duration of the active service.

See the 14-day Fast Pilot Calculate process value

Model

Fast Pilotone process

Instanceproduction environment

Caremaintenance and development

VSA Fast Pilot — 14 days

One process. One data source. One GO / NO-GO decision.

The pilot is not a free demo. It is a controlled experiment on one operational bottleneck, using Shadow Mode and Human-in-the-Loop.

Days 1–3

Process isolation

We select one process and one sample from the previous 30 days: enquiries, technical requests or a defined document set.

one process owner
one controlled data source
dedicated VSA micro-instance in Shadow Mode

Days 4–9

Shadow Run + Human-in-the-Loop

VSA prepares a System Proposal. The operator makes the Operator Decision: approve it or change a parameter.

nothing is sent to the customer autonomously
time and corrections are measured
operator decisions are recorded

Days 10–14

Metrics and decision

We compare time before and during the pilot, the correction rate and proposal quality. The pilot ends with a decision, not an obligatory purchase.

operation time before / during pilot
approval and correction rate
GO / improve / NO-GO

Process Value Engine

Before the pilot, calculate whether the process is economically worth automating.

The calculator estimates current manual cost, recoverable time and net monthly value after the VSA cost is included.

Calculate the process Submit a Fast Pilot request (PL)

Service definitions

Fast Pilot, Instance and Care have different jobs.

Each stage answers a separate question: does the use case work, how does it run in production and how is it maintained afterwards?

VSA Fast Pilot

A controlled 14-day validation of one process before a production instance is launched.

Submit a process for Fast Pilot (PL)

VSA Instance

An isolated platform instance assigned to one organisation with its Dashboard, communication layer and active modules.

Discuss a production instance (PL)

VSA Care

Maintenance, monitoring, updates, backups and agreed development of the active instance.

Define the support scope (PL)

Full path

Five stages without a blind jump into production.

Every stage ends with a concrete output and a decision on whether to continue.

Measurement

Free tools and diagnostics identify technical issues, knowledge gaps and automation potential.

Demonstration

A private demonstration of VSA behaviour on example or tightly limited data.

VSA Fast Pilot

A controlled test of one process, success criteria, responsibility and operating boundaries.

VSA Instance

Activation of an isolated instance, VSA Connect, Dashboard and agreed modules.

VSA Care

Monitoring, updates, backups, diagnostics and agreed development of the production instance.

VSA Fast Pilot

The pilot must prove value, not imitate a complete product.

The scope is deliberately narrow. We define inputs, operating boundaries, error scenarios and measurable success criteria before the Shadow Run starts.

a specific process and a client-side owner
limited approved knowledge or test documents
metrics: completeness, time, effectiveness and hand-off quality
decision: stop, improve or move to production

Example criteriameasured before and during the pilot

01Handling timeminutes saved per process02Completenesswhether the case contains required data03Effectivenesshow often the process reaches the correct outcome04Safetywhether boundaries and escalations are respected

VSA Instance

What the client receives after production launch.

The exact scope follows from the pilot. The platform core remains operated and controlled by Vis-Sol.

Dedicated environment

Own tenant, configuration, data, logs, rules, modules and communication channels.

VSA Connect

A widget or endpoint connected to the correct instance through controlled routing and origin checks.

VSA Dashboard

Views for knowledge, imports, conversations, leads, reports, widget and client-accessible settings.

VSA Care

Monitoring, updates, diagnostics, backups, limit control and incident handling.

Module development

Additional processes can be added without transferring VSA Core source code to the client.

Access control

Activity state, validity period, limits, roles and settings exposed by the Vis-Sol administrator.

Short answers

Common questions about VSA deployment.

Technical scope and data-handling rules are confirmed before a pilot or production instance starts.