The System Your Office Runs On.
Jobs, customers, approvals, documents and management visibility in one custom system — shaped around how your business already works, wired into the accounting and field tools you keep, and owned by you rather than rented by the seat.
Five Systems, and theTruth in Someone's Head.
Most established operations did not choose their software — they accumulated it. A scheduler here, a quoting tool there, an accounting package, a shared drive, and spreadsheets filling every gap between them. It works, until the business grows past the point where one person can hold the whole picture. Here is where it leaks.
The answer lives in five places
Job status is in one app, the customer history is in another, the signed paperwork is in email, the numbers are in the accounting package, and the real story is in somebody's head. Answering where a job stands means asking a person.
Approvals happen verbally
Work gets authorised in a phone call or a text and nobody writes it down in a place the invoice can find later. The gap between what was agreed and what gets billed is margin, and it only shows up at month end.
Documents scatter
Photos on phones, PDFs in inboxes, signed changes in a folder someone made. When you need the trail — a dispute, a claim, an audit — reconstructing it is its own project.
Double entry everywhere
The same job gets typed into the scheduler, then the invoice, then the spreadsheet management actually reads. Every re-key is a chance to be wrong, and the three copies drift apart.
Management reporting is archaeology
Knowing this month's real position means somebody exporting, pasting and reconciling for half a day. By the time the picture is assembled, it describes a month you can no longer change.
The software rents you its shape
Off-the-shelf platforms charge per seat, per month, forever, and make your operation fit their workflow. The parts that do not fit become manual workarounds — which is where the spreadsheets came back from.
One Record of the Work.
What a build in this category typically covers. Scope is set against your operation, not against this list — but this is the shape.
Jobs & work orders
One record per job carrying its scope, schedule, crew, site, status and history — created once, updated where the work happens, and readable by anyone who needs it without asking a person.
Customer & account records
Every customer's sites, contacts, history, pricing and paperwork in one place, so the person picking up the phone has the same picture as the person who ran the last job.
Approvals in writing
Scope changes and authorisations captured where they happen, priced against the agreement, and recorded before the work proceeds — so billing reflects what was actually agreed.
Document handling
Photos, signed changes, certificates and reports attached to the job that produced them, organised while crews just do the work — not filed afterwards by whoever has time.
Management visibility
The operating picture as a live view rather than a monthly reconstruction: what is open, what is stalled, what is owed, and where the work actually stands right now.
Roles & permissions
Office, field and management each see what they need and nothing they should not, so one system can safely replace the five that grew up around the gaps.
Answer the Question Without Asking Anyone.
A build in this category has done its job when the state of the business is visible without a phone call: where each job stands, what was approved and by whom, which documents exist, and what the month actually looks like while there is still time to steer it. Kilt Contracting describe the result as the office running on one system instead of five.
- We build the operational layer, not your accounting ledger. Your books stay in QuickBooks, Sage or Xero, and we integrate with them.
- We do not replace systems that are working. Where an off-the-shelf tool already fits, the honest answer is to integrate with it and build only what is missing.
- We do not sell per-seat licences. The system is yours; adding people does not change what it costs to run.
- We do not take on work we cannot staff properly. If a build is not a fit, we say so on the first call.
Five systems → one
Kilt Contracting · live in production
A general contractor working across Edmonton and Calgary ran the office on spreadsheets, texts and memory. We built one custom operations platform shaped around how they actually run projects — intake through to invoicing — owned by the company that runs on it. The result is client-reported, not independently audited.
Operational Software, Answered.
What Counts as Operational Software?
The system your business actually runs on day to day: jobs and work orders, customer records, approvals, documents, and the reporting that tells management where things stand. It sits between the field and the books — it is not your accounting package, and it is not a generic CRM built for sales pipelines. It is the record of work.
How Is This Different From Buying an Off-the-Shelf Platform?
Off-the-shelf software rents you a workflow, per user per month, and your operation has to bend to fit it. A custom build is shaped around how you already run, integrates with the tools you are keeping, carries no per-seat fee as you grow, and is an asset you own. That said, custom is not automatically right — where a packaged tool genuinely fits, integrating with it is cheaper and faster than replacing it, and we will tell you so.
Will It Work With the Systems We Already Have?
That is usually the point. Most builds keep the accounting package, the field app and the document store already in place, and connect them so a job entered once appears everywhere it is needed. Our integrations catalogue covers the platforms we build against most often; a connector your operation needs is part of scope rather than a feature request on someone else's roadmap.
How Long Before We Are Actually Using Something?
Builds are phased so working software reaches the people who need it early — usually the piece that stops the biggest leak first — rather than one launch months out. What that sequence looks like for your operation is what the first call is for: we map how work moves through your office and put a real scope and timeline against it.
Who Owns the System and the Data In It?
You do. The software is built for your business and the data in it is yours, exportable on request. How hosting, access, permissions and export work on your specific project gets written into the scope agreement rather than left to assumption — the Trust Center covers the questions we answer before a build starts.
Start with the operation, not the software
Book a 30-Minute Call.
30 minutes. We map how work moves through your office today, show you where it leaks, and hand you a costed plan for the system that fixes it — whether you build it with us or not.
Edmonton, Alberta · No commitment · 587-937-6948