Data AI in a Day · on-site workshop for data teams

AI workshop for data teams: one day from request to merged PR

In one day at your office, your project managers, engineers and analysts take one data project from a stakeholder transcript to a merged pull request with Claude Code, and keep the setup.

The workshop at a glance

Format

One day at your office, 09:00 to 17:00, five modules

Who

Anyone in the data team, up to 12 people: project managers, data protection officers, data engineers, analysts

Fee

From EUR 9,000, fixed in the proposal. Licences for the day included

Data

NordicMart, a synthetic online retailer, or an anonymised mirror of your data. Your production systems are untouched

MD

Michał Dębski runs the day

Co-founder, Managing Director and Solution Architect. 15 years in data and AI; delivers in English, Polish or French.

The day runs on its own stack and dataset, so the whole team can join without access to your production systems. Data engineers only? See the data engineering workshop →

What agent-assisted delivery did at a global manufacturing group, what it can be worth for your team, and what we commit to

75%+less developer effort per high-complexity task: from 8 person-days to 0.5-2 once agents joined delivery (measured)
€345ka year of capacity for an 8-person team (model, see how it pays back)
4xROI on your own numbers, or we tell you not to book
30 daysof Microsoft Teams support with our engineers after the day
The day

Five modules, one mixed team, one project from request to PR

ModuleWhat the team doesWhat it keeps
09:00 to 10:15 · All rolesThe AI-native data team

A shared Claude Code repo with three MCP servers (filesystem, DuckDB, Azure DevOps), skills, and a markdown knowledge base the agent reads on demand.

A configured repo with team and personal workspaces

10:15 to 11:30 · Project manager and data protection officer leadRequirements

A three-page stakeholder transcript becomes epics, user stories and a source-to-target map, with a data-protection check of every personal-data field, and the team cuts sprint one.

A populated backlog, a DPIA-lite note and the ticket-writer skill

11:45 to 13:45 · Data engineer leadsEngineering

Bronze, silver and gold models in dbt, a legacy margin script refactored, deduplication matches reviewed.

dbt models with tests, docs and lineage

14:30 to 15:45 · Analyst leadsAnalytics

A Streamlit dashboard that answers questions asked in plain English, behind three guardrails: 30-second timeout, SELECT-only access, PII masking.

The dashboard and a findings log

15:45 to 17:00 · All rolesTicket to pull request

An agent takes an Azure DevOps ticket through plan, code and tests to a pull request, and the team reviews and merges it.

Merged pull requests and a governance and cost playbook

Stack for the day

Claude Code, MCP servers, dbt, DuckDB, Airflow, Streamlit and Azure DevOps, in Docker on each laptop. The team also keeps the prompt library, the knowledge base and a one-page runbook. Coffee at 11:30, lunch at 13:45; the hour-by-hour plan is in the brief.

For the sponsor

A cycle-time baseline from the day, a written scope for the next 90 days, an AI governance starter pack (DPIA-lite template, scope boundaries, controls, audit hooks, escalation) and an answer for the board on how the data team uses AI.

The business case

How it pays back

Data engineers and analysts

8

Loaded cost per person a year

EUR 180,000

Time on model authoring, tests and PR drafting

40% (assumption)

Reduction on that work

60% (assumption)

Capacity recovered a year

About EUR 345,000

The model: 8 × EUR 180,000 × 40% × 60% = EUR 345,600. In the scoping call we redo the sum with your own figures, starting with how many days one change takes your team from spec to merged model. If they show less than 4x ROI, we tell you not to book.

The process

How it runs

1

Scoping call, 30 minutes

We walk your stack and the work your team does, and choose the case the day is built around.

2

Proposal within 48 hours

Fixed fee, scope and date. We work under our MSA or sign yours.

3

One week before

We tune the environment to your case and send a 15-minute pre-read with the install steps.

4

The day, 09:00 to 17:00

Five modules at your office. The runbook stays with your team.

After the day

Your team runs the pattern itself with our Teams support, or continues into a 90-day implementation sprint at a fixed fee, or into a monthly capacity pack with a named Astral Forest engineer.

Before you book

Five questions procurement asks first

Security, ownership, logistics and the guarantee

Does our production code or data go anywhere?

No. The stack runs in Docker on each participant's laptop, with the synthetic NordicMart dataset or an anonymised mirror of your data, so your production code and data stay outside the engagement. Models run in enterprise mode, where inputs and outputs are not used for training. A security one-pager covering data handling, access, agent scoping and subprocessors is available under NDA.

Who owns what the team builds?

You do, from the end of the day. The repo, agent setup, skills, prompts, knowledge base and runbook are transferred to you under the engagement.

Can you adapt the day to our tools and our data?

Yes, and we confirm it in the scoping call. Common swaps are Jira for Azure DevOps, GitHub Copilot next to Claude Code, Snowflake or BigQuery for DuckDB, and Power BI or Looker for the dashboard. Bring an anonymised or synthetic mirror of your data and we build the modules around your case; otherwise we use NordicMart.

Where does it run, and for how many people?

On-site at your office, for up to 12 people from one company, because above 12 each person stops getting hands-on time with the agent. For a larger team we run the day twice. Inside the EU and the UK, travel is included in the fee; elsewhere, including the US East Coast on request, travel and one prep day are billed at cost. We deliver in English, Polish or French.

Do you offer a guarantee?

Yes. The SOW sets the success criterion: by the end of the day the team has merged at least two agent-drafted artefacts into the workshop repository. If we miss it, we run a second session at no extra cost. If the pattern has not stuck 30 days later, we tell you so and what we would change.

Next step

By 17:00 your team has merged its first agent-drafted pull requests.

Book 30 minutes with Michał Dębski to walk your stack and agree the case the day is built around. If you want to hear from a client before you sign, we set up a reference call after the scoping call.