Organizations

Roll out Crewdle in your organization: the first 30 days

Last updated:

How owners and admins get a team using AI well in 30 days, with a pilot, clear rules and a monthly review. No chaos, no surprise costs.

This guide is for owners and admins. It gives you a simple path to get your team using AI well in 30 days, without chaos or surprise costs.

Do’s and don’ts

Do

  • Start with a pilot group and 2 or 3 real use cases
  • Set roles, budgets and approval rules first
  • Pair your AI champions with colleagues
  • Share the Academy, the 30-day plan and the Request library
  • Review hours saved monthly

Don’t

  • Invite everyone at once with no use case
  • Allow every tool and model from day one
  • Use levels to rank or evaluate people
  • Expect people to figure it out alone
  • Look only at spend

Week 0: set up before you invite anyone

Do these in Admin first. They take a few minutes each, and they are much easier before people arrive.

  • Roles: decide who is an admin and who is a regular member, and add other roles if different people need different access.
  • Budgets: set a budget per member or per role, so nobody is surprised by a cost.
  • Models and tools: choose which models and tools are allowed.
  • Approval rules: decide what needs a person’s OK before it goes out.
  • Knowledge sources: decide what you add and who can see it.
  • Microsoft sign-in: if your organization uses it, ask IT to set it up first. See Microsoft 365 and Entra setup.

The Governance checklist walks through each control.

Week 1: run a pilot

Pick 3 to 5 motivated people and 2 or 3 real use cases where you can measure the time saved. Good examples are inbox triage, weekly reports and client proposals. Share the 30-day plan and the Request library so nobody starts from a blank page.

Week 2: add agents and routines

Each pilot person sets up one routine. Use one team (project) for a job that has several steps. See Routines.

Week 3: invite the rest

Hold a short kick-off. Pair newcomers with your AI champions, the people at Délégateur level and above. Run an Academy group session so everyone learns the same basics.

Week 4: review

Open the Home tiles (tasks done, hours saved, cost per hour saved) and Usage in Admin. Keep what works, and adjust budgets and access. Measuring the return on AI shows how.

After 30 days

Review once a month. Add new use cases and retire what nobody uses.

Budgets and tools per role

Explain how to set budgets per role and limit which tools members can use in our Crewdle organization, step by step.

Needs
Nothing
Result
Step-by-step instructions
Cost
A few cents . Indicative. Plans always show the cost before anything starts.

Build your weekly delegation list

Look at what I asked my agents in the last month and propose 5 recurring jobs I could hand over completely, with the agent and schedule for each. Then help me set them up one by one.

Needs
Agents
Result
A personal automation plan
Cost
A few cents . Indicative. Plans always show the cost before anything starts.

Replace the [brackets] with your details. The more context you give, the better the first answer.

Frequently asked questions

How many people should be in the pilot?

Start with 3 to 5 motivated people and 2 or 3 real use cases. A small group gives you real numbers and feedback before you invite everyone.

What if we are a very small team?

You can skip the pilot and go straight to a few real use cases. Set budgets and approval rules first, then review after 30 days.

Who are the AI champions?

They are colleagues who have reached the Délégateur level or above. Pairing them with newcomers helps people get started. Levels are there to help, not to rank anyone.

Crewdle Crewdle AI