AI Analytics Use Cases · on-site workshop for analysts

AI workshop for analysts: agents that explain why the numbers moved

When finance asks why a number moved, the answer usually waits in the analytics queue until after the meeting it was for. In one day your analysts and business teams build three AI agents that find the cause, set it against a benchmark and draft the next action for a person to approve.

The workshop at a glance

Format

One day at your office

Who

Data analysts and BI developers, analytics managers, and the finance or commercial leaders who use the answers

Fee

From EUR 9,000. The cloud environment, travel inside the EU and the UK, and 30 days of Microsoft Teams support are included

Data

Our cloud environment with a synthetic dataset. Your production systems are untouched

Engineers or a mixed data team? See the workshop for data engineers or Data AI in a Day.

What governed finance data and AI did at a global professional services group, and the day itself

13,400estimated hours a year handed back, with AI writing the quarterly variance commentary in production
Minutesto answer "which ten clients generate the most revenue?" on the governed ledger, down from weeks
3scenario agents on the day, and each participant leaves with a working agent for their own question
€9,000starting fee for one day on site, with 30 days of Teams support
The day

Three agents, each from question to drafted action

AgentWhat it does in the workshop scenarioThe action it drafts
Receivables root cause

Overdue receivables jump 35% in a month. The agent breaks them down by client, region, ageing bucket and payment terms, finds the two clients behind most of the rise, checks their invoice history, flags a payment-term change nobody approved and compares DSO with its six-month average.

Follow-up emails to account managers, with the invoice data filled in

Revenue against the market

The agent splits revenue growth by category, region and channel, sets it against external category growth rates, separates real outperformance from a market tailwind, and finds fast-growing segments where the company is barely present.

An opportunity brief posted to Slack and a calendar invite for the category review

Supply disruption

When a supplier cannot deliver, the agent maps the affected products, stock and production schedules, calculates revenue at risk on committed orders and forecast, and sets out two scenarios, waiting or emergency sourcing, with the cost and customer impact of each.

On the manager's decision: a Slack alert to production, a Jira ticket for procurement, emails to key account managers

Every action waits for a person

The agent drafts each action, and nothing goes out until a person approves it. The figures in the scenarios come from the workshop's synthetic dataset.

What the team learns

The playbook that makes an agent reliable

Decomposition rules

Which dimensions to drill first, in what order and at what threshold, so the agent reaches the cause a senior analyst would.

Benchmarks

Historical averages, industry benchmarks and internal targets that decide when a deviation is worth flagging.

Action triggers

When to send an email, open a Jira ticket, post to Slack or draft a calendar invite, always with a person's approval.

Hallucination checks

Tests, feedback loops and monitoring that keep the agent inside what it knows and make it say when it does not know.

The process

How it runs

1

Scoping call, 30 minutes

We agree the questions your participants bring and the people who should attend.

2

Proposal

We send the fee, the scope and the date.

3

Before the day

We set up the cloud environment with a synthetic dataset.

4

The day and after

Your team builds the three agents and one for each participant's question at your office, then gets 30 days of Microsoft Teams support from our engineers.

Before you book

Questions analytics leads ask

Data, reliability, fit and logistics

Does our data go anywhere?

No. The day runs on our cloud environment with a synthetic dataset, so your production data stays outside the engagement.

What do participants bring?

One real business question each, the kind that now waits in the analytics queue. Each participant leaves with a working agent for it.

How do you stop the agent inventing answers?

The playbook does that work. Give 1,000 people the same ERP extract and an AI assistant and you get 1,000 answers, the lesson self-service BI already taught with dashboards. Decomposition rules, benchmarks, tests, feedback loops and monitoring keep the agent inside what it knows, and it says when it does not know. Every action it drafts waits for a person's approval.

How is it different from your other two workshops?

Choose this day if the business waits on your analysts for answers: analysts and the people who use their answers build agents that explain why a number moved and draft the next action. Choose the AI workshop for data engineers if delivery is the bottleneck: it builds the warehouse, CI/CD and a Jira agent. Choose Data AI in a Day if a mixed data team, analysts included, should take one project from request to merged pull request. Each is one day from EUR 9,000.

Where does it run?

On site at your office. Inside the EU and the UK, travel is included in the fee; elsewhere it is a separate line in the proposal.

Next step

Bring one business question to a 30-minute call

You talk to Michał Dębski, co-founder, about the questions your analysts answer by hand, and leave knowing which agents the day would build.

We are here to answer your questions

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.