Discuss your projectChange orders captured and signed on site and billed instead of lost, with job cost visible while the work is underway. Daily logs, subcontractor documents, and equipment records move from paper to the phone.
Illustration of a change-order application built by Baybloom for a contractor: changes recorded on site, routed for approval, and posted to the job in accounting.
Owners, operations managers, and controllers at general contractors, specialty trades, and building services firms. A project platform may already be in place; the workflows that still run on paper and email are the ones between the field, the office, and the accounting system.
The workflow
The steps we see most often in this kind of operation.
What we build
Capture scope changes on site with photos, pricing, and signatures, route them for approval, and post approved amounts to the job budget.
Record crews, weather, deliveries, delays, and photos from the phone, giving project managers a reliable record for claims and client updates.
Track insurance certificates, lien waivers, and licenses per subcontractor, with expiration alerts and automatic payment holds when something lapses.
Know where each machine is, which job it is charged to, and when service is due, with hours and costs posted to the job.
Show committed, actual, and forecast cost against budget for each job, updated from the field and accounting as the work progresses.
Let foremen record crew hours against jobs and cost codes on the phone, feeding payroll and job costing from the same entry.
Your first release
How the work runs
We start with the people doing the work and the systems around it, then write down the first release: what it includes, what it leaves for later, the integration decisions, and the acceptance criteria. Nothing is built until that scope is agreed.
We build in releases you can review as the work takes shape, using realistic data. Every release carries tests, a security review, and documentation. Integrations are tested against real records, with exceptions visible.
Your team receives the documentation, the runbooks, and the training to run the system, and we stay on for continued engineering when you want it.
Scope and price
Every project is priced from a written scope. These are the factors that move it most.
Construction accounting systems vary in how they accept job costs and change orders, and complex cost code structures add mapping and testing.
Connecting to an existing project platform for jobs, budgets, and documents adds integration work that depends on what the platform’s API exposes.
Sites without a signal, gloved hands, and shared devices require offline capture, simple screens, and testing in real site conditions.
Different trades and divisions often use different forms, approval paths, and cost structures that each need to be agreed on and configured.
Mechanical contractor
On many mechanical jobs, a foreman agrees to a change on site, photographs a paper form, and hopes it reaches the office before the job closes; some changes never get billed. A first release puts change orders on the foreman’s phone, working without a signal, with photos and the client’s signature. Each change routes to the office for approval and posts to the job in Sage or Foundation, and the project manager sees cost to date while the work is underway. Subcontractor document tracking, with payment holds on expired certificates, often comes next.
Questions
What leaders in this industry ask us first.
Keep it. The gaps are usually the workflows the platform does not model for your trade, and the connection to accounting. We build those and connect to the platform rather than replace it.
Yes. The field screens capture offline and sync when the signal returns.
That is usually the point. Change orders, time, and equipment charges post to the job, with exceptions visible to the controller.
Certificates, waivers, and expiration dates are tracked as records, and payment is held when a document is missing or expired.
Yes. The change order is sent to the client contact with scope, photos, and price, and they approve with an electronic signature on a phone or computer. The signed record is stored on the job, and the approved amount flows to the budget and billing.
Foremen help design the screens and test them on site. The app opens to the current job, each common action takes a few taps, and it replaces paperwork they already do. A walkthrough at a toolbox talk is usually enough to get crews started.
Yes. Schedules of values, progress by line item, and retainage can be tracked per job, with progress billing drafts produced from approved field quantities and change orders. The controller reviews each draft before it posts to accounting, so billing reflects the work in place.