Claude Code consulting and setup

• Project instructions.

  Instruction files that tell Claude how your codebase, clients and conventions work, so nobody starts from a blank screen.

• Skills.

  Custom SKILL.md files written to Anthropic's conventions and tuned to the job they do.

• Plugins.

  Manifests, hooks and commands, packaged with versioning and upgrade paths.

• MCP connections.

  Presets and servers that give Claude Code access to the tools your team already uses.

  custom MCP servers

• Claude Code pipelines.

  Repeatable jobs driven through Claude Code, such as avatar video through HeyGen or carousels through the Canva API.

• Engineers in your repo.

  Our developers work through your backlog with Claude Code, and every change goes through your team's review before merge.

• Civil engineering firm: Claude across the whole office

  A firm of about fifteen people wanted Claude in daily use without risking its project files. We set up its Claude Team workspace, wrote a company plugin with the firm's facts and ground rules, and built three front office workflows with the people who run them: weekly timesheets into Sage Timeslips, permit status across 15 agency portals, and comment-letter responses in the firm's own format. Nothing is sent, filed or invoiced without a person. The first full timesheet run matched 159 of 159 slips.

  Read the full case study

• Accounting firm: Claude Enterprise with zero data retention

  An accounting firm would only let AI near client tax data with zero data retention. We checked every route against that condition and planned Claude Code on six PCs under Claude Enterprise, reading client folders read only and filling CCH Axcess's own import templates, with no live link to the tax software and staff making every tax decision.

  Read the case study

• Strategy Stack: a plugin product line for 12 professions

  Knowledge workers were opening an AI assistant that knew nothing about their clients, their voice or their files. We built one foundation plugin and 12 profession packs, covering accountants, real-estate agents, insurance brokers and nine other professions. The foundation plugin runs a 13-question interview, then generates the user's instruction file, folder structure, memory system and connectors manifest. Each pack adds 20 to 24 named capabilities. All 12 packs were verified live through the public download path.

  Read the full case study

• AI tooling company: plugins and skills for a Claude accelerator product

  A company building a commercial accelerator on Claude Cowork (now part of Claude) needed its plugin layer built. We wrote the plugins end to end: manifests, hooks, commands and MCP presets, with versioning and upgrade paths. The skills were written as SKILL.md files and tuned for each vertical. Everything was tested in both the Claude Code CLI and the Claude desktop app. We also built a HeyGen video pipeline, driven through Claude Code, for the client's marketing.

• UK legal-tech company: Claude Code on a .NET and Angular backlog

  A UK legal-tech company needed full-stack support on a SaaS platform built on C#/.NET, Angular and Microsoft Azure, including Office Add-Ins. Our engineers used Claude Code every day to work through the ticket backlog: new features, debugging and Azure deployments. Every change went through the client team's own review before it was merged.

• “Abdul has been an outstanding find. He's technically deep in Claude Code and Claude Cowork plugin development, asks the right questions, and approaches every project like a partner…”

• “Abdul delivered a comprehensive architecture recommendation for a complex Claude Cowork plugin project, well-structured, technically sound, and showed genuine independent thinking. He challenged several of our assumptions with solid reasoning…”

• Claude Code setup or plugin build

  Scope, timeline and a fixed price agreed in writing before work starts.

  From $1,500

• Dedicated engineer

  A senior engineer who joins your team and works inside your tools. Billed monthly.

  $25 per engineer, per hour

• Support after launch

  80 hours of support a month from the team that built it.

  $1,450 per month

The first call is free and takes 30 minutes.

1. 01

   Listen first. We interview the owners and each person who will use Claude, and design from how they work.

2. 02

   Write the rules down. A security review and ground rules for each role say what Claude can reach, what it never does and who signs off.

3. 03

   Set up the workspace in your name. A Claude Team or Enterprise account on your billing, your administrators, and a private GitHub repository you own.

4. 04

   Build the company plugin. Your firm's facts, people, drives, projects and rules, so Claude starts each task knowing your business.

5. 05

   Build the first workflows with the people who do them. Working sessions on real files, a step-by-step card for each, and a personal plugin where one person's job needs it.

6. 06

   Roll out in groups and hand over. Each group gets its ground rules first, and you get a playbook and a plain-language architecture document your own Claude can read.

For a civil engineering firm of about fifteen people, this meant weekly timesheets into the billing system, permit status across 15 agency portals and comment-letter responses in the firm's own format. Read the case study.

Where this is running now

• Civil engineering firm, about 15 people. In pilot with the front office. Read the case study.
• Accounting firm, six CPAs. Stage 1 plan prepared for Claude Enterprise with zero data retention. Read the case study.
• Benefits consulting firm, about 30 people across two offices. Stage 1 starting in November 2026: listening sessions with the IT lead, a power user and the CEO, a test on a sample of up to five completed projects, and a plan for how Claude reaches the firm's files safely. Nothing is connected to the firm's drive until the IT lead approves the rules in writing.