Built online.
For everyone.

David Afiakurue is the driving force behind ZWAP. As CEO and Co-Founder, he does not manage from a distance. He is a daily active user of the product, experiencing every conversion, every delay, every friction point firsthand. This is not a gimmick. It is how he leads.

Before ZWAP, David spent years studying financial systems across multiple African markets. He saw the same pattern everywhere: people needed to move between crypto and fiat, and every existing solution failed them. Fees were hidden. Speeds were slow. Interfaces were built by engineers for engineers. Nobody was building for the grandmother in Lagos who needs to convert USDT to pay her grandson's school fees.

David's role at ZWAP goes beyond the typical CEO. He leads fundraising conversations, translating technical product strengths into investor language without losing the truth of what ZWAP actually does. He builds regulatory relationships across multiple jurisdictions, staying ahead of compliance requirements before they become problems. And he oversees partnership strategy, identifying the banks, payment processors, and liquidity providers that make ZWAP work.

But his most important job is saying no. Features that do not serve the core mission get cut. Partnerships that compromise user trust get rejected. Growth tactics that sacrifice experience for metrics get blocked. This discipline is rare in a startup, and it comes directly from David.

He envisions ZWAP not as a crypto company, but as payments infrastructure that happens to use crypto as one of its rails. The distinction matters. It means ZWAP's value does not depend on any single blockchain, token, or narrative. It depends on solving a real problem reliably.

David is also the company's public voice. He shares building updates, transparently discusses challenges, and engages directly with users on social media. He believes founders should be accessible, not hidden behind PR teams. If something breaks, you will hear from him directly.

Dominion Afiakurue is the architect behind everything you cannot see at ZWAP. As CTO and Co-Founder, he designed the entire technical infrastructure from the ground up, a microservices system where the trading engine, wallet service, notification system, and compliance module each run independently. If one service has an issue, the others keep working. Users never notice.

His approach to engineering is rooted in a simple principle: systems should fail safely. Every layer of ZWAP's architecture has redundancy built in. Every API call has a timeout and a fallback. Every transaction has a state machine that can recover from any failure point. This is not theoretical. Dominion has tested these failure scenarios deliberately, simulating everything from database outages to third-party API failures.

Dominion built the API platform that allows third-party developers to integrate ZWAP's conversion engine into their own applications. This was not an afterthought. He designed the internal systems with external access in mind from day one, which meant clean interfaces, proper rate limiting, and comprehensive documentation. What takes most companies a year to retrofit, Dominion built into the foundation.

He obsesses over latency. The target is under 30 seconds for a complete conversion, from the moment a user confirms to the moment funds arrive. This involves optimizing database queries, implementing intelligent caching, managing connection pools across multiple liquidity providers, and building real-time monitoring that alerts the team the instant anything slows down.

As an engineering leader, Dominion runs weekly architecture reviews where every engineer presents their designs before implementation. The rule is simple: the best idea wins, regardless of seniority. A junior engineer's suggestion has the same weight as Dominion's. This culture attracts strong engineers who want to grow, not just execute.

He also built ZWAP's security stack using a defense in depth model. Encryption at rest and in transit. Hardware security keys for critical operations. Automated vulnerability scanning on every deployment. Penetration testing on a regular schedule. Privilege separation so no single engineer has access to production data. These are not checkboxes. They are woven into every development workflow.

Before ZWAP, Dominion built systems for companies that needed to handle high-throughput, low-latency operations. He brought that discipline to ZWAP, treating every user transaction with the same rigor that financial institutions apply to trading systems. The difference is he made it fast and simple on top of being robust, which is the hard part.

Christian Anigbata is the reason ZWAP feels the way it does. As Head of Product Design, he is responsible for every pixel, every transition, every word that a user encounters. This is not an exaggeration. Christian reviews every design change personally, and the standard is relentless.

His design philosophy is built on a conviction most tech companies ignore: the experience is the product. You can have the best backend in the world, but if a user cannot figure out how to convert USDT in under ten seconds, the engineering is wasted. Christian makes sure that never happens.

He maps not just the happy path but every possible path through the product. What happens on a slow network? The loading states need to feel intentional, not broken. What happens when a user taps the wrong button? The error needs to be clear and the recovery needs to be obvious. What about first-time users versus hundredth-time users? The interface needs to teach without patronizing and streamline without hiding.

Christian made specific, deliberate choices that define ZWAP's identity. The dark theme was not an aesthetic preference. It reduces eye strain during extended use and, psychologically, creates a sense of seriousness and trustworthiness that matters when people are moving money. The EB Garamond typography was chosen for its editorial quality. It makes ZWAP feel like a premium publication, not a typical fintech app. Every feedback animation was designed so users always know what the system is doing, eliminating the anxiety of "did it work?" that plagues most financial apps.

His north star metric is not user satisfaction scores or net promoter scores. It is simpler: ZWAP should feel like sending a text message. So natural, so seamless, that the technology completely disappears. You do not think about SMS when you send a text. You should not think about crypto infrastructure when you convert USDT.

Beyond visual design, Christian leads user research. He conducts regular interviews with ZWAP users, watching them use the product in real time. Every confusion, every hesitation, every wrong tap gets logged and prioritized. He maintains a living document of user pain points that directly feeds the development roadmap. When engineers want to add a feature, Christian's first question is always: "How does this make the core flow simpler?" If it does not, it does not get built.

Christian also designed the micro-interactions that make ZWAP feel alive. The way a confirmation slides in. The way a balance updates with a subtle animation. The way error states guide you toward resolution instead of just showing a red box. These details take hours to get right and milliseconds to experience, but they are the difference between a product that works and a product that feels right.

Before ZWAP, Christian designed digital products across fintech, e-commerce, and SaaS. He brought a cross-industry perspective that prevents ZWAP from falling into the traps that crypto-native products typically do: overcomplicating interfaces, using jargon instead of plain language, and prioritizing technical impressiveness over human usability.