PAYSTACK BEGAN
WITH A FRIENDSHIP

Ezra does not frame honesty as a dramatic reveal reserved for difficult moments. He describes an everyday posture: remaining open to questions and answering directly. That consistency lowers uncertainty in a relationship because other people do not have to guess which version of the truth they will receive. Trust grows when candor becomes predictable, including when the answer is uncomfortable. This does not mean sharing everything with everyone or abandoning tact. It means distinguishing the legitimate protection of information from the temptation to evade. Before an important conversation, clarify what you know, what you do not know, and what you are genuinely prepared to stand behind.

Looking back at his religious upbringing, Ezra notices how deeply birthplace and family shape what each person considers obvious. That realization does not require replacing one certainty with another. It invites him to examine where his convictions came from. Understanding inherited context creates useful distance between what we believe and what we have actually questioned. That distance can encourage humility without dismissing faith or family history. When you hold a strong conviction, ask which experiences formed it, how another person might reasonably have reached a different conclusion, and which part still deserves examination. The purpose is not permanent doubt. It is a more conscious relationship with belief.

Ezra and Shola did not discover their compatibility when they founded Paystack. They became friends at university, collaborated on projects, and later worked together as freelancers. This gave them opportunities to observe each other’s methods, reliability, and approach to problems before sharing a company. Trust between partners becomes stronger when it rests on experienced work, not only a shared vision. Previous collaboration cannot guarantee success, but it reveals behaviors that abstract conversations often hide. Before formalizing an important partnership, complete a limited project together. Watch how each person communicates, follows through, responds to pressure, and repairs a mistake. A small shared commitment can expose more than an ambitious pitch.

The digital wallet was designed to help people buy mobile airtime. Yet some users began keeping money inside it as a store of value. Rather than treating that behavior as an anomaly, the team saw a broader need: letting people use that value elsewhere. Unexpected use can reveal the real problem more clearly than the designer’s original intention. It is not enough to count clicks or collect explicit requests. Teams must also notice detours, repeated behaviors, and improvised solutions. Before adding a feature, identify what people already do despite the product’s limitations and ask why that behavior persists. The answer may point toward a more meaningful opportunity.

The complementarity between Ezra and Shola is not limited to a simple division between technology and relationships. Both help maintain the culture and can point out what the other person does not see. Ezra also describes developing his own understanding of people and behavior. A strong partnership does not freeze roles; it creates mutual vigilance around blind spots. That dynamic requires enough trust to receive an observation without treating it as rivalry. It also asks each person to keep widening their abilities. In an important collaboration, define primary responsibilities, then create a regular moment when each partner can identify a risk, a human need, or a tension the other may have missed.

Ezra acknowledges the central role of engineers, but he does not reduce Paystack to the people writing code. A customer-oriented company must also invest in operations and teams that support its users. Technology fulfills its promise only when people can understand it, trust it, and receive help. Human service is not a layer added after the product. It is part of the real experience, especially when the product handles money and reliability matters. To understand an organization, do not look only at what it automates. Look at who listens to difficulties, resolves exceptions, and carries the relationship when the system is not enough. Those roles reveal what the company truly values.

In the early days, Ezra and his team did not pretend to possess every advanced capability in house. They identified work beyond their current depth, then relied on existing services instead of turning every gap into an improvised internal project. Acknowledging a missing skill is a construction decision, not an admission of weakness. That honesty protects attention, limits avoidable mistakes, and lets a small team focus on work it can understand and own well. The human principle is simple: name what you do not know, choose support deliberately, and remain accountable for the outcome. Outside help does not replace judgment. It creates a more realistic boundary for judgment, learning, and responsibility while the team develops the knowledge it genuinely needs.

Ezra remembered the first fundraising process as relatively smooth. He also recognized that this perception reflected how the work was divided: his co-founder was closer to the investor conversations and carried much of the legwork. A result that looks easy can conceal the relational labor absorbed by someone else. Before telling a collective success story, ask who prepared the conversations, followed up, handled rejection, and maintained trust. That attention does not diminish the achievement. It makes the account fairer and more useful. Within a team, make invisible work discussable, share credit for it, and prevent the person carrying it from becoming invisible too. A complete story includes both the visible outcome and the effort that allowed others to experience it as effortless.

Ezra describes financial restraint as a governance choice. Paystack was not pursuing the largest possible round simply to display the number. The team valued its autonomy and wanted to avoid bringing in voices that could redirect its decisions. Good capital is measured not only by its size, but by what it enables without distorting the mission. Before accepting funding, clarify the actual need, the strategic value of the investor, and the rights being exchanged. More money may accelerate an ambition, but it can also alter power and expectations. The announced amount is therefore not the final measure of success. The better question is whether the capital strengthens the work while preserving the organization’s ability to decide with consistency and purpose.

Asked which friendship has shaped him most, Ezra thinks of someone he had known for ten years. What matters in his account is not professional advantage, but the freedom to converse and the confidence that he can rely on her in almost any situation. An important relationship reveals itself through repeated reliability, not immediate usefulness. Such bonds require time, listening, and a presence that continues beyond easy moments. They also provide a place where uncertainty can be expressed without performing a role. To care for this kind of friendship, do not measure only how often you speak. Ask whether both people can be honest, request help, and respond when circumstances make reliability matter most.

While exploring his style, Ezra found few men he could use as references. He could have concluded that the models he needed did not exist. Instead, he learned from women who were already exploring the forms, clothing, and expressions that interested him. A useful idea does not lose value because it comes from a category different from your own. Boundaries of gender, industry, country, or generation can unnecessarily shrink the field of learning. Looking more widely does not mean copying without context. It means identifying a useful principle, understanding why it works, and adapting it to your reality. Inspiration becomes richer when it can move between experiences that are not identical, while respecting the people and contexts that produced it.

Asked how to choose a technical co-founder, Ezra does not begin with tools or programming ability. He looks for someone who genuinely shares the mission and is willing to build the relationship required to pursue it. A durable partnership begins with common commitment, not only complementary skills. Skills still matter, but they do not reveal how two people will respond under pressure, cross a disagreement, or negotiate sacrifice. Before sharing responsibility and ownership, discuss the purpose, limits, values, and difficult scenarios. Learn about each other through a real decision or small piece of work. The goal is not to remove every difference. It is to discover whether a shared direction can hold those differences when the work becomes demanding.