How Atlas Excavating built the guardrails to take Claude company-wide
Faye authored the control design that let Atlas Excavating take Claude company-wide, and gave the organization a foundation it keeps extending with workflows and automations of its own.
The Challenge
Reading spec packages was the one job no tool could touch — until it could
Atlas Excavating is a heavy-civil and underground-utility contractor. Its commercial work turns on reading long municipal spec packages.
Atlas moved to Claude on its own. Adoption was organic, usage quadrupled between January and June 2026, and in February 2026, before engaging Faye, Atlas wrote its own company-wide AI policy.
Widening access across the company was a larger undertaking. Atlas works under client confidentiality obligations, and leadership wanted a governance framework in place first.
Atlas engaged Faye to build that framework. Faye ran a readiness assessment across staff and management, then a two-day on-site AI strategy workshop. The control design followed, together with per-integration guardrails that Faye fully developed, covering the contractor’s ERP, estimating, project management, CRM and HR systems.
What Faye Delivered
A control design built around four layers
Control design
Organized around four layers — permission, source system, instruction and detection — with an explicit rule assigning each kind of risk to a layer. What must not happen is blocked at the permission layer; what is a matter of judgment is steered at the instruction layer.
Instruction layer
An organization-instruction set written to apply to every person in the organization, in every conversation. Project-level instructions sit beneath it.
Project architecture
Five Claude projects specified for Atlas’s recurring workflows, each carrying explicit limits: analysis and drafting only, with pricing, bid issuance and contract positions reserved to qualified staff.
Per-integration guardrails
A read-by-default, write-by-exception posture across the contractor’s operational systems. Read access is granted only where a role requires it, and write access requires a documented use case and a named approver.
Human-in-the-loop by design
Two rules govern every workflow. First, anything touching a bid, an estimate or a contract position is a draft until a qualified person signs off. Second, no workflow is released until the same question, run three times, returns materially consistent answers.
Review Cadence
Usage is reviewed monthly, connector scope quarterly, and the full policy semi-annually, with an unscheduled review on any material change to the stack.
Ownership
The design assigns ownership to platform administrator roles and to an AI committee that owns use-case intake and exception review.
The decision it enabled
With the control design in hand, leadership approved company-wide access.
What Atlas Achieved
Adoption
Atlas had 37 Claude users as of September 2026.
Scheduling at scale
On a 1,300-home water service line replacement, building the phase one schedule took a manager 40 hours. Using Claude, with the first job as the reference, the schedule for the full 1,300 homes was rebuilt in 45 minutes.
Workflows built in-house
Atlas employees built every production workflow:
- An inbox triage playbook distributed company-wide, staff self-reported 30 minutes a day in return; plus scheduled automated reports
- Long-running project records organized into searchable Claude projects, so teams can review a project’s full history in one place
- Automated monthly reorganization of historical project reporting into a queryable structure
- Meeting action items routed automatically into the company’s existing management-reporting system
Self-sustaining adoption
Atlas continues to identify and build its own use cases.
Our hardest problem has always been documents. We bid off long municipal spec packages, and that’s the part of this business nobody could ever put a tool against. Claude can. Our people found that out on their own and it spread fast — faster than I expected.
What we needed before we could open it up to everybody was a control design. Which role can reach what, which systems stay read-only, what the ground rules are. That’s what Faye built. Their guardrails say plainly that anything touching a bid, an estimate or a contract position is a draft until a qualified person signs off — and that if you ask the same question three times and get three different answers, the workflow isn’t ready. That’s the right standard, and it’s why I was willing to say yes to the whole office with Faye supporting us.
The tool does the reading and the comparing. We still do the deciding. Nobody here is confused about that
Casey Dillon
CEO, Atlas Excavating