The Bilingual Tender Qualifier
Screen Arabic and English tenders fast to decide which are worth a full bid
You waste days preparing responses for tenders you should never have chased. Documents arrive in Arabic, English, or both, and key eligibility criteria hide in different sections across languages.
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
Business development teams in the UAE who receive tenders in both Arabic and English
How it works
The skill file does five things, in this order.
1. Feed both language versions. Upload Arabic and English tender documents together so the model cross-references requirements that appear in only one version.
2. Extract the gate criteria. Ask for mandatory requirements, financial thresholds, and pre-qualification terms in a single list, noting which language specified each.
3. Check your company profile. Paste your standard capabilities statement and registration details, then ask for a go or no-go recommendation with reasons.
4. Flag translation discrepancies. Request a list of any material differences between Arabic and English versions that could affect compliance or scoring.
5. Build a decision log. Save the output as a dated record so your team learns which tender types to pursue or avoid over time.
What comes back
A structured brief in under five minutes showing whether you meet hard requirements and where language versions conflict
The mistake to avoid
Arabic tender documents often add cultural or local preference clauses not present in English versions. If the model summarizes only one language, you miss criteria that disqualify you or boost your score.
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 a tender qualification assistant for a company operating in the UAE.
I will provide tender documents in Arabic, English, or both languages. Your task is to:
1. Extract all mandatory eligibility requirements, including:
- Minimum years of operation
- Financial turnover thresholds
- Required licenses and certifications
- Geographic or nationality preferences
- Prequalification criteria
2. Note which language version each requirement appears in (Arabic only, English only, or both).
3. Compare the Arabic and English versions and flag any material discrepancies in:
- Scope of work
- Eligibility criteria
- Evaluation weightings
- Submission deadlines or formats
4. After I provide my company profile with {registration_details}, {years_in_business}, {annual_revenue}, {certifications}, and {past_project_examples}, give a clear go or no-go recommendation with specific reasons.
5. Highlight any requirements where we are borderline or where interpretation differs between languages.
6. If cultural or local preference clauses appear in only one language version, flag them prominently.
Present your analysis in a structured format with sections for mandatory criteria, language discrepancies, and final recommendation. Be direct about disqualifying factors.
Tender documents:
{tender_files}
Company profile:
{company_profile}