The CRM your firm bought in 2022 has 60% data entry. The other 40% is a graveyard. The estimator updates it twice a month when the BD director sends a passive-aggressive reminder. The PMs never log into it. The PX checks it once before a quarterly review and gets frustrated because half the active pursuits aren't in there.
The license costs your firm somewhere between fifty and two hundred dollars per seat per month. Across thirty seats, that's somewhere between $1,800 and $7,200 a month for a system that's mostly vibes.
What if the data lives where your team already lives? Outlook. SharePoint. Excel. Teams. Things they're already in eight hours a day.
That's the move. Not a new platform. A working layer of Power Automate flows that turn the tools you already pay for into the CRM your team will actually use.
Step One: Capture Opportunities From Email Automatically
Opportunities almost always start the same way. An email lands. ITB, GC outreach, forwarded lead from a project executive who got the inside scoop.
A Power Automate flow triggers on new email to the BD inbox. It reads the email and pulls: project name, GC name, bid date, walk-through date, drawing release, contact name, contact email. It writes those fields to a SharePoint list.
That list is now your opportunity master record. Every legitimate lead is captured in real time. The BD analyst stops spending Monday morning entering Friday's leads.
The flow is light—a "When new email arrives" trigger, an AI extraction step (Copilot or Azure OpenAI in your tenant), a "Create item" action against SharePoint. Forty minutes to build. Pays back in week one.
Step Two: Stop Maintaining a Contact Database
Outlook is already your contact database. You just don't think of it that way.
A flow checks every outgoing email from the BD team. If the recipient isn't in your contacts list, it creates a new entry: name, company, email, phone (if it's in their signature), date of first contact. Every reply updates the "Last Contacted" field.
The result is a contact list that updates itself. The PE who emailed a new GC contact yesterday—their name is in the list this morning. The contact who hasn't responded to anything in eight months gets flagged automatically.
No data entry. The list reflects what's actually happening, not what someone remembered to log.
Step Three: Follow-Up Tracking That Doesn't Rely on Memory
This is where most BD teams lose the most ground. Pursuits go cold because nobody remembered to check in.
When an opportunity gets created or updated in SharePoint, a "Next Follow-Up Date" field is set. A daily Power Automate flow runs at 7 a.m., checks the list for follow-ups due today, and sends a single consolidated email to each BD person with their list.
When an email reply comes in on a thread tied to an opportunity, the flow updates "Last Activity" automatically. The list always shows what's stale.
Result: the BD team starts each day with a clear list of what needs a touch. Not a CRM dashboard they have to log into. An email in the inbox they're already opening.
Step Four: Deadline Alerts That Don't Get Missed
Bid dates, addenda drops, walk-throughs, scope calls, RFI deadlines. These need visibility.
When a new opportunity hits the SharePoint list with a bid date, the flow creates an Outlook calendar event 7 days, 3 days, and 1 day before. It posts a Teams notification to the BD channel. It updates a shared BD pipeline calendar.
If the bid date field is missing, the flow flags the opportunity in a separate "needs attention" view. The BD lead sees it in the Tuesday pipeline review.
Nobody is surprised by a bid day three days before. The system surfaces it on day seven.
Step Five: A Pipeline Dashboard That Updates Itself
With opportunities flowing into a structured table, reporting becomes easy. Total opportunities by GC. Win/loss trends. Bids due this week. Pursuits with stale follow-ups (no activity in 14+ days). Activity by BD rep. Engagement patterns by GC.
A Power BI report against the SharePoint list, refreshed every 4 hours. Or just a pivot table in Excel pointed at the list. Either works.
The PX walks into the quarterly review with the dashboard already current. The conversation is about what to do, not about what happened.
Step Six: Auto-Organize the Project Files
When an opportunity record is created, the flow generates a SharePoint folder named after the project. Subfolders: Drawings, Specs, Emails, Notes, Addenda, Proposal, Awarded. The original ITB email and any attachments get filed into the correct folder.
The folder is tagged with opportunity metadata so search works.
By the time the estimator sits down to start the takeoff, the file structure is already built. The first hour of every project—organizing the inputs—doesn't exist anymore.
Step Seven: An Interface Your Team Will Actually Use
Everything runs against SharePoint and Excel. The team uses what they already use.
A Teams tab pinned to the BD channel that shows the pipeline. Excel for fast filtering when somebody wants to slice the data a specific way. SharePoint search for finding old pursuits. Outlook categories so opportunities can be visually flagged in email. Power Automate buttons in Outlook—"Log Follow-Up," "Mark as Lost," "Update Contact"—so updates happen with one click from inside the email the user is already reading.
No new logins. No second screen. No "I have to remember to update the CRM."
Why This Works When the Real CRM Didn't
Construction BD is deadline-driven, email-heavy, and time-crunched. The work happens in the inbox. The CRM your firm bought wanted the work to happen in a different tool, and the team voted with their feet.
This setup runs in the inbox. The data fills itself in. The follow-up reminders show up where the team is already looking. The pipeline updates without anybody having to type into a separate system.
The cost is lower than your existing CRM. The adoption is higher because adoption isn't even a thing—the team uses Outlook and SharePoint by default.
The catch: you need somebody who can build and maintain the flows. Usually that's a Power Automate-literate BD analyst or an internal builder. If your firm doesn't have that yet, see Why Construction Firms Should Choose Industry-Native Software Builders. It's not a hard hire.
Get in touch if you want a step-by-step build guide, the flow architecture, or a working PDF for your BD leadership.