Copilot · Claude Code · Codex

AI tool setup.
Training for your team.

Practical Microsoft 365 Copilot training for office teams, and Claude Code or Codex setup for developers. We help you choose a tool, check access and practise on useful tasks. You do not need all three.

We do not sell licences and we are not tied to one supplier. If one tool is enough, we will say so.

The invoice export drops the VAT column. Find it and fix it.

Reading project instructions… searching 214 files…

Found it: export.ts skips columns added after March.

Edit export.ts and add a test? (y/n)

y

1 file changed, 1 test added. All 86 tests pass.

Claude Code · illustrationA person approves every change

Choose for the work

Office work or development? Start there.

The products overlap. These examples help you choose what to pilot; capabilities and permissions depend on the plan and setup.

Microsoft · GitHub

Copilot

For office work and software development.

Two products share the name. Microsoft 365 Copilot works inside Word, Excel, Outlook and Teams. GitHub Copilot works inside the code editor, suggesting and writing code as developers type.

Best for
Whole-office work in Microsoft 365, and developers who live in VS Code or Visual Studio.
Watch out for
Copilot can find anything a person already has access to. Untidy file sharing shows up on day one, so we check that first.
Anthropic

Claude Code

For changes across a codebase.

A coding agent that works in the terminal, the editor, a desktop app or the browser. It reads the codebase, plans a change, edits the files and runs the tests, asking permission along the way.

Best for
Changes that touch many files, tidying old code, writing tests and getting to grips with a project nobody remembers.
Watch out for
Project instructions and memory provide context; they are not security controls. We configure permissions separately and check the result.
OpenAI

Codex

For scoped development tasks.

A coding agent for scoped tasks such as edits, tests and code review. Local and cloud environments have different access controls. We agree those controls and a review process before your team uses it.

Best for
Clear, well-scoped tickets, and running several jobs side by side while the team does something else.
Watch out for
What it may do without asking is a setting. We choose it with you, and every change still gets a human review.

Product features change often and vary by plan. We check the current version of each tool when we set it up for you. Copilot, GitHub, Claude and Codex are trademarks of their owners; we are independent of all of them. Product guidance checked on 11 November 2026: Microsoft data and permissions, Claude project memory, Codex permissions.

A quick steer

Which one do we need?

Our steer

Start with Microsoft 365 Copilot.

Start with a permissions review and training in the Microsoft 365 apps your team already uses. Practise drafting, summarising and checking outputs on approved examples before a wider rollout.

Microsoft 365 CopilotPermissions checkStaff guidance

What we set up

What your team gets.

A scoped setup, hands-on training and a written handover. We agree the number of people, tools and sessions before work begins.

The right plan

Which licence, for which people. We check what you already pay for before anyone buys more seats.

Safe data settings

What each tool may read, what it must never see, and how your data is used. Set, tested and written down.

Project instructions

Short, maintained guidance for each project: conventions, commands and review requirements. We check how your chosen tools load it; permissions are configured separately.

Permissions

What may run without asking and what always needs a yes. Passwords, keys and live systems stay out of reach.

Connections

Link the tools to your tickets, documents and databases where it helps. Read-only first.

Review steps

Every change is checked by a person before it reaches anything live. We build that into the workflow.

Team training

Hands-on sessions using real tasks from your own list, not a slide deck about the future.

A written guide

A short handbook for the next person who joins, plus the rules that sit in your AI policy.

Same licence, different result

What a proper setup changes.

Switched on and left alone

  • Five people, five different ways of asking for the same thing.
  • Nobody is sure whether client data may be pasted in.
  • The tool does not know your project, so its answers are generic.
  • Licences bought for everyone, used by three.
  • Changes go live because the AI sounded sure.

Set up properly

  • Maintained project guidance, with checks that the tool is using it.
  • A clear rule for what goes in, checked in the settings.
  • Answers that use your code, your documents and your conventions.
  • Seats for the people who use them, reviewed each quarter.
  • A person reviews every change. The AI drafts; your team decides.

How it runs

Four steps. Then you decide.

01

Look

We learn what your team does, what you already pay for and where time goes. You get a short written recommendation.

02

Set up

Accounts, settings, permissions and project instructions, done with your IT person or provider.

03

Pilot

A few people use the tools on real work. We sit with them, fix what gets in the way and record what happened.

04

Decide

Review the results together. Roll out wider, change the setup or stop. All three are fine outcomes.

Scope, responsibilities and price are agreed in writing before any work begins. The rules your team follows become part of your AI governance.

Not only for developers

Microsoft 365 Copilot training for everyday work.

Microsoft 365 Copilot reads what each person can already open. If old folders are shared with everyone, Copilot will find them. Our Copilot review checks licences, sharing and everyday use before you roll it out wider.

See the Microsoft Copilot review

Want someone to own all of this for you, every month?

See the Head of AI service

WHO DOES THE WORK

Set up by people who use these tools every day.

We build our own software with Claude Code and Codex, so the setup you get is the one we rely on ourselves.

WHO YOU WORK WITH

Deepanshu Sahni

Delivery lead and AI developer

  • The first call: understanding the task, the tools involved and whether we are a fit.
  • Scoping: the workflow map, approved sources, permissions and the definition of a good result.
  • The build and its tests, including the failure cases.
  • Handover: documentation, review steps and the agreed support arrangement.

One named person from the first call to handover. The person you speak to is the person who does the work.

Tell us about your team

We use your details to reply to this enquiry. Leave out passwords and confidential code. Scope and price are agreed in writing before any work begins.

01 A little about you

02 What you have in mind

Enquiry about Set up Copilot, Claude Code or Codex

A few sentences are enough. Please leave out confidential or sensitive information.

1,500 characters remaining

The security check is still loading, please wait a moment.

Prefer not to use a form? Call 0330 043 7414 or email hello@nerdster.ai.

YOUR ENQUIRY

How many people, and which tools?

Tell us the size of the team, what you use today and what you want the tools to help with. A few sentences are enough.

What happens next

  1. We read your enquiry and reply within one working day.
  2. A short call to understand your team and the tools you already pay for.
  3. A written scope and price before any work begins.

GOOD QUESTIONS

Common questions

Do we need all three?

Usually not. Most teams settle on one main tool and sometimes a second for a different kind of job. We look at the work you do and the software you already pay for, then recommend the smallest set that covers it.

Will our code or documents be used to train AI models?

It depends on the plan you buy and the settings chosen, and suppliers change their terms. We check the current terms for the exact plan, set the options with you and write down what was chosen, so you can show a client or an auditor.

We are not a software company. Is this still for us?

Yes. Microsoft 365 Copilot works in Word, Excel, Outlook and Teams, with no code involved. And a small office with one technical person can get a lot from Claude Code or Codex for scripts, reports and small internal tools.

Will these tools replace our developers?

No. They take on the typing, the searching and the first draft. A person still decides what to build, reviews every change and owns the result. We set up the review steps so that stays true.

How do you keep it safe?

We agree what each tool may read, what it may run without asking and what it must never touch, such as passwords, keys and client records. Changes go through review before they reach anything live. Those rules are written into the setup, not left to memory.

What does it cost?

Licences are paid directly to Microsoft, GitHub, Anthropic or OpenAI. Our setup work is scoped and priced in writing before we start, based on the number of people, tools and projects involved.

Can you train the team as well?

Yes. Training is part of the setup. We work through real tasks from your own backlog with your people, and leave a short written guide for whoever joins later.