In short
In many SMEs, all procurement knowledge resides in one or two people. They know which winning themes work, where the best texts are, how the process runs and what the assessor wants to see. As long as that person is there, everything goes well. But as soon as he or she goes on holiday, gets sick or leaves, tender work comes to a standstill. That is an insidious risk: it is not noticeable until it goes wrong. You record that knowledge with four building blocks: a library with your best previous texts and the assessment, your winning themes per type of tender, your standard texts and company information, and a recorded process from search to submission. AI then makes that knowledge reusable and transferable, so that it is no longer stored in a head but in a system that the entire team can access.
This article shows why dependence on a key person is such a silent risk, how to capture the knowledge and process step by step, and how AI reduces that dependence.
Last year we spoke to more than 300 bid managers and procurement professionals. The quotes in this article come from those conversations, presented anonymously. It is what we hear in the market, also about ourselves.
The creeping risk: all knowledge in one head
In an SME, ask who does the tendering and you will often be given a name. One person. That person knows the customers, the winning themes, the pieces, the platform and the deadlines. That works until it doesn't work anymore.
The striking thing is that the people involved see it coming themselves. A director of a translation agency put it sharply: "It scares me that there is such a dependence on my knowledge. A good manager makes himself redundant." That's not false modesty. It is the realization that a company that runs on one head is vulnerable.
The risk is insidious because it does not present itself as long as things are going well. There is no warning light. Only when the key person is not there for a while does it become apparent how much was never recorded. A tender comes along with a tight deadline, and the only person who knows how to handle it is abroad for two weeks. Or someone drops out in the middle of a current registration and no one knows where the texts are or what the strategy was. Or the bid manager resigns, and years of knowledge leave with him: which texts won, which arguments appeal to which client, where the pitfalls lie. What remains is a folder with loose documents that the successor must try to reconstruct himself.
Moreover, it is not only a continuity risk, but also a brake on growth. As long as everything goes through one person, that person is the bottleneck. The company simply cannot move faster than that one head.
Why things go wrong here in SMEs
Large organizations often have a tender desk with several people and established procedures. In SMEs, writing tenders is usually an additional task, not a separate department: the entrepreneur does it himself, or one bid manager takes care of the entire process. This provides short lines of communication, but the knowledge becomes personal rather than company-related. And much of that knowledge is implicit. It is not on paper but is based on experience (this type of question is easily addressed, with this client price is more important), and that is difficult to convey in two weeks.The result is that every registration partly starts from scratch, not because it has to, but because the reuse is in someone's head instead of in a system. Many teams underestimate how much of their work is repeatable. A tender consultant: "We always think that all tenders are different, but for 50 or 60 percent there is really a part that you can reuse." That reusable part is exactly the knowledge you want to capture, so that not one person has to dig it up again and again.
What exactly you record: four building blocks
In practice, recording involves four concrete things. If you guarantee this, the dependency on one person immediately decreases.
| What you capture | Why it removes a risk | What it looks like |
|---|---|---|
| A library with your best texts | The quality is no longer in someone's memory, but can be found by everyone | Won tenders, per award criterion, including the assessment |
| Your win themes | The strategy that works becomes transferable instead of personal | Per type of tender: what sets us apart, what evidence is required |
| Standard texts and company information | Fixed components do not have to be re-thought each time | Quality policy, sustainability, certifications, cases, references |
| A defined process | A successor knows what the steps are, even without the key person | From searching and qualifying to writing, reviewing and submitting |
1. A library with your best texts
The core is a library: your best previous registrations, organized and findable. Not a folder full of loose Word files that only the writer can find, but a searchable collection that states what won and why.
The detail that most teams skip: record the assessment. A bid manager in construction explains why this matters: "If you want him to learn from old plans, you have to give him the assessment. Then he knows whether you have won or not." A text without a result is a guess, a text with the score is knowledge. Also read our guide to a text library for tenders that works.
2. Your winning themes
A winning theme is the point where you distinguish yourself and gain points. Experienced bid managers have these themes in their heads: for this type of assignment we focus on continuity, for that type on sustainability, with this proof. As long as that is only in one head, it will walk out the door as soon as the person does that. Therefore, determine for each type of tender which winning theme works, with what substantiation and which requirements must literally be included. In this way, the strategy that wins becomes a shared asset instead of personal intuition. More about this in how to increase your chances of winning tenders.
3. Standard texts and company informationPart of each registration is repeatable: quality policy, sustainability, certifications, company profile, cases and references. Record these properly once and keep them up to date. That saves time, and it ensures that everyone who registers starts from the same approved basis, not from the version that happened to be in someone's mailbox.
4. A defined process
The fourth building block is about working methods: how does a tender run from start to finish, with which steps and checks? A documented process ensures that a new colleague or substitute knows what to do, even without the key person next to him. How do we identify and qualify, how do we determine the strategy, how do we write, how do we review before submission, and what do we check when we press the button? That is precisely what turns a person-dependent approach into a repeatable method.
How AI reduces dependency
A library and a defined process help even without technology. But a filled folder with old registrations is not yet transferable knowledge: someone still needs to know which text is relevant, where the right passage is and how to adapt it to the new question. And there you again lean on someone's experience.
AI changes the situation on that point. Not by replacing people, but by making the recorded knowledge actively reusable and transferable. Three things make the difference.
The knowledge becomes discoverable instead of hidden. With a new tender, no one needs to know in which old document that strong passage about continuity was contained. An AI trained on your library will retrieve the relevant previous texts and arguments itself. The knowledge comes to the user, even if he or she is new and does not know the history by heart.
The writing style becomes transferable. One of the most difficult things to transfer is a company's own voice. A tender writer describes this style very precisely: "We write to your employees instead of employees, and we adhere very strictly to what is stated here." Those kinds of details are normally in the head of the regular writer. An AI that learns from your written history takes over that voice, so that a new colleague also writes texts that sound like your company, and not just a bit too Jip-en-Janneke.
The process is built in instead of remembered. Once the steps, the winning themes and the review are in the tool, the method no longer needs to be in someone's head. The tool focuses on the award criteria, enforces evidence instead of promises, and scores the text for submission. What used to be the key person's experience becomes a step that everyone follows. You can read more about that review step in review and score tender or quotation with AI before submission.
The net effect: knowledge moves from a head to a system. This does not make the experienced bid manager redundant, his work actually becomes more valuable, because his knowledge now scales up to the entire team instead of evaporating when he is not there. And that is exactly what the director of the translation agency meant: a good manager makes the organization less dependent on itself.
An honest side note
Capturing doesn't solve everything, and it costs something. A few fair points.The knowledge has to be there. An AI that learns from your history is only as good as the library you feed. If you start with an empty library, little will come of it in the beginning. Putting in the first texts and assessments takes one-off work, but then it pays off with every subsequent tender.
And you never fully capture the tacit knowledge. Part of what an experienced bid manager knows is that feelings are difficult to translate into rules. The goal is not to replace that person, but to reduce the dependency: from one hundred percent on one head to a shared basis that carries the team, with the experienced person as director instead of as the sole executor.
Finally, the human remains the final editor. Captured knowledge and AI bring you to a strong version faster and with fewer hands. But the responsibility for what you submit, and the judgment as to whether the content is correct, remains human work.
A practical starting point
You don't have to capture everything at once. Start small and build it up.
- Collect your five best registrations from the past year, preferably with the assessment included. This is the core of your library.
- Write down your top three winning themes for the types of procurement you do most often, with supporting evidence.
- Put your standard texts in one place: quality policy, sustainability, certifications, cases. Good once, then maintained.
- Describe your process in half an A4: from signaling to submitting, with the steps and checks. Enough that a new colleague can follow it.
- Choose a place where this meets and is searchable by the team, not a private folder. Software that learns from your own history turns that recorded knowledge into a working, reusable basis.
With these five steps you have extracted the most important knowledge from one mind and put it into a shared basis. Not perfect, but a lot less vulnerable.
Frequently asked questions
Why is dependence on one tender employee a risk? Because all the knowledge (win themes, the best texts, the process, the contacts) is in one head. In the event of vacation, illness or departure, tender work comes to a standstill, or a successor has to reconstruct everything. It is an insidious risk: it is not noticeable as long as things are going well. A director of a translation agency put it this way: "It scares me that there is such a dependence on my knowledge. A good manager makes himself redundant." And it slows down growth, because the company can't move faster than that one person.
How do you capture procurement knowledge? With four building blocks: a library with your best previous texts (including the assessment), your winning themes per type of tender, your standard texts and company information, and a recorded process from search to submission. Start small: collect your five best entries, write down your three most important winning themes, put your standard texts in one place and describe your process in half an A4. If you want to see how an AI platform does this, read what is bid management software and tender writing with AI.How does AI help you become less dependent on one person? AI makes recorded knowledge reusable and transferable. An AI that learns at your library will retrieve the relevant previous texts, adopt your writing style so that a new colleague also writes in your voice, and build the process and the review instead of someone having to remember it. The knowledge moves from one head to a system that the entire team can access. The experienced bid manager remains the director and editor-in-chief.
Do I have to commit my entire archive for it to work? No, you start with your best lyrics and build on it. However, an AI that learns from your history is only as good as the library you feed it. An empty library yields less in the beginning. Putting in the first texts and reviews takes one-off work and then pays off with every tender.
Does this make my experienced bid manager redundant? No, it makes his work more valuable. His knowledge scales up to the entire team instead of evaporating when he is not there. He becomes director and editor instead of the only one who can do it. The goal is not to replace, but to reduce dependency: from everything on one head to a shared basis that carries the team.
Conclusion: from person-dependent to transferable
In many SMEs, procurement work is run by one or two people. That works until someone goes on holiday, gets sick or leaves. Only then will it become clear how much knowledge was not recorded anywhere. The risk is insidious, because it only shows itself when it is too late.
The solution is not an act of heroism but a habit: record what is repeatable. A library with your best texts and the assessment, your winning themes, your standard texts and a defined process. AI then makes that knowledge findable, your writing style transferable and your process repeatable, so that it is in a system and not in a head.
This is how TenderRender works: an AI bid management platform that learns from your previous winning bids, writes in your writing style, and scores and reviews your text against the award criteria before you submit. It makes your team's knowledge reusable and transferable, so that your registrations no longer depend on one person. The security is in order: ISO 27001 certified, GDPR compliant, and TenderRender does not train on your data. Made for teams that write themselves and win on quality, from SMEs without their own tender desk to bid teams within larger organizations.
