AI pilot: a scenario test on your data

A pilot answers one question: does the scenario deliver an effect on your data. In eight weeks you get a prototype, a before-and-after measurement, an economics report, and a scale recommendation.

We build a working prototype of one AI scenario in 6–10 weeks and hand over the metrics for a launch decision.

Pricing

from ₽700,000

per project

This is the lower bound of a project. We scope the exact quote after a brief: it depends on volume and the number of integrations.

What's included

Capabilities

One scenario

We take a process with a clear owner and a measurable result. The pilot covers one scenario, one data loop, and up to six integrations so the team reaches the measurement inside eight weeks.

Metrics before the start

In week one we record the baseline: time per operation, processing cost, error rate, and the volume of manual work. The same metrics become the acceptance test for the prototype.

Data and access

We check two sources, the access rights, and the record quality. When the data is thin, we add manual labeling for 300–500 examples and record the assumptions in the report.

Launch decision

At the end you get a recommendation: scale the scenario, rework the loop, or close the hypothesis. The decision rests on the measurement, the economics, and the risk list. The demo shows the numbers and the next step.

How we work

From request to result

  1. 1

    Framing

    We meet the process owner and record the goal, the boundary, and the metric. The output is one page with the hypothesis and the success criterion.

  2. 2

    Data

    We collect exports from two sources, check completeness and access rights. We mark the gaps and decide which examples we add by hand.

  3. 3

    Build

    We assemble the prototype in your environment or in our cloud. We connect up to six integrations and set up an action log for review.

  4. 4

    Measurement

    We run the scenario on historical data and on the live stream. We compare the result with the baseline and prepare the report for the decision.

Who it fits

Check if it fits you

Good fit

  • A process owner exists

    The process has a manager who owns the metric and can assign two specialists for interviews and acceptance.

  • Data in two systems

    The records already live in a CRM, an ERP, or a task database. Read access saves two weeks of approvals and lowers the preparation cost.

Not a fit

  • The team is shipping a release

    A pilot needs three to four hours per week from the process owner and an analyst. With a tight schedule, the start moves to the next quarter.

  • The budget is already committed

    A RUB 700,000 project is easier to approve as a separate line. When the budget is closed, start with a readiness audit and return to the pilot.

Track record

What you get

1

One scenario

The pilot takes one scenario to a working prototype. The report shows the loop boundary and the integration list that came with the delivery.

4

Four metrics

Four metrics: operation time, cost, error rate, and manual work. The comparison runs on your data in the same loop.

8 wk

Eight weeks

The standard pilot runs eight weeks from the kickoff to the demo. The calendar covers the build, the measurement, and the report.

Scope of work

What the delivery includes

Pilot report

The report holds the hypothesis, the baseline, the measurement result, and the economics. Assumptions and limits sit next to every number.

Working prototype

The prototype runs the chosen scenario on your data and writes an action log. The code and the deployment guide go to your team.

Metrics pack

The pack includes a dashboard with four metrics, the calculation method, and a control plan for the launch. It shows how the scenario behaves in daily work.

How it works

How the system is built

  1. Pilot loop

    We build the loop from your sources, the model, and a verification layer. The loop runs on historical data, then on the live stream, and the log records every step for review.

  2. Metrics

    The metrics are fixed before the prototype build: the baseline and the target. After the launch we compare the operation time, the cost, the error rate, and the manual work on one sample.

  3. Decision

    The team puts the measurement, the economics, and the risks into one table. At the demo you see the scenario in action, the numbers, and the recommended next step, then decide on scaling.

Limitations and cost

Where the solution pushes back

  • 01

    One scenario

    The pilot tests one scenario and one data loop. A second scenario needs a separate build, a new measurement, and its own estimate.

  • 02

    Timeline and budget

    The 6–10 week timeline depends on export readiness and the number of approvals. Every week of delay on the client side moves the demo and the final report.

  • 03

    Data access

    Access to the sources sets the start speed. A two-week export delay moves the prototype build and the measurement date.

Budget estimate

Cost calculator

This is an indicative range, not a quote. We scope the exact estimate after a brief: it depends on volume and the number of integrations.

Additional scenarios

0

Data preparation

Integrations

0

Pilot timeline

Add-ons

Support

Year one: updates and monitoring, a reply within 2 business days.

Service

AI pilot: a scenario test on your data

The estimate covers our team's work. Hardware, third-party service licences and travel are added on request.

Estimated cost

₽700,000

Timeline

6 wk

Pilot timeline

8 weeks

Questions

Frequently asked questions

What does a pilot cost?

The base price is RUB 700,000 for one scenario and one data loop. Each integration adds RUB 80,000, an additional scenario adds RUB 150,000 and two weeks, and extended data preparation adds RUB 120,000.

How long does it take?

The standard timeline is eight weeks. A six-week option fits ready data, while ten weeks cover two loops and access approvals.

Who works on the client side?

A process owner, an analyst, and a data engineer. Together with our team they run interviews, check the exports, and accept the result at the demo.

What do we need to start?

A process description, access to two sources, and the owner's contact. On the call we settle the metric and the integration scope, then fix the estimate.

What happens after the pilot?

You receive the report, the prototype, and a scale plan. Your team can move the loop to internal development or run the rollout as a separate project.

Ready to discuss your task?

Leave a request – we'll get back with a proposal and a preliminary estimate.

Contact us