Team AI enablement
A training day your team can use the next morning.
Not a prompt-engineering lecture and not a vendor demo. We collect five real tasks from each department beforehand and rebuild them live, with the people who actually do them.
Why most AI training fails
Because it teaches the tool instead of the job.
A generic curriculum produces a room full of people who can write a clever prompt and then go back to working exactly as before. Nothing changes, because nothing in the session touched what they actually do on a Tuesday.
This day is built the other way round. The content is assembled after the intake, from your team's own recurring work — the report that takes a morning, the emails that all say the same thing, the document nobody wants to summarise.
It also means the session doubles as a discovery exercise. By the end of the day you will have heard twenty people describe, in specific terms, where their time actually goes. That list is usually worth more than the training itself.
What your team leaves with
- Everyone has used AI on their own real work, at least once, with supervision
- A written SOP pack specific to your workflows, not a generic prompt library
- A shared vocabulary so "use AI for it" stops meaning five different things
- Clear rules about what must never be pasted into a third-party tool
- A ranked shortlist of tasks worth automating properly
- A 30-day channel for the questions that surface in week two
The shape of the day
One day, four working sessions, and thirty days of follow-up.
Delivered as a single full day or split into two half-days if taking the whole team offline at once is not realistic.
- Before the day
We collect five real tasks per department
Not hypotheticals. Actual recurring work with actual documents, gathered through a short intake form and a call with whoever runs each function. The session is then built around those.
- Session 1
Where this genuinely helps, and where it does not
A short, concrete framing: which categories of work language models are reliable at, which they are dangerous at, and how to tell the difference before you trust one with something that matters.
- Session 2
Rebuilding your own tasks, live
Everyone works on their own submitted task, with me in the room. People leave having done it once themselves rather than having watched a demo — which is the entire difference in whether it sticks.
- Session 3
Making it repeatable and safe
Turning what worked into a written SOP the rest of the team can follow: what to check before sending, what never to paste into a public tool, where the review step belongs, and how to spot a confident wrong answer.
- Session 4
What to automate properly
The tasks that came up during the day that should not be done by a person with a chat window at all. You leave with a shortlist of genuine automation candidates, ranked — whether or not you ever build them with me.
- After the day
Thirty days of follow-up
A shared channel for the questions that only appear once people start applying it to real work, plus the take-home SOP pack and all session materials.
Formats
Quoted per session, not per seat
Up to twenty participants either way, so the cost per person falls as you bring more of the team. Each format is quoted after a short call about which departments are attending and what they work on.
Full day — remote
One full day live online, up to 20 participants, anywhere in the world.
Half day — remote
A focused half day for a single team or function.
Full day — on-site
In the room with your team. Available within Bengaluru; elsewhere quoted with travel.
Included in every format
- One day live, built entirely around tasks your team actually does
- Live rebuild of those tasks — everyone leaves having done it once
- Take-home SOP pack your team can apply the next morning
- 30-day async question channel after the session
Practicalities
- Group size
- Up to 20 participants. Beyond that, run two cohorts.
- Delivery
- Remote anywhere, or on-site within Bengaluru. On-site elsewhere in India is quoted with travel.
- Payment
- In advance, or against a purchase order. Indian invoices carry 18% GST.
- Lead time
- Two weeks, to allow for intake and building the session around your tasks.
What it costs
Every engagement is quoted individually — and quickly.
There is no price list here because there is no honest one. What a workflow or an agent costs depends on how many systems it touches, how clean the data is, and how much of the process is already written down. A number quoted before knowing those is either padded to cover the unknown or discovered to be wrong halfway through the build.
What you get instead is a fixed price, in writing, before you commit to anything — and fast enough that it is never the reason a project stalls.
From first contact to a number
- 01
A reply within 24 hours
From the person who would actually do the work, not an automated sequence.
- 02
A 20-minute fit call
Qualification only. Which process, how many hours a week, across how many people, and who signs off. No advice given and no pitch.
- 03
A written proposal within 24 hours of that call
A fixed price, with the scope caps, timeline, deliverables and payment schedule already in it.
- 04
The price then does not move
Two revision rounds are included. Anything outside the written caps is quoted and agreed before it happens, never billed as a surprise.
Want the day built around your team's actual work?
Tell me which departments would attend and what they spend their week on. If a training day is not the right first move, I will say so — sometimes the honest answer is to automate one thing instead.
Prefer email? hello@soloz.ai