Skip to main content

Step-by-step

Emerging Technologies RFQ: Resources for Pool Vendors

Emerging Technologies

The Emerging Technologies Request for Qualifications (RFQ) pool is a two-year pilot of a new "try before you buy" framework. If you are already in the pool, use these resources to navigate the process.

Not in the pool yet? Learn how to join on our Emerging Technologies RFQ page.

Find the full Vendor guide here:

ET RFQ Vendor Guide

1

Keep your information up to date

To update your contact information, email EmergingTechRFQ@sfgov.org.

To update your products, capabilities, features, integrations, or other details, submit a new Response Form.

2

Receive and Respond to Mini-RFPs

Once you are in the pool, City departments will send you mini-RFPs via email. Each mini-RFP includes:

  • a problem statement and the outcomes the department wants
  • constraints, including available data, timeline, and budget (up to $230,000 over 12 months)
  • the criteria the department will use to choose a vendor
  • instructions for submitting a proposal

Mini-RFPs are real use cases. Respond only if your solution is a genuine fit.

3

Sign a Short-Form Contract

A department may select you based on your response. If it does, you will sign a short-form contract before work begins. Review the key terms before you reach this step.

4

Run a Pilot

After you sign the contract, you will work with the department to run a pilot using synthetic or public data. Pilots run in a sandbox and do not touch City production systems.

Each pilot has three parts:

  • Discovery and prototyping: You refine requirements and build a working prototype to validate the approach early.
  • Iterative development: You build the solution in increments, or sprints, delivering working functionality and updating requirements and design as you go. The department reviews each increment against acceptance criteria and performance benchmarks.
  • Validation and testing: You and the City test the solution for accuracy, fairness, security, and robustness.
5

Handoff

After the pilot ends, the department will assess:

  • Did the solution work as intended, and will it meet the department's needs?
  • Were risks such as bias, privacy, accessibility, and security managed well?
  • Can you meet the full technical and contract requirements for a long-term contract and production deployment?
6

Next steps

There are two possible outcomes.

Scale to a long-form contract. The department exercises its option to move to a long-form contract amendment.

Stop. The pilot ends. You keep your proprietary technology, and the City owns all deliverables produced under the contract. You stay in the pool and remain eligible for future mini-RFPs.