Datapraxis
A keyboard under working hands on a Tallinn office desk at three in the afternoon, cold window light raking across a printed sheet and a mug.

Datapraxis OÜ · pilootprojekt, worked in the open

How does a small AI pilot run?

A short, bounded test with review baked in. The sequence from first email to closing notes — what we ask for, what you check, and when to stop.

The path though this page

  1. 01 Describe one recurring task
  2. 02 Agree scope, review, stop rule
  3. 03 Run the pilot with your material
  4. 04 Weekly review, correct, log
  5. 05 Closing notes and one next step

Before any setup

The first email, the talk, and the brief that comes out of it

Datapraxis OÜ keeps this step small on purpose. Nothing runs before the scope is written down and you have agreed what would make us stop.

Step
What happens
Who moves

Introduction

Step 01 · replies within one working day

First email: describe one task

Write to [email protected] with one recurring task, who does it now, and what good output looks like. Add volume per week and where the source material lives. Two paragraphs are enough. We reply to arrange an introductory consultation — no extra fields, no automatic anything.

You write

Fit

Step 02 · a short written scope, not a proposal

Introductory talk: scope and fit

We discuss inputs, outputs, and who reviews drafts. We ask about the andmekaitse scope and any sector limits that apply to your team. If the task needs legal review, we say so early. If a different tool pattern fits better, we point to it — that answer is still useful to you even if it is not our work.

Both

Setup

Step 03 — where the red tab sits

Setup runs with your own material

Only the sources the scope names get connected. For knowledge-heavy work the set is cleaned first — structuring facts, flagging contradictions, scheduling the reviews that keep the set honest. For support work, the help articles are updated before anything is connected, because a workflow repeats whatever the knowledge base says. The test runs in a separate folder or inbox view so live queues stay clean.

Live now

The pattern is the same for Tallinn offices, county offices and a two-person ecommerce team: one task, one source set, one stop rule.

Why this shape

One checklist fits every pilot in a small market

Estonian teams often hire advisory help to frame the question before they buy anything. Whether you work with us, with another studio, or entirely in-house, the same three lines keep a pilot honest: data sources, review routine, stop rule. Put those three on one page and you have your brief.

  1. Two figures in winter coats waiting at a snow-edged tram stop in Tallinn at dusk.

    01

    Data sources

    Say where the input lives today and who owns it. If nobody owns it, that is the first thing to fix.

  2. A half-plowed county road in Estonia in winter lined with bare birches under a low grey sky.

    02

    Review routine

    Name who reads the drafts and when. One weekly slot in the first month beats a monthly meeting you keep postponing.

  3. A red-brick municipal building in an Estonian town in winter with windows lit at three in the afternoon.

    03

    Stop rule

    Write down what would make you pause. Corrections staying flat after source cleanup is a real signal to change the scope.

  4. A lone wooden power-line pole standing in a flat snow-covered Estonian field in winter with a long low shadow.

    04

    Then walk it

    The brief is three lines on one page. Everything else in this folder is you choosing where to start.

After setup, two shapes

Contact coverage, or grouping — pick the one you can review weekly

The two patterns most small teams start with. Neither replaces the review routine you wrote in the brief — both depend on it in the first month.

A headset on a hotel reception counter in Tallinn's old town beside a keyboard and a small shift sheet.

Contact coverage

Pick this when you miss enquiries rather than when your drafts are wrong. A voice workflow answers calls, checks availability, manages a reservation, and hands a complex case to staff instead of improvising. The weekly job is simple: listen to the handoffs, correct the ones that missed, log the date.

Grouping and themes

Pick this when you cannot set priorities because the feedback is in too many places. A grouping workflow reads tickets and surveys and returns themes linked to usage, so the weekly meeting has something concrete to rank. The weekly job: check the theme boundaries, correct the misfiled ones, keep the same log.

Both need
A weekly review slot in the first month, with corrections logged by date.
Neither needs
A new tool on day one. Both can begin in a separate folder or inbox view.

Two more variants worth knowing

Varied stock, or approval steps — two shapes with their own review rules

Both are still pilots. The difference is what you have to check before the output goes live.

Unlabelled small products laid out on a white sheet in a small ecommerce backroom, ready for photographing.

Listing drafts

One product line, one photo standard

For shops with varied stock, a pilot can draft listings from photographs and produce search-friendly descriptions, aggregated from research rather than invented from nothing. Two things have to be in writing first: the photo standard and the verification checklist. Keep the test to a single product line so the corrections stay readable.

A wooden tray of folded printed pages beside a pen and a closed notebook on an office desk in Tallinn.

Governed packs

One procedure, one written approval chain

For offices with approval steps, a pilot can assemble documents that still pass through a written chain — policies, named approvers, and the execution step kept separate from the drafting step. Nothing leaves the pilot until someone with the authority says yes. Keep the test to a single procedure.

Both need one more thing in common: someone who can pause the pilot for a week without the whole team losing their place.

Review rhythm and stop rule

Corrections are the score — not fluency

Experienced users judge a pilot by correction trends, not by how confident the output sounds. That is why the log is short and the meetings are short.

When
One short meeting each week during the first month — same slot, same people, thirty minutes is enough.
What you look at
Drafts produced since the last meeting, the corrections you made, and the source that caused each one.
What you decide
Whether the corrections are falling. If they are, keep going. If they are flat, clean the source or change the scope.
An empty Tallinn office corridor in winter at three in the afternoon with daylight falling at the far end.

Closing notes and next steps

What you get at the end, and what you do with the log

The pilot ends on purpose. You get short notes: what was tested, what changed, what to keep. Limits are stated plainly. To continue, you send the log and the next question.

Reference half · a pilot you could run next month

One task, one source set, one stop rule

Any of these patterns can start as a bounded pilot. Send the four columns of your log — date, sample, issues, source fixed — plus the next question you want tested, and we will say plainly whether it is a pilot or not.

Reference · Datapraxis OÜ pilot brief template · 01 page, 4 columns · no automatic renewal or hidden follow-up sequence

Ask about a use case

Write to [email protected] with two paragraphs and the log if you have one.

Keeping this page current

The same routine as any pilot: dated changes, source-led corrections, a stable address.

This explainer is maintained the way we ask you to maintain a pilot brief: when a programme name or a product function changes, the sentence is adjusted and the date is noted here. Broken links are replaced, not redirected into nothing. If you spot something that no longer matches reality, write to [email protected] and it gets corrected at the source.

Last reviewed · November 2026

Office hours · Monday to Friday, 9:00 – 18:00

Pärnu mnt 22, Tallinn 10141