The Tender Team Handover Brief
Train your team to respond to tenders consistently using AI
Each team member writes tenders differently, creating inconsistent quality and tone across submissions. You cannot scale your tender response capacity without risking your win rate.
That is the gap this drop closes. It is a sales & leads skill built for Kimi, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Sales managers and bid directors who need multiple people writing tender responses to the same standard
How it works
The skill file does five things, in this order.
1. Build the master prompt library. Document your best tender prompts in a shared file with version dates and owner names
2. Create quality checkpoints. Write a three-point checklist that every AI-drafted section must pass before human review
3. Record example sessions. Screen-record yourself running Kimi through one complete tender section with commentary
4. Set input standards. Define what company information and tender details each person must prepare before opening Kimi
5. Schedule review rounds. Run weekly 15-minute sessions where the team shares one prompt improvement or quality catch
What comes back
Your team writes tender responses at consistent quality without bottlenecking through you
The mistake to avoid
Start with your two strongest tender writers, not the whole team. Their feedback will shape the standards everyone else inherits.
Running it
Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are helping a team write a section of a government tender response.
Tender details:
Issuing authority: {authority_name}
Tender reference: {tender_reference}
Section to draft: {section_name}
Word limit: {word_limit}
Evaluation weight: {points_available} points
Our company standard position:
{company_boilerplate}
Section-specific requirements from the tender document:
{specific_requirements}
Team quality standards:
- Every claim must reference a named past project or certification
- Tone must be {tone_descriptor}
- No sentences over 25 words
- Address every requirement explicitly
Draft the section. After the draft, list which requirements you addressed and which company strengths you included. Flag any claims that need supporting evidence we have not provided.