The Code in Our Name
The history, ideas, and ambition behind Nubian Code—and our belief in the best AI for the most people.
Was this newsletter forwarded to you? to get it in your inbox.
Nubian Code takes its name from a story about the value of knowledge that others overlook.
Accounts of the 1973 October War describe Nubian speakers using their language to carry military messages. The idea is credited to Ahmed Idris, a Nubian soldier. Beyond the details of that history lies the principle that inspired us: knowledge understood by the people closest to a problem can become the key to solving it.
That principle shapes how we think about AI.
Intelligence needs context
A capable AI model can produce a fluent answer. Useful work demands more.
A procurement lead needs a response grounded in tender requirements and supporting evidence. A professional turning expertise into an article or video needs structure, source checking, and editing. A business presenting its products needs accurate information about prices, availability, and policies.
The model does not automatically know which information matters, how the work gets done, or what someone must check before putting their name to the result.
We begin there—with the people, information, and processes behind the work.
The best AI for the most people
Our belief is simple: powerful AI should be useful beyond organizations with large technology budgets and specialist teams.
We focus on professionals and small and mid-sized firms doing substantial work with limited time and resources. They work across languages, documents, and systems. Their workloads vary, their budgets have limits, and mistakes carry consequences.
Giving them access to a model is a starting point. We aim to bring the surrounding pieces together so they can complete a useful job.
We package relevant solutions and products around business problems, combining suitable AI models, customers’ content, structured workflows, and checks against sources.
The model is a component. The product is the solution built around your work.
From principle to practice
With Tenda, we are building around finding relevant opportunities and preparing tender responses, connecting requirements with supporting evidence.
With Griot, we are building around developing and publishing professional ideas, bringing material, drafting, source checking, and review into a coherent process.
With HabaMart, we are exploring how businesses could present their catalogues, prices, and policies, help customers find products, and prepare orders.
These directions share a method: start with the job, build the service around the work, and match the model to the task. People retain responsibility for the decisions and the finished result.
Carrying the code forward
The history behind our name is specific. The principle travels.
Every organization holds knowledge that a general-purpose system cannot simply assume: how its customers behave, what its documents mean, where its processes break down, and what a good result requires.
We want that knowledge to shape the solution from the beginning.
“The code in our name is both memory and method.” It remembers the inspiration behind Nubian Code and describes how we intend to build: close to the problem, guided by the people doing the work, and judged by whether the result is useful.
One job at a time, well enough that a professional would stake their name on it.