Decide whether to pursue an RFP for my professional services firm
A go/no-go scorecard for a proposal opportunity that weighs win probability, fit, capacity, risk, and pursuit cost.
The prompt
Help me decide whether my firm should pursue a request for proposal (RFP).
Firm type: [accounting / consulting / architecture / engineering]
Opportunity summary: [client, scope, estimated fee, contract length, due date - paste key RFP sections]
Selection method: [low price / best value / qualifications-based / sole source likely]
Our relationship with the client: [none / met before RFP / current or past client / know the decision makers]
Incumbent and likely competitors: [WHO, and what we know]
Our relevant experience and staff: [projects, people, licenses, certifications]
Capacity: [who would do the work and what else they're committed to]
Pursuit cost: [estimated proposal hours, interview prep, any required travel or design work]
Contract terms in the RFP: [insurance limits, liability, payment terms, small or disadvantaged business participation goals]
Score the opportunity 1-5 on:
1. Client relationship and pre-RFP positioning (did we help shape this, or is it wired for someone else?).
2. Technical fit and directly relevant references.
3. Competitive position against the incumbent and likely bidders.
4. Staff availability if we win.
5. Fee adequacy and profitability given the selection method.
6. Contract and liability risk.
7. Strategic value: new market, anchor client, or follow-on work.
Return:
- A scorecard table with reasons for each score.
- An estimated win probability range with reasoning, and expected value (win probability x margin) vs. pursuit cost.
- Go, no-go, or go with conditions (e.g. teaming partner, questions to submit before the deadline).
- If no-go, a short, gracious message to the client that keeps the door open.
Base scores only on what I provide; flag any score that rests on an assumption.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Business Strategy & Startups prompts
What to fill in
- accounting / consulting / architecture / engineering
- WHO, and what we know
- projects, people, licenses, certifications
- who would do the work and what else they're committed to
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Plan how to start a nonprofit organizationA step-by-step launch plan for a nonprofit: mission, legal setup, board, first funding, operations, and measuring impact.
- Decide whether to build, buy, or partner for a capabilityA side-by-side recommendation on building in-house, buying a vendor tool, or partnering, with total cost and risk.
- Prepare a data room and SaaS metrics pack for fundraisingA due-diligence-ready data room index and metrics pack, with the definitions investors will check and the gaps to fix first.
- Agree on co-founder roles, equity, and decisions in writingA structured discussion guide and term summary for co-founders to take to a lawyer before signing anything.