Get Your Whole Team Using AI

Most AI guides are written for individuals. But Adam Bike has a team: customer service, mechanics, sales, management. When more people use AI, the benefits multiply. A customer service rep saving 30 minutes a day is significant. Three people each saving 30 minutes is transformational.

This page covers how to introduce AI to your team in a way that works, not in a way that gets ignored.

Share the context file

The first step is making sure everyone uses the same Adam Bike context. You do not want three people writing captions with different brand voices and different price lists.

How to share:

  1. Save your context file to a shared Google Drive or Notion page
  2. Create a shared Claude Project for the team (Teams plan) or have each person create their own Project and upload the same context file
  3. Include the context file in your employee onboarding

With Teams plan (AED 91/user/month), you can create shared Projects where the context is set once and every team member’s conversations in that Project start with the same business context. Everyone gets the same Adam Bike context automatically.

One person, one task, one week

The biggest mistake when introducing AI to a team is trying to change everything at once. Pick one person. Give them one specific task. Give them one week to try it.

Good first tasks by role:

Customer service (Mayna or whoever handles DMs/WhatsApp): “This week, use Claude to draft your first reply to every customer message. You review and send it. Report back on Friday: did it save time? Did the drafts need a lot of editing?”

Mechanic (workshop team): “This week, use Claude to look up repair information when you are not sure about a specific bike model. Paste the bike name and the issue. See what it says.”

New hire or junior team member: “Use Claude to learn about our product range. Ask it questions about our bikes. It has our context file so it knows what we sell. Test it.”

Management: “This week, use Claude Research to look into one topic you have been meaning to research: e-cargo bike trends, a competitor, or a supplier you are considering.”

After one week, have a 10-minute conversation about what worked and what did not.

The Friday AI share ritual

Every Friday (or in your weekly team meeting), spend 5 minutes asking: “Did anyone use AI for something interesting this week?”

This does three things:

  1. It keeps the habit alive
  2. It lets people share prompts that worked (the whole team learns)
  3. It surfaces resistance or confusion so you can address it

Over time, this builds a team prompt library: your best prompts, saved and shared, so no one is starting from scratch.

Handling resistance

Some team members will be skeptical. “This is going to take my job.” “The output is never right.” “It is too complicated.”

Address it directly and honestly:

  • AI does not replace your team. It handles the repetitive parts of their job so they can focus on the parts that actually require a human: customer relationships, judgment calls, hands-on work.
  • The output is not always perfect. That is fine. Review it. Edit it. It still saves time even if you change 30% of it.
  • It is not complicated. The first step is typing a question in plain English. If someone can write a WhatsApp message, they can use Claude.

The best proof is a small win. When Mayna saves 20 minutes on customer replies in one day, she will tell the rest of the team herself.

Role-specific prompts

For customer service:

I handle WhatsApp and email for Adam Bike in Dubai. I often get questions about sizing, delivery, and pricing. Give me 10 canned reply starters I can customize quickly for common questions. Keep each one under 60 words, warm tone.

For the workshop (mechanic):

I am a bike mechanic working on a [bike brand and model]. The customer is reporting [describe the issue]. What are the most likely causes and how would I diagnose them? Keep it practical and technical.

For a new hire learning the product range:

I am new to Adam Bike and want to learn our product range. Ask me a quiz about our bikes, one question at a time. Start simple (categories and prices) then get more specific (features, target buyers). Give me feedback on each answer.

Claude Teams plan

If you have 3 or more people regularly using Claude, the Teams plan (AED 91/user/month) is worth evaluating. It provides:

  • Shared Projects with shared context (everyone works from the same business context)
  • Higher usage limits for each user
  • Admin controls so you can manage who has access
  • No training on your data (important for business privacy)

For a small team of 3 to 5 people, the total cost is AED 270 to AED 450/month. If each person saves 30 minutes per day, that is 45 to 75 hours per month of time recovered. Do that math against your hourly team costs.

The simplest team introduction:

This Friday, send your team a message:

“I have been using AI for [specific task] and it saves me about [X] minutes per day. I want us to try it together. Next week, each of us will use Claude for one task. I will share the context file for Adam Bike. Let us compare notes on Friday.”

No training session. No big rollout. Just: here is the tool, here is what I tried, here is how to start.