It is Monday morning, and three new RFQs came in over the weekend. One is a CM-at-risk support contract for a community college district. One is on-call inspection services for a city public works department. One is program management for a transit agency you have never worked with.
The principal looks at the list and says what most principals say: "We should go after all three."
Two weeks later, the proposal team is working nights. One response goes out thin. Another goes out late in the day because a resume needed a rewrite. Six weeks after that, the results come back. The firm wins none of the three, and the one it had the best shot at got the least attention.
Nobody made a bad decision on purpose. The problem is that no decision was really made. The firm said yes because saying no felt like leaving money on the table.
Why go/no-go turns into a guess
Most PM/CM firms have some kind of go/no-go process. In practice, it often looks like this:
- A short email thread or a five-minute hallway conversation
- A gut call from whoever knows the owner best
- A spreadsheet scorecard that gets filled in after the firm has already decided to pursue
- A "let's see what the team thinks" meeting with no clear criteria
The reasons are understandable. Opportunities arrive with short deadlines. The people who could judge fit are billable and busy. And the information you need to qualify an opportunity well is scattered: past proposals on a shared drive, project history in a PMIS or in people's heads, win/loss results in someone's inbox.
So the decision falls back on instinct. Instinct is valuable, but it is not consistent, and it tends to say yes.
The real cost of a weak yes
Every pursuit has a cost even if no one tracks it. A typical qualifications-based response pulls in a proposal manager, a marketing coordinator, a principal, and two or three key staff who are supposed to be billable.
When a firm chases a poor-fit opportunity, three things happen:
- The good pursuits get less attention. Proposal capacity is fixed. Every weak yes takes time from the opportunity you could actually win.
- Billable people go non-billable. The key staff who write project approach sections and review resumes are the same people running your projects.
- Win rates drift down quietly. A firm that submits on everything will see its win rate fall, and the team starts to feel like proposals are a lottery.
Saying no to the wrong pursuits is how you say a stronger yes to the right ones.
What a real go/no-go looks like
You do not need software to make this better. You need the same questions, answered the same way, before the team commits.
Start with a short, fixed set of questions
A useful go/no-go fits on one page. For a PM/CM pursuit, it usually covers:
- Owner relationship. Have we worked for this owner? Do we know the decision makers, or are we meeting them through the RFP? Tracking capital budgets and budget proposals shows which owners are about to spend, long before the RFP drops.
- Relevant experience. Do we have recent, similar projects we can name, with references who will take the call?
- Key staff. Do we have people who meet the minimum qualifications, and are they actually available for the duration?
- Pass/fail requirements. Licenses, certifications, insurance limits, participation goals, local office requirements. Any of these can end the pursuit on its own.
- Competition. Who is likely to bid? Is there an incumbent, and is the owner happy with them?
- Strategic value. Does this move the firm toward a market or client it wants, even if the odds are long?
- Effort. How much will this response cost the team, and what else is due in the same window?
Score each one simply. A 1 to 3 scale works fine. The point is not precision. The point is that every opportunity gets looked at through the same lens.
Decide after the basics are pulled from the RFP, and before anyone starts drafting
Firms often make the call too early, on a skim of the cover page, or too late, after a week of writing. The right moment is after the basic facts are pulled out of the RFP (requirements, criteria, dates) and before anyone starts drafting.
Write down the reason
A "go" with a one-line reason is worth more than a "go" with a perfect score. "Go: strong relationship with the facilities director, and our inspector lead meets every requirement" tells the team what to emphasize. "No-go: requires a local office we do not have" saves the next person from asking the same question on the next pursuit with that owner. IQ-Pursuit logs a standard no-go reason such as capability gap or unfavorable terms, so the reasons stay consistent from one pursuit to the next.
Close the loop when results come back
This is the step almost everyone skips. When you win or lose, go back to the go/no-go and ask: were we right about fit? Did the score predict the result? Over a year, this turns go/no-go from opinion into something closer to evidence about where your firm actually wins.
Before and after
Before: An RFQ lands. The principal forwards it with "thoughts?" Two people reply yes. The proposal manager starts building an outline. Halfway through, someone notices the resident engineer needs a license your available candidate does not hold. The team pushes through anyway because they have already started.
After: An RFQ lands. Once the RFP is uploaded, the team typically has the key requirements, scoring criteria, and dates in front of them, and a quick search pulls up the firm's past projects and proposals for that type of work. The go/no-go meeting takes 20 minutes and runs on a fixed scorecard. The license requirement is on the table before any writing starts. The team says no, logs the reason, and puts that capacity into the transit pursuit where it has a real shot.
The principal still makes the call. They just make it with the full picture instead of a gut feel and a deadline.
Where AI helps, and where it does not
Qualifying a pursuit has a mechanical part and a judgment part. AI is useful for the mechanical part.
Where it helps:
- Surfacing opportunities from agency portals such as PlanetBids, BidNet Direct, Cal eProcure, and SAM.gov, scoring them against your firm's criteria and the market segments you target, and sending a daily 8:00 AM PST email digest of new high-relevance bids, so the go/no-go starts with a shortlist instead of an inbox. A promising opportunity can be promoted into an active pursuit in one click, with its documents attached.
- Pulling mandatory requirements, forms, evaluation criteria, and dates out of the RFP into a compliance matrix so they are on the table at the decision meeting
- Letting your team search past proposals and projects in plain English, with citations back to the source passage, so "do we have the experience?" gets answered with examples, not memory. A deduplicated projects database and master resumes help answer the relevant experience and key staff questions.
- Keeping a running record of pursuits, decisions, and outcomes, including the reason for every no-go.
Where people still decide:
- Whether the relationship is real or wishful
- Whether a long shot is worth it for strategic reasons
- Whether the team has the energy for one more pursuit this month
What to watch:
- Garbage in, garbage out. Search and scoring are only as good as the past project and proposal data behind it. If your project history is thin or out of date, fix that first.
- Scores are not decisions. A high relevance score does not mean you should bid. It means you should have the conversation.
- Sensitive data. Fee schedules, past proposals, and staff information are confidential. Know where they are stored and who can see them. In IQ-Pursuit, every company's data is isolated, fee schedules are restricted to admins, and every AI answer cites the source passage.
How we approach it
At InstinctIQ, we work as a forward-deployed team. Before we build anything, we sit in on your actual go/no-go conversations and follow a few pursuits from RFP to result. We want to see what questions your principals really ask, where the answers live today, and which decisions get made on instinct because the facts take too long to find.
From there, IQ-Pursuit supports the process your team already runs. It finds opportunities across agency portals and scores them against your firm's criteria and the market segments you target. It lets your team search past proposals and projects in plain English, with citations back to the source passage. It pulls mandatory requirements, forms, and dates into a compliance matrix, records the outcome and debrief feedback for each submission, and reuses your win themes on similar pursuits. It gives your team a structured go/no-go matrix and a standard list of no-go reasons, so decisions are scored the same way every time. The difference is that the people scoring it have the requirements, dates, and relevant past work in front of them instead of working from memory.
A useful next step
Pull your last ten submitted proposals. For each one, write down why the firm decided to pursue it and whether it won. Then ask two questions:
- How many of these had a clear, written reason to pursue before writing started?
- How many of the losses could have been predicted from information that was in the RFP on day one?
If the answers make you uncomfortable, start with a one-page scorecard on the next pursuit that comes in. And if you want to see what that first qualification pass looks like when the facts are already pulled together, we are happy to walk through a recent opportunity with you.
Ready to win more pursuits?
Join hundreds of AEC teams already saving hours every week.