Before you renew your RFP software: a checklist
Disclosure: we make Iris, an RFP and security questionnaire tool. The checklist below works for any vendor, including the one you have now. Renewing is often the right answer; the point is to renew on evidence.
Short answer: Before you renew RFP software, start about 90 days out. Find your notice deadline, compare the seats you pay for with the people who actually used the tool, check how much of your answer library is current, and re-run one RFP you've already submitted to grade the AI's answers. Then confirm you can export your content, list what your security team will need, and get every quote on the same assumptions. That gives you three real options: renew as is, renegotiate, or switch.
Who this is for: proposal managers, RFP and bid managers, and content library owners whose RFP software contract (Loopio, Responsive or another tool) renews in the next few months.
On this page
- The checklist at a glance
- When should you start?
- The 10 checks, one by one
- How to grade the AI on a past RFP
- Renew, renegotiate or switch?
- How Iris fits
- FAQ
The checklist at a glance
| # | Check | What to pull together | What good looks like |
|---|---|---|---|
| 1 | Contract terms | Renewal date, notice period, auto-renew clause, term length, price-change terms, data export and deletion terms | You know the last day you can give notice, and it's on a calendar |
| 2 | Usage | Projects completed in the last 12 months, by type (RFP, security questionnaire, DDQ, proposal) | Volume and mix match what you're paying for |
| 3 | Seats vs active users | Seats licensed vs people who logged in during the last 90 days; occasional SMEs | Few idle seats, and the SMEs who need access have it |
| 4 | Library health | Total entries; share reviewed in the last 12 months; entries with an owner; duplicates; conflicting answers | Most answers are owned and recently reviewed |
| 5 | AI answer quality | A blind re-run of one RFP you've already submitted, graded answer by answer | Most drafts usable with light edits; gaps flagged, not guessed |
| 6 | Export fidelity | The buyer's original Excel, Word and PDF files, exported back from the tool | Submittable without reformatting |
| 7 | Security review | What your security, legal and procurement teams will ask any vendor | You know the list before you talk to vendors |
| 8 | Integrations | Where your content lives today; CRM, chat and SSO needs | The tool reads your live sources instead of copies |
| 9 | Migration effort | Export format for your library; a test import into any alternative | You've seen your own library come out cleanly |
| 10 | Total cost | Seats, add-ons, services, overages and renewal terms, for every option | Every quote is on the same assumptions |
When should you start?
Start about 90 days before your renewal date, or earlier if your notice period is long. Many SaaS subscriptions renew automatically unless you give notice by a set date. Responsive's master agreement, for example, says subscriptions "will automatically renew" unless either party gives written notice of non-renewal at least 60 days before the renewal term (responsive.io/legal/msa, read 2026-11-22). Your own order form decides, so read it rather than assuming.
| When | What to do |
|---|---|
| Day −90 | Find the renewal date and notice deadline. Pull usage, seat and library numbers (checks 1–4). |
| Day −75 | Pick one past RFP and one past security questionnaire for the AI test. Request a library export from your current vendor, in writing. |
| Day −60 | Run the past-RFP test on your current tool and on one or two alternatives. Send each vendor your security questions. |
| Day −45 | Get quotes on the same assumptions. Test an import of your library into any alternative you're serious about. |
| Day −30 | Decide: renew as is, renegotiate, or switch. Give notice before the deadline if you're switching. |
| Renewal | If switching, run one live project in parallel before cutting over. |
The 10 checks, one by one
1. Contract terms
Find the signed order form and master agreement, not the pricing page. Write down:
- The renewal date and the notice deadline (the last day you can cancel or change the plan).
- Whether the contract auto-renews, and for how long.
- Any price-change terms at renewal.
- Data terms: how you get your content out, in what format, and how long the vendor keeps it after you leave.
2. Usage audit
Count the projects your team completed in the last 12 months, by type: RFPs, RFIs, security questionnaires, DDQs and proposals. Note which features you used and which you paid for but didn't touch. If security questionnaires run outside the tool (in spreadsheets or a separate tool), note that too. It's often the biggest hidden workload.
3. Seat count vs active users
Compare seats licensed with people who logged in during the last 90 days. Then list the people who should have used it but didn't: SMEs in security, legal, product and finance who answer a few questions a quarter. Ask your vendor how it counts a seat, and what it charges for occasional contributors.
How vendors package this varies, which is why the count matters:
| Vendor | What its own site says about plans | Source (read 2026-11-22) |
|---|---|---|
| Loopio | Three plans (Foundations, Enhanced, Enterprise), all with "Unlimited Projects" and no prices shown. Foundations "includes 10 seats". Add-ons are sold separately. | loopio.com/pricing |
| Responsive | Emerging Edition "Starting from $10,000"; Growth and Enterprise "Contact sales". A deployment is an annual platform fee plus user licenses plus add-ons and services. Its pricing page lists "Unlimited Response Projects". | responsive.io/pricing |
Pricing pages change. Your contract and quote are what count.
4. Content library health
Export or report on your answer library and check:
- Freshness: what share of answers was reviewed in the last 12 months?
- Ownership: what share has a named owner?
- Duplicates: how many questions have several near-identical answers?
- Conflicts: do any answers contradict each other, for example two different data-retention periods?
- Expired content: are there answers built on a policy, certification or product version that has changed?
A stale library is costly in any tool. If you switch, cleaning it once during import is cheaper than fixing it in every bid.
5. AI answer quality, tested on a past RFP
Marketing pages can't tell you how a tool's AI handles your content. A past RFP can. Take one RFP or questionnaire you've already submitted, run it through your current tool and any alternative, and grade the drafts against what you actually sent. The method is in the next section.
6. Export back to the buyer's format
Take the buyer's original files: an Excel workbook with dropdowns and comment columns, a Word document with a prescribed outline, and a PDF if your buyers send them. Export the answers back from each tool. Check:
- Do answers land in the right cells and sections?
- Do dropdowns, numbering and formatting survive?
- How long does cleanup take before the file is submittable?
7. Security review needs
List what your security, legal and procurement teams will ask before approving any vendor, including your current one at renewal:
- SOC 2 report and period; pen test summary
- DPA and subprocessor list
- Which AI models process your content, and whether your data is used for training
- Data residency and hosting region
- SSO, SCIM and role-based access
- Data export and deletion on exit
Send the same list to every vendor so the answers are comparable.
8. Integrations and where your content lives
Write down where your source content lives today (SharePoint, Google Drive, Confluence, Notion, a trust center) and which systems the work touches (CRM, Slack or Teams, SSO). For each integration, ask whether it syncs (stays current when the source changes) or imports (a one-time copy you'll need to refresh).
9. Migration effort and Q&A import
Ask your current vendor, in writing, how to export your full Q&A library and in what format (CSV or Excel is typical). Then test it:
- Export the library, or a large sample.
- Import it into any alternative you're seriously considering.
- Check that questions, answers and any metadata you rely on come through.
- Plan the cleanup: de-duplicate, resolve conflicts, and assign owners and review dates.
Migration effort depends on library size and how clean it is. Seeing your own library imported is the only reliable estimate.
10. Total cost on the same assumptions
Ask every vendor, including your current one, to quote the same shape: the same number of users (including occasional SMEs), the same volume of RFPs and questionnaires, the add-ons and services you need, and the same term. Ask about overage charges and price changes at the next renewal.
How to grade the AI on a past RFP
Use one RFP or questionnaire of 40 or more questions that you've already submitted, so you know the right answers.
- Load the same content into each tool: the documents and answer library you actually used.
- Add a stress test: include 3–5 questions your content can't answer, and two documents that contradict each other on one fact.
- Grade every answer against what you submitted:
| Grade | Meaning |
|---|---|
| Usable as is | Submittable with no edits |
| Light edit | Right substance; wording or length changes |
| Major rework | Wrong, incomplete or off-topic |
| Flagged gap | The tool said it didn't have enough information |
| Invented | Confident answer to a question your content can't support |
- Check the sources: can a reviewer see which document each answer came from?
- Check the conflict: did the tool notice the two contradicting documents?
The "Invented" row matters most. A blank answer routed to an expert costs minutes; a confident wrong answer in a submitted security questionnaire costs much more.
Renew, renegotiate or switch?
| If you found… | Consider |
|---|---|
| The tool scores well on your past-RFP test, the library is healthy, and seats match usage | Renew. Use your usage numbers to confirm the seat count. |
| The tool works, but you pay for idle seats or unused add-ons | Renegotiate seats and add-ons before the notice deadline. |
| Weak AI results on your own content, heavy export cleanup, or a library nobody maintains | Switch, after a clean test import and one live project in parallel. |
Switching mid-contract rarely pays back. If your renewal is far away, use this checklist to prepare, and run it again 90 days out.
How Iris fits
If you're testing alternatives, here's what Iris does on the checks above:
- Try it on check 5 for free. Try Iris free on an RFP you've already answered. Our team sets it up with you on your own content, so you can grade Iris's drafts against what you submitted. There's no self-serve sign-up.
- Q&A import for check 9. Iris imports existing Q&A pairs from CSV or XLSX (up to 10 MB per file). It then groups near-duplicate answers and marks each group Consistent or Contradictory, so an owner resolves each one once. Owners, tags and expiry dates can be set in bulk.
- Gaps flagged, not guessed. Iris drafts only from your content, links every answer to its sources, labels it High, Medium, Low or Contradictory, and says "There is not enough information to answer the question" instead of guessing.
- Export for check 6. Answers go back into the buyer's original Excel workbook, into Word (including your branded template), or onto the source PDF.
- Pricing for check 10. Iris is priced per active user, with unlimited RFPs, proposals, DDQs and security questionnaires and no usage caps. There's no public list price: ask for a quote on the same assumptions as everyone else.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026).
Try Iris free on an RFP you've already answered
FAQ
When should I start evaluating before an RFP software renewal?
About 90 days before the renewal date, or earlier if your notice period is longer. That leaves time to test alternatives on a past RFP and still give notice.
Can I get my answer library out of my current RFP software?
Usually, as a CSV or Excel export. Ask your vendor in writing how to export the full library, and check your contract's data terms.
How do I compare AI answer quality between RFP tools?
Re-run one RFP you've already submitted in each tool, with the same content, and grade every answer: usable as is, light edit, major rework, flagged gap or invented. Add a few questions your content can't answer to see whether the tool guesses.
Should I renegotiate or switch?
If the tool performs well on your own content but you pay for idle seats or add-ons, renegotiate. If it performs poorly on your past-RFP test or exports need heavy cleanup, test a switch before your notice deadline.
How long does it take to migrate an RFP answer library?
It depends on the size and state of the library. Export it, test an import into the new tool, and run one live project in parallel before cutting over.
See it live
Respond to RFPs
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
