Getting started with Bex is measured in hours, not months. Provision an email account, enable API access to your system of record, and you're live. This article covers what Bex integrates with out of the box, how simple onboarding really is, and why managing users requires virtually zero IT overhead.
Jump to:
Two steps to get started
Most enterprise software rollouts involve weeks of planning, infrastructure changes, and training. Bex is different.
For example, to get the Observations Module (punch lists) running, your IT team does two things:
- Provision an email account for Bex in your existing email system (e.g., [email protected]).
- Enable API access to your system of record, such as Procore, Autodesk Construction Cloud, or ProjectSight.
That's it. Two steps. In a typical environment, this takes less than 30 minutes to complete and test.
No servers to deploy, no databases to configure, no firewall rules to write. Bex runs in harmonic mean's secure cloud infrastructure and communicates with your systems through the same standard APIs and email protocols you already use.
Any customizations to Bex's behavior, such as approval routing, notification rules, or tone of voice, are handled by your dedicated customer success manager.
What Bex integrates with
Out of the box, Bex connects to the platforms commercial construction teams rely on every day:
Construction management:
- Procore
- Autodesk Construction Cloud (ACC)
- ProjectSight
Email:
- Microsoft Exchange / Microsoft 365
- Google Workspace (Gmail)
File storage:
- SharePoint / OneDrive (read and write)
- Email attachments (any format)
For teams whose system of record is a collection of spreadsheets or other files, Bex handles that too. It can generate and maintain structured spreadsheets and deliver them via email, or for Microsoft customers, read and write them directly through SharePoint and OneDrive.
And as we noted in our use cases article, harmonic mean is always adding new integrations. If your team uses a platform not listed here, reach out and let's talk.
User management that runs itself
One of the hidden costs of enterprise software is ongoing user administration: creating accounts, managing permissions, handling offboarding. Bex eliminates nearly all of this.
Since Bex operates through email, access control is built in. Only emails originating from your organization's domain(s) can trigger record creation. There are no Bex-specific user accounts to provision, no passwords to manage, and no licenses to track. When someone joins your team and gets a company email address, they can work with Bex immediately. When someone leaves and their email is deactivated, their access ends automatically.
There is one intentional exception: subcontractors can reply to emails that Bex sends them, for example to update the status of an observation or punch item. This is a deliberate and low-risk design choice. It only works when Bex initiated the conversation, the subcontractor can only update items assigned to them, and confidential project data is never exposed.
Conclusion
Flexibility and incredibly low friction were key goals when harmonic mean built Bex. 30-minute setup, zero infrastructure changes, and self-managing user access mean your team starts saving time almost immediately, without creating new work for IT.