Get the free template
What's in the workbook (7)
Every tab starts with real content from our guides, so you are editing, not starting from a blank sheet. A "Start here" tab explains how to use it.
- 01
RFP outline
The ten sections a Salesforce RFP should include, what to put in each and why partners need it, with space for your draft.
Columns: Section · What to include · Why partners need it · Your draft, from company background to how responses will be evaluated.
- 02
Facts to gather
The eight facts partners need to quote accurately, with an owner and status for each.
Columns: Fact partners need · Gathered? (Yes, In progress, No) · Owner · Notes.
- 03
Requirements
Sixty numbered rows in user-story form with acceptance criteria and a Must / Should / Could / Won't (this phase) priority.
Columns: ID · Team · As a (role) · I need to (capability) · Acceptance criteria · Priority · Notes. Three worked examples show the style: a territory pipeline dashboard, a discount approval and a one-screen customer view for service agents.
- 04
Scoring
Nine weighted criteria with what a 5 looks like; score up to three partners and the weighted totals calculate.
Columns: Criterion · Weight · What a 5 looks like · one 1–5 column per partner. Scores accept whole numbers from 1 to 5 only, the weight total highlights if it drifts from 100, and each partner gets a weighted score out of 100.
- 05
Questions
Twelve questions to ask finalists, with what a good answer and a red flag sound like.
Columns: Topic · Question · A good answer sounds like · A red flag sounds like · notes for each partner. Topics are experience and fit, people and continuity, and approach and delivery.
- 06
References
Eight reference-check questions with space for each partner.
Columns: Reference question · one column per partner, including whether the people who sold the project delivered it.
- 07
Proposal comparison
Fourteen line items to compare proposals like for like before comparing prices.
Columns: Item · Partner A · Partner B · Partner C · Notes. Scope, exclusions, migration, testing, hypercare, named team and assumptions come first; price and payment terms sit at the bottom on purpose.
Who uses it, and when (4)
Open this workbook before you contact any partner, and keep it open until the contract is signed. The outline and facts tabs come first, while you are still working out what you need. Scoring weights get agreed next, before the first partner meeting. The questions, references and proposal comparison tabs do their work once responses arrive and you are down to finalists.
Who works in it
- Project owner or sponsor drafts the RFP, owns the facts list and makes the final recommendation.
- Business process owners describe their team’s processes and write the requirements for their area.
- IT and security supply the integration list, the existing org details and any access or privacy rules.
- Finance or procurement review pricing models, payment terms and the change request process.
How to use it, step by step (6)
- 01
Gather the facts before you write
Put a name in every Owner cell on Facts to gather. If several rows are still at No near your release date, consider a short paid discovery first: you get a written scope you own and can take to several partners.
- 02
Draft the RFP section by section
Use the What to include column as your prompt and write in the yellow Your draft column. Describe outcomes, volumes and constraints, and leave the solution design to the partners you are evaluating.
- 03
Write requirements as testable user stories
Replace the three examples with your own. Every row needs an acceptance criterion someone could check, and a priority. Won't (this phase) keeps parked ideas visible without inflating every quote.
- 04
Lock the weights before anyone meets a partner
Move points between criteria until the weights reflect what makes your project risky, keep the total at 100, and have each evaluator score separately before you compare.
- 05
Interview finalists with the same questions
Ask every finalist every question, and note each answer against the good-answer and red-flag columns while it is fresh.
- 06
Check references, then compare proposals line by line
Fill the scope, assumptions and team rows of Proposal comparison before you read the price row. Then score.
Mistakes it helps you avoid (4)
Designing the solution in the RFP
Specifying objects and fields gets you bids that build your guesses. The outline asks for problems, processes and constraints instead.
Asking for quotes with facts missing
When volumes, history or integrations are left out, each partner assumes something different and the totals stop being comparable.
Adjusting weights after the demos
Weights agreed in advance stop a favourite from being scored into first place. The tab’s note also reminds you that a slightly lower total can still win on the criterion that matters most.
Comparing prices before scope
Two quotes that look alike usually differ in what they assume about your team’s time, data and support after launch.
How it works with the other templates (3)
- Salesforce Implementation Project Plan: Your prioritized requirements become the requirements sign-off task on its Plan tab, and the phases the winning partner proposed set the week offsets.
- Salesforce Data Migration Workbook: The Data and Integrations sections of your outline, and the record-volume fact, are the starting rows of its Inventory tab, so data owners are not asked twice.
- Salesforce UAT Test Script Workbook: Each acceptance criterion you write here becomes the expected result of a test script later. Keep the REQ numbers and every script can trace back to what you asked for.
Related pages
- Partner evaluation scorecard (online): a quicker browser version of the scoring step if you are not ready for a full RFP.
- How to prepare for Salesforce discovery: what to have ready if the facts tab tells you to start with paid discovery.
- Salesforce implementation cost drivers: why the facts on the second tab move a quote up or down.
- Salesforce partner vs freelancer: if your shortlist mixes firms and independent consultants.
Questions about the RFP and partner scoring workbook (5)
Do we need a formal RFP to choose a Salesforce partner?
Not always. If you are talking to two or three partners about a contained scope, the Facts to gather, Scoring and Questions tabs on their own keep the comparison fair. A written RFP earns its effort when procurement requires one, when several bidders are involved, or when the scope is large enough that partners need the same written brief to quote against.
How should we set the scoring weights?
Start from the defaults in the file (four criteria at 15, three at 10 and two at 5) and move points toward whatever makes your project risky. A project with heavy data and several integrations deserves more weight on that criterion; a team with no admin may weight support after go-live higher. Decide before the first meeting and keep the total at 100.
How is the weighted score calculated?
Each partner’s 1–5 score on a criterion is multiplied by that criterion’s weight, the results are added up, and the total is scaled so that a partner scoring 5 on everything gets 100. Because the scale is fixed, changing one weight changes every partner’s total in the same way.
How many partners can we compare in the workbook?
The Scoring, Questions, References and Proposal comparison tabs each have columns for three partners. That fits a shortlist of finalists; narrow a longer list first using the facts and a short first conversation.
Can we send the Requirements tab to partners as it is?
Yes, that is what it is written for: role, capability, acceptance criteria and priority in a format partners can estimate against. Clear out or hide the Notes column first if it holds internal comments.
The guidance behind it (3)
This template follows the advice in our guides, written by the consultants at Abstrakt Solutions, a Salesforce Select partner with 138 certifications.