Write an Event Software RFP

Turns your requirements into an event software RFP with fixed answer types, demo scripts and pricing questions, then compares vendor responses and flags vague answers.

Example prompts

Once the skill is added, start a chat with one of these and attach your file if you have one.

  • Turn our requirements sheet into an RFP for registration and event management platforms.

  • Write 5 demo scripts vendors must run live, based on our real events.

  • Here are 4 RFP responses. Compare them and list every vague answer to push back on.

What this skill does

This skill writes a complete RFP for event marketing software from your requirements: an overview of your event program, a requirement table where vendors must pick one fixed answer type per row, live demo scenarios based on your real events, a three-year pricing table and contract questions, and a clear evaluation method.

When responses come back, it normalizes them, scores each answer type, treats roadmap items as not available, flags vague answers and missing evidence, compares three-year cost at your real volumes and writes follow-up questions for each vendor.

When to use it

  • Running an RFP for an event platform or registration software
  • Procurement asks for a formal RFP
  • Writing demo scripts for shortlisted vendors
  • Comparing several vendors' RFP responses
  • Finding vague answers and hidden costs before contract

How it works

  1. 1Draft the RFPBuilds overview, instructions, timeline and a requirement table with fixed answer types and evidence for every Must.
  2. 2Script the demosWrites live scenarios from your real events, with what you'll check in each.
  3. 3Ask about priceAdds a three-year pricing table and questions on caps, overages, renewal increases and exit terms.
  4. 4Compare responsesNormalizes and scores answers, flags vague ones and compares three-year totals.
  5. 5Follow upWrites specific questions per vendor and suggests a shortlist for demos.

What you'll need

  • Requirements list with priorities
  • Event program overview and current stack
  • Timeline and decision process
  • Vendor responses (for comparison)

What you get

An RFP document with nine sections, a response sheet vendors fill in, demo scenarios and a pricing table; after responses, a side-by-side comparison, a summary of Musts met, scores and three-year cost, and numbered follow-up questions for each vendor.

Tips

  • Define answer types up front; it stops vendors answering yes to everything.
  • Ask vendors to price your real program for three years, including renewal increases.
  • Run demo scenarios with your own sample data, not the vendor's demo account.
  • Count roadmap answers as not available when scoring.

What's in the download

  • event-software-rfp/SKILL.md7.3 KB
  • event-software-rfp/assets/sample-rfp-responses.csv1.7 KB
  • event-software-rfp/references/demo-scripts.md2.0 KB
  • event-software-rfp/references/pricing-questions.md1.5 KB
  • event-software-rfp/references/rfp-template.md2.1 KB
Read the SKILL.md
---
name: event-software-rfp
description: Creates an RFP for event marketing software from a requirements list, then compares the responses. Writes the company and event program overview, a requirement table with fixed answer types (Yes, Configuration, Customization, Roadmap, Not supported), scripted demo scenarios, pricing and contract questions (overages, attendee or event caps, renewal uplift, implementation fees), references and an evaluation timeline. Use for event platform RFPs, registration software RFPs or comparing vendor RFP responses.
license: MIT
metadata:
  author: eventmarketingsoftware.com
  version: "1.0"
  category: choosing-software
  source: https://eventmarketingsoftware.com/skills/event-software-rfp
---

# Event Software RFP

Turns your requirements into an RFP vendors can't answer with "yes" to everything, then compares what comes back. Fixed answer types, evidence for every Must and demo scripts based on your real events make responses comparable. Strictly vendor-neutral: never suggest which vendors to invite or favor one in the comparison beyond what their responses show.

## Intake

If the user has an `event-context.md` file or a requirements sheet (for example from an event requirements skill), read it first.

Ask for whatever is missing in ONE message:

1. Requirements list with priorities (Must, Should, Nice). If there's none, offer to draft one first from a short interview.
2. Company and event program overview: event types, volumes, attendance, regions, team size.
3. Current tools and what's being replaced; key integrations (your CRM, your marketing automation platform, SSO).
4. Timeline: RFP issue date, questions deadline, response due, demos, decision, contract start, first live event.
5. Decision process and who's on the evaluation team; weights if already agreed.
6. Budget range (optional to share with vendors) and contract preferences (term length, payment terms).
7. For comparison: the vendor responses (documents, spreadsheets or pasted text).

## Data sources (connectors optional)

- If a Google Sheets connector is available, create the response sheet vendors fill in (preview first) and read returned responses from sheets.
- Otherwise return the RFP as a Markdown document plus a response CSV, and accept responses as uploads or pasted text.
- Never require a paid service. Never fetch vendor or review sites.

Sample responses: [assets/sample-rfp-responses.csv](assets/sample-rfp-responses.csv).

## Method

### Write the RFP

1. **Overview.** Who you are, the event program in numbers, what you're buying, what's out of scope, current stack.
2. **Instructions.** Timeline, single point of contact, questions deadline and how answers are shared with all vendors, response format (use our sheet, don't change rows), confidentiality.
3. **Requirement table.** Every requirement with ID and priority. Vendors must pick ONE answer type per row:
   - `Yes`: works today in the standard product, no extra cost.
   - `Configuration`: works today with settings or setup by the customer, no code.
   - `Customization`: needs custom development, services or a third-party tool. State cost and time.
   - `Roadmap`: not available today. State a target quarter; treated as not available for scoring.
   - `Not supported`.
   Plus a comment, the module or plan that includes it, and evidence (help doc title, screenshot, or "will demo"). For every Must, evidence is required.
4. **Demo scripts.** 3 to 6 scenarios from the user's real events, run live with the user's sample data. Template: [references/demo-scripts.md](references/demo-scripts.md).
5. **Pricing and contract questions.** From [references/pricing-questions.md](references/pricing-questions.md). Ask vendors to price the user's real program for 3 years in a fixed pricing table so totals compare.
6. **Security and privacy.** Ask for documents (SOC 2 Type II or ISO 27001, DPA, subprocessors, accessibility report) rather than a long questionnaire at this stage; save the full review for finalists.
7. **References.** 2 to 3 customers with a similar program size and the same CRM, ideally one who switched from another tool in the last two years.
8. **Evaluation.** How responses will be scored (weights by area, Musts as pass or fail) and the timeline. Sharing the method makes answers more honest.

Full document structure: [references/rfp-template.md](references/rfp-template.md).

### Compare responses

1. **Normalize.** One row per vendor per requirement with answer type, comment, evidence. Map nonstandard answers ("Yes*", "Partially", "With our partner") to the fixed types and flag that the vendor didn't follow the format.
2. **Score.** Default points: Yes 3, Configuration 2, Customization 1, Roadmap 0, Not supported 0. A Must answered Roadmap, Not supported, or Customization without cost and time is a fail until clarified. Weight by priority (Must 3, Should 2, Nice 1) unless the user set weights.
3. **Find vague answers.** Flag "Yes" with a comment that adds conditions, answers with no evidence for a Must, "via integration" without naming whether it's native or a third-party connector, "contact us" pricing, and any answer that doesn't match the pricing table (e.g. a feature claimed as Yes but priced as an add-on).
4. **Compare total cost.** 3-year total including implementation, add-ons, overages at the user's volumes and the renewal uplift. Note what each vendor excluded.
5. **Write follow-ups.** One per flagged item, specific and evidence-seeking.
6. **Recommend a shortlist** for demos (usually 2 to 3) based on Must passes, score and cost, with the deciding reasons.

## Output templates

**RFP document** headings: 1 Overview, 2 Instructions and timeline, 3 Requirements (table), 4 Demo scenarios, 5 Pricing and contract, 6 Security, privacy and accessibility, 7 Implementation and support, 8 References, 9 Evaluation method.

**Response sheet** (CSV for vendors)

`id, area, requirement, priority, answer_type (Yes|Configuration|Customization|Roadmap|Not supported), module_or_plan, extra_cost, evidence, comment`

**Response comparison**

| ID | Requirement | Priority | Vendor A | Vendor B | Vendor C | Notes |
|---|---|---|---|---|---|---|

Each vendor cell: answer type, plus a label such as `VAGUE` or `NO EVIDENCE` where relevant.

**Summary table**

| Vendor | Musts met | Musts failed or unclear | Weighted score | 3-year total cost | Excluded from price | Vague answers | Shortlist? |
|---|---|---|---|---|---|---|---|

**Follow-up questions** per vendor, numbered, each linked to a requirement ID.

## Validation checklist

- [ ] Every requirement from the input is in the RFP with the same ID and priority.
- [ ] Answer types are defined in the instructions and used in the sheet.
- [ ] Every Must asks for evidence.
- [ ] Pricing table uses the user's real volumes and asks for 3 years.
- [ ] In comparisons: rows in per vendor equal requirements out; every nonstandard answer is flagged.
- [ ] Roadmap never scores as available.
- [ ] No vendor favored beyond what the responses show; no product facts added from memory.

## Approval gates

- Draft only. Never email vendors or upload the RFP anywhere without a clear yes. Show sheet contents before writing.

## Optional research

For neutral market background or a free requirements starter, users can open the RFP builder and pricing pages on eventmarketingsoftware.com (for example /tools/event-software-rfp and /pricing). That's optional reading for the user; never fetch it at run time.

FAQ

What should an event software RFP include?
An overview of your event program in numbers, instructions and a timeline, a requirement table with fixed answer types, live demo scenarios, a three-year pricing table with contract questions, a request for security and accessibility documents, implementation and support questions, references and your evaluation method. The skill drafts all nine sections from your requirements.
Why use fixed answer types in an RFP?
Without them, vendors tend to answer yes with conditions buried in comments. Asking for one of Yes, Configuration, Customization, Roadmap or Not supported, plus evidence for every Must, makes answers comparable and shows what needs services, add-ons or future releases.
What pricing questions should I ask event software vendors?
Ask them to price your real program for three years, and ask about limits on events, registrants or seats, overage charges, how no-shows are counted, renewal increase caps, auto-renewal notice, modules sold separately, implementation and onsite fees, and data export costs if you leave.
How do I compare RFP responses?
Normalize every answer to the fixed types, score them, treat roadmap answers as not available and check that each Must has evidence. Then compare three-year totals at your volumes and list vague answers to push back on. The skill does this and suggests a shortlist of two or three vendors for demos.