Common questions aboutconstruction workflow automation.

One fixed price, set in writing after scoping — no hourly billing, no T&M. We scope the workflow on a 20-minute call, then quote the build with acceptance criteria and a go-live date in the contract before kickoff. Pay app assembly, subcontractor compliance, and Sage export pipelines are the workflows we know best.

Yes. Pay app assembly is the workflow we know best — we built and ran pay-app automation inside a national home builder. We pull cost data from Sage 300 CRE, reconcile against committed cost in Procore, assemble the per-subcontractor pay app PDF, and log every step for the controller's review. An engagement typically takes 4–6 weeks; the goal is converting a one-day-per-month manual process into a one-click run.

Discovery to live system in about 4–6 weeks for a single workflow. Week 1 is blueprint and scope lock. Weeks 2–4 are build with scheduled department check-ins. Week 4–6 is walkthrough, training, and handover. Larger multi-workflow builds run 8–12 weeks. Every milestone date is in the contract.

Yes to all three. We build inside the systems you already pay for. Most of our work has been on Sage 300 CRE and Procore, but we've worked across Sage Intacct, Buildertrend, SharePoint, Microsoft 365, Bluebeam, and a long tail of Excel-heavy internal tools. If your team already opens it daily, we can build on top of it.

Scope, acceptance criteria, fixed dollar amount, and a firm go-live date — all in writing, all in the contract, all signed before kickoff. 50% deposit on blueprint sign-off, 50% on go-live. If we miss the date, the price doesn't move up. No discovery sprint, no T&M creep, no quarterly status committee.

No. We build inside your accounts, using your credentials, on your infrastructure. Code lives in your repo. Logs live in your systems. Nothing is hosted on our side after handover. We're a partner, not a vendor with a data lake.

We stay on call through the first full cycle (a month for monthly workflows, a quarter for quarterly ones) and watch the first run without touching it. After that, the runbook in your repo covers recovery steps for the failure modes we've seen. Optional ongoing support is available as a separate monthly retainer — but the systems we build are designed to run unsupervised after the first cycle.

Both. Our AI Trainings practice covers Copilot rollouts for office staff, custom assistants trained on your specs and SOPs, and AI integrations into Sage, Procore, and SharePoint. The same fixed-price model applies. We start with the task, not the model — and pick the model based on your data sensitivity and existing licensing (Microsoft, Google, Anthropic, OpenAI).

Our sweet spot is general contractors and home builders doing roughly $20M to $200M in annual volume — large enough that manual workflows are bleeding real money, small enough that adding a six-figure head count for a data team isn't the right move. We've worked inside a national home builder too and can scale up.

Confluxion Point was built inside a national home builder — running the data function from solo hire to team lead. We know what manifest billing looks like, why pay apps take ten days, and how Sage data actually flows. Most consultants who pitch construction firms have never seen the inside of a pay app cycle. We have.

Alongside, almost always. The analyst knows the business — we hand them better tools, a cleaner data layer, and dashboards that don't need to be rebuilt every Monday morning. We can also help you scope and hire your first dedicated data person when the time comes.

Yes. The Utah Artificial Intelligence Policy Act (Utah Code Title 13, Chapter 72) has been law since May 1, 2024 and was amended May 7, 2025. It explicitly names construction contractors as a regulated occupation, which means you face stricter scrutiny than a generic Utah business. The law requires disclosure when AI is involved in consumer interactions, makes you legally accountable for what your AI says, and eliminates “the AI did it” as a defense. Our full UAIPA guide for contractors walks through the penalty math and the five mistakes we see most often.

Up to $2,500 per violation as an administrative penalty under Utah Code §13-2-5 (imposed by the Utah Division of Consumer Protection, no court action required), and up to $5,000 per violation as a civil penalty under §13-11-17 for knowing violations (imposed by the Attorney General, in addition). Because penalties are counted per violation, a pattern of undisclosed AI interactions can aggregate into a five- or six-figure exposure, plus a possible DOPL referral.

Three credentials, ranked by what matters in court. (1) We hold the AIGP — the IAPP's Artificial Intelligence Governance Professional credential — most IT firms don't. (2) We carry AI-advisory E&O insurance, explicitly written to cover attestation work; standard IT E&O policies are starting to exclude AI advisory entirely. (3) We have an internal framework (CARF — the Construction AI Risk Framework) mapped to UAIPA, NIST AI RMF, and ISO 42001. Beyond credentials, your IT vendor implemented your tools — auditing implementations they did themselves is a conflict of interest.

No. A policy on paper is not a defense under §13-72 — the Division does not care that the policy existed, they care whether it was enforced. Real enforcement requires four things: technical controls (public AI tools blocked or proxied on company devices), usage logging, quarterly re-review, and annual signed acknowledgments from every employee. Most firms we talk to have a draft policy and none of the enforcement scaffolding.

It's a formal opinion letter, AIGP-signed, stating where your firm stood against Utah Code §13-72 as of the engagement date. Three audiences use it. Insurance carriers are starting to ask for documentation like this on E&O renewals. GC subcontractor agreements and government RFPs are starting to include AI compliance clauses, and our letter is the document you hand the GC's compliance team. Most importantly, if a complaint ever lands, you hand it to your attorney — it's the evidence that you took the obligation seriously.