Home/Mindbreeze/Use cases/RFP Question Answering
Use cases · Tenders and RFPsRFP Question Answering: tender questions pre-answered from what you already wrote
Every tender asks the same hundred questions in a slightly different way. RFP Question Answering drafts answers from approved earlier answers and product documentation, so the bid team reviews instead of rewrites.
Discuss this use case All use cases
Illustrative example
In short
RFP Question Answering is a Mindbreeze agent that drafts answers to the questions in RFPs, tenders and security questionnaires. It draws on approved answers from earlier bids, product and service documentation and policies, links every draft to its sources and flags where information may be outdated. The bid team reviews, adjusts and approves every answer. SoftAdvice connects it to the systems where your bid material lives and sets it up with your bid team.
Good answers exist; they are in last year’s bid
Bid teams work against a deadline and depend on experts who have other jobs. Much of each questionnaire was answered before, but finding the best approved answer, checking that it is still true and adapting it takes most of the time.
- Approved answers from earlier bids
- Product and service documentation
- Security and privacy policies
- Certificates and references you may cite
From questionnaire to reviewed answers
The agent drafts; the bid team owns every answer that leaves the company.
Load the questions
The bid team adds the questions from the RFP or questionnaire.
Draft answers
RFP Question Answering drafts each answer from approved material and links the sources.
Expert review
Flagged answers go to the right expert; the others are checked by the bid team.
Approve and reuse
Approved answers are stored with the bid, so the next tender starts from them.
A person decides, the sources stay visible
The agent prepares; a person checks and decides. Every answer links to the documents it used, so anyone can see later what it was based on.
Mindbreeze applies the permissions of each source system: what someone cannot open in the source, they do not see in the answer. If access in a source is too broad today, that is fixed in the source; we check it before the start.
- Answers support, people decide
- Permissions of each source respected
- Sources linked in every answer
- Access checked before the start
What we measure on a first use case
We agree the baseline with your team before the start, so the result is measured on your own questions.
Time per questionnaire
Hours spent on a comparable questionnaire, before and after.
Drafts accepted
How many drafts the bid team accepts with little or no change.
Expert time
How much time subject experts still spend on standard questions.
Permission tests
Test users confirm that nobody sees what they may not open.
What this use case needs, and what it does not do
Drafts are only as good as the approved material. Before the start we agree which earlier answers and documents count as approved, who reviews which topics and how outdated content is handled. No answer is sent without review by the bid team.
These pages describe how a Mindbreeze agent can be set up for this task. They are not customer references: we describe them without names or figures, and the example answers are illustrative.
- Approved answer library agreed
- Reviewer per topic
- Nothing sent without review
- Outdated content flagged
Questions about this use case
What is RFP Question Answering?
RFP Question Answering is one of the pre-built agentic use cases (Insight Touchpoints) in Mindbreeze Insight Workplace. SoftAdvice connects it to your sources, sets it up for your rules and team, and measures the result with you.
Can it also answer security questionnaires?
Yes, in the same way: drafts from your approved security documentation, reviewed by the person responsible for security before they are sent.
Do we need to move our documents?
No. The documents stay in the systems where they are today. Mindbreeze connects to them; which systems can be connected is confirmed per system before the start.
How do we start?
With a conversation about one use case: the team, the typical questions and the systems involved. From there we propose a scoped first step.
Would this help your team?
Tell us about the team, the questions and the systems involved. We come back with a proposal for a scoped first step.