--- title: "Your team uses AI on real work · Update Labs" description: "8 to 12 weeks: rules on what can be uploaded, a prompt playbook built on your documents and a pilot assistant, with Copilot, Claude or Gemini." url: https://updatelabs.it/en/lab/tech/ai-adoption lang: en --- # AI Adoption your team uses AI on everyday work In eight to twelve weeks your team uses Microsoft 365 Copilot, Claude or Gemini on everyday work. You start with one page of rules on what can be uploaded, then build a prompt playbook on your documents and a pilot assistant on one process. After that, someone on your team takes over looking after it all. - price based on hours, quote within 48 hours - length 8 to 12 weeks, in phases - where at your company or on a call - afterwards, if you want follow-up sessions for 6 to 12 months [Ask for a quote](https://updatelabs.it/en/contact?offerta=adozione-ai) [Book an intro call](https://updatelabs.it/en/contact?offerta=call) ## Does this sound like you? - You bought the licences, and two people use them. Everyone else opened them once. You start from the jobs the team does every week, and use them there. - Everyone uses ChatGPT their own way, and nobody knows what goes into it. The risk is client data. The first thing that gets written down is the rule on what can be uploaded, and where. - The one person who learned it properly is the only one who uses it. If they change jobs, it all leaves with them. The prompts that work go into a playbook for everyone. works best when someone on the team will look after the tools afterwards: updating the playbook, answering colleagues’ questions. ## Four phases, on real work Between one meeting and the next, everyone tries things out on the week’s work, and the next meeting starts from there. ### Rules and tools One page that says what can be uploaded and what can’t, for each tool, with examples from your work. You also decide who uses what. ### The playbook You pick the jobs the team does every week. For each one you find the prompts that work, tested on real documents, in Italian and in English. ### The pilot assistant An assistant for one process, built on your documents inside the tool you already use. ### Handing over Someone on your team takes charge of it all: the internal library, the questions that come up during the work, the updates. Then, if you want, follow-up sessions every two or three weeks, along the lines of Update Next. ## First, your team really uses it Meeting minutes, a reply to a client, a draft quote: the team prepares them with AI and reads them through, instead of writing them from scratch. It already happens during the programme, on the week’s work. Then you’re left with two things, and they keep AI in use once the programme ends. ### Your team’s prompt playbook For every job you picked, the prompt that works, tested on your documents. It sits somewhere everyone can find it, and grows with what the team discovers later. What’s inside, with an example - the jobs you picked, one by one - for each, the prompt, with a real document as a model - what to check before sending - an Italian version and an English one Say one of the jobs is the minutes of the weekly meeting. The playbook has the prompt to use with the meeting notes, a real set of minutes as a model and what to check before sending them: names, dates, decisions taken. ### The rules, on one page What goes into AI tools and what stays out, which tool to work in, who to ask when a case isn’t clear. People no longer have to ask for permission, or guess. What’s inside, with an example - the approved tools, and for whom - the data that can be uploaded and the data that stays out - examples taken from your work - who answers for the unclear cases Say a salesperson wants help with a quote. The page tells them whether they can upload the price list, whether the client’s name has to stay out and which tool to work in. They know before they start, without asking anyone. ### And on top - The pilot assistant Built on one process and on your documents: proof that it can be done, and the model for the next ones. - The internal library The questions that come up during the work, with their answers, somewhere everyone can find them. ## What does it cost? Quoted within 48 hours. The hours are estimated on how many people, how many departments and which jobs. [Ask for a quote](https://updatelabs.it/en/contact?offerta=adozione-ai) Rather talk it through first? In the intro call we work out together which team it makes sense to start with. - The options The quote comes in three versions: one pilot team, every department, or every department with follow-up sessions afterwards. - How long it lasts 8 to 12 weeks, in phases. Follow-up sessions, if you want them, for 6 to 12 months. - What’s included The meetings, the rules, the playbook, the pilot assistant and the library. They stay yours. Tool licences are extra: you start from the ones you have. ## Questions about AI Adoption Do we need to buy more licences? Usually not: you start from the ones you have. If a job needs a different tool, the rules from the first phase say so, and why. Will AI replace anyone? How do I talk to the team about it? You talk about it at the start, because as long as the question is open people try very little. You look at each person’s work to see what goes to AI and what stays with them, and the team sees it on their own tasks before starting. How much time does it take from the team? The meetings, plus the practice between one meeting and the next. The practice happens on the week’s work: the usual things, prepared with AI. Does it work if my team works in English? Yes. The playbook has every prompt in Italian and in English, each tested on your documents. - [previous step AI Map usually three days](https://updatelabs.it/en/lab/tech/ai-map) - [next step Custom AI Assistant quoted](https://updatelabs.it/en/lab/tech/custom-ai) ## Start with the team that will use it first [Ask for a quote](https://updatelabs.it/en/contact?offerta=adozione-ai) [Book an intro call](https://updatelabs.it/en/contact?offerta=call)