Contractors & builders

Bid Invites to the Right Subs

A commercial contractor's subcontractor book, merged from their project-management system and Outlook, with bid invitations that go out from the company's own mailbox, one at a time.

Commercial general contractor · Set up Jul-Sep 2026 · handed off Sep 2026

bids.newera.osillustrative

SUB BOOK · FIRST SYNC

read-only

SOURCES

2

MATCHED

1,900+

SENDS FROM

your mailbox

BID INVITES · YOUR MAILBOX, YOUR SUBS

41 sec

First full sync

Project system + Outlook, into one book (Jul 2026)

1,900+

Matched, not doubled

contacts found in both systems

3,600+

Contacts in the sub book

after the team's own cleanup (Sep 2026)

The challenge

A contractor's subs live in two places: the project-management system and the estimator's Outlook, with many of the same people in both. Getting a bid invite to the right subs means knowing, for every job and every trade, who is in the book and who has already been asked.

What we built

We synced the vendors and jobs from the contractor's project-management system and the team's Outlook contacts into one sub book, read-only toward both: nothing is written back to either system. The same person found in both is merged, not doubled. The team starts from a job in their project system: its budget becomes the scope, the scope splits into trade packages, and each package pre-ticks the subs in that trade and region, so the team only unticks exceptions. Invitations go out from the company's own Microsoft 365 mailbox with its signature, paced by a gap the team sets and sent in the background, so the tab can close. A Check inbox button counts replies and bounces from reply headers only, never message content.

  • One sub book from their project system and Outlook, read-only toward both
  • The same person in both systems merged, not doubled
  • Scope from a job's budget, split into trade packages
  • Trade buckets plus a region filter; untick anyone before sending
  • Invites from the company's own Microsoft 365 mailbox, with its signature
  • Paced in the background, with pause and resume
  • Nobody gets the same invite twice; opt-outs re-checked at send
  • Postal address and an Unsubscribe link on every invite
  • Replies and bounces counted from reply headers, never message content
  • No open-tracking pixels

By the numbers

First full sync
0
Companies, first sync
0
Matched across both
0
Contacts at handoff
0
Sep 2026
Trade buckets
0
Sep 2026
Ready to invite, Texas job
0
Sep 2026
Writes back to either system
0
Sends from
Their mailbox

What worked

Beside the tools they keep

  • Their project system and Outlook stay the source; the sync only reads
  • Nothing is ever written back to either system

The right subs, pre-ticked

  • A job's budget becomes the scope and the trade packages
  • Each package pre-ticks the subs in that trade and region

Their mailbox, their pace

  • Invites go out from the company's own mailbox and signature
  • A minimum gap between sends, set by the team; the tab can close

A staged go-live

  • A lab copy of the real book, then our own addresses
  • Handed off with the team's own logins in Sep 2026

How a bid invite flows

Step

What happens

Sync

Their project system and Outlook read into one sub book

Scope

A job's budget becomes trade packages

Pick

Each package pre-ticks subs by trade and region

Send

From the company's mailbox, paced, in the background

Replies

Check inbox counts replies and bounces from headers