Cost vs estimate, by category
Actual cost against the budget it was sold on, split into labour, material, subcontract, equipment and overhead — so the variance has a cause, not just a number.
Private betaThe AI layer for construction — now onboarding
Know which jobs are going over —
Know which jobs are going over —
while they are still running.
It reads your accounting, project and payroll systems and answers one question in seconds: is this job making money? Cost against estimate, forecast at completion, and the jobs about to go over.
Self-hosted and read-only · no per-seat pricing · how the prediction works
One intelligence layer across the platforms you already run4 live · 10 coming soon · 41 mapped
Sage 300 CREQuickBooks DesktopNYC Open DataCSV / JSON & REST APIPower BI & ExcelNetSuiteSoonDynamics 365 Business CentralXeroSage IntacctSoonSage 300 (Accpac)Sage 100AcumaticaViewpoint Vista / SpectrumSoonCMiCFOUNDATIONDeltek VantagepointDeltek ComputerEaseJonasPentaSage 300 CREQuickBooks DesktopNYC Open DataCSV / JSON & REST APIPower BI & ExcelNetSuiteSoonDynamics 365 Business CentralXeroSage IntacctSoonSage 300 (Accpac)Sage 100AcumaticaViewpoint Vista / SpectrumSoonCMiCFOUNDATIONDeltek VantagepointDeltek ComputerEaseJonasPenta
Oracle Primavera P6SoonMicrosoft ProjectSoonSmartsheetProcoreSoonAutodesk BuildSoonAutodesk TakeoffSoonBuildertrendSTACKBuildingConnectedeSUBRakenOpenSpaceFieldwirebusybusyHCSS HeavyJobBluebeamSharePoint / Microsoft 365GCPayTexturaQuickBooks OnlineSAP S/4HANASoonRhumbixSoonOracle Primavera P6SoonMicrosoft ProjectSoonSmartsheetProcoreSoonAutodesk BuildSoonAutodesk TakeoffSoonBuildertrendSTACKBuildingConnectedeSUBRakenOpenSpaceFieldwirebusybusyHCSS HeavyJobBluebeamSharePoint / Microsoft 365GCPayTexturaQuickBooks OnlineSAP S/4HANASoonRhumbixSoon
An overrun caught in the week it starts is a conversation. The same number in a month-end pack is a post-mortem.
Your infrastructureRuns on your own server. No third-party cloud copy of your financials.
Every system you runAccounting and ERP, project management, scheduling, payroll and field.
Read-only, loopback-onlyNothing is written back, and the API is not reachable over the network by default.
Status you can checkLive or coming soon, stated per system. See what is wired up →
constructelligence · on your server
Live · read-only
Executive dashboardAll companies · updated 2 minutes ago
This monthQuarterYear to date
Contract value$48.2M▲ 6.1% vs last quarter
Gross profit21.4%▼ 0.8 pts vs estimate
AR outstanding$886K31% past 60 days
Jobs at risk3$1.06M projected overrun
Cost actuals vs estimateEstimate Actual Over
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Job profitabilityWorst margin first
Riverside$4.00M-6.2%
Foundry Lofts$2.11M-1.4%
Harbourview$3.05M+4.1%
Cedar Ridge$0.86M+6.8%
Mason Street$1.06M+9.3%
!26-104 Riverside is forecast $670K over budget — labor is running 14% above estimate since week 2.Open job →
What we mean by the AI layer
Not a chatbot bolted onto a spreadsheet. One layer on top of the systems you already run — and three specific things it commits to doing.
One layer that reads every system you already run, understands what the data means, and answers whether a job is making money — in seconds, while the job is still running, instead of being rebuilt by hand after close.
Cost vs estimateForecast at completionMoney at riskLabor forecastSoon
ConstructelligenceThe AI layer — reads, maps and answers across every system below
ReadMapAnswer
Accounting & ERPSage 300 CRE · QuickBooksLive
Labor & payrollTimecards · burden · OTLive
PurchasingPOs · commitments · APLive
Project managementProcore · AutodeskSoon
SchedulingPrimavera P6 · MS ProjectSoon
Field & documentsDaily logs · invoices · OCRLive
01
It reads where the data already lives
Not a copy somebody re-keys, and not a nightly extract that is stale before it lands. The layer sits on the accounting, project and field systems that already hold the truth — read-only.
02
It knows what the data means
Cost codes, change orders, retentions, payroll burden, over- and under-billing — mapped across systems that each name the same thing differently, including the decade of inconsistencies every installation carries. That mapping is the AI layer's real work.
03
It answers while the job is running
An overrun caught in the week it starts is a conversation with a project manager. The same number in a month-end pack is a post-mortem. That difference is the whole product.
What it is not
- A data warehouse
- A BI tool you model yourself
- An accounting system
- Anything that writes to your books
- A chatbot bolted onto a spreadsheet
It reads, shows the working, and stops there — the connector is read-only by design and the query
layer refuses anything that is not a SELECT.
Everything that makes a job cost more than it should
Twelve views across one intelligence layer, grouped the way a contractor asks the question: is this job going wrong, what is it doing to my cash, and can I trust the numbers I am looking at.
01
Catch the overrun
The four views that tell you a job is going wrong while there is still time to do something about it.
Forecast at completion
EAC, variance at completion and months-to-budget-exhaustion from each job's own burn rate, refreshed as transactions post rather than at month-end.
Overrun radar
Jobs ranked by exposure and by how far cost is ahead of schedule, with the driver named — the five you would ring this week, not the fifty in the ledger.
Committed cost & change orders
costed · committed · unapproved
Subcontracts awarded but not yet costed, and change-order work performed without an approval — the two ways a job's cost is worse than its ledger says.
02
Run the money
What is owed, what is unbilled, and what the hours are really costing — the four views a controller opens every morning.
Money at risk, in one figure
$4.1M · four causes
Projected overruns, work done but not billed, receivables past 60 days and the overtime premium — summed, broken down, and never guessed at when a table is missing.
Billing against cost (WIP)
Over- and under-billing per job, retention held, and how much of the portfolio you are financing rather than the owner.
AR and AP aging
Aged receivables and payables by customer, vendor and job, with collection risk and the invoices most likely to pass 90 days.
Labour burn, overtime and burden
Hours and loaded cost by job, month, employee and pay type — because on most jobs the overrun starts as hours, not as invoices.
03
Trust the numbers
The views that keep the other nine honest: what is misfiled, what is missing, and how to get it out.
Financial audit findings
7 checks · 2 findings · 1 to review
Duplicate invoice numbers, unnumbered bills, round-number bunching, cost on closed jobs, unallocated cost and pay-rate outliers — each with the money it implicates and the rows to check.
Costs posted where they should not be
Unallocated cost, closed-job postings and missing fields in the source data — found before they distort every number above.
Manpower and productivity
Headcount and hours per job against the plan, with non-productive time and double-time hotspots surfaced before they are another month of payroll.
Export and API
CSV · Excel · JSON
Any table as CSV or Excel across every company at once, and every module as a JSON endpoint — so Power BI, Excel or a script reads the same numbers the dashboard does.
Get the numbers out, in the shape you already use
Every table behind these views is a JSON endpoint, and any table can be exported as CSV or Excel — filtered, or in full across every company at once. Power BI, Excel and your own scripts read the same numbers the dashboard does, which is also how an accountant checks them.
- CSV or Excel for any table, with your own column order
- "All companies" exports stack every company database into one file, tagged by company
- Every module is also a REST endpoint — no connector project to get the data out
- Read-only throughout: nothing here can change your accounting data
Contract value
$48.2M
Gross profit
21.4%
AR outstanding
$886K
Jobs at risk
3
Being built now
What beta customers are getting next, in the order the cohort asked for it. These are not shipping today — they are the work in front of us, published so you can see whether the thing you need is on it before you commit.
Labor forecasting
Crew-level hours and cost projected to completion from the burn rate you are actually running, not the one in the estimate — by job, phase and trade, with the overtime premium separated out.
Example output
Riverside · labor to complete+$31K
1,840 hrs left at the current burn vs 1,420 budgeted
Cash-flow forecasting
Projected receipts and outlays by week, built from AR aging, the billing schedule and committed costs — so a retention release or a slow payer shows up before it is a problem.
Example output
Next 6 weeks · net cash−$212K
Low point week of the 14th, then a retention release lands
Change-order impact
What a pending change order does to margin and to the completion date, priced before it is signed rather than discovered in the next WIP.
Example output
CO #14 · pending, +$48K−1.4 pts
Margin 11.2% → 9.8% and the finish moves 6 days
Subcontractor risk scoring
Exposure by subcontractor across every job — payment history, backcharges, schedule slip and how much unbilled work sits behind them.
Example output
Glazing sub · across 3 jobsHigh
$186K of unbilled work behind them and 2 open backcharges
Automated WIP schedule
The WIP package generated from the same figures the dashboard already reads and reconciled against last month, instead of rebuilt by hand every close.
Example output
WIP · generated for 38 jobs2 to check
Reconciled to last month; 2 variances flagged for review
Field cost capture
Daily labor and installed quantities from the field feeding the same forecast, so percent complete stops being a number somebody estimates once a month.
Example output
Curtain wall · installed quantity+13 pts
34% installed in the field against 21% by cost
Beta customers set this order. The module your cohort asks for most is the one built next — the same rule the connector list runs on.
The questions this answers, in the words you would use
Ask it the way you would ask your controller. Each of these is a live view in the dashboard rather than a report someone assembles — and each names the module it lives in, so you can check the claim against the product.
You ask“Which jobs are over budget, and on what?”
Three jobs are forecast over budget. The worst is 26-104 Riverside: labor is +$212K (14%) against estimate, and the finishes crew is most of it.
26-104 Riverside · labor+$212K
26-121 Summit Hotel · subcontract+$96K
26-109 Elm Park · materials+$41K
Ask nextWhy is Riverside labor over?
Job cost variance
The gap between what a job was estimated to cost and what it has cost so far, split by cost category.
CostOpens Costs & estimates
You ask“Are we over-billed anywhere this month?”
Three jobs are billed ahead of cost, $418K in total. Most of it is one job billed to a schedule of values that is running ahead of the work.
26-104 Riverside+$186K
26-095 Foundry Lofts+$131K
26-101 Mason Street+$101K
Ask nextWhich jobs are under-billed?
Work in progress: over- and under-billing
How much you have billed against how much cost you have put in place, job by job — the number that decides whether revenue this month is real.
CashOpens Predictions → WIP aging
You ask“Where does this job finish if nothing changes?”
At the current rate it finishes at $4.19M against a $3.52M budget. CPI is 0.84, so it is paying $1.19 for every $1.00 of work earned.
Forecast at completion$4.19M
80% range$4.02M – $4.37M
Crosses budgetweek 26
Ask nextWhat if labor improves 10%?
CPI, SPI and forecast at completion
Earned-value cost and schedule performance, plus EAC, VAC and TCPI per job, with burn-rate projections for months-to-budget-exhaustion.
CostOpens Predictions → EVM
You ask“What does a foreman actually cost us an hour?”
$48.20 of pay is $71.90 once it is loaded — 49% on top. That is the rate your estimates should be carrying, not the pay rate.
Base pay$48.20
Burden & fringe+$17.30
Insurance & payroll tax+$6.40
Ask nextWhich crews run the hottest rate?
Labor burden and fringe
The difference between a worker's pay rate and what they actually cost the company, including fringe and burden, by job and by employee.
LaborOpens Labor & payroll
You ask“Who is burning overtime, and on which job?”
Crew 4 on 26-112 is at 31% overtime and $38K of premium this month. No other crew on any job is above 12%.
Crew 4 · 26-11231% · $38K
Crew 2 · 26-10412% · $11K
Crew 7 · 26-0959% · $6K
Ask nextWhat does that do to the loaded rate?
Overtime and double-time exposure
Which jobs are running on overtime, where double-time hotspots are forming, and what that is doing to the loaded rate.
LaborOpens Manpower
You ask“Who owes us money past 60 days?”
$2.26M is past 60 days across 9 customers. The largest single balance is one GC at $610K, all of it on one job.
Northline Builders$610K
City of Elm Park$480K
7 other customers$1.17M
Ask nextWhich invoices go past 90 next?
AR aging and collection risk
Open receivables by bucket, by customer and by job, with the retention you are owed and the invoices most likely to go past 90 days.
CashOpens AR / AP
You ask“Did we pay any invoice twice?”
Two payments look like duplicates, $14,860 together: same vendor, same amount, and invoice numbers one character apart.
Keystone Glazing · INV-20418$7,430
Keystone Glazing · INV-2O418$7,430
PaidAug 4 and Aug 11
Ask nextAny other payments worth checking?
AP aging and duplicate invoices
What you owe, how old it is, and which vendor payments look unusual — duplicate invoice numbers, round-number clustering and Benford's Law deviation.
ControlsOpens Financial audit
You ask“What have we committed that has not hit cost yet?”
$1.3M is awarded but not yet costed, across 9 subcontracts. It is real exposure that will not appear in job cost until the first invoice.
Electrical · 3 subcontracts$520K
HVAC · 2 subcontracts$410K
4 other trades$370K
Ask nextWho is billing ahead of progress?
Committed cost and subcontract exposure
Subcontracts awarded but not yet costed, so the commitment is visible before it lands in job cost.
CostOpens Costs & estimates → Subcontracts
You ask“What work is going in without a signed change order?”
Six change orders are pending, and $287K of that work is already in place — the cost is in the job while the revenue is not.
CO-07 · 26-104 Riverside$118K in place
CO-04 · 26-121 Summit Hotel$96K in place
4 smaller change orders$73K in place
Ask nextWhich one has waited longest?
Unapproved change orders
Change orders with work performed but no approval, and the cost already sitting in the job.
CostOpens Executive → Change orders
You ask“What did our companies bill each other this quarter?”
$942K of intercompany billing this quarter, with 2 mismatches where one company posted and the other has not.
Intercompany billed$942K
Posted one side only$18,200
Amount differs$6,450
Ask nextShow the unmatched entries
Multi-entity and intercompany billing
When one of your companies bills another, and how that looks across every company database on the server — with your own vendor record kept out of vendor rankings.
CashOpens Multi-company
You ask“How much signed work is still ahead of us?”
$31.4M of contracted work is still to perform — about 14 months at the rate you are currently burning it.
26-118 Northgate$5.1M left
26-121 Summit Hotel$2.6M left
12 other jobs$23.7M left
Ask nextHow much of it is at risk?
Backlog and revenue recognition
Contracted work not yet performed, and where this period's revenue is coming from.
CashOpens Executive → Backlog
You ask“Is anything posted to closed or unallocated jobs?”
37 cost lines worth $52K are sitting on 3 closed jobs, and they are quietly distorting every margin above them.
Job 25-061 · closed May$31K · 19 lines
Job 25-208 · closed Jun$14K · 12 lines
Job 25-190 · closed Mar$7K · 6 lines
Ask nextWho posted them?
Costs posted where they should not be
Unallocated cost, costs on closed jobs, and missing fields in the source data — found before they distort every other view.
ControlsOpens Data health auditor
Example answers use illustrative figures. In the dashboard every one is read live from your own databases, with the rows behind it one click away.
Private beta
Join the private beta
Onboarding is hands-on, so it happens a few contractors at a time: we connect the systems you already run, reconcile the numbers against a report you already trust, and you keep using the dashboard while we build what is missing.
- Testing-phase pricingHalf price while the product is in beta, held for 24 months.
- A direct line to the people building itOne shared channel with the engineers, not a ticket queue.
- Your connectors built firstThe systems the beta asks for most are the ones built next.
1Apply below
290-minute setup call
3Live on your data
No lock-in: cancel at the end of any term and keep the installer. Details in pricing.
Works with the systems you already run
One layer across the ERP, project, scheduling, payroll and field systems a contractor already runs. Forty-one are mapped, the majors are being built now, and the one contractors ask for most is next.
Four connections live today, ten majors coming soon. Live now: a direct ERP connection, a QuickBooks
Desktop mirror, public bid feeds and the JSON API your own tools can read. Next: Procore, Autodesk, SAP,
Rhumbix, Viewpoint and more.
Loading the inventory…
Run something that is not on the list? Tell us which one when you join the beta.
See the forecasts in the demo →
Not ready to connect anything? Start with the free cost tools →
Comparing options? Read the construction AI tools buyer's guide →
Why not the spreadsheet you already have?
Every contractor already has a version of this: a workbook, a monthly export, someone who is good at pivot tables. The honest comparison is not "we have charts" — it is how long the answer takes, and how much of it depends on one person remembering to run it.
| Monthly export + Excel | Generic BI tool | Constructelligence | |
|---|---|---|---|
| Time to a live number | A day or two after close, if nobody is busy | A project: model, warehouse, refresh schedule | The tab loads — it reads the database directly |
| Knows your ERP's schema | Only what the person who built it knew | No — you model it yourself | Yes — job cost, payroll, AR/AP, contracts, retentions |
| Cost overruns caught before month-end | Rarely — the export is monthly by definition | Possible, if someone builds the alert | Yes — forecast at completion and risk metrics per job |
| Where the data lives | Workbook copies on laptops and in email | Usually the vendor's cloud warehouse | Your own server. There is no Constructelligence cloud |
| Cost model | Free, plus the hours nobody counts | Per seat, per month, forever | One licence per deployment, unlimited users |
| When the author leaves | The workbook stops being trusted | The model keeps running — if the licence does | It is an install you own, with the source in your hands |
| Writes to your accounting system | Not applicable | Usually read-only | Never — the connector is read-only by design |
The middle column is not a straw man: a good BI team can model all of this, and if you already have one, that team is the best customer for the JSON API rather than for the dashboard. Constructelligence exists for the contractor who has neither a BI team nor a spare analyst.
It tells you before you could have known
The expensive part of an overrun is not the money — it is how late you find out. These are the three things the dashboard calls early, how each call is made, and what to do with it.
“This job is going over — here is by how much”
Every open job is forecast to completion two ways: budget ÷ cost performance (what the work is costing you per unit of progress) and actual cost plus the recent burn rate carried to the completion date. When the two disagree, the job is flagged.
Fires when forecast at completion exceeds budget · Gives you the dollar exposure, the month it happens, and the cost category driving it.
“This is behind, and that is what it will cost”
Progress is read against the plan's own dates — activities past their finish date that are not complete, and jobs where cost has run ahead of the schedule. A slip is priced, not just highlighted, because extra weeks mean extra supervision, equipment and overhead.
Fires when activity dates pass unfinished or cost outruns time · Gives you the activities most exposed and their dollar weight.
“This is where the cash is going”
Work done but not billed, receivables past sixty days, overtime premium and unapproved change orders are summed and ranked — the four ways a contractor loses money without anyone deciding to spend it.
Fires when exposure appears in any of the four · Gives you the total, the cause, and the jobs and invoices behind it.
Watch it forecast
Job 26-104 · Riverside Apartments, week by week
Drag the week, or press play. Everything below is worked out from the cost posted by that week — nothing is hindsight.
Week 12 of 34
What an early call looks like
The same job seven weeks after the flag above, in the week a month-end pack would first have shown it: two flags, one about cost, one about time, each with the arithmetic that produced it.
Week 5Cost performance slips to 0.98 → the forecast crosses budget
Week 6PM walks the job and confirms the driver
Week 8Change order raised, crew resequenced
Week 12The month-end pack catches it — seven weeks later
1The job, as the ledger has it26-104 · Riverside Apartments
Contract$4,000,000
Budgeted cost$3,520,000
Cost to date$1,230,000
Work complete30%
Schedule complete24%
Spend, last 3 months$690,000
2What the layer works out from it
CPI0.86paying 16% more than the work is worth
Forecast at completion$4,090,000against a $3,520,000 budget
Exposure$571,000forecast overrun on this job
Schedule slip3 weeksfour activities past their finish date
Caught in week 5, that is a conversation — resequence the trades, chase the change order, put the crew somewhere else. The month-end pack shows it in week 12, by which point another $959,000 has gone out of the door.
3The same week, across every job
Cost · worst first
6 jobs flagged
26-104 Riverside$670,000
26-088 Harbourview$412,000
26-112 Cedar Ridge$188,000
26-095 Foundry Lofts$64,000
26-101 Mason Streeton budget
Time · activities against today
4 late
Site setup
Footings
Structural steel
Curtain wall
Mechanical rough-in
Interior fit-out
Week 1Today · week 2Week 34
On accuracy — what we will and will not claim
There is no invented hit-rate on this page. A prediction here is arithmetic on your own numbers, not a black box: the forecast at completion is your cost performance carried forward, the schedule flag is your own activity dates, and every figure arrives with the working attached, so you can check it against the job rather than trust it.
What that means in practice: it is right when the remaining work behaves like the work so far, and it is wrong — visibly, and early — when it does not. A flag that turns out to be nothing costs you a five-minute look; a flag you never saw costs the margin. Beta participants get the honest accuracy report as we build it: every flag we raised, tracked to how the job actually finished, with the misses included.
What is chasing the numbers costing you?
Move the sliders. Everything below is calculated in your browser from your own inputs — nothing is sent anywhere until you apply for a beta place.
Hours returned per year
—
Cost of that time, per year
—
The same number, if two jobs go sideways
—
One job at your average contract value, 8% over on cost, twice over. Catching that in the
week it starts is the whole point of a live dashboard rather than a monthly one.
How this is calculated, honestly: hours returned assumes 70% of assembler time is mechanical work a live dashboard removes — not 100%, because someone still reads it and argues with it. The average contract value is your annual revenue divided by your active jobs. Payback compares the annual saving with the $4,800/yr planned GA price of the Multi-company licence, so a beta customer on the founding rate pays it back faster still.
Priced per deployment. Here is what it will be.
One annual licence per deployment: every module, every company database, every user. While the product is in its testing phase, every licence is half price. The struck-through figure is what the same licence lists at once the beta closes — so you are not guessing at what this costs later.
Single company
One company database
$1,200 / year — beta
$2,400 while the product is in testing. That is the planned GA price — beta customers
keep this rate for 24 months from signature.
- Every module — job cost, labor, AR/AP, EVM forecast, risk metrics
- Unlimited users and API keys
- CSV/Excel export of any table, and a REST endpoint for every module
- Setup session, email support, updates for 12 months
Most common
Multi-company
$2,400 / year — beta
$4,800 while the product is in testing. That is the planned GA price — beta customers
keep this rate for 24 months from signature.
- Everything in Single company
- Unlimited company databases on one server
- Multi-entity billing and intercompany comparison
- QuickBooks Desktop and the public bid-opportunity feed
- Priority support, updates for 12 months
Enterprise
Custom and white-glove
from $4,500 / year — beta
from $9,000 while the product is in testing. For groups, franchised GCs, and anyone
whose blocker is a connector we have not built yet.
- Everything in Multi-company
- One custom connector build per year (Viewpoint, CMiC, Sage Intacct, Acumatica, your own ERP)
- Onboarding on your server with your IT
- Security review, SSO and network hardening
- Named support contact with a response SLA
What the testing-phase discount is, exactly: 50% off the planned GA list price, held for 24 months from signature, on a self-hosted deployment — you supply the SQL Server (or Azure SQL instance) and the machine it runs on, which a modest VM covers. The beta can be cancelled at the end of any term. GA pricing is our current plan rather than a promise about a number we control in perpetuity: it is what we intend to list at, published here so a beta customer can see the difference now instead of discovering it at renewal. The final figure is always set with you, after we have seen your server, your companies, and which connectors are in scope.
Set up once, with us
There is no SaaS account to create and no per-seat provisioning. One connection string, one API key, and a first session where we reconcile the numbers with you.
01
Point it at your SQL Server
Add a read-only connection string to appsettings.json. Constructelligence discovers every company database on that server — no per-company configuration.
02
Reconcile one report together
On the setup call we open a report you already trust — job cost, WIP, AR aging — and check the dashboard against it, line by line, before anyone relies on it.
03
Turn the team loose
Issue API keys per person or per tool. Every module populates from live data, with no nightly sync, no stale export and no per-seat billing.
The questions that decide it
Short answers, including the ones that end with "no".
Where does our data live?
Where it already lives. Constructelligence runs on your own machine or VM and reads your ERP and project data over the connection you configure — there is no Constructelligence cloud, no nightly copy of your financials, and no third party in the path. The browser page is served by that same local process.
Which ERPs and systems does it work with?
It is built to sit on whichever ERP you run. Live today: a direct, read-only connection to Sage 300 CRE, a QuickBooks Desktop mirror, public bid feeds, and a JSON endpoint for every module — so Power BI, Excel or a script of your own reads the same numbers with no connector build at all.
Coming soon: Procore, Autodesk Build and Takeoff, SAP S/4HANA, Rhumbix, Viewpoint Vista and Spectrum, Sage Intacct, NetSuite, Primavera P6 and Microsoft Project. The integration list maps 41 systems in total and states what each connection would take; the one contractors ask for most is built next.
Does it write anything back to my ERP?
No. The connection is read-only, the SQL layer refuses anything that is not a SELECT, and nothing in the dashboard can change your accounting data. If a feature ever needs to write, it will be a separate, explicitly-enabled connector rather than a surprise.
How is it secured?
The API binds to loopback only and rejects any request that does not come from the machine
itself, so it is not reachable over the network by default. Every data API call needs a key
(X-Api-Key), keys are compared as constant-time hashes, requests are rate limited
per key, and responses carry no-store caching plus clickjacking and MIME-sniffing protection.
There is no login page to phish because the app is not exposed to the internet; when it is
deliberately fronted by a reverse proxy, that proxy owns authentication.
What does the beta actually involve for us?
A 90-minute session where we install it on your server and connect one company database. We reconcile the dashboard's numbers against a report you already trust, on the call. Then you use it, and we talk monthly about what is missing or wrong. You can cancel at the end of any term and keep the installer.
What does it need to run?
A machine that can reach your SQL Server — Windows or Linux, a VM is fine — plus a read-only login to your ERP database. The published build is a self-contained executable, so there is no runtime to install. Most deployments are reading live data the same day.
What about the AI document extraction?
It is off unless you turn it on, and it is the only feature that can send anything off your machine. OCR and field extraction run locally in the browser; if you configure an external model for the hard documents, that call is the one place your document text leaves your network, and the page tells you when it is about to happen.
What happens if we stop paying?
The app keeps working until the licence term ends, and your data was never ours to hold. There is nothing to export from a Constructelligence account because there is no Constructelligence account — the dashboard reads your database, and the only files it owns are its own settings, its log, and the leads you send us.
Your numbers are already there. Go look at them properly.
Self-hosted, read-only, priced per deployment. The beta is 20 minutes of setup and a licence you can cancel at term.