Case studyWork/AI

A consulting firm hands its busywork to Claude.

Expense statements sorted by hand. Client calls that took days to write up. Research that had to look like a big firm made it. Now Claude does the first draft of all of it, and a person approves every output.

Company
Consulting firm, small senior team
Service
AI · Build
Delivery
Remote, phased, one job at a time
We used
Claude, custom Claude skills, Claude Code, SharePoint, Excel, Word, Outlook, Teams
4jobs Claude does every week: finance, delivery, research, operations
6documents drafted from every client call
50+briefing components in the firm's own brand
3Microsoft 365 tools built with Claude Code
Alwaysa person approves. Claude never sends or records anything.
Counts from the engagement. Client not named. Screens below are mock-ups with sample data.
The story

The expertise was the product. The paperwork wasn't.

  1. Before

    A small, senior team doing junior work.

    Every quarter someone sorted a folder of statements and receipts by hand. Client calls turned into scoping documents days later. Leave and policies lived in spreadsheets and email threads.

  2. The ask

    Not a chatbot.

    Claude doing real work inside the business, on their own files and templates, with a person approving everything it produces.

  3. What we built

    Four jobs, one at a time.

    Custom Claude skills for expenses, client calls and briefings, and a set of Microsoft 365 tools built with Claude Code. Each job was proven before the next one started.

01 · Finance · Custom Claude skill

Read the folder. Return the load sheet.

Claude reads a quarter's statements and receipts and returns an Excel load sheet with every transaction attributed and every doubt flagged.

Receive

The quarter's folder

Card and bank statements, receipts, scans and emailed receipts.

Read

Claude sorts it

By content, not file name. Matches each line to a person and a receipt, and pulls the tax.

Draft

Two load sheets

One row per transaction, and one row per source file.

Approve

A person signs off

Only approved rows go on to the books.

Mock-up with sample data. The real load sheet has the same structure.

1Payments and refunds caught. A card payment is marked "not an expense" and a credit becomes a negative line, so nothing is counted twice.
2Every line has an owner. Each row carries the account it came from and the person it belongs to.
3Flag, don't guess. Claude applies the firm's rules. If none fit, the row goes to a person instead of getting a guess.
4Every file accounted for. A second sheet lists each source file, what it was, who sent it, and whether it was a duplicate.
What changed

The finance lead stopped sorting paper and started approving a finished sheet.

02 · Delivery · Custom Claude skill

Hang up. Open the project kit.

After a client call, Claude turns the transcript, or a spoken summary, into six standard documents ready to review and send.

  • Three Word documents: a scoping document, a preliminary project plan and a statement of work, in the firm's own templates.
  • Three drafts: a follow-up email to the client, an internal briefing, and a short note for the team in Teams.
  • Only what was said. Dates, budgets, scope and names appear only if they came up on the call.
  • The gaps are the to-do list. Anything not discussed is marked "to be confirmed with client".

"If it wasn't said, it isn't written."

The skill's first rule
What changed

A client call becomes professional follow-up the same day, not the same week.

1Unknowns are marked, never invented. The budget didn't come up, so it stays open.
2Nothing sends by itself. Every document opens as a draft for the team to finish.

Mock-up with a fictional client.

03 · Briefings · Component library and Claude

Pick the parts. Claude builds the briefing.

We built the firm a library of more than 50 components in its own colors and typeface. The team picks what a briefing needs, and Claude assembles it.

Mock-up with sample content, shown in Floor 16 colors.

1A library, not a blank page. Figures, charts, benchmarks, timelines, options, stakeholders and evidence, ready to drop in.
2On brand without trying. Every component is drawn in the firm's own colors and typeface.
3Charts that don't overstate. Values read off a source report are marked approximate and cited.
  • Each briefing comes out as a web page and a matching Word document, built from the same content so they never drift apart.
  • Each briefing uses only the components it needs, so no two look templated.
What changed

Briefings that read like a much larger firm made them, with no designer on staff.

04 · Operations · Built with Claude Code

The spreadsheets became tools.

Claude Code is how Floor 16 builds. With it we built the firm a set of SharePoint tools that set themselves up, share one staff list, and run inside the firm's own Microsoft 365.

  • Intranet: news, quick links, events, people and HR bulletins in one place.
  • Policy Center: a manager publishes a policy, everyone acknowledges it, and every version keeps its own record of who has.
  • Leave tracker: balances in hours, requests routed to each person's manager, public holidays built in, and a full history.
  • One staff list, real permissions. The team is defined once, and roles are enforced by SharePoint permissions, not hidden buttons.
  • Tested every release, with automated checks written and run in Claude Code.
What changed

No new login. The tools live in the firm’s own Microsoft 365, with its own permissions.

1Balances in hours, so half days and hourly leave just work.
2Policy acknowledgments, with a record for every version.
3Public holidays (shaded) are skipped when leave is counted.

Mock-up with sample data.

The rule

A person always approves.

Every job was scoped with one question answered in writing: what may Claude do by itself? It reads and drafts. It never sends, records or deletes.

JobReadsDraftsSends or recordsDeletes
Statements and receipts
Call transcripts
Client email and Teams
Briefing sources
By itselfA person approves firstNever
Claude draftsThe load sheet, the kit, the briefing
Gaps are marked"To be confirmed", never filled in
A person approvesThe one decision, before anything leaves
The team sends itRecorded, sent or published by a person
The rollout

One job at a time.

Each job was proven on real work before the next one started. The firm saw each one working before it moved on.

Intranet on Microsoft 365The staff list, roles and branding everything else uses
Done
Expense skillStatements and receipts into load sheets
Done
Client call to project kitSix documents from every call
Done
Briefing component libraryThe firm's own components, first briefing delivered
Done
Policy Center and leave trackerGoing live in phases
Now
Claude for the whole companyOne company plan, shared projects, the firm's skills, training
Next
Phase 1Phase 2Phase 3Phase 4Phase 5
01 Done13 In progress, and it matters18 Planned
What changed

Three ways to measure it.

For finance
Approve

a finished load sheet instead of sorting a folder by hand every quarter.

For the team
Same day

from a client call to six documents, with the open questions already listed.

For leadership
Every

output approved by a person, on the firm's own files, inside its own Microsoft 365.

Something like this on your desk?

Thirty minutes on what's working, what isn't, and where Claude could take the busywork.