ANC
CRM TrainingWorkflows

RFP to Win Workflow

A cross-tool workflow map from RFP received through proposal, SOW, CRM attachment, and won/lost status.

Listen to this lesson
0:00
—:—
15 min Everyone Core
CONNECTED

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. 1

    Log the opportunity in the CRM with due date, stage, and bid status.

  2. 2

    Analyze and price the RFP in the proposal workflow.

  3. 3

    Attach proposal/SOW outputs back to the opportunity.

  4. 4

    Mark submitted, won, lost, or no-bid so reporting stays honest.

Swimlane

EMAIL / EXTERNAL
Client sends RFP
CRM
Log Opportunity: stage=PROPOSAL, Bid Status=RFP_RECEIVED
Optional Scout analysis extracts requirements, due date, league, business unit, and missing information.
PROPOSAL ENGINE
Price in Excel -> Mirror Mode -> One-Pager Generated
CONNECTED
Pricing Complete = TRUE, proposal attached to CRM Files
PROPOSAL ENGINE
Generate SOW: Premium + Installation
CRM
SOW attached -> Move to BID_SUBMITTED -> Mark WON or LOST
SERVICES, IF INCLUDED
Create service fulfillment path: tickets, events, staffing, venue operations
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 LOST

Stage 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

Where this lives:CONNECTED Universal CRM Push: proposal and SOW files usually attach in 5-10 seconds
Where this lives:CONNECTED Real-time CRM Sync: service ticket and event changes usually appear in CRM in about 1 second

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

Analyze this RFP and extract requirements, due date, league, business unit, and missing information.

Audit the flow for stuck deals

Show open opportunities by Bid Status with proposal due date, flagging any past due or unchanged for 30 days.
Emergency: A deal went all the way to submission but the files are not on the CRM opportunity
Fix: Check Deal -> Files after a few seconds; if still empty, the proposal work was probably generated against a different deal. Open the correct deal in the Proposal Engine and regenerate.
Prevention: Confirm the deal context in the Proposal Engine header before generating — files attach to whatever deal you launched from.
Emergency: The bid was decided weeks ago but the CRM still shows Bid Submitted
Fix: Mark it Won (with a completion date), Lost, or No Bid now — late is better than never for the win-rate data.
Prevention: Sweep Bid Submitted deals weekly; anything past its decision window gets a follow-up call and a status update the same day.

Prove It Under Pressure

Decision drill: Run the full flow

Pick the move you would actually make. Score at the end.

1 / 3

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

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?

On this page