TWO UNICORNS,
A WORLD TO BUILD

A visible user problem is not yet a viable market. Iyin’s first team disliked its university learning software and saw an opening, but it had not studied how institutions replaced systems: formal tenders, large contracts, risk controls, and qualified suppliers stood between the user pain and a purchase. Customer discovery must include the person who controls the budget and the process that controls that person. Before building deeply, map who uses, approves, procures, integrates, and can block the product. A solution can be desirable and still be commercially unreachable through the route you chose.

After apologizing, Iyin did not defend the disputed product. He asked the professor whether the underlying technology could be useful in a legitimate way. That question surfaced another need: websites for courses taught outside the university. An objection can contain better customer discovery than praise. First resolve the harm or disagreement; then ask what the stakeholder was actually trying to protect, achieve, or improve. The answer may reveal a lawful adjacent use, a different buyer, or a missing constraint. A conflict becomes productive only when listening replaces the urge to win the argument.

The first company did not produce a founder payday. Its sale allowed the team to repay investors and close the chapter cleanly. That outcome matters because an early venture is also a test of how a founder handles other people’s confidence when the original plan fails. Not every responsible exit maximizes immediate personal return. Preserve records, communicate the real state of the company, settle obligations fairly, and protect relationships when possible. Reputation is not a consolation prize: it becomes part of the operating capital available for the next attempt.

A compelling education story and successful pitch competitions did not make Fora scalable. A mentor with relevant operating experience broke down the costs, limited pricing power, and customer behavior until the model no longer held. Praise, funding interest, and presentation quality cannot overrule unit economics. Write down what it costs to acquire, serve, support, and retain one customer; then test what that customer will reliably pay and how those numbers change with scale. Let the model disconfirm an exciting narrative early enough that the team can reuse its capability elsewhere.

Andela did not appear as a perfectly formed first idea. The team moved from a blocked university-credit model to professional education, then through another skills hypothesis before concentrating on software development. Each version carried learning into the next. A pivot should preserve validated insight while changing the assumption that failed. Compare adjacent opportunities by urgency, willingness to pay, learner outcomes, and available talent. Do not remain loyal to the first expression of the mission. Stay loyal to the problem, and let stronger market signals narrow the mechanism.

Fora and Andela were meaningfully different ventures, yet Iyin did not simply abandon the people who had backed the earlier company. He structured continuity and gave those investors an opportunity to participate again. The exact legal treatment will vary, but the underlying standard is durable. A pivot is also a governance event. Explain what changed, what value or assets remain, what the new risks are, and which choices existing stakeholders have. Fairness cannot be improvised after the new direction succeeds; it must be designed while the outcome is still uncertain.

As Andela grew, capital became a binding constraint. Iyin brought Jeremy Johnson into the CEO role and concentrated on recruitment, where he believed his own advantage was strongest. Founder titles should serve the company’s next stage, not preserve personal status. Name the bottleneck—capital, product, distribution, regulation, or organization—then ask whose capabilities and credibility can unlock it. Changing roles is not the same as abandoning responsibility. Done well, it places each founder where their contribution compounds and gives the company the leadership configuration the next phase actually requires.

Failure showed whether an idea could survive. Rapid growth at Andela exposed a different class of ignorance: management processes, organizational design, and the systems required to coordinate at scale. Iyin’s claim is intentionally provocative, but its practical value is clear. Success creates new evidence about what the organization cannot yet do. When demand accelerates, study the strain instead of celebrating only the headline. Which decisions wait for one person? Where does quality vary? What knowledge remains tribal? Growth is a diagnostic load test; use it to build the operating system the smaller company never needed.

Payments was not an abstract trend for Iyin. At Andela, he had seen Nigerian clients excluded because the infrastructure did not let them pay. That operational pain helped make Flutterwave a more compelling alternative than business school. Firsthand friction gives a founder context that market size alone cannot provide. Record where work stops, which customers are excluded, and what teams repeatedly patch by hand. Then test whether the pain is shared widely enough to support infrastructure. Personal exposure should open the investigation, not replace broader validation.

Flutterwave needed banks and public stakeholders aligned with a model that was still unfamiliar. The difficult work was not only software or sales; it was explaining change to powerful people without turning their knowledge gap into humiliation. In a regulated ecosystem, stakeholder education is core product work. Learn the incentives and language of each institution, build personal trust, and design win-win paths that let others move without losing face. Technical correctness does not create adoption by itself. Diplomacy is the mechanism that converts a new possibility into coordinated action.

Iyin describes the companies as vehicles and takes pride in what they enabled: new work, new businesses, and opportunities beyond the original organization. This does not make financial health irrelevant; a vehicle must survive to carry anything. But company value is not the only measure of company consequence. Track the capabilities, markets, careers, and downstream ventures that the infrastructure makes possible. A broader impact lens can sharpen product choices because it asks not only who buys today, but what users will be able to build tomorrow.

The first syndicate product was not an automated platform. Iyin wrote investor-style memos that reduced the work required to evaluate opportunities, delivered them manually, and initially did it free. Charging followed when usage and value began to grow. Before scaling a service, perform the valuable job closely enough to understand it. Manual delivery reveals which information matters, where trust breaks, and what users repeatedly request. Free work should remain bounded and intentional: define what it is testing, what evidence will justify pricing, and when the experiment ends.

Experience recognizes familiar patterns quickly, but genuinely new work can be damaged when every possibility is forced into an old template. Iyin prefers people who can reason with him about what might be possible, then layer relevant experience as the organization encounters repeatable problems. The useful contrast is openness versus dogma, not youth versus age. Build teams that can ask naïve questions, test first principles, and still import hard-earned judgment when it fits. Novelty needs imagination; scale needs memory. Strong organizations create room for both without allowing either to dominate automatically.