Issue 01 — The Founding Brief

This is a document I have wanted to write for a while, and have postponed writing because the conditions for writing it honestly were not yet in place. They are now. TEK NAIJA exists. It is incorporated. The first system we own — LEGTEK NAIJA — is in production with real users. The first system we built for another company — STK Industries Ltd's trade platform — is in production and doing real volume. The architecture for our next owned product, LITIGATEIQ, is laid down and roughly seventy percent of the build is complete as of this writing. There is enough on the ground to describe the thing without straining to make it sound like more than it is.

So this is the brief. Plain language. What we are. What we are not. Why now.

What we are is two things, run as one firm. We are a holding company for the software we own — LEGTEK NAIJA, LITIGATEIQ, and what comes after. And we are a services firm for the software we build for other Nigerian companies — STK Industries Ltd's export trade platform is the live example. The two sides share a single bench of people, a single set of standards, and a single bias for institutional work. They do not share an income statement; the portfolio is the portfolio and the services book is the services book. But they share everything else.

What we build is infrastructure software for institutions — for ours, and for the institutions of a country that is still building most of its institutions. Procedural systems for the courts. Trade platforms for the merchants and exporters. Intelligence layers for the legal profession. The instinct in this space is to build for consumers — for the millions of phones, the visible market, the dashboards that look good on demo day. We build for the institutions behind those phones. The chambers, the regulators, the ministries, the trading houses, the export operators. The customers are smaller in number, harder to reach, slower to decide. The work compounds.

A note on what we are building next, because it is the question we get most often. LITIGATEIQ is an intelligence layer for Nigerian litigation. It does the unglamorous work of preparation: strategy mapping, precedent retrieval against Law Pavilion and the Nigerian Weekly Law Reports, document review at the volumes modern matters now generate, citation tooling that produces what a court will accept, and forensic analysis of court proceedings and counsels counter-strategy — patterns in how a particular bench reasons, how a chamber tends to argue, where a case turned on a procedural point rather than a substantive one. The point is not to replace the judgement that counsel brings to a brief. The point is to give a lawyer the same depth of preparation that a much larger team would have produced over a much longer time, and to do it before the first conference. A well-prepared lawyer is, in the ordinary case, a more effective advocate. That is the entirety of the claim. As of this writing the system is roughly seventy percent built; the remaining work is the slow part — testing against real chamber workflows with real lead counsel, which is where products like this are made or broken.

There is a question we get often, usually politely, sometimes not. Why hold a portfolio and run services at the same time? Why not pick one? The honest answer is that the two halves feed each other. The services work pays the bench while the owned products mature. The owned products demonstrate, in public, what the bench is capable of. And the lessons travel both ways: things we learn in client engagements end up in the architecture of products we own, and the rigour we apply to the owned products gets imported into client work that would otherwise be built to a lower standard. Picking one would mean either starving the portfolio or thinning the bench. We are doing both because both are needed.

A second question, also fair. Why a holding company structure for the portfolio specifically, rather than separate operating companies under common ownership? The structural answer is that each owned product needs its own room. LEGTEK NAIJA started as a single product. As it grew it kept revealing adjacent infrastructure problems that were not LEGTEK's problems to solve, but were nobody else's either. The intelligence layer over case law. The procedural ground truth that should sit beneath any litigation platform. Each of those, if pursued, would have either distorted LEGTEK or been abandoned. Spinning them out as separate products owned by a common parent gave each one room to be itself, and gave the parent a logic for capital and standards that a single product cannot.

That is the structural argument. The cultural argument is plainer. We come from a generation of Nigerian builders who watched the country's first wave of digital infrastructure get built almost entirely as adaptations — foreign software, foreign frameworks, foreign assumptions, retrofitted to local conditions. The retrofits work, sometimes well. But they are retrofits. They were not designed for our cases. They do not encode our procedural rules. They do not understand the customs of our trade. They cannot tell you what an okada is, or what makes a Nigerian Weekly Law Report citation valid, or how a Lagos magistrate's court actually schedules adjournments. We are building software that knows.

A few things this is not.

It is not a moonshot. The work is unglamorous. Hearing-room interfaces. Procedural rule engines. Trade compliance dashboards. Citation graphs. None of these will make a magazine cover. They will make the institutions that depend on them measurably better at the work those institutions exist to do. That is the entirety of the ambition.

It is not a vehicle for raising venture capital. TEK NAIJA is 100% founder-owned, with no external dilution at incorporation and no immediate plans to change that. We may take strategic capital later if a specific product requires it. We will not take generic growth capital to chase metrics. The discipline of building inside our own means is part of the value of the firm.

It is not anti-Western, anti-anything, or in any way a posture. We use Next.js. We use Supabase. We use TypeScript. We deploy on Vercel. The point of building Nigerian software is not to reject the global stack — it is to apply the global stack to local problems, with local knowledge, and to own the resulting institutional artefacts. The frontier is where the cases get encoded, not where the framework is written.

A word on what this Insights archive will be. It will not be a content marketing programme. We will not be publishing on a calendar. The posts that go here will be operational documents — analyses, post-mortems, notes from the practice — written by the people doing the work, when there is something to say. If you find yourself reading something here that feels like it could have been written by anyone, about anything, send us a note. We will have failed.

That, plainly, is the brief.

The work begins.