Over the past two decades, construction software has promised repeatedly to move project communication out of the inbox and into a portal. The portals arrived, and many of them are good. Email remains. Not as a legacy habit that training will eventually stamp out, but as the actual medium through which commercial construction coordinates itself. We think that persistence is rational, and that it has a practical consequence for anyone buying automation software: the highest-value place to automate is the inbox itself.
Every portal still runs on email
Watch how any project management platform actually operates. When an RFI needs an answer, the platform sends an email. When a submittal is returned, the notification is an email. When a sub is invited to bid, the invitation is an email, and when they have a question about it, the question comes back as an email. The portal holds the record; email carries the communication. Even the most portal-committed organizations run this hybrid, because the alternative—expecting every participant to log in and check—fails immediately.
The input side is more lopsided still. The documents that drive a project's back office arrive almost exclusively by email or physical mail: the architect's field report as a PDF attachment, the broker's certificate of insurance, the supplier's invoice, the attorney's lien notice scanned at the front desk. No portal mandate reaches these senders, because they're outside your organization and often outside your industry. A GC can require its own staff to use anything; it cannot require an insurance broker in another state to adopt its software.
Why email persists
Email's survival isn't inertia. It has properties that no proprietary channel matches, and they matter more in construction than in most industries.
It is universal. A commercial project involves the GC, dozens of subs, the owner, the architect, consultants, brokers, suppliers, and occasionally lawyers—organizations of wildly different sizes and technical sophistication. Email is the one system every one of them already operates, with no onboarding, no license negotiation, and no password reset queue. The oldest plumbing contractor in the county and the newest owner's rep both have working inboxes.
It is durable and searchable. Corporate email systems ship with archiving, retention policies, and search that legal and compliance teams already trust. In an industry where disputes surface years after substantial completion, "it's in the email record" is a sentence with real weight—discoverability is built into the medium rather than bolted onto it.
It is neutral ground. Platforms come and go from a project; participants join and leave; but the email thread survives platform migrations, corporate acquisitions, and the end of the subscription. Nobody's workflow is hostage to anyone else's vendor choice.
The conclusion we drew: build on it, not against it
If email is where the documents arrive, where every participant already lives, and where the durable record sits, then automation that fights email—by demanding yet another portal login from people who never asked for one—starts with a structural handicap. Adoption is the silent killer of automation projects, and every added login is a toll on adoption.
So we built Bex as, in effect, a tireless colleague on your email system. Work arrives by forwarding a document to an address like bex@yourdomain.com. Bex reads it, does the clerical processing, holds a plain-English conversation about corrections, and writes the approved result to Procore, ProjectSight, or your spreadsheets. Subs, consultants, and brokers interact with Bex the way they interact with any project engineer: they reply to an email. Nobody outside your walls installs anything or creates an account.
The design has second-order benefits we didn't fully anticipate. There are no passwords to manage—the few web dashboards Bex offers use one-time codes sent by email—so when an employee leaves, their Bex access ends with their inbox, automatically. Every action Bex takes is itself an email, which means your existing Exchange or Google Workspace archive is a complete, tamper-resistant audit trail of everything the AI did, inspectable by anyone who can search a mailbox. And because your email system is the durable store, Bex doesn't need to hoard your data: our default is to delete Bex's copies after 30 days. Recovery, in the rare case it's needed, is as simple as re-reading the original messages. The security posture this produces is described more fully in secure, observable, trustworthy.
The obvious objection
The case against email is familiar: inboxes are overloaded, threads sprawl, attachments get lost, and nothing enforces structure. All true—and worth examining, because the chaos isn't produced by the medium. It's produced by the volume of clerical work flowing through the medium with only humans to process it. The thread sprawls because a person is manually coordinating five parties; the attachment gets lost because a person had to file it. Put a capable automation on the receiving end and the same properties that made email chaotic make it orderly: every document has a timestamped arrival, every decision has a written record, and the tireless party in the thread never loses track of who owes what. The problem was never email; it was email without staff.
What this means for a software evaluation
None of this argues against portals. Systems of record are necessary, and we spend our days writing data into them. The argument is narrower: when you evaluate automation, look hard at which side of the email boundary it lives on. A tool that operates inside a platform can only automate what reaches the platform—and the expensive manual work is precisely the translation from inbox to platform. A tool that operates on email meets the work where it already is, with an adoption cost near zero, a point we expand on in meeting users where they are.
Construction ran on paper for a century and has run on email for a generation. The next layer, we're convinced, doesn't replace that substrate; it staffs it. If you'd like to see what a competent AI colleague on your own email domain looks like, send us a note—by email, naturally. The address is below.