For bid managers
Nine people, one deadline, forty pages of requirements
SecondBrain 365 is an AI agent inside your Microsoft 365: it reads the bid pack, pulls the dates out of it, and does the chasing on Teams. You spend the time on the answer instead of on assembling it.
See how SecondBrain 365 supports bid teams, from the tender pack to the answers you wrote last year.
Most of a bid is not writing. It is collecting.
Nine people who each have another job, one set of dates buried in the tender pack, and the certainty that your company has already answered most of these questions before — somewhere.
9
contributors on an average RFP response — a number that has not moved in four years.
Loopio RFP Trends 2025 — n=1,544, with APMP
48%
name collaborating with subject-matter experts as their top challenge. It has been first for five years running; finding accurate, up-to-date answers is second at 39%.
Loopio, same study
41.8%
of EU public tenders received a single bid in 2021, up from 23.5% in 2011. Average bidders per procedure fell from 5.7 to 3.2.
European Court of Auditors, Special Report 28/2023
The last figure is a census of every above-threshold EU procedure, not a survey. Competition is thinning — which is an argument for bidding more often, if bidding did not cost what it costs.
The dates
It reads page 40 so you do not have to
Put the tender documents in the workspace and the agent pulls out every date — because your context file says that is what to look for. Then it does the follow-up itself.
Nobody transcribed the tender
The clarification window, the site visit, the submission time to the minute: they came out of the documents, not out of somebody's afternoon with a highlighter.
It chases the contributors
Nine people, each with a day job and none of them reporting to you. The agent asks them about their sections, and what comes back lands in the bid file.
Silence is visible
On a bid, the section nobody has answered is the one that sinks the submission at six in the evening. You see it while there is still time.
Dates in this tender
Pulled out of the bid pack, because the context file says to.
- Clarification questions to the authoritydoneAnna· due Thu 18 SepWhat the agent did“The clarification window closes today — anything still to send?”Anna: “Sent two questions this morning.”Recorded, with the questions attached to the bid file.
- Technical section — security architecturedate movedMarco· due Mon 22 SepWhat the agent did“The technical section was due yesterday — is it on track?”Marco: “Need two more days, waiting on the datacentre certificate.”Flagged: the new date leaves three days before submission, not five.
- Signed declarations from the consortium partnerno answer yetSara· due Wed 24 SepWhat the agent did“The partner declarations are due tomorrow — do we have them?”No answer yet. On a bid, this is the one worth a phone call.
The dates came out of the tender documents, the reminders went out on their own, and the one nobody answered is visible two days before it matters.
The answers you already wrote
Your company has answered this before
The security questionnaire, the ISO certificates, the three references, the methodology section. All written, all approved, all somewhere — in a submission from last March that only one person can find.
Regional framework 2025 — technical response
Submitted 14 Mar · won
3.2 Data residency — all processing takes place in EU datacentres,
with no transfer outside the EEA at any stage.
3.4 Continuity — recovery point objective of four hours,
tested twice a year with a documented restore.
5.1 Team — three named architects, CVs in annex B.
Pick a record to see where it came from.
Every answer keeps the submission it came from and its date — so you can see at a glance whether it still describes the company you are today.
The date is the useful part
A reusable answer with no date is a liability: certifications lapse and teams change. One that says “March 2025, from the framework we won” can be judged in a second.
Not saving time — moving it
Teams with the best win rates spend more hours per bid, not fewer. The point is not to answer faster: it is to spend those hours on the answer rather than on finding out what you said last time.
And it tells you when two answers disagree
Two submissions describing the same capability differently is the kind of thing an evaluator notices and you do not.
What goes in, what comes out
The bid pack and the conversations around it. Nothing to re-key, and nothing for the contributors to learn.
In
- The tender documents, as the authority published them
- The clarifications and their answers
- The Teams channel where the bid gets built
- Past submissions, won and lost
Out
- Every date, with who owns the section
- Reminders that go out without you sending them
- A library of past answers, dated and sourced
- The requirements, as a list you can tick
- Alerts when two answers describe the same thing differently
And after this bid
The next one starts further along
Every answer written for this tender is already in the library for the next, with the date it was true.
It survives the bid manager
Bid knowledge is famously concentrated in one or two people. This is the part of it that can be written down.
The delivery team inherits it
What you promised, and when you promised it — available to the people who now have to deliver it.
FAQ
Questions bid managers ask
No. It assembles: the dates, the requirements as a checklist, and the answers your company has already given, each with its date and the submission it came from. The response is written by the people who know the work — what changes is that they start from what exists instead of from a blank page and a search through last year's folders.
Treat it as a very well-organised colleague, not as a compliance system. It reads the documents you give it and flags what it finds, but the submission is yours: what goes in, what the answer says and what gets signed stays a human decision. On a public procedure you would check the pack against the authority's own documents anyway — this makes that check faster, it does not replace it.
Every answer carries the date and the submission it came from, precisely so you can judge it — a certificate from 2023 announces itself. And when two submissions describe the same capability differently, the agent flags the pair rather than picking one, which is how a stale answer gets noticed instead of quietly resubmitted.
They do not have to use anything. The agent asks them on Teams about the section they own, and their reply is the contribution — no portal, no login, no training. Nine contributors is the average on an RFP, and none of them reporting to the bid manager is the normal condition, not the exception.
In your own Microsoft 365 tenant: a SharePoint site under the bid's Teams group. Nothing is copied to a third-party platform, which matters here because a bid file contains pricing and commercial terms. Your existing permissions apply, and you can restrict the workspace to the bid team only.
Need it for something else?
Same agent, same mechanism. What changes is the rules you write in the context file.
Project management
Stop chasing people for updates: the agent asks, and the plan stays current
Product management
Why the product is the way it is — written down while you decide it
HR
The answer your team already wrote, found by the next person who asks
IT service desk
Forward the reply you just sent. That is the whole documentation step
ISO audit
Evidence recorded as it happens, not reconstructed the month before
Onboarding & offboarding
What leaves with a person becomes smaller — and it is honest about the rest