Template
Vendor evaluation criteria: 30 criteria, weights and a scorecard template
Vendor evaluation criteria are the factors you score every candidate vendor on before you buy: cost, quality, delivery, capability, risk and security, financial stability, relationship and ESG. Score each criterion from 1 to 5 against written anchors, multiply by a weight that fits the purchase, and the vendor with the highest weighted total that passes your pass/fail gates wins.
Updated November 17, 2026 ยท 17 min read
Key takeaways
- Use 30 criteria in 8 groups as a menu, then keep the 10 to 15 that matter for this purchase.
- Every score needs an anchor ("3 means...") and a piece of evidence, or two people will score the same vendor differently.
- Weights change with the purchase: security dominates software, people and quality dominate agencies, delivery and quality dominate physical suppliers.
- Some criteria are gates, not scores. A vendor that fails a gate is out, no matter how high its total.
- Lock the weights before you see proposals. In the worked example below, a 10-point weight shift flips the winner.
- Selection scoring and ongoing performance scorecards are different tools: one compares candidates on evidence, the other tracks a signed vendor on KPIs.
Free vendor scorecard template (CSV)
All 30 criteria with measurement notes, 1/3/5 anchors, gate flags, weights for three purchase types and score columns for three vendors. A plain CSV that opens in Excel and Google Sheets.
The 8 groups of vendor evaluation criteria
Most lists of vendor selection criteria stop at "price, quality, service". That is fine for a one-off order of office chairs, but it hides the questions that cause expensive mistakes: who exactly does the work, what happens to your data, how hard it is to leave. The 30 criteria below sit in eight groups, and each group answers one question.
| Group | The question it answers | Criteria |
|---|---|---|
| Cost | What will this really cost over the contract, and how predictable is it? | 4 |
| Quality | Does the output meet our written requirements, proven rather than promised? | 4 |
| Delivery | Will it arrive on time, and keep arriving as we grow? | 3 |
| Capability | Have they done this exact job, with these people, in a setup like ours? | 4 |
| Risk and security | What can go wrong with our data, systems or legal position? | 4 |
| Financial stability | Will they still exist, and be insured, when we need them? | 3 |
| Relationship | What is it like to work with them, and to stop working with them? | 5 |
| ESG | Do their environmental, labor and ethics practices meet our standards? | 3 |
Before you score anything, gather the candidates. Most teams already hold more offers than they remember: proposals in someone's inbox, quotes from last year, cold pitches that arrived with a price. If your team files incoming offers in PitchBin, search the category first and you get the vendor names, the quoted prices (a sent pitch is an immutable snapshot, so the price stays on record) and your colleagues' notes and ratings. The full sequence from need to contract is in our vendor selection process guide.
30 vendor evaluation criteria with scoring anchors
Each criterion has a measurement method and three anchors on a 1 to 5 scale. Use 2 and 4 for vendors that fall between anchors. Write one line of evidence next to every score ("reference call with client X, 14 Oct"). A score without evidence is an opinion, and opinions are where the loudest pitch wins.
Cost (weight: software 20%, agency 20%, physical supplier 25%)
Cost is never just the quoted price. Score the full three-year cost and how much of it is written down.
| Criterion | How to measure it | 1 means | 3 means | 5 means |
|---|---|---|---|---|
| 1. Total cost of ownership (3 years) | Add price, setup, training, add-ons, expected overages, renewal increases, your internal time and exit cost over 36 months. Score = 5 x (lowest credible TCO / this vendor TCO). | About 5x the lowest credible bid | About 1.7x the lowest credible bid | Lowest credible bid |
| 2. Price transparency | Check whether the quote is itemized and whether usage limits, overage rates, setup fees and renewal price are in writing. | One lump sum, extras "to be discussed" | Itemized, but overages or renewal price unclear | Fully itemized, overage rates and renewal price in writing |
| 3. Payment terms | Compare deposit, upfront billing and invoice terms to your standard terms (for example net 30). | 100% upfront, no refund on exit | Annual upfront or 50% deposit | Your standard terms, or monthly in arrears |
| 4. Price protection | Look for a renewal cap, indexation clause, minimum commitment and the right to change prices mid-term. | No cap, prices "subject to change" | Cap for year 2 only, or tied to an index | Fixed for the term plus a written renewal cap |
Quality (weight: software 15%, agency 25%, physical supplier 25%)
Quality scores must rest on something you saw: a trial, a sample, a reference, a document. A claim in a sales deck scores nothing.
| Criterion | How to measure it | 1 means | 3 means | 5 means |
|---|---|---|---|---|
| 5. Fit to written requirements Gate: every must-have met | Count must-haves and nice-to-haves that were demonstrated, not just claimed. Any missing must-have is a fail. | Must-haves met only with workarounds | All must-haves, about half the nice-to-haves | All must-haves and most nice-to-haves, shown live |
| 6. Proof of quality | Relevant work samples, a paid pilot, a sample batch checked against your spec, or certifications such as ISO 9001 where they matter. | Generic samples only, no trial offered | Relevant samples, no trial | Passed your trial, pilot or sample inspection |
| 7. Defect and rework history | Ask references about errors, rework and returns. For goods, ask for defect rate data (percent or parts per million). | References describe repeated rework | Occasional issues, fixed promptly | Low defects in data and references, fixes at vendor cost |
| 8. Quality process | Ask the vendor to walk you through how work is checked before it reaches you, with real artifacts. | "We are careful", no process | Documented process, not shown | Documented and shown: test reports, review checklists, inspection records |
Delivery (weight: software 5%, agency 10%, physical supplier 20%)
Delivery covers when you get the thing and whether the vendor can keep delivering as you grow.
| Criterion | How to measure it | 1 means | 3 means | 5 means |
|---|---|---|---|---|
| 9. Lead time or time to go live | Compare the vendor plan with your deadline. Ask for milestones in writing. | Misses your deadline | Meets the deadline with no buffer | Meets it with buffer, written milestone plan |
| 10. On-time record | Ask references how often deadlines slipped. For suppliers, ask for their own on-time delivery report. | References report regular slips | Occasional slips, with early warning | On time per references and data |
| 11. Capacity and scalability | Ask whether they can handle double your volume or your seasonal peak, and with how many people. | You would be their biggest client by far, no headroom | Headroom for your current volume | Proven at 2x your volume with larger clients |
Capability (weight: software 20%, agency 25%, physical supplier 5%)
Capability asks whether this vendor has done this exact job before, with these exact people, in a setup like yours.
| Criterion | How to measure it | 1 means | 3 means | 5 means |
|---|---|---|---|---|
| 12. Relevant experience | Clients of similar size and industry, and similar projects in the last two years. | None in your industry or size | Some similar clients | Several comparable clients, available as references |
| 13. Named team and key people | Who will do the work, their experience, and whether that is written into the contract. | "A team will be assigned" | Lead named, rest to be decided | Named people who attended the pitch, written into the contract |
| 14. Technical fit and integration | Software: SSO, API, data export, integration with your stack. Agency: tools and access. Goods: specs and standards. | Needs custom work or manual exports | Works through a workaround or third-party connector | Native fit shown in your environment or trial |
| 15. Roadmap and improvement | Product roadmap for software; proposed improvements and cost savings for services and goods, with proof of past delivery. | Stagnant product or no ideas offered | Vague roadmap | Specific roadmap or savings plan, track record of shipping it |
Risk and security (weight: software 20%, agency 5%, physical supplier 5%)
This group matters most when the vendor touches your data, your systems or your customers. Several criteria here work best as pass/fail gates.
| Criterion | How to measure it | 1 means | 3 means | 5 means |
|---|---|---|---|---|
| 16. Information security Gate: if they hold your data or system access | A current SOC 2 Type II report or ISO/IEC 27001 certificate (check scope and date), or a completed security questionnaire. MFA and encryption as a minimum. | No evidence, cannot answer a questionnaire | Questionnaire answered well, no independent audit | Current independent audit covering the service you buy |
| 17. Data protection Gate: if they process personal data | Data processing agreement, data location, list of subprocessors, breach notification terms. | No DPA, data location unknown | DPA on request, vague subprocessor list | Standard DPA, published subprocessors, data location stated |
| 18. Business continuity | Backups, disaster recovery testing, second source for key components, dependency on one person. | One person or one site, no plan | Written plan, never tested | Plan tested in the last 12 months, summary shared |
| 19. Legal and compliance Gate: sanctions hit or missing license = out | Licenses and registrations, sanctions screening, litigation search, industry rules that apply to you. | Unresolved red flag | Clean checks, documents incomplete | Clean checks, documents supplied without chasing |
Financial stability (weight: software 10%, agency 5%, physical supplier 10%)
A great vendor that runs out of cash mid-contract is a bad vendor. Check this in proportion to how hard it would be to replace them.
| Criterion | How to measure it | 1 means | 3 means | 5 means |
|---|---|---|---|---|
| 20. Financial health | Years trading, filed accounts in the public company registry, a credit report, funding status. | Under a year old, no or late filings | 2 to 5 years, filings on time | 5+ years, profitable or well funded, filings on time |
| 21. Dependency risk | Your expected spend as a share of their revenue, and how much of their revenue comes from their largest client. | You would be over a third of their revenue, or one client dominates | Moderate concentration | Diversified client base, you are a small share |
| 22. Insurance coverage Gate: optional, minimum cover for high-risk work | Certificates for the cover you require (professional or general liability, cyber, product liability) and limits versus contract value. | No relevant cover | Some cover, limits below your requirement | All required cover at required limits, certificate supplied |
Relationship (weight: software 8%, agency 8%, physical supplier 5%)
How a vendor behaves while selling is the best preview you get of how they behave after you sign.
| Criterion | How to measure it | 1 means | 3 means | 5 means |
|---|---|---|---|---|
| 23. Responsiveness during evaluation | Time to answer your questions and whether the answers address what you asked. | Days late, answers off-topic | On time, generic answers | Fast, specific, says plainly what they cannot do |
| 24. Support model and SLA | Support channels, hours, response and resolution times, service credits, named contact. | Email only, no SLA | Business-hours SLA, weak credits | Written SLA with times and credits, named contact |
| 25. Reference quality | Two or three calls with comparable customers, ideally including one former customer. | Refuses references | Positive but not comparable | Comparable, specific, open about problems they fixed |
| 26. Contract flexibility and exit | Term length, auto-renewal and notice period, termination rights, data or asset handover on exit. | Multi-year lock-in, long auto-renewal notice, no data export | Annual term, 30 to 60 day notice | Short term or clean exit, free export in a standard format |
| 27. Communication and working style | Whether the delivery team (not just sales) joined the process; clarity of written updates; time zone overlap. | Sales says yes to everything, delivery team absent | Acceptable | Delivery team present, clear written communication |
ESG (weight: software 2%, agency 2%, physical supplier 5%)
Environmental, social and governance criteria carry more weight for physical supply chains and for buyers with their own reporting duties.
| Criterion | How to measure it | 1 means | 3 means | 5 means |
|---|---|---|---|---|
| 28. Environmental practices | Written policy, measured emissions or waste data, packaging, certifications such as ISO 14001 where relevant. | Nothing in writing | Policy, no data | Measured data and targets, certification where relevant |
| 29. Labor and human rights | Signed supplier code of conduct, modern slavery statement where the law requires one, audits of their own suppliers. | Refuses to sign a code of conduct | Code of conduct signed | Published statement or audits, extended to their suppliers |
| 30. Business ethics Gate: any inducement = out | Anti-bribery policy, conflict of interest disclosure, gifts policy. | Offers gifts or kickbacks during the evaluation | Policy exists | Policy, staff training, conflicts disclosed without being asked |
Gates before scores: the pass/fail criteria
A weighted total averages strengths against weaknesses. That is what you want for "responsiveness" and "roadmap", and exactly what you do not want for "will they sign a data processing agreement". Decide which criteria are gates, check them first, and drop any vendor that fails before you calculate a single total. Typical gates:
- All must-have requirements met. If a must-have is negotiable, it was a nice-to-have.
- Data processing agreement signed when the vendor will process personal data on your behalf. Under the EU and UK GDPR this is a legal requirement, not a preference: Article 28 of the GDPR requires a written contract with each processor that covers specific terms.
- Minimum security evidence for vendors with access to your systems or customer data, for example an independent audit report or a questionnaire your IT lead accepts.
- Clean sanctions and legal checks, plus any license the work legally requires. Our vendor due diligence checklist lists the checks in order.
- No inducements. A vendor that offers gifts or personal benefits to evaluators during the process is out.
- Modern slavery statement where the law requires your supplier to publish one. In the UK, section 54 of the Modern Slavery Act 2015 applies to commercial organisations supplying goods or services with a total turnover of 36 million pounds or more.
If you are not sure the vendor is a real company at all, settle that before the gates: our guide on how to verify a vendor covers registry lookups, domain checks and the warning signs of a fake supplier. This page is a practical framework, not legal advice.
How to weight vendor evaluation criteria by purchase type
A single universal weighting is the most common flaw in free vendor scorecard templates. Security matters a lot when you buy software that holds customer data and barely at all when you buy printed brochures. These starting weights sum to 100 for each purchase type. Adjust them, but do it before the first proposal arrives.
| Group | Software / SaaS | Agency / professional services | Physical goods supplier |
|---|---|---|---|
| Cost | 20% | 20% | 25% |
| Quality | 15% | 25% | 25% |
| Delivery | 5% | 10% | 20% |
| Capability | 20% | 25% | 5% |
| Risk and security | 20% | 5% | 5% |
| Financial stability | 10% | 5% | 10% |
| Relationship | 8% | 8% | 5% |
| ESG | 2% | 2% | 5% |
| Total | 100% | 100% | 100% |
Why the weights move
- Software: you live with the product for years, it holds your data, and switching is painful. Capability (integration, roadmap) and risk (security, data protection) carry 40% between them. Delivery is light because go-live depends as much on you as on the vendor.
- Agency or professional services: you are buying people. The named team and relevant experience sit inside capability, so capability and quality together carry 50%. Security matters less unless the agency gets access to your systems or customer lists; if it does, move 10 points from capability to risk.
- Physical supplier: late or defective goods stop your own operation, so delivery and quality together carry 45%. ESG gets more weight because labor and environmental issues in supply chains are where buyers carry real reputational and reporting exposure.
The CSV template splits each group weight across its criteria (for example, software cost 20% = total cost of ownership 9, transparency 4, payment terms 3, price protection 4), so you can score at criterion level and still land on these group totals.
Worked example: weighted scoring of three vendors
A fictional 40-person company is choosing customer support software. Three fictional vendors, called Vendor A, Vendor B and Vendor C, passed the requirements gate. The team uses the software weights from the table above and scores at group level (each group score is the average of that group's criterion scores).
Step 1: score cost with a formula, not a feeling
Three-year total cost of ownership: Vendor A $18,000, Vendor C $22,500, Vendor B $45,000. Cost score = 5 x (lowest TCO / vendor TCO):
- Vendor A: 5 x (18,000 / 18,000) = 5.0
- Vendor C: 5 x (18,000 / 22,500) = 5 x 0.8 = 4.0
- Vendor B: 5 x (18,000 / 45,000) = 5 x 0.4 = 2.0
Step 2: multiply each group score by its weight
Points = score x weight. The maximum is 5 x 100 = 500 points. Divide the total by 100 to get a weighted score on the same 1 to 5 scale.
| Group | Weight | A score | A points | B score | B points | C score | C points |
|---|---|---|---|---|---|---|---|
| Cost | 20 | 5 | 100 | 2 | 40 | 4 | 80 |
| Quality | 15 | 3 | 45 | 5 | 75 | 4 | 60 |
| Delivery | 5 | 4 | 20 | 4 | 20 | 3 | 15 |
| Capability | 20 | 3 | 60 | 5 | 100 | 4 | 80 |
| Risk and security | 20 | 2 | 40 | 5 | 100 | 4 | 80 |
| Financial stability | 10 | 3 | 30 | 5 | 50 | 3 | 30 |
| Relationship | 8 | 4 | 32 | 3 | 24 | 5 | 40 |
| ESG | 2 | 3 | 6 | 4 | 8 | 3 | 6 |
| Total points | 100 | 333 | 417 | 391 | |||
| Weighted score (1 to 5) | 3.33 | 4.17 | 3.91 |
Step 3: apply the gates
The team set a gate of at least 3 on risk and security, because the tool will hold customer conversations. Vendor A scored 2: no independent audit, and its data processing agreement was "available on request" with no subprocessor list. Vendor A is out, even though it is the cheapest option by a wide margin. Without the gate, nobody would have noticed that the cheapest option was also the one most likely to cause a data incident.
Step 4: test how fragile the result is
Vendor B leads Vendor C by 0.26 points (4.17 vs 3.91), and costs $22,500 more over three years. Now suppose the CFO argues, after seeing the prices, that cost should weigh 30% and capability only 10%. Rerun the same scores:
- Vendor B: (2 x 30) + (5 x 15) + (4 x 5) + (5 x 10) + (5 x 20) + (5 x 10) + (3 x 8) + (4 x 2) = 60 + 75 + 20 + 50 + 100 + 50 + 24 + 8 = 387, or 3.87
- Vendor C: (4 x 30) + (4 x 15) + (3 x 5) + (4 x 10) + (4 x 20) + (3 x 10) + (5 x 8) + (3 x 2) = 120 + 60 + 15 + 40 + 80 + 30 + 40 + 6 = 391, or 3.91
A 10-point shift in weights flips the winner. Neither result is wrong, which is the point: the weights are a business decision, and if you make it after you see the prices, you are choosing a vendor and then building the math to justify it. Agree and sign off weights before proposals arrive, and treat any margin under about 0.3 points as a tie that needs a judgment call written into the decision record.
Step 5: decide and write down why
Under the agreed weights, Vendor B wins. The decision record states: "Vendor B chosen over Vendor C at 4.17 vs 3.91. The gap comes from capability (native integration with our CRM, shown in the trial) and risk (current independent audit). We accept $22,500 more over three years for those two. Vendor C is the fallback if contract terms fail." That paragraph is what you will want in 18 months when someone asks why you are paying more. When prices are close and scope differs, compare quotes line by line first with our quote comparison template.
Vendor evaluation vs vendor performance scorecard
The phrase "vendor scorecard" is used for two different tools. Mixing them up is why many templates feel half useful: they ask you to rate "on-time delivery" for a vendor you have never received a delivery from.
| Pre-selection evaluation | Ongoing performance scorecard | |
|---|---|---|
| Question | Which of these candidates should we pick? | Is the vendor we picked delivering what we agreed? |
| When | Once, before the contract | Monthly, quarterly or yearly for the life of the contract |
| Evidence | Proposals, demos, trials, references, documents | Your own data: delivery dates, tickets, invoices, defects |
| Compares | Vendors against each other | One vendor against its contract targets and its own past |
| Criteria | The 30 criteria above, weighted | 5 to 8 measurable KPIs written into the contract |
| Outcome | Award, shortlist, or decline | Keep, expand, improvement plan, or replace |
The link between them: the targets you promise to track later (on-time rate, SLA, defect rate) belong in the contract you negotiate after evaluation. If they are not written down at signing, the performance scorecard has nothing to measure against.
Vendor performance scorecard KPIs and formulas
Pick the five to eight KPIs that apply to the vendor type. Set the target in the contract, then convert each result to a 1 to 5 score so the scorecard reads the same way as your selection scoring.
| KPI | Formula | Use for |
|---|---|---|
| On-time delivery rate | Orders or deliverables received on or before the agreed date / total due in the period x 100 | Suppliers, agencies |
| In-full rate | Order lines delivered complete / order lines ordered x 100 | Suppliers |
| Defect rate | Defective units / units received x 100 (or x 1,000,000 for parts per million) | Suppliers |
| First-pass acceptance | Deliverables accepted without rework / deliverables submitted x 100 | Agencies, contractors |
| SLA adherence | Tickets or incidents responded to and resolved within SLA / total tickets x 100 | Software, IT and support services |
| Uptime | (Minutes in period - downtime minutes) / minutes in period x 100. A 30-day month has 43,200 minutes, so 99.9% uptime allows about 43 minutes of downtime. | Software, hosting |
| Invoice accuracy | Invoices paid without correction / invoices received x 100 | All vendors |
| Price compliance | Invoice lines at the contracted price / total invoice lines x 100 | Suppliers, rate-card services |
| Budget variance | (Actual spend - agreed budget) / agreed budget x 100 | Agencies, projects |
| Issue response time | Median hours from your report to the vendor's first substantive reply | All vendors |
| Corrective actions closed on time | Corrective actions closed by their due date / corrective actions due x 100 | Suppliers, critical vendors |
Turning a KPI into a 1 to 5 score
Score against the target, not against a generic benchmark. A simple banding for any percentage KPI: 5 = at or above target, 4 = up to 2 points below, 3 = up to 5 points below, 2 = up to 10 points below, 1 = more than 10 points below. With a 95% on-time target, a quarter at 91% scores 3.
Review cadence and what the score triggers
- Monthly for vendors your operation cannot run without; quarterly for most vendors; yearly for low-spend, low-risk ones.
- 4.0 and above: keep, consider for more work.
- 3.0 to 3.9: keep, with one or two named improvement items for the next review.
- Below 3.0: written corrective action plan with a deadline, usually one quarter.
- Below 3.0 twice in a row: start a replacement process and review the vendor's status on your approved vendor list.
Share the scorecard with the vendor. A supplier that sees its numbers each quarter fixes problems before they reach a renewal conversation.
How to build your vendor scorecard in 6 steps
- Write the requirements first. List must-haves (gates) and nice-to-haves. The scorecard can only be as good as the requirements behind it.
- Pick criteria from the 30. Keep 10 to 15. Criteria that get 1% or less in the template for your purchase type are the first to cut: fold their points into a related criterion so the weights still sum to 100.
- Set the weights for this purchase type and get the budget holder to approve them in writing before any proposal arrives.
- Agree the anchors. Use the 1/3/5 descriptions in the CSV as a start and edit them to your context ("5 = integrates with our CRM natively").
- Score independently, then calibrate. Each evaluator scores alone with evidence notes. Then meet and discuss only the criteria where scores differ by 2 or more.
- Check gates, total, test sensitivity, decide. Drop gate failures, calculate totals, rerun with one alternative weighting, and record the reason for the decision.
Common vendor scoring mistakes
- Scoring the pitch, not the evidence. A polished demo is evidence of a good sales team. Score the trial, the references and the documents.
- Price scored by gut. Use the formula. Otherwise the cheapest vendor gets a 5 and everyone else gets a 3, regardless of whether they cost 10% or 200% more.
- Comparing quotes with different scopes. One quote includes onboarding and support, another does not. Normalize scope before scoring cost.
- Too many criteria. Forty criteria at 2.5% each produce totals where every vendor lands between 3.4 and 3.7 and nothing is decided.
- Averaging away a deal-breaker. A 1 on data protection should not be rescued by a 5 on responsiveness. That is what gates are for.
- One evaluator. A single scorer's preferences become the result. Two or three scorers, including someone who will use the product or service every day, catch what one misses.
- No record of losers. The vendors you scored and declined are your best fallback list. Keep the scores and quotes where the team can find them next year.
Frequently asked questions
What are the most important vendor evaluation criteria?
The core groups are cost (total cost of ownership, not just price), quality, delivery, capability, risk and security, financial stability, relationship and ESG. Which matter most depends on the purchase: security and integration lead for software, the named team and quality lead for agencies, delivery and defect rates lead for physical suppliers.
What is a vendor scorecard?
A vendor scorecard is a table that rates vendors on weighted criteria using a fixed scale. Before you buy, it compares candidates on evidence from proposals, trials and references. After you sign, a performance scorecard tracks the chosen vendor against contract KPIs such as on-time delivery, defect rate and SLA adherence.
How do you calculate a weighted vendor score?
Score each criterion from 1 to 5, multiply each score by its weight in percent, add the results and divide by 100. For example, a score of 4 on a 20% criterion contributes 80 points; a total of 391 points across all criteria is a weighted score of 3.91 out of 5.
How many criteria should a vendor scorecard have?
Ten to fifteen is enough for most purchases. Use a longer list such as the 30 criteria here as a menu, keep the ones that fit, and cut criteria that would get 1 percent or less of the weight, because they add work without changing the outcome.
What is a good vendor scorecard score?
On a weighted 1 to 5 scale, 4.0 or higher is strong, 3.0 to 3.9 is acceptable with improvement items, and below 3.0 calls for a corrective action plan. In selection, the ranking and the gap between vendors matter more than the absolute number; a gap under about 0.3 points is effectively a tie.
How often should you review vendor performance?
Monthly for vendors your operation depends on, quarterly for most vendors, and yearly for low-spend, low-risk ones. Share the results with the vendor so problems get fixed before renewal.
Are supplier evaluation criteria different from vendor evaluation criteria?
They are the same framework. "Supplier" is more common for physical goods, so supplier evaluation leans on delivery, defect rates, capacity and ESG; "vendor" is common for software and services, where security, integration and the named team weigh more.
Keep reading
Start every evaluation with the offers you already have.
Forward vendor emails to save@pitchbin.com and each one becomes a filed offer with company, service and quoted price, searchable by your whole team when the next evaluation starts. Free for companies.