AI-powered project intelligence for construction contractors
Search, chat, and connected workspaces across all your systems. Every answer cited. Every number sourced.
Good morning, Jordan
5 projects · 14 connected sources · last sweep 6:00 AM. 9 items need you.
Differing site condition at Grid C: notice due in 2 days. Letter drafted, you send it.
Metro Medical · Contract §4.3.7 · parsed at award
Sub change ↓ $8,400 received, pass-through drafted ↑ at $9,660, your markup applied.
Metro Medical · sub email · T2
Cost efficiency slipped 0.96 → 0.91, field labor burning ahead of earned.
Metro Medical · WIP export · T2 · Jun 30
Copper: 12t committed of 28t budget; spot +9% since bid. Locking now ≈ saves $31K.
Metro Medical · PO log T1 + index
Rev D adds 6 VAV boxes not in bid set Rev B, entitlement $14.2K. PCO drafted.
Metro Medical · drawing diff
3 RFIs acknowledged · submittal log reconciled · daily logs filed on 4 of 5 jobs · notice log current.
9
Connected workspaces, in the two groups your week already splits into
5
Weighted dimensions behind every health score, each naming its source
T1–T3
Source tier and age on every figure: live feed, export, or entered by hand
0
Figures on screen without a named source
The reality of construction data
Six to ten systems that don't talk to each other, and a clock running in every one of them.
Four things that don't wait for you to have time
efilo watches what's already in your systems, and tells you the moment one of them needs you.
See margin fade while you can still act on it
Bid margin to forecast margin, recomputed nightly: buyout, productivity, escalation, rework, changes won. Each step names why. You find fade in June, not at closeout.
Never miss a notice
efilo pulls the notice provisions out of your contract at award and runs the clock in business days or calendar days, against your holiday calendar. It warns you at 14, 7, 3 and 1 day, drafts the letter, and waits for you to send it.
Know what needs you today
One ranked list across every project: dollars at risk, deadline, what's blocked. Items facing your subs and items facing the GC rank on the same scale. A footer names what was handled without you.
Find anything, and be able to prove it
Ask in plain language across drawings, specs, contracts, submittals and email. Scope it to this project, every project, or general knowledge. Every answer comes back cited, and only ever shows what you're already allowed to see.
Every answer shows its work
An answer you can't trace is an answer you can't take into a claim, a pay app, or an OAC meeting. efilo cites the document and names the source behind every figure.
A citation on every answer
Documents and email, linked back to the page they came from.
Permission-aware by inheritance
efilo inherits access controls from the system each document lives in. If your access can't be confirmed, you don't see it.
A human gate on anything irreversible
Notices, RFIs, pass-throughs, pay-app adjustments: drafted by efilo, reviewed and sent by you.
Never a fabricated number
A figure efilo can't compute says so, and names the connection that would fix it.
Do we have notice rights on the Grid C differing site condition, and how long do we have?
Yes. The prime contract requires written notice within 7 business days of discovery of a concealed or unknown physical condition. Discovery was logged Jun 30, so notice is due Jul 10, 2 business days from today, accounting for the Jul 4 holiday on this project's calendar. A letter is drafted and waiting on your review.
Upload a file, or connect the source. Both work today.
Every capability takes a document directly, so you can see it work on your own contract in the first session. Connect Microsoft 365 when you want it to keep itself current. You don't wait on a data project either way.
Every capability takes a file
There is an upload button on each workspace, and each one states plainly what your file activates. Getting a document into the library populates nothing by itself, and we say so rather than implying otherwise.
The contract
Notice provisions come out at award and the deadlines start counting. Nothing else you upload matters as much.
A WIP or job-cost export
Margin bridge, EAC, and the cost dimension of the health score.
A P6 file or a schedule sheet
A timeline either way. Float and critical path only when the file actually carries the logic.
Pay apps, change logs, production logs
Billings and retention, exposure in both directions, and the measured mile behind a disruption claim.
Microsoft 365 / SharePoint
Contracts, drawings, specs and submittals from the sites and folders you point us at, with per-document access controls and Entra identity, so answers are correct for the person asking.
T1 · API · read + identity
Outlook
Project correspondence, searchable inside chat and citable in an answer. Approved notices and RFIs go out from your own mailbox, so the record stays where your lawyers expect it.
T1 · API · read + send on approval
Every contractor's stack is different
We build first-class adapters against real customer stacks. Until yours exists, two paths already carry you.
Map any documented endpoint or file drop
A REST endpoint, a scheduled export, SFTP, or a watched folder. Point your system's fields at efilo's and it syncs.
Or just send the reports you already run
WIP reports, pay applications, schedules: the PDFs and spreadsheets you already produce. efilo reads them and fills the same fields.
The numbers don't lie
Construction technology fragmentation has real costs, and a workforce that is about to take its institutional knowledge home with it.
Join the Design Partner Program
We're working with a small set of contractors on live jobs. What they tell us still changes the roadmap.
What you get
- Value in the first session: connect Microsoft 365 and your notice clocks start
- Direct input into the roadmap
- White-glove onboarding and a standing feedback loop
What we ask
- A few structured working sessions
- Clear success criteria
- Fast feedback on what saves time, and what doesn't