Seven Things We Build.
We build the software established operational businesses run on, integrate it with the systems they keep, and apply AI inside it where that genuinely helps. Everything below is scoped against your operation and owned by you when it ships.
Most Operations Did Not Choose Their Software.
They accumulated it. Whichever of the six below you start with, this is usually the picture we are working from.
Five systems → one
General contractor · live in production
A general contractor across Edmonton and Calgary moved off spreadsheets, texts and memory onto one operations platform built around how they actually run projects. Client-reported.
See it01
Operational Software
The business problem
The state of the business lives in five systems and one person's head. Job status is in the scheduler, history is in the inbox, approvals happened on the phone, and the number management reads is a spreadsheet somebody rebuilds each month. It holds together until the business outgrows the person holding it.
Example workflows
- Jobs and work orders — one record carrying scope, schedule, crew, site and status
- Customer and account records, with history and paperwork in one place
- Approvals captured in writing before the work proceeds
- Documents attached to the job that produced them
- Live management visibility instead of a monthly reconstruction
- Roles and permissions so office, field and management each see their own view
The intended outcome
The state of the business is answerable without a phone call — what is open, what is stalled, what was approved and by whom, and what the month looks like while there is still time to change it.
2–3 hrs → minutes
Demolition contractor · live in production
Bid assembly that took two to three hours per submission now runs in minutes, with a go or no-go read available in under a minute. Client-reported.
See it02
Quoting & Document Workflows
The business problem
Pricing work depends on judgement held by one or two people and a spreadsheet only they fully trust. Quoting capacity is capped by their availability, two similar jobs get priced differently, and when a number is questioned six months later nobody can reconstruct how it was reached.
Example workflows
- Structured estimating against your own rate card
- Proposals and quote documents generated from the priced scope
- Pricing inputs — materials, labour, equipment, subcontract, margin
- Review and approval before anything reaches the client
- Extraction of the details buried in incoming tender and spec documents
- A recoverable record of how each price was arrived at
The intended outcome
Quotes go out consistently regardless of who prepared them, estimator hours go to the work worth winning, and the basis of any price can be reconstructed long after the job closed.
52 platforms
Integrations catalogue · capability
The platforms we build against across accounting, CRM, field service, payments and messaging. A catalogue entry means we build against that platform — not a partnership, a certification, or a finished connector on a shelf.
See it03
Systems Integration
The business problem
When two systems do not talk, a person becomes the integration — exporting, re-keying, reconciling and catching the mistakes. That work scales with volume, produces no new information, and stops entirely when that person is away.
Example workflows
- Accounting handoffs — invoices, payments, customers and job costs
- CRM and sales data flowing into the systems that deliver the work
- Field systems connected to the office record
- Retries and idempotent writes so outages recover instead of dropping data
- Failure visibility — a broken handoff raises itself the day it breaks
- Field-level decisions about which system is authoritative
The intended outcome
A record entered once is correct everywhere it is needed, the monthly reconciliation stops being a task, and nobody's job is being the bridge between two products.
Inside the software
How we scope it
We treat AI as a capability within an operational system, not as the starting point for a project. If a workflow does not need it, we will say so and build the system without it.
See it04
Applied AI & Automation
The business problem
Most AI spending starts with the technology and goes looking for a use. That produces demos rather than systems. The useful version is narrower: specific, repetitive work inside software people already use, where the input is known and being wrong has a bounded cost.
Example workflows
- Extraction — pulling structured detail out of documents and email
- Drafting — first-pass quotes, summaries and replies a person then approves
- Knowledge retrieval — answers from your own documents, with the source shown
- Bounded actions — narrow, reversible steps with a human in the loop where it matters
- Routing and triage of incoming work
- Human review wherever the cost of being wrong is real
The intended outcome
AI does the part of the job that is genuinely repetitive, inside the system people already work in, and a person stays accountable for anything that reaches a customer or a ledger.
The task picks the model
How we scope it
We build with Claude, Gemini, OpenAI and Grok. The choice comes down to the job, the integrations, the data rules, the per-call cost and how much review the workflow needs.
See it05
AI Integration
The business problem
The system holds the work correctly. It is the reading, the drafting and the looking-up around it that still costs a person an afternoon — and none of that is a reason to replace software that otherwise does its job.
Example workflows
- Bid and tender documents read against your service lines before anyone opens them
- First-draft quotes priced from your own rate card rather than invented numbers
- Answers pulled from your own specs, contracts and past jobs with the source cited
- Inbound requests sorted to the right queue with a reason attached
- A named approver on anything priced, client-facing or contractual, recorded
- Defined behaviour when the model is unsure or the provider is unavailable
The intended outcome
One expensive workflow stops taking an afternoon, inside the software you already own, with a person still accountable for anything that reaches a customer or a ledger.
The record comes first
How we scope it
A portal is only ever as good as the record behind it, so we build it as a view onto records your operation already keeps rather than a second system to maintain. If the internal record is not trustworthy yet, we say so before publishing it to your customers.
See it06
Customer & Partner Portals
The business problem
Where is it, what did I approve, can I have that document again, what do I owe. Four questions your customers cannot answer for themselves, so someone in the office answers them all week by reading out of a system the customer could have read. The approval trail lives in whoever's memory is longest.
Example workflows
- Job and order status in the customer's language, drawn live from your own records
- Approvals and sign-offs captured in the portal, timestamped and attributed
- Documents, certificates and invoices tied to the job or order that produced them
- Owner, partner and subcontractor views under one permission model
- Reorder, service requests and other self-service actions that would otherwise arrive as email
- Access control enforced at the data layer, not hidden on a screen
The intended outcome
The status call becomes a link, the approval trail is shared rather than contested, and the customers who expect a portal stop treating you as the less professional option on the shortlist.
A different job
How we scope it
Getting a working prototype to production is not more of the same building — it is the part the prototype deliberately skipped. It is scoped as its own engagement so the boundary is explicit rather than discovered halfway through.
See it07
Vibe-Coded to Production-Ready
The business problem
You already built it yourself in Lovable, Replit, Bolt, Cursor or Claude Code, and it works. Then the first real customer arrives and the questions change: who can see what, what happens when a payment webhook fires twice, what happens when the schema needs to change, and whether anyone has ever restored the backup.
Example workflows
- Authorisation and access control that holds up to a real user list
- Data integrity — constraints, migrations and a schema that can change safely
- Payments that survive duplicates, retries and a provider having a bad day
- Error handling and monitoring, so a failure surfaces instead of going quiet
- Backups somebody has actually restored from
- The load it will genuinely see, measured rather than assumed
The intended outcome
The thing you built becomes something a business can run on and be responsible for, without throwing away the work that got it this far.
Specifically, What Would We Build?
The four categories below are how the deepest work is organised. These are the builds operators actually ask for by name — each with its own page, its own scope and its own honest account of where it stops.
- Legacy System ModernizationRetiring the Access database, the unsupported tool and the spreadsheet stack, without stopping work.
- Internal Tools & Admin PortalsThe one internal screen that replaces a spreadsheet, a shared inbox and three logins.
- Custom Web Application DevelopmentMulti-user operational web apps on a current stack, integrated and owned by you.
- Mobile Apps for Field CrewsCapture on site, work without signal, sync when it comes back.
- Job Costing & Margin TrackingKnow which jobs make money while they are still running, not at month end.
- Scheduling & Dispatch SystemsOne board the office and the field read the same way, built around your real constraints.
- Field Ticketing & Ticket-to-InvoiceTickets captured at the work, priced automatically, invoiced without retyping.
- Asset, Fleet & Maintenance TrackingWhere each unit is, what it earned, what it cost, and what service is due.
- Rate Cards & Contract PricingPer-client rates, tiers, minimums and escalators as rules — not as one person's memory.
- Proposal & Contract AutomationDocument generated from your numbers, signed in the same flow, deposit taken at signature.
- Document Data ExtractionSupplier invoices, POs, specs and tickets read into structured records instead of retyped.
- Field Forms & Site CaptureInspections, safety paperwork and photo evidence captured on site and filed automatically.
Estimating itself is covered on the category page above — custom estimating software.
- Custom API DevelopmentThe integration layer between your systems, built for the day a vendor changes the schema.
- Accounting IntegrationsQuickBooks, Sage and Xero wired to your operation so nothing gets entered twice.
- Data Migration & ConsolidationHistory moved across intact, duplicates resolved, and reconciled against the old system.
Reporting built on consolidated data has its own page — operational analytics & reporting.
The Rest of the Bench.
Real engagements that sit alongside the seven solutions above rather than inside them. Most clients arrive through one of the four and pick these up later, if at all.
Fractional AI Department
An ongoing engagement with a named lead and a live roadmap, for businesses that want continuous capacity rather than a single build.
ReadAI Consulting
Where the question is what to do rather than what to build: assessing workflows, sequencing the work, and saying plainly where software is not the answer.
ReadTraining & Enablement
Getting a team genuinely using what was built, plus practical AI training for people who need to work with these tools day to day.
ReadReporting & Analytics
Turning the data an operational system produces into the reporting management actually reads, rather than another export to reconcile.
ReadField Data Capture
Getting what happens on site into the system as it happens — tickets, quantities, photos, signatures and daily logs — so the office is not rebuilding the day from memory.
ReadCompliance & Document Control
Certificates, inspection records, safety documents and client prequalification held against the job and the crew, so a required package is produced rather than assembled under pressure.
ReadCustom CRM Builds
Where the operational system is primarily about customers and pipeline rather than jobs and crews.
ReadStart here
Bring Us the WorkflowThat Keeps Breaking.
30 minutes. We map how the work moves today, determine whether the problem justifies custom software at all, and hand you a scoped first phase — including an honest read on whether we are the right firm for it.
Edmonton, Alberta · No commitment · 587-937-6948