A forty-page questionnaire for bread rolls
A contract caterer that runs several school kitchens wants a bread supplier. The questionnaire arrives as a Word document and a spreadsheet: company details, delivery areas and times, product list with specifications and prices, certificates, insurance, policies on sustainability and modern slavery, references, and a section on how you would handle a missed delivery.
The owner fills it in at the kitchen table over several evenings, copying answers from the last one, which was for a care home group and had a different layout. Half the documents are in an email from two years ago.
Why every tender feels like the first
Each buyer writes their own questionnaire, so the questions are similar but never identical. A small bakery has no bid team, and past answers are scattered in old documents. The work is repeated each time, by the one person who knows the answers.
- Past answers sit in old documents and sent emails.
- Certificates and insurance documents are hard to find.
- Product lists and prices are rebuilt for each tender.
- Deadlines arrive while the owner is working nights.
- Nobody records which tenders were won and why.
What the effort costs
Evenings and weekends of the owner's time, often in the same week as a bank holiday or a busy season, because buyers set their deadlines to suit their own calendar. Tenders not entered because there was no time. Answers that contradict earlier ones. And good contracts, which can bring steady volume on quiet weekday nights, going to larger bakeries that answer faster.
Whether to bid, what to promise and what your policies say are your decisions, and legal or insurance questions are for your advisers. We make the paperwork quicker.
The tender library we build
- Your approved answers to common questions are collected once into a library, grouped by topic: company, delivery, products, quality, policies, references.
- Certificates, insurance documents and policies are stored with expiry dates, and you are reminded before any expire.
- Product lists with the specification details and prices the buyer asks for are generated from your product records.
- When a new questionnaire arrives, an AI step using a model such as Anthropic Claude or OpenAI matches each question to library answers and drafts a response in the buyer's format, marking questions it could not answer.
- You review every answer, edit what needs changing and fill the gaps. New answers are saved back to the library for next time.
- Each tender is recorded with its deadline, what was submitted and the outcome, so the next bid can learn from it.
| Tender section | Filled from |
|---|---|
| Company and delivery details | Approved library answers |
| Product list and prices | Product records and price list |
| Certificates and insurance | Document store with expiry dates |
| Policies | Your approved policy documents |
| New or unusual questions | Marked for you to answer |
A bid that takes an evening, not a week
You start each tender from a draft that already holds most answers, and spend your time on the questions that are genuinely new. Documents are current and to hand. Deadlines are visible. And over time, the library gets better with every bid.
It also makes it realistic to bid for work you would previously have passed over, such as a school kitchen contract that would fill the quieter weekday nights.
Because every submission is kept, a buyer's clarification question weeks later can be answered from what you actually sent, not from memory.
Is this how tenders feel?
- Tender questionnaires take several evenings.
- Past answers are copied from old documents.
- Certificates and insurance papers are hard to find.
- You have skipped tenders for lack of time.
- You do not know why past tenders were won or lost.