AI Sprint.
A week on site to see results before committing for the long term.
Our engineers go team by team to spot the use cases, then build the first ones with the people who do the work.
- Duration
- 3 to 5 days on site
- Who it’s for
- A leadership team and its business teams
- Location
- On site, at your premises
To build over time: our forward deployed engineers.
What is an AI Sprint?
What is it?
A week on site
The short format of our embedded engineers: team by team, to spot the cases, build the first ones and decide what comes next.
Why?
See results before committing
On your own work, before building over time with our embedded engineers.
The objective
At least one automation in production per team
And each team’s automation matrix, to decide what comes next.
How does the week work?
Understand and train, pool what we learned on the third morning, then build with each team.
Understand and train
Days 1 and 2
- Meet the teams
- Train the teams on the tools
- Note every recurring task
What comes out of it
The list of use cases, across the organization or by team
Bring findings together
Day 3, morning
- Share what we have learned
- Rank use cases by value and ease
- Choose which ones to build
What comes out of it
Shared findings and priorities
Build with each team
Day 3 afternoon, days 4 and 5
- Build around real tasks
- Resolve technical blockers
- Document the method for later use
What comes out of it
Automations in service and a plan
What your teams take away.
Live automations
At least one per team, in service before the sprint ends.
The automation matrix
Each case spotted, placed with management by its value and ease.
The plan for the next cases
Each case is built, assigned to the team, scheduled, or dropped, with a reason and an owner.
Methods to carry on
The sprint’s instructions, taken over by your teams.
In an SME, a week as we ran it.Read the case
Our methodology.
Every use case found is placed by its value and ease of implementation, then gets one of the four decisions.
↑ Value for the company
Ease of implementation →
Built on site
High value, easy to implement
In use before the sprint ends, at least one case per team.
Built by the team
Easy to implement, more local value
The team builds it itself, using the sprint’s skills.
Scheduled
High value, harder to implement
In the plan, with an owner and a date.
Dropped
Lower value, harder to implement
Removed from the plan, with the reason in writing.
FAQ.
Forward Deployed Engineering or a custom system: how do we choose?
Forward Deployed Engineering for an evolving portfolio of use cases: our engineers join your teams two to four days a week for one to six months. A custom system for a complete system, defined during scoping. To start, the AI Sprint takes one week on site.
Compare servicesMasterclass, Team workshops, or AI Day: which should we choose?
The Masterclass is for leaders and managers. A Team workshop has one team work on its own cases. The AI Day brings all teams together: shared foundations, then workshops by function. For your first use cases in service within a week, there is the AI Sprint from Forward Deployed Engineering.
Compare formatsHow should we prepare tools and access for the workshops?
For an AI Day or AI Sprint, we choose with your sponsor the cases to work on and the people to involve, then prepare accounts, access, and usable data with your technical leads. If needed, we provide AI tool accounts.
AI Adoption formatsHow much time will our teams need to commit?
From 2 to 3 hours for a Masterclass to a week for an AI Sprint. With your sponsor, we set each team’s attendance without bringing the company to a halt. For a custom system, a business lead and, ideally, a technical profile spend a few hours a week on it.
AI Adoption formatsWhat happens after the engagement?
You keep the tools and skills we build, their documentation, and the code, with trained AI champions to keep them running. Your teams take over, or we provide follow-up: maintenance is agreed during scoping.
Custom AI systemsDoes the AI Sprint suit an SME?
Yes: in an SME, three to five days on site are enough to meet each team and build the first automations with them.
AI in an SME or a mid-sized company