Funding ask
Ufakazi began as a hackathon project, but its findings have real-world consequences. It would be irresponsible to leave our work at a hackathon. We have since made contact with researchers and policy advisors in South Africa, who have offered to assist with disseminating the work through the appropriate channels. For that work to be taken seriously, it needs to be polished and published in a reputable journal. Any funding we receive goes towards the extensions that help us get there. We group these extensions by necessity.
The first extension is one we believe necessary for the work to be publishable. We need to increase the repetitions per experiment from five to ten and grow the scenario set from 20 to 40. The headline findings are already statistically significant and we expect them to hold, but we would like to tighten the confidence intervals to pre-empt fair questions from reviewers.
Three further extensions would be valuable, but not necessary. Adding frontier models (Claude Fable 5.1, GPT-6 Astra, Gemini 3.1 Pro and Qwen 3.8 Max) shows whether our findings hold for the most advanced models. Acquiring native translations for isiXhosa and isiZulu removes any remaining doubt that translation fidelity could be the true explanation. Finally, varying the language of the system prompt tests whether the bias shifts to align with the language of the instructions. Each of these extensions addresses a question that could reasonably be raised in review.
The final two extensions are nice-to-have. One investigates whether commonly used legal AI products (such as Harvey and Legora) are similarly susceptible to language bias. Their domain-specific harnesses could change language sensitivity, but they are not directly comparable and are harder to access. Adding very low-resource African languages such as isiNdebele and Tshivenda would also show how language prevalence shapes model bias.
All budget line items are assuming that we extend the scenario set to 40 scenarios.
Contingency buffers account for any testing, bugs or unforeseen expenses.
Necessary extensions:
- Added token usage for statistical hardening (extending scenario set and increasing repetitions): $134.83
- 20% contingency buffer: $26.97
Valuable extensions:
- Added token usage for adding frontier models: $378.96
- Added token usage for native translations: $375.26
- Paying for native translators: ~$180
- Added token usage for varying system prompt language: $2716.92
- 20% contingency buffer: $721.19
Nice-to-have extensions:
- Token usage for two more low-resource languages: $757.77
- Paying for native translators for the two additional languages: ~$180.00
- 20% contingency buffer: $151.554
Private comment. Only shown to approved funders and grant reviewers.