Indaba Works · Convergence AI

Perspectives

How Indaba came to be, where it's going, and who's building it — the thinking behind a system built so that organization becomes leverage.

In this collection
01Building for Tomorrow's Use Cases, TodayThe frontier02A $2.2 Billion Lesson in AccessHow it came about03The Long GameThe builder
Perspective 01 · The frontier

Building for Tomorrow's Use Cases, Today

Most software is reactive. A problem exists, someone names it, a tool gets built to fix it. That work matters, and Indaba started there. But the more interesting frontier is not fixing yesterday's problem faster — it is anticipating the situations people will face tomorrow and having the rails already laid when they arrive.

That shift is deliberate. We are no longer only asking "what's broken?" We are asking "what will ordinary people need to do, and be trusted to do, in the next few years — and what infrastructure doesn't exist yet to let them?" The answers tend to rhyme. People will keep facing complex systems alone. They will keep needing to assemble their own truth into a form professionals will act on. They will increasingly want to bring a trusted helper. They will demand privacy and control as table stakes. And the professionals on the other side will want vetted, comparable, low-noise ways to find the work worth taking. Indaba is being built to meet those needs before they fully harden into problems.

Three ideas define the niche we're creating. The first is readiness infrastructure: treating a person's preparedness as something measurable, portable, and matchable, rather than a hidden variable only an expert can assess. The second is the merit market: anonymized, scored matching that lets value be judged before identity — reducing bias, protecting the vulnerable, and giving professionals a cleaner signal. The third is dignity-first data: consent, per-item visibility, and human-in-the-loop approval built in at the foundation, so that scaling access never means scaling exposure. None of these is a feature request anyone filed. They are categories we are choosing to bring into being.

What makes this credible rather than aspirational is that the same engine keeps proving it. A certification system built to train one case helper becomes a tiered program that can credential a workforce across industries. An approval toggle built to protect one case becomes a governance pattern we apply everywhere sensitive actions live. A scoring model built to guide one injured person becomes the currency of a marketplace. We are not imagining these capabilities; we are generalizing ones we've already shipped, then pointing them at tomorrow.

The upside of building ahead of demand is that when the need arrives, adoption is not a construction project — it's a configuration. New vertical, same identity, vault, consent, roles, automation, certification, and score. That is how a small team creates outsized optionality: every build widens the platform, and every platform capability lowers the cost of the next anticipated use case.

There is a discipline to this, too. Anticipating the future is not licence to overreach. We keep the surface warm and human, we keep the substance rigorous, and we keep the person the system serves firmly in control. Building for tomorrow only earns trust if it honors the same values today.

Indaba's bet is simple to state and hard to execute: the platforms that matter next will be the ones that showed up early, with dignity and rails intact, for needs the rest of the market hadn't named yet. We intend to be there — here, today, already building.

# Indaba — Origin & Meaning (Article Set II) Continuation of the "Building for Tomorrow" narrative. Two articles + a short "Indaba, defined" callout. Voice: warm, grounded, confident. For the Commons / Perspectives and investor materials.

Perspective 02 · How it came about

How This Came About: A $2.2 Billion Lesson in Access

Some products are dreamed up in a room. This one was learned in the field.

A few years ago, the U.S. government did something it has almost never done: it agreed to pay for its own discrimination. Section 22007 of the Inflation Reduction Act set aside $2.2 billion for farmers, ranchers, and forest landowners who had been discriminated against in USDA farm lending. It belongs to a very short list — alongside the landmark settlements for Black farmers (Pigford), Native American farmers (Keepseagle), Hispanic farmers (Garcia), and women farmers (Love) — of times this country has formally reckoned, in dollars, with how it treated the people who feed it. That rarity is the point. These moments are hard-won, and they do not come around often.

I had a front-row seat. As a lead on a team of specialized cooperators named to help deliver that $2.2 billion program, I got to see, up close, how a promise of justice actually reaches — or fails to reach — the person it was written for.

Here is what I saw. The program was designed to be humane: you were not supposed to need a lawyer. And yet the application ran past thirty pages. It generated PDFs and reports that had to be interpreted, forms that had to be reconciled, evidence that had to be assembled into something a reviewer could act on. We built out two and three reports just to make sense of what a claim required. In practice, a program that promised "no lawyer needed" needed an army of technical assistance to help ordinary people fill it out. Meanwhile, on a parallel track, distressed-borrower relief moved on a page or two and could deliver life-changing sums. The people who most needed help were handed the heaviest paperwork.

And the whole thing sat on fragile ground. The earlier debt-relief effort — billions of dollars in promised loan forgiveness — had been frozen by lawsuits from white farmers alleging reverse discrimination, then repealed and rebuilt in race-neutral language just to survive. So even as we worked, the lesson was written on the wall: access is not the same as eligibility. You can be owed something and still never reach it, because the road between you and it is too long, too technical, and too easily contested.

That is where Indaba comes from. I kept thinking: we could have done so much more with the right system. Not more money — better rails. A guided, plain-language path that carried a person through the complexity instead of dropping them into it. A private place to assemble their story and their documents once, cleanly, so nothing had to be rebuilt. A way to bring a trusted helper alongside them. A clear picture of where they stood and what was left. The software that existed was not built for the person; it was built for the file.

I have always been about equity, access, and opportunity — about economic development through tools that give ordinary people the leverage the big players take for granted. The $2.2 billion program crystallized it. The gap was never talent or deservingness on the applicant's side. The gap was infrastructure. The powerful have systems; the underserved get forms.

So I started building the system I wished we'd had — first for injured people organizing a case, then, as the engine generalized, for anyone facing a complex process alone. Indaba is what "we could have done so much more" looks like when you actually build it: organization turned into leverage, access turned into a right, and a hard-won moment of justice given rails strong enough to reach the person it was meant for.

Perspective 03 · The builder

The Long Game: A Builder Who Wouldn't Back Down

Some people read the future. A few build the tools to survive it. Fewer still do it from the outside, without the backing, without the permission, and without blinking.

The founder of Convergence and Indaba belongs to that last, smaller group. His résumé does not read like a Silicon Valley origin story, and that is exactly the point. It reads like decades of showing up — years of hands-on technology work layered onto something most builders never earn: a startup founded in Zimbabwe, at the frontier of tech, crypto, and blockchain, in a market where you don't get to assume the power, the bandwidth, or the safety net. There, technology is not a lifestyle brand. It is leverage you have to fight for, and infrastructure you often have to build yourself before you can build anything on top of it.

That is where the instincts were forged. He learned to advocate — not in theory, but in practice — at the grassroots, in the village and the community, and at the level of government and policy, arguing for access and opportunity for people the system was not designed to serve. He learned economies from the bottom up and the top down at the same time: how money actually moves, how the powerful keep their tools inside the fence, and how a well-placed piece of technology can quietly cut a hole in that fence. Crypto and blockchain weren't hobbies; they were early lessons in what happens when you route value around gatekeepers instead of through them.

What makes him dangerous to the status quo is the combination. He is not a nostalgist who knows the history but can't build, and he is not a technologist who can build but has no memory. He carries both — the long view of how these systems came to be unfair, and the modern toolkit to do something about it. He can walk into the new fully tooled with knowledge of the old, the kind of understanding that only years and full-on engagement can buy. That is rare. Most people trade one for the other.

And he does not fold. The through-line of this whole enterprise is persistence — a study in perseverance against odds that have been stacked, repeatedly, by design. He has been underestimated, under-resourced, and told, in a hundred quiet ways, that this is not how it's done and not for people like him. He kept building anyway. Not talking about building. Building. And the proof is no longer a pitch: it's several working prototypes, a platform engine that is real, and an ecosystem — Indaba, the Exchange, the editions — that is visibly starting to take shape and, crucially, to make sense as a whole.

That coherence is the tell. Anyone can ship a demo. What he is assembling is a system where the pieces reinforce each other and can scale at pace — a brand, a toolset, and an architecture built with intelligence and the horsepower to match. It is the work of someone who intends not just to participate in the shift that's coming, but to shape who it serves.

He is challenging the powers that be in the dimension that actually matters: not with noise, but with infrastructure. Systems that give ordinary people the leverage the powerful hoard. And he is willing to take it on at whatever scale the fight requires.

The odds said no. He is still here — prototypes running, ecosystem forming, and only getting started.

← Back to the Commons
Indaba Works · Convergence AI LLC — organization becomes leverage. A case-organization service; not a law firm, and not legal advice.