Automated bid intake from Gmail and Outlook
The bid desk's most repetitive work is also its most mechanical: open the invitation, find the project name, the due date, the location, and the square footage, and decide whether it duplicates something already open. That is the part worth automating — and the part where automation has to show its work.
Gmail and Outlook
Connect one mailbox. Invitations are read as they arrive; nothing is forwarded, filed, or re-typed by hand.
Confidence on every field
Extractions arrive scored and queued for review, with a link back to the source email. You approve, correct, or reject.
Duplicates merged, not multiplied
Matched on project, address, and client — not subject line — so addenda attach to the existing job.
Revocable at any time
Disconnect from Settings or straight from your Google or Microsoft account. Revoking stops all scanning immediately.
What gets extracted
- The general contractor — resolved from the invitation's display name and body, not the sending address. Invitations from PlanHub and BuildingConnected come from relay addresses; filing by sender puts unrelated GCs in the same bucket.
- Project name and location — as the GC writes them, so a later search matches their language rather than yours.
- Bid due date — the field triage actually turns on.
- Scope and size — square footage and system types where the invitation states them.
- Contact details — including the reply-to alias, stored alongside the real contact rather than in place of them.
Why there is a review queue
Extraction from unstructured email is very good and not perfect. A system that writes directly into your pipeline without review will eventually get a due date wrong on a job you cared about, and you will stop trusting all of it — which is worse than not having it.
So every extraction lands in a queue with its confidence score and a link to the source email. High-confidence records are a glance and an approve. Low-confidence ones are where you spend your attention. The result is that automation handles volume while judgment stays with the estimator.
Beyond email: phone calls and website forms
Commercial work arrives as an invitation to bid. Residential and direct-to-customer work does not — it arrives as a phone call or a form submission, usually while you're on a jobsite and can't answer. Both land in the same queue:
- Inbound phone calls — connect an AI phone agent and calls get answered, qualified, and captured as leads. Nobody takes a message, and nothing depends on someone being free at 2pm. This is the channel most residential and small-commercial work actually comes through.
- Website form submissions — a quote request from your site arrives alongside everything else rather than in an inbox somebody checks on Fridays.
- Manual entry — a referral, a walk-in, a job scoped on site. Enter it directly and it behaves like any other job.
The point is a single queue: one place where every inbound opportunity, whatever channel it arrived on, waits for a bid/no-bid decision — and then follows the same path to a proposal. See how residential work runs through the same pipeline.
What it does not do
It does not read your whole mailbox for unrelated purposes, and it does not train models on your data — your bids, pricing, and correspondence are used to run your account and nothing else. Access is revocable from Settings or from your Google or Microsoft account directly, and revoking stops scanning immediately. Full detail in the privacy policy.
How does automated bid intake handle invitations from PlanHub or BuildingConnected?
Those platforms send from relay addresses, often per-thread aliases, so the sending address identifies the platform rather than the general contractor. The GC is resolved from the invitation's display name and body instead, and the relay address is stored separately so replies still route correctly.
What stops the same project being logged twice?
Incoming invitations are matched against open work by project name, address, and client rather than by subject line, which changes with every addendum. Matches are merged into the existing record so revisions attach to the original job.
Does it act on invitations without me seeing them?
No. Every extraction lands in a review queue with a confidence score and a link back to the source email. You approve, correct, or reject before anything enters the pipeline.
Can I revoke email access later?
Yes, from Settings or directly from your Google or Microsoft account. Revoking stops all scanning immediately.
Can it capture leads from phone calls?
Yes. Connect an AI phone agent and inbound calls are answered, qualified, and captured as leads in the same queue as email invitations and website forms. This matters most for residential and small-commercial work, which arrives by phone rather than as a formal invitation to bid.
Try it before connecting your inbox
Every account starts with a sample project loaded, so you can see exactly how intake, review, and de-duplication behave first.
Start your free trialMore on IntelBid
- Flooring contractor CRM and bid management softwareOne pipeline for every flooring job — commercial bid invitations from your inbox, website forms, and inbound calls answered by an AI phone agent. Proposals, follow-up, and project management included.
- Bid management software for commercial subcontractorsOne pipeline for every bid invitation, no matter which platform it came through. Proposals, follow-up, outcome tracking, and project management for specialty trades.
- Moving from residential to commercial flooring workWhat changes when you take your first invitation to bid: prequalification packets, how GC bid lists actually work, retainage and pay applications, and the systems that break on the way.
- Bid follow-up automation for subcontractorsSubmitted bids that go quiet surface on their own, grouped by general contractor, with the draft already written. Follow-up stops depending on someone remembering.