Post many RFPs at once

Paste one JSON list and post an open RFP for every tool, up to 60 at a time. Each tool is also added to your stack. A tool that already has an open RFP from you is skipped, so pasting the same list twice is safe. To post one tool with the full feature checklist, use the single RFP form.

Sign in to post RFPs

Posting an RFP needs an account so sellers know who they are bidding to.

Format

A JSON array of objects. An object with an “rfps” array also works, and a markdown code fence around it is ignored.

vendor
Required. The product name, e.g. "HubSpot". Names match the directory the same way the stack paste box does.
annualSpend
Required. What the company pays per year, in USD. A number, or a string such as "$4,800".
features
Required, at least one. A feature name, or an object with name, importance ("must" or "nice") and evidence. Names that match the vendor's feature list link to it, so use the names on the vendor's page under /vendors where you can. Others are kept as custom features.
seats
Optional. A whole number.
renewalDate
Optional. YYYY-MM-DD.
plan
Optional. Saved as the note on the stack entry.
title
Optional. Defaults to "Replacing <vendor> for a <seats>-seat team".
description
Optional. Plain text.
anonymous
Optional. true hides the company name on the RFP.
[
  {
    "vendor": "Notion",
    "annualSpend": 9600,
    "seats": 40,
    "renewalDate": "2027-03-01",
    "plan": "Business plan",
    "features": [
      "Docs",
      "Wiki",
      {
        "name": "Databases",
        "importance": "must",
        "evidence": "212 active databases"
      }
    ]
  },
  {
    "vendor": "Zoom",
    "annualSpend": 2400,
    "seats": 15,
    "features": [
      "Meetings",
      {
        "name": "Webinars",
        "importance": "nice"
      }
    ]
  }
]

Report only figures and feature usage. Do not paste contract text or an invoice. Every RFP is public.