We are hiring. See the roles

Case study · Metec

Turning an engineering firm AI native.

Summarise with AI
Industry
Consulting and MEP engineering
Customer
Metec, 100+ people, Bray
Engagement
Training and Change Management, Claude for the team, FDE build
Since
April 2026
Metec
The challenge

The rules before the tools.

Metec is a consulting and MEP engineering firm in Bray with more than a hundred people, and in the spring of 2026 its managing director sponsored bringing AI into the firm. An engineering practice handles client and project information all day, so the work started with a question of order rather than a question of tools: the firm’s AI policy was written and in place before any tool reached the team.

From there the engagement has run in sequence. Policy and training first, then Claude for the whole team with Nomad running onboarding and governance month to month, then a four week discovery that mapped how the firm actually runs, and now a resourcing tool in build on the systems Metec already uses. Each step has set up the next.

Policy first
the firm's AI policy written in April 2026, before a tool reached the team
Whole team
Claude across the firm, seats added month by month as people asked, onboarding and governance run by Nomad
Mapped
the firm's processes drawn department by department in a four week discovery
In build
a resourcing tool with live timesheets, forward allocation and cash flow forecasting, go-live in weeks
The approach

Rules, then tools, then the systems.

01

Policy and training

In April 2026 Nomad wrote Metec's Artificial Intelligence Policy before any tool reached the team, so the rules were in writing first. Training Phase 1 followed straight after: the policy, Claude set up for the firm, and the first hands-on sessions. Phase 2, through May and June, ran on the team's own work rather than on examples.

02

Claude across the firm, supported month to month

From May 2026 the team has worked on Claude under Nomad's managed seats. Nomad runs onboarding and keeps use aligned with the policy on a monthly cadence, and seats have been added month after month as more people asked for one. The number is still growing, and that is the point: adoption that builds instead of fading after the launch.

03

From the process map to a resourcing tool

A four-week discovery in June assessed the whole company, mapped how the firm runs department by department, set out a plan for Claude across the business, and specified a Resource Visibility Tool: who is on what, when, and what is coming. Signed in September and now in build on Nomad's own platform, wired to the systems Metec already runs, their CRM among them. Live timesheets with a mobile app land first, then pipeline and forward allocation with profitability by job, and cash flow forecasting.

This engagement is ongoing. The policy, the training and the Claude rollout are delivered and supported month to month. The resourcing tool is in build, with go-live in six to eight weeks and a platform subscription after that, and Metec keeps the systems it already runs. We add outcomes here as the work lands. The build is the kind of work we do as FDE, and the first phase is our training.

One email a month.

What we are seeing inside the businesses we work with, what worked and what did not.

One short email a month. Unsubscribe any time.