One Operational System for
Kilt Contracting's Entire Back Office.
AltaPro AI built Kilt Contracting a custom operations platform connecting jobs, quotes, contracts, invoices, communications and owner approvals — with control enforced in the software.
The Office Work Was Competing With the Field Work.
Kilt Contracting is a general contractor working across Edmonton and Calgary. Like most owner-operated construction businesses, the same person who runs the machines is also the one who has to win the work, close it, and keep the money moving.
That's the tension we set out to solve: the office work that wins and closes jobs shouldn't have to compete with the field work that delivers them.
So we built Kilt Contracting Operations Software— one operational system that takes repetitive work off the owner's plate and keeps the business moving, while preserving human control over the decisions that matter.
At a glance
- Client
- Kilt Contracting
- Industry
- General Contracting
- Location
- Edmonton & Calgary, Alberta
- Build
- Custom operations software
- Approach
- Controlled automation with owner approval
- Status
- Live in production
One Platform Across the Whole Operation.
Instead of adding another disconnected tool, the platform connects the work already moving through the business.
It wins and closes the work
The office work that turns a lead into a booked, paid job gets handled — so the owner isn't stuck at a desk to keep revenue moving.
It runs the day
The moving parts of a live operation stay organized and up to date, without the back-office admin quietly eating the week.
It never lets a lead go cold
Inbound gets answered and followed up across the channels the business actually uses — nothing slips through the cracks.
It works when nobody's watching
The platform keeps routine work moving in the background and surfaces only the decisions that genuinely need the owner.
Autonomy You Can Turn Up Like a Dial.
Graduated autonomy is AltaPro AI's answer to the number-one worry about business AI: "I can't just let it loose on my clients." You don't. Every capability starts under human control and only earns more independence once it's proven itself — and the owner can always dial it back.
Draft
The platform prepares the work; a person always sends it.
Ask First
The platform acts only after a clear go-ahead. This is the default.
Automatic
The platform acts on its own only for capabilities the owner has approved.
Anything touching money or a client starts on the tightest setting — and nothing is ever on autopilot without the owner deciding it should be.
Production Software. Real Operations.
Kilt Contracting Operations Software runs against real jobs, a real crew and live client conversations. It is deployed software doing operational work for an Alberta business every day.
The result is a persistent operational layer that keeps routine work moving and escalates the decisions that require the owner.
Architecture & The Hard Parts.
The engineering behind the platform — how it connects to a live business while keeping permissions, approvals and reporting grounded in what the software actually did.
An Operations Layer That Acts on Real Data
The platform includes an embedded AI operations layer powered by Anthropic's Claude. A typed tool layer lets it work against the live CRM: moving jobs through the pipeline, preparing documents, logging expenses, organizing communications, booking events and escalating decisions. Next.js, React, Prisma and Postgres keep the AI connected to the same governed operational data the office uses.
Autonomy as a Code-Enforced Dial
Every outbound, money- or client-touching capability carries a level — draft-only, ask-first, or auto — checked server-side before anything leaves the building. Sending quotes, contracts and invoices, and replying to clients, all start on the tightest setting; a background job can only send once a capability has been explicitly promoted to auto. The hard part was a permission model that's safe by default yet can be turned up one notch at a time as trust is earned.
Wired to the Channels the Business Actually Uses
Outreach runs on real infrastructure, not a sandbox — Twilio for SMS and voice, in-app calling with a SignalWire-first, Twilio-fallback path behind a single UI, email over standard IMAP and SMTP, and Facebook Messenger. Inbound messages are read and threaded; outbound always passes back through the autonomy gate.
It Works When Nobody's Watching
Scheduled jobs — morning briefings, invoice-reminder sweeps and message follow-ups — keep the operation moving in the background and escalate by SMS only when a human decision is genuinely needed. A hard backstop prevents the system from quoting a price, rate or commitment on its own.
One rule sits above all of it: the system never reports an action as completed unless the underlying tool ran and returned success.
Out of respect for our client
We'll talk architecture, but the specifics stay private: how the system is configured, its prompts and guardrails, and the day-to-day details of the operation are our client's — and we keep them that way. When we build for you, your systems and your numbers get the same discretion.
Your operation is next
What Should Your Operations System Run?
In 30 minutes, we map your operation, identify the work slowing it down and determine whether custom software is the right next step.
Edmonton, Alberta · No commitment · 587-937-6948