RFP to Win Workflow
A cross-tool workflow map from RFP received through proposal, SOW, CRM attachment, and won/lost status.
This is the cross-tool flow from a client RFP to a won or lost CRM outcome. Every deal ANC pursues travels this exact path, and every role touches part of it: sales logs and owns the deal, estimation prices it, proposals packages it, and leadership reads the honest outcome at the end. The connective tissue is automatic — files attach themselves, statuses stamp themselves — so the flow only breaks when a human skips a handoff, not when someone forgets an upload.
RFP to win at a glance
- 1
Log the opportunity in the CRM with due date, stage, and bid status.
- 2
Analyze and price the RFP in the proposal workflow.
- 3
Attach proposal/SOW outputs back to the opportunity.
- 4
Mark submitted, won, lost, or no-bid so reporting stays honest.
Swimlane
Email / External
Client sends RFP
|
v
CRM
Log Opportunity: stage=PROPOSAL, Bid Status=RFP_RECEIVED
|
v
CRM / Scout
Analyze RFP and extract requirements
|
v
Proposal Engine
Price in Excel
|
v
Proposal Engine
Mirror Mode -> One-Pager Generated
|
v
CRM
Pricing Complete = TRUE, proposal attached to Files
|
v
Proposal Engine
Generate SOW: Premium + Installation
|
v
CRM
SOW attached to Deal
|
v
CRM
Move to BID_SUBMITTED in Bid Tracker
|
v
External
Client review
|
v
CRM
Mark WON or LOSTStage By Stage
1. RFP Received — sales owns it
The clock starts when the RFP is logged, not when it arrives in an inbox. Search the Company first so the deal links to the account's real history, then create the opportunity with stage, Bid Status, business unit, league, and — non-negotiable — the proposal due date. The due date is what the estimation queue sorts by; without it, the deal is invisible to the people who need to price it. Confirm the deal shows up on the Bid Tracker board before calling this step done.
2. Scoping — requirements get real
Scoping is where ambiguity dies. The RFP Analyzer turns the client's document into a compliance matrix — requirement by requirement, with a proposed ANC response — so nothing on page 34 gets discovered the night before submission. Questions back to the client happen now, while there is still time for answers. Move the deal's Bid Status to Scoping so the board reflects reality.
3. Pricing and packaging — estimation and proposals own it
Pricing is built in Excel, and the client-facing one-pager is generated with Mirror Mode so the PDF reproduces the spreadsheet exactly. The moment the one-pager generates, two things happen in the CRM without anyone touching it: the file attaches to the deal through Universal CRM Push, and Pricing Complete flips to true with the date stamped. The SOW follows — Premium for the client, Installation for the field — and both attach the same way, each leaving a timeline note on the deal.
4. Bid Submitted — back to sales
When the package goes to the client, move the deal to Bid Submitted. From here the discipline is follow-up: a bid sitting in Bid Submitted for weeks with no touch recorded is a decision you have not heard about yet. If the client narrows the field, Shortlisted signals the deal deserves extra attention — reference calls, exec involvement, sharpened pricing.
5. Won, Lost, or No Bid — everyone benefits
Every pursuit ends in one of three honest states. Won requires a contract completion date — the platform reverts the status without one, because that date drives the backlog and renewal reporting. Lost and No Bid are not failures to hide; they are the data points that make the win/loss-by-league analysis mean something. A deal left open forever is the only truly bad outcome, because it corrupts both the pipeline and the win rate.
Time Indicators
Decision Points
Is this a Venue Services deal?
- Yes: include Service Dashboard fulfillment, event staffing, tickets, and venue operations. The won deal becomes an operating account, and its service history syncs back onto the CRM Company from day one.
- No: continue through CRM and Proposal Engine only.
Should ANC bid at all?
No Bid is a legitimate exit at any point before submission. A deal that is out of footprint, unwinnable on timeline, or strategically wrong costs less as an early No Bid than as a Lost after two weeks of estimation work. Record it — a deliberate No Bid keeps the win rate honest and the estimation queue focused.
Kick off the analysis
Audit the flow for stuck deals
Prove It Under Pressure
Decision drill: Run the full flow
Pick the move you would actually make. Score at the end.
A metropolitan transit authority releases an RFP for platform display systems. Due in 21 days. You own it end to end.
Day 1. The RFP is in your inbox. What makes it real?
Keep Going
- Sales & Account Management track — steps 1, 4, and 5 in depth.
- Proposals & Estimation track — steps 2 and 3 in depth.
- Services & Operations track — the fulfillment path for Venue Services wins.
- Executive Summary track — how leadership reads the outcomes this flow produces.
Key takeaways
- One flow, four owners: sales logs and closes, estimation prices, proposals packages, leadership reads.
- The due date set at logging drives the entire estimation queue — it is the single highest-leverage field in the flow.
- Files and pricing status move to the CRM automatically; humans move the Bid Status.
- Won demands a completion date, and Lost or No Bid are honest data, not embarrassments.
- The only bad outcome is a deal left open forever — it corrupts pipeline and win rate at the same time.
Check yourself
An RFP is out of footprint and unwinnable on timeline. What is the right move?