Tribal Knowledge Isn't a Scalable Asset

FieldCo runs a multi-branch field service operation. Thousands of jobs move through their system every week, coordinated by schedulers who, until recently, built their plans from a flat table view and years of hard-won instinct.

Senior schedulers knew which techs a client always requested, which technicians worked well together, which sites had certification requirements, and which routes looked fine on a map but weren't in practice. The problem was that none of that knowledge was written down anywhere. It just lived in people's heads, impossible to hand to a new hire and impossible to scale past the person who carries it.

Results in weeks that most scheduling software never delivers.

• ~$7M Projected revenue increase from national growth enablement through additional jobs booked per tech.
• ~$13M Projected EBITDA uplift from national expansion driven primarily by tech utilization, route optimization, and scheduler-driven growth.
• ~89,000 Hours saved annually across scheduler time and tech utilization time.

Years of routing experience in a scheduler's head isn't a scalable asset.
It’s a bottleneck.

The FieldCo's scheduling team's expertise, knowing which tech to send and each technician's scheduling preferences, is their competitive advantage.

But it was simultaneously the primary constraint on their growth.

The software system they worked out of daily exacerbates this constraint further. Gaps compounded from FieldCo’s software system being unable to adapt to their business workflows:

• Route inefficiency Technicians weren't being assigned optimal paths between jobs. No system was reasoning about geography, load, and availability at the same time, so hours that should have been billable were wasted.
• Mismatched labor costs Senior technicians, with their higher billable rates, were regularly sent to jobs a junior tech could handle. Without an automated check, the overspend was invisible until it showed up later in margins.
• No utilization visibility A static list doesn't show when one technician is overloaded while another two postcodes over has open capacity.
• Knowledge that couldn't be written down Schedulers carried years of context: which technician a client always requested or who preferred early morning vs. late night jobs. When that person left or went on vacation, the knowledge went with them.

Ciridae built an agentic system that let schedulers completely reimagine how they interface with their scheduling platform. Now, instead of comparing notes with a co-scheduler or reading through pages of tedious documentation on their legacy platform before scheduling a job, it’s as simple as a conversation with their AI agent, Beacon. What started as a pilot with 6 technicians is now expanding nationally, because the business impact is so dramatic FieldCo can’t wait to get it in the hands of all schedulers across every single branch in every province.

• 01Route optimization engine A constraint solver reasons simultaneously across geographic locations, drive times, technician certifications, regional legal requirements, client site preferences, team compatibility, and trainee pairing rules. The output is the right technician, at the right job, via the right path, matched by cost and qualification together.
• 02AI scheduling chatbot Schedulers can ask Beacon who is available in a region next Tuesday, surface a routing conflict, or define a rule the system should follow. Each request adds operating context for subsequent schedules.
• 03Rules engine Schedulers define pairing requirements, certification constraints, site preferences, and technician compatibility rules through conversation. Beacon encodes those rules and applies them permanently.
• 04Privacy-preserving architecture Technician personal data informs routing without being exposed in Beacon's interface. FieldCo's existing database remains the source of truth; Ciridae built around it, not on top of it.

"It's definitely a more foolproof way to be more strategic about scheduling."- Client scheduler

"I like the fact that there is good visibility from a high level and then it also digs into details."- Client scheduler

The FieldCo platform is powered by Crucible.

Crucible gives teams the speed of AI-assisted software development without giving up the ownership, robustness, and engineering discipline required to run real business software.

The Ciridae team built the initial agent, Beacon, in a single day, because Crucible provides all of the agentic components needed out of the box: observability, evals, tracking, and tool reliability. When none of that has to be built from scratch, it means engineering time can go straight into the product instead of the plumbing underneath it.

That head start is how we build enterprise-grade software for FieldCo at a previously unfathomable pace.

• Production infrastructure without the cold start.+
  Crucible eliminates weeks of foundational setup (deployment, environments, auth, monitoring, IaC) so engineering time went directly into the workflows and agentic components that mattered to FieldCo's scheduling team.
• Enterprise-grade security at startup pace.+
  Ciridae moved at the pace of a small team without compromising the standards a nation-wide field operation requires. Hardened defaults for security, governance, and reliability ship out of the box.
• A managed system today, extensible tomorrow.+
  Ciridae operates and maintains the platform for FieldCo as a fully managed system. Because Crucible preserves full access to code and infrastructure, that arrangement is a choice, not a lock-in. As FieldCo expands nationally, the platform expands with them.