The takeaway
RFP intake triage that protects win rate — operator guide for the people doing the work. Win rate dies in intake more often than in prose.
Bid desks and sales leaders who lose quiet weeks to low-fit packages while good deals starve for SME time.
Silent no-bids, political yes-bids, and intake that only checks whether the PDF opened.
Written fit gates, named decide-by times, resource math, and feedback to sales on why a package was declined or reshaped.
Governed response operations so intake, answers, and reuse share one system instead of a pile of heroic spreadsheets.
Win rate dies in intake more often than in prose.
A package arrives. Someone says we should respond because the logo is good. Someone else is already late on two better-fit deals. The team starts answering anyway because declining feels political. Two weeks later you shipped a tired workbook into a deal you never had a right to win, and the deals you could win waited on security review.
RFP intake triage is how you protect scarce SME attention. It is not a graveyard for ambition. It is how ambition stays funded.
In practice, write the object, the owner, and the clock before the week gets loud. A reader should know what to open tomorrow morning without another alignment meeting. Prefer CRM fields, stem IDs, exception tickets, and package states over slogans.
Name the failure mode you refuse to repeat and the artifact that proves the strong path. If the only artifact is a slide, you do not have a system yet. If two teams would still answer differently after reading this, add the limit line and the escalation path.
Clarity is not more adjectives. Clarity is fewer surprises after the buyer compares notes across channels.
What does good intake triage decide?
Triage answers four questions fast enough to matter.
Should we bid? If yes, at what depth? Who must be on the core team? What is the first risk that could make this a no later?
If your intake only captures due date and customer name, you built a mailbox. Mailboxes do not protect win rate.
Depth matters as much as yes or no. A light response, a full workbook, and a strategic pursuit are different products. Treating them as one queue is how everything becomes medium and late.
Operators feel this in the calendar first. When guidance is vague, people invent under deadline. Make the next action obvious: who decides, what is blocked, and what ships customer-ready.
Keep the language short enough for a live call and strict enough for a security review. That double duty is the job. Long internal essays do not survive either room.
If you cannot point to a reused stem after two weeks, the process is still theater. Reuse is the grade. Activity is not.
Which fit gates should be written down?
Write gates the bid desk can apply without reading minds.
Solution fit. Do we sell what they are buying in the region and deployment pattern they need? Proof fit. Can we show relevant proof without inventing adjacency? Access fit. Do we have a champion or path to the economic buyer, or is this a blind RFP from nowhere? Commercial fit. Are security, legal, and pricing constraints inside a range we can defend? Capacity fit. Do we have the people this month, not in theory?
Gates should produce a visible outcome: bid, bid-light, reshape with sales, or no-bid. “Maybe, start drafting” is how queues rot.
Revisit gates quarterly. Markets move. Sacred gates that never change become superstition.
Treat this as a weekly operating standard, not a one-time initiative. Put the check in an existing meeting so it does not depend on hero memory.
When something breaks in a deal, write the scar into the library the same day. Delayed write-back is how the next team pays the tribal tax again.
Managers should coach from the opportunity record and the stem, not from vibes. If coaching cannot see the object, the object is not real yet.
Scenario: Monday 9:40, three packages and one security lead
Two RFPs and one security workbook land before standup. Logo A is famous and vague. Logo B is mid-market with a champion who already ran a technical validation. Logo C is a partner-led package with a brutal timeline.
Weak path: the team starts all three because declining feels like giving up. Security is thrashing by Wednesday. Logo B, the real deal, gets thin answers. Logo A burns cycles and ghosts. Leadership asks why win rate dipped while activity looked heroic.
Strong path: intake scores fit in ninety minutes. Logo A is no-bid with a note to sales on missing access and solution match. Logo C is bid-light with partner-owned sections and a hard internal cutoff. Logo B is full bid with named SE and security hours reserved. Win rate protection looks like calendar math, not slogans.
The strong path feels uncomfortable the first times you no-bid a shiny logo. That discomfort is the point. Attention is the scarce asset.
After triage, write the decisions where sales can see them without asking. Logo A no-bid with gate reasons. Logo C bid-light with cutoff. Logo B full bid with named hours reserved. If those notes only live in a private ops doc, sales will recreate shadow pursuits.
Then protect the calendar. If Logo B’s security hours get stolen by a late shiny logo, triage was theater. The operating rule is simple: full-bid reservations move only with an explicit trade decision, not with hallway urgency. Win rate protection is calendar integrity wearing a process name.
How do you run decide-by times without theater?
Every intake item needs a decide-by time shorter than the customer due date by enough margin to produce quality. Publish the decide-by next to the due date. If stakeholders miss it, the default should be no-bid or bid-light, not silent drift into full pursuit.
Decision meetings should be short and factual: gate results, capacity, open risks, owner asks. Long storytelling meetings reward politics. Bring the champion path and the capacity board, not vibes.
When sales disagrees with no-bid, use an escalation path with an executive owner who also owns the resource tradeoff. Escalation without tradeoff is how everything becomes yes.
Publish decide-by next to due date on every intake card. If stakeholders miss it, default to no-bid or bid-light, not silent drift into full pursuit. That default feels harsh once and then trains the company to show up.
Decision meetings stay short: gate results, capacity, open risks, owner asks. Long storytelling meetings reward politics. Bring the champion path and the capacity board. When sales disagrees with no-bid, escalation must include a named executive who also owns the resource tradeoff. Escalation without tradeoff is how everything becomes yes.
How should capacity and SME load show up in intake?
If intake cannot see security, legal, solution consulting, and proposal load, it will over-commit. A simple board beats a perfect resource management fantasy.
Show committed hours for the next two weeks. Show who is already on critical path deals. Show blackout dates. When a new full bid would break a better deal, make that trade visible in the same meeting where people fall in love with a logo.
Capacity is not only headcount. It is whether your exception path and library can absorb the package’s hard stems. A clean library can take more volume. A tribal library cannot.
Show committed hours for the next two weeks, who is on critical path deals, and blackout dates. Include whether the library and exception path can absorb the package’s hard stems. A clean library takes more volume. A tribal library cannot.
When a new full bid would break a better deal, make that trade visible in the same meeting where people fall in love with a logo. Capacity honesty is uncomfortable. It is also how good teams stay good through busy quarters.
What should sales hear when you no-bid or reshape?
Silence breeds shadow RFPs. Sales will go around the desk.
Give a short reason tied to gates. Offer a reshape when possible: pursue commercially without the full workbook, or wait until a champion path exists. Put the reason in the CRM so the account story stays honest.
No-bid is not a moral judgment on the rep. It is portfolio management. Leaders should defend good no-bids in public or the system collapses into performative yeses.
In practice, write the object, the owner, and the clock before the week gets loud. A reader should know what to open tomorrow morning without another alignment meeting. Prefer CRM fields, stem IDs, exception tickets, and package states over slogans.
Name the failure mode you refuse to repeat and the artifact that proves the strong path. If the only artifact is a slide, you do not have a system yet. If two teams would still answer differently after reading this, add the limit line and the escalation path.
Clarity is not more adjectives. Clarity is fewer surprises after the buyer compares notes across channels.
Where Tribble fits
Tribble helps teams run response operations where intake context, answer ownership, and reuse live together. Intake triage still needs human judgment. The software job is to keep the decision artifacts, the answer spine, and the deal context from scattering across five tools nobody reopens.
If you only need a shared inbox, keep the inbox. If you need win rate protection at volume, you need intake that connects to how answers are actually produced.
Operators feel this in the calendar first. When guidance is vague, people invent under deadline. Make the next action obvious: who decides, what is blocked, and what ships customer-ready.
Keep the language short enough for a live call and strict enough for a security review. That double duty is the job. Long internal essays do not survive either room.
If you cannot point to a reused stem after two weeks, the process is still theater. Reuse is the grade. Activity is not.
Which metrics keep triage honest?
Track no-bid rate by reason, not as a vanity “we are selective” score. Track win rate on full bids vs bid-light. Track SME hours per pursuit. Track how often late exceptions appear because intake missed a hard constraint. Track shadow packages that bypassed intake.
If win rate is flat while volume climbs and SME burnout climbs, triage is failing even if every PDF got a reply.
Treat this as a weekly operating standard, not a one-time initiative. Put the check in an existing meeting so it does not depend on hero memory.
When something breaks in a deal, write the scar into the library the same day. Delayed write-back is how the next team pays the tribal tax again.
Managers should coach from the opportunity record and the stem, not from vibes. If coaching cannot see the object, the object is not real yet.
In practice, write the object, the owner, and the clock before the week gets loud. A reader should know what to open tomorrow morning without another alignment meeting. Prefer CRM fields, stem IDs, exception tickets, and package states over slogans.
Name the failure mode you refuse to repeat and the artifact that proves the strong path. If the only artifact is a slide, you do not have a system yet. If two teams would still answer differently after reading this, add the limit line and the escalation path.
Clarity is not more adjectives. Clarity is fewer surprises after the buyer compares notes across channels.
FAQ
Should marketing influence intake?
They can flag strategic logos. They should not override capacity math without an executive trade. Strategy without staffing is a press release.
What if legal requires us to answer everything from a certain buyer?
Then that constraint becomes a gate and a capacity reserve. It should be explicit, not a surprise every quarter.
How detailed should scoring be?
Detailed enough to decide, light enough to finish fast. Ten-factor models that nobody trusts lose to a five-gate sheet people use.
Can AI score fit?
It can pre-read and flag missing sections, odd requirements, and likely hard stems. Humans still own bid or no-bid. Do not outsource politics to a model.
What about RFI vs RFP vs security workbook?
Use different depth defaults. An RFI can be bid-light more often. A security workbook on an active opportunity may outrank a cold RFP with a prettier cover.
How do we stop intake from becoming a blame forum?
Keep artifacts factual. Review patterns monthly. Coach sales on access and solution fit earlier in the cycle so intake is not the first serious conversation.
What if leadership wants higher response volume?
Then fund SME capacity and library quality. Volume targets without capacity are how win rate and people both break.
What to do this week
Audit the last eight pursuits. Mark which ones failed gates you still “somehow” bid. Total SME hours on the bottom two. Move those hours in the next cycle toward the top two patterns you actually win. Publish the gate sheet where sales can see it before the PDF arrives.
Audit the last eight pursuits. Mark which ones failed gates you still somehow bid. Total expert hours on the bottom two. Move those hours in the next cycle toward the top two patterns you actually win. Publish the gate sheet where sales can see it before the PDF arrives.
Operators feel this in the calendar first. When guidance is vague, people invent under deadline. Make the next action obvious: who decides, what is blocked, and what ships customer-ready.
Keep the language short enough for a live call and strict enough for a security review. That double duty is the job. Long internal essays do not survive either room.
If you cannot point to a reused stem after two weeks, the process is still theater. Reuse is the grade. Activity is not.