Out of the box:

Integrations

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:

Most enterprise software rollouts involve weeks of planning, infrastructure changes, and training. Bex is different.

For example, to get Bex Punch running, your IT team does two things:

  1. Provision an email account for Bex in your existing email system (e.g., bex@yourcompany.com).
  2. 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. Other modules—Liens, Insurance, Risk—follow the same pattern: an inbox, plus whatever connection (if any) the module needs to reach your existing systems. Bex Walks adds the iOS app, distributed through the App Store the way your team already gets every other app.

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—approval routing, notification rules, scoring rubrics, tone of voice, branding—are handled by your dedicated customer success manager.

Out of the box, Bex connects to the platforms commercial construction teams rely on every day:

Construction management:

  • Procore
  • ProjectSight
  • Autodesk ACC and other CMSes added upon request
  • Homegrown, spreadsheet-based CMS, with available SharePoint integration

Email:

  • Microsoft Exchange / Microsoft 365
  • Google Workspace (Gmail)

File storage:

  • SharePoint / OneDrive (read and write)
  • Google Drive
  • Email attachments (any format)

For teams whose system of record is a collection of spreadsheets or other files, Bex handles that too. Bex Liens, for instance, can act as your system of record outright, write to a master log spreadsheet you own, mirror data into Procore, or do all three. The choice is yours.

Harmonic Mean is always adding new integrations, and in the age of AI-assisted development, building a new connector is faster than you might expect. If your team uses a platform not listed here, reach out and let's talk.

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 allowlisted 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: external parties (subcontractors providing COIs, assignees confirming punch items, suppliers responding to lien correspondence) can reply to emails that Bex sends them. This is a deliberate and low-risk design choice. It only works when Bex initiated the conversation, the external party can only act on items addressed to them, and confidential project data is never exposed.

Where web access is needed—the Lien Notice Viewer, the Lien QA tool, the Project Risk dashboard—Bex uses a magic-PIN login tied to the same allowlisted email addresses. Still no passwords for your IT team to manage.

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.