“We rolled it out. Nobody uses it.” Training on each department’s own work, and upkeep after launch.
Training built on the work each department already does, and a monthly plan that keeps connectors, permissions and skills in order as your systems and your people change.
- For
- Teams that have their AI agents connected and want them used every day
- You get
- Sessions per department, written playbooks and a monthly upkeep plan
- Commitment
- Monthly. Cancel any time
- Price
- Monthly, quoted for your setup
- Your systems
- Stay as they are. Nothing is replaced or migrated
Training and upkeep is what keeps a rollout working after the first month. Deep Blue Coding trains each department on its own reports and requests, writes down how to do them, and then looks after the connectors, permissions and skills every month, because systems get upgraded and people join and leave.
What happens after launch
A system gets a new version and a connector stops returning a field. Someone changes team and still sees the old team's data. A template is redesigned and the skill still produces the old one. None of it is dramatic, and all of it makes people trust the answers a little less.
Generic training does not help much either. People learn fastest on their own work.
What you get
- Sessions by department
- Each one built around that team's real reports and requests, on their own data.
- Written playbooks
- A short guide per department: the questions that work, the skills available, what to check before sending.
- Connector upkeep
- Updates when a connected system changes, and fixes when something stops returning what it should.
- Permission reviews
- A regular check that access still matches who is in which team.
- New skills
- As templates change or new document types appear.
- A named engineer
- The same person each month, who knows your setup.
What a first month looks like
| Week | Department | Session | They leave able to |
|---|---|---|---|
| 1 | Finance | The weekly debt report, from question to PDF | Produce the report without an export |
| 1 | Operations | Purchase requests and stock checks | Send a request that arrives complete |
| 2 | Sales | Customer history and proposals in house format | Prepare a proposal from the CRM |
| 2 | Support | Answering from the knowledge base and order data | Draft replies ready for review |
| 3 | Administrators | Connectors, permissions and skills | Add a team member, a group or a skill |
| 4 | All | Open session: questions from real use | Know who to ask |
How upkeep runs each month
Check
We run each connector and skill against known cases and look at what failed during the month.
Fix and update
Changes in your systems, templates and teams are carried into the setup.
Review permissions
Joiners, leavers and people who changed team.
Report
A short note: what changed, what we fixed, what we recommend next.
What we need from you
- A contact who tells us when a system, a template or a team is about to change.
- A slot in each department's calendar for its session.
What it costs
A monthly plan, quoted for your setup, that you can cancel at any time. Training sessions at launch are part of the project price. See engagement models.
Questions buyers ask
Can our own team maintain it instead?
Yes. Everything we build comes with documentation and source code, and we train your administrators. The monthly plan is for companies that prefer not to staff it.
What does monthly upkeep include?
Checking and updating connectors when your systems change, reviewing permissions as people join and leave, updating skills when templates change, and a short monthly report.
Is there a minimum term?
No. The plan is monthly and you can cancel at any time. What was built stays with you.
Do you train every employee?
We train by department, on that department's real work, and we train your administrators to add people and skills themselves. In a large company we can train a few people per team, who then train the rest.
Read next
Last updated 18 November 2026.
Start with one process.
The report your team dreads building, or the approval that sits in an inbox for days. Tell us about it and a senior engineer tells you whether it can be automated and what it would take.
Email social@deepbluecoding.com
We reply within one working day.
Deep Blue Coding