Answer a tender with the first draft written from what you have already said
A tender lands with ninety questions. The first draft is built from your past answers, your case studies and your policies, with the gaps marked, so your team edits instead of starting blank.
A tender is a long questionnaire with a deadline. Most of the questions have been answered before, in a different order, in a document someone wrote two years ago. Finding those answers, checking they are still true and adapting them takes a small team the best part of two weeks, and the questions nobody has answered before are found last, when there is least time.
Plugs into
These are examples. Every use case is built around the tools you already run, whatever they are, and you keep using them exactly as before.
Then it runs on its own
- 1
Breaks the tender down into every question and requirement, with the reference numbers
- 2
Finds the closest answer you have given before, and the case study or policy that backs it
- 3
Drafts an answer to each question in your voice, rewritten for this client
- 4
Marks the questions with no past answer and the claims that need checking
Delivered where you already work
When a tender lands, and again whenever a new version of the questions arrives, in whichever channel your team already uses. We set the timing around how you work, not the other way round.
What you get back
- A first draft of the whole response, question by question
- A list of what still needs writing from scratch, so the team starts there
- Every claim with the source it came from, so nothing is said that is no longer true
What it actually looks like
An example of the output, using sample data.
Tender draft · Port authority, customs software
- Q12, data hosting: from the 2024 municipal tender, updated to the new data centre.
- Q31, support hours: from your service description, matches the current contract with Meridian Shipping.
- Q47 asks for a Greek-speaking on-site engineer in Piraeus. No past answer covers it.
- Q52 asks for ISO 27001. The certificate on file expired in June.
- Nine answers quote a team size of 45. Your HR system shows 52.
Your team spends the two weeks on the answers that win, not the ones that repeat
We build it with your team
Every workshop is built around the use cases you pick. This one is usually covered in the Accelerator, on your own tools and your own data.
- We work on a tender you are actually answering, or the last one you lost
- Your team builds the library of past answers as part of the session
- You leave with a draft and with the setup that made it
Want it extended, maintained and connected to more of your systems afterwards? Let's discuss →
Want this running in your team?
30 minutes. Tell us what your team spends its week on and we'll tell you which of these would save the most time.