The forms app. The field tracker. The workflow add-on. Each one covered most of the job and left your crew carrying the rest in spreadsheets and phone calls. When standard software doesn’t fit the work, the same BC team that builds ALPHA OS builds what’s missing.
One call. Describe the workflow, we take it from there.
§ 01: What we build
Recent builds, each one a workflow off-the-shelf software could not carry. Custom software for construction, scoped and priced before we start.
An estimating and project desk for a residential builder.
Bids, budgets, and job tracking that had sprawled across a Power Apps patchwork and a wall of Excel, rebuilt as one platform the office and the field both work from.
A full CRM, built to fit how a company sells.
Pipeline, contacts, quotes, and follow-up shaped around a real sales process instead of bent to fit an off-the-shelf tool, with estimating and project tracking in the same system.
Performance reviews and the people record, in one place.
Review cycles, ratings, and the employee details that usually live in a dozen spreadsheets and someone's inbox, pulled into a single module a manager can actually run.
Field forms for a mechanical contractor.
Crews wrote job details on paper and handed it in days later. Now they log it from their phones at the site, and the office sees it the same day.
ERP connectors.
The connectors that post ALPHA AP's coded payables into maestro*ERP and Sage 50 were custom builds first. If your systems need to talk to software that won't talk back, that's a job we know well.
§ 02: How an engagement runs
No discovery retainer. No hundred-page requirements document. Four stages, and you know what you’re buying before you buy it.
Scope
One call. You walk us through how the work actually happens. We come back with a fixed scope in plain English and a straight number.
Build
You see working software early, running your scenario, not wireframes. Your people tell us what’s wrong while it’s still cheap to change.
Install
The same white-glove install as every ALPHA deployment. We connect the build to your systems, load your data, and train every desk that touches it.
Care plan
Every build ships with one. When something needs to change, you call the people who wrote it, not a ticket queue.
§ 03: Why the same team
The team that builds your tool is the same team that runs ALPHA OS every day, next to an AP module posting payables into real ERPs right now. When your build runs on ALPHA OS, it inherits plumbing the platform has already proven on live jobsites: sign-in, permissions, review queues, approval routing. You pay for the part that’s actually new.
And some builds don’t stay custom. When your problem turns out to be the whole industry’s problem, it becomes the next ALPHA OS module, built with you as the first client.
§ 04: FAQ
What does a custom build cost?
You get a scoped quote before work starts. Walk us through the workflow on one call and you leave with a fixed scope and a straight number. Pricing scales with the size of the build, and the quote covers the build and the install, with a care plan priced alongside it.
Can you connect a custom build to our ERP?
Yes. Connectors are one of the most common things we build. The connectors posting ALPHA AP’s coded payables into maestro*ERP and Sage 50 run today. Tell us what you run, and we build the connector.
Who supports a custom build after launch?
The same ALPHA team in BC that built it. Every build ships with a care plan: we watch it, we fix it, and we change it as your operation changes. No handoff, no ticket queue in another time zone.
§ 05: Get started
One call. Walk us through the forms, the spreadsheets, and the workarounds, and you leave with an answer: a custom build, an existing module, or not worth building at all. We’ll tell you which.
Bring us the problemBack-office software for construction. Built in BC, working across Canada, since 2016.
Platform
Get started