Everyone Got Distracted by One Sentence. Nobody Read the 7 Lessons.

The clip that went viral was not from his prepared remarks. It was a comment Tosin made in passing — responding to a topic raised by another speaker on the same panel — about Moniepoint's difficulty filling hundreds of vacancies with talent that meets global standards. That is what Nigerian Twitter screenshot, clipped, captioned, and turned into a days-long argument.

Meanwhile, the rest of what he said on that stage — a detailed, honest, hard-earned framework for building a company from the ground up — passed through largely without comment. A few thoughtful threads. Then silence, buried under the noise of the talent debate.

Here is what I want to do in this piece. First, give Tosin's seven lessons the attention they deserved and did not get. They are the real message he came to deliver — not a side note, not a throwaway framework, but a founder playbook built from years of experience scaling one of Africa's most valuable fintechs. Second, come back to the talent comment and tell the full story — because the gap he described is real, and the reasons it exists are more structural and more uncomfortable than anything that was said in that Twitter argument.

Both things are true. Both deserve to be said properly.

---

Before product, before team, before a single investor meeting — Tosin's first lesson is about direction. Not a mission statement. Not a values slide. A real, grounded answer to a deceptively simple question: what problem are you solving, for whom, and can you build a sustainable business doing it?

He frames it as fundamental and viable deliberately. Fundamental means the problem must matter enough to justify years of your life — you have to care about it in a way that outlasts motivation, survives failure, and holds when the money runs out. Viable means the economics must work in principle from the start. Not eventually, not after Series C. There must be a credible path from the problem you are solving to the value you can capture from solving it.

This is where most Nigerian founders fail before they ever hire a single person. They build solutions in search of problems. They chase trending verticals because investors are funding them this cycle. They write a mission about "empowering Africa" and mistake the language for a direction. The energy is real. The clarity is not.

If you cannot describe exactly who your customer is, what specific problem you are solving for them, and how you capture value from that solution — you do not have a direction. You have ambition dressed up as a startup.

Moniepoint's direction was specific from the beginning: underserved merchants and businesses in Nigeria who needed financial infrastructure that actually worked for them. Not a broad fintech play. Not "financial inclusion" as a concept. A specific customer, a specific problem, a specific model. That specificity is what allowed everything else to be built with discipline instead of improvisation.

Tosin is explicit about the composition he believes works: a Hacker, a Hustler, and a Hipster. This framework has existed in startup circles for years, but the way he applies it grounds it in something more practical than a personality exercise.

The Hacker builds the thing. Not necessarily a software engineer in the narrow sense — the Hacker is whoever can take an idea from concept to something real. They are comfortable with uncertainty, capable of working without full requirements, and energised by creation itself. The Hustler sells it and keeps the lights on. They knock on doors, land the first ten customers, convince the first investor to write a cheque before there is any proof to show them. The Hipster understands the user. They feel what the customer feels. They know when the product is off, when the experience is broken, when the interface is asking someone to do something unnatural.

What you cannot afford is a founding team of the same type. Three Hustlers with no one who can build. Two Hackers who have never sold anything. The imbalance becomes visible quickly and is almost impossible to correct once the company has momentum. Hiring can fix skills — it cannot fix gaps in the founding DNA.

More critically, Tosin emphasises that the founding team must have genuine commitment to each other, not just to the idea. The idea will change — Moniepoint itself has evolved significantly over the years. The market will surprise you. The product you thought you were building will turn out to be different from the one that actually works. The only thing that holds through that chaos is a founding team that trusts each other's judgment, can disagree without breaking, and is genuinely in for the long game. Most co-founder disputes that kill African startups are not about strategy. They are about this — the founding team was never truly right from the beginning.

Lesson three is about early-stage survival, and it is one of the most honest things Tosin says across the entire session. He does not romanticise fundraising. He does not tell founders to go build a pitch deck and queue up for VC meetings. He tells them to hustle out their seed capital — from personal savings, from family and friends, from early customers willing to pay before the product is perfect, from angel investors betting on you personally before the business proves itself.

The point is not to raise a lot. The point is to prove enough to justify the next phase.

This is a critical mindset shift for a generation of Nigerian founders shaped by TechCrunch announcements and YC acceptance tweets. They see fundraising as the milestone — the thing that validates you are real, that the company matters, that you have arrived. They optimise for the announcement, not the business.

Tosin built Moniepoint on scrappy early capital. He knows what it means to operate without a safety net, to make every naira count, to grow through revenue rather than runway. That experience is part of what gave Moniepoint its operational rigour. Companies born into abundance rarely develop the discipline that survival teaches.

Do not wait for permission from a VC to start. Hustle what you need to get to the point where your traction speaks louder than your pitch. Money should follow proof — it should not precede it.

There is also a deeper lesson about independence. Founders who raise too early, too large, before they have a real sense of their own business, cede control of the narrative at the exact moment when clarity is still being formed. Hustling your seed capital keeps the steering wheel in your hands until you know where you are actually going.

The fourth lesson is one every product manager and founder can recite from memory and violates in practice. Build your MVP fast. Get something real in front of real users as quickly as possible.

The word Tosin emphasises is fast. Not polished. Not feature-complete. Not ready for a Product Hunt launch. Fast. The only purpose of the first version is to answer the most important question you have: will someone pay for this, or meaningfully change their behaviour because of it?

He specifically names the trap Nigerian founders fall into most often: spending six months to a year building before testing a single real assumption with a real customer. They add features because they are afraid to launch without them. They polish screens nobody has seen yet. They run internal consensus exercises — does the team like it? does the founder like it? — as if that is a proxy for market validation.

An MVP is not a beta product. It is not a soft launch. It is the minimum expression of your idea that lets the market give you a genuine signal. The faster you get that signal, the faster you know whether you are building something real or something you merely believe is real — which are very different things.

There is a specific kind of damage in the talent pool that connects here. The hardest candidates to place are not those with no experience — they are often people who have shipped products nobody used, inside environments where "done" meant "built" and never meant "validated." They have portfolios, timelines, and metrics nobody tracked. They have never truly faced the market. The MVP lesson is not just about speed. It is about building the reflex to seek external truth over internal comfort, as early and as often as possible.

This is the lesson that would have received a very different reception online if people had been paying attention — because it speaks directly to the talent conversation that consumed the discourse, and says something far more useful than either side of that debate managed to say.

Tosin's fifth lesson is about who to hire and how to treat them. He calls them Spartans: people with exceptional ability and even more exceptional commitment. People who do not need to be managed into caring about the outcome. People who figure things out when the playbook runs out and there is no one to escalate to. People who treat your company's problems as their own problems — not because you asked them to, but because they have decided to.

Spartans are not unicorns. They exist in Nigeria. They exist everywhere. But you will not find them by posting a job description with seventeen requirements and a market-rate naira salary. You find them by being the kind of company Spartans want to be part of — and that means building something with a mission worthy of their commitment, a culture that respects their intelligence, and a growth path that rewards their investment in the outcome.

That is why the second half of this lesson matters as much as the first: give them equity. Real equity. Not a fraction of a percentage buried in a contract nobody reviews until something goes wrong. Skin in the game. A genuine stake in the outcome. A reason to stay and build rather than leave when the next opportunity comes along.

Here is the part of the talent conversation nobody said directly: many of the companies loudest about not finding global-standard talent are not offering equity to their best early hires. They are not building career growth structures that reward ambition. They are not creating product cultures where high performers feel genuinely challenged and genuinely heard. They want Spartans, but they have not built a place where Spartans would choose to stay. The talent gap is not only about who is in the market — it is also about what you are offering the people already there.

Lesson six is unglamorous. It does not make for compelling conference content. It is also, by Tosin's account, the one that separates companies that survive from companies that should have survived but didn't.

Cash flow — not revenue, not ARR, not GMV, not valuation — is what determines whether your company is alive on any given Tuesday. You can have a profitable business model in theory and run out of money in practice if your receivables cycle is long, your payroll is ahead of your collections, or you made a bet on a large customer who pays in ninety days while your team needs to be paid in thirty.

Tosin is direct about this because he has seen it happen — not just to other companies, but to companies in his orbit with real products and real revenue that ran dry not because the business was bad, but because no one was watching the actual numbers week to week. Revenue in a spreadsheet and cash in the bank are two different things, and the distance between them is where companies die quietly.

This is especially true for African startups in enterprise and B2B sales. Long sales cycles. Slow-paying clients — often government contracts or large corporates with procurement processes designed for their convenience, not yours. Fast-growing teams with infrastructure costs that arrive before the revenue does. The cash gap is invisible in the pitch deck and lethal in the account.

Almost all startup content in Nigeria talks about growth. Almost none of it talks about survival. Watching your cash flow is a survival skill before it is a growth skill — and if you do not learn it early, you may never get to the growth conversation at all.

The seventh lesson — be pragmatic — is the one Tosin spends the most time on, because it is the hardest to operationalise and the easiest to get wrong in both directions.

Pragmatism, in his framework, is not a personality trait. It is a discipline. Specifically, it means having a clear, honest read on where you are at any given moment, what the capital situation actually is, and what the most rational path forward looks like — regardless of what you wish were true, what your ego prefers, or what would make a better story at the next conference.

He applies this most concretely to the bootstrap versus raise question, which every founder faces and almost every founder answers ideologically rather than practically. Some founders should bootstrap longer but get seduced by the status of a fundraising announcement — and end up accountable to investor timelines completely disconnected from their market reality. Others bootstrap out of pride or fear, starving businesses with genuine potential that needed capital to accelerate past a critical threshold.

Neither ideology is right. The arithmetic is right. What does the business actually need? What will capital enable that the business cannot reach organically in the relevant time window? What does raising now cost you in dilution and control — and is that trade worth it at this specific moment?

Pragmatism extends beyond fundraising. It applies to people: knowing when to give someone more time and when the evidence has already made the decision. It applies to products: knowing when your conviction is a genuine signal and when it is stubbornness in disguise. It applies to timing: knowing when to push hard because the window is open, and when to slow down because the market is not ready — regardless of how ready you feel.

This is the gap Tosin was describing. Not a skills certification gap. Not a pipeline gap. A depth-of-thinking gap — the distance between where most founders and operators are in their clarity and self-awareness, and where you need to be to build something that survives real contact with the world. These seven lessons are, in large part, a roadmap for closing it.

---

Here is something that barely came up in the debate: a significant portion of Nigeria's tech talent pool spent their formative professional years inside failed startups.

This is not their fault. Nigeria's startup ecosystem has seen a wave of closures over the last four years — underfunded companies, premature scale, founder ego, bad unit economics. Many talented people, especially in product and engineering, joined these companies with genuine ambition, only to spend two or three years firefighting with no real systems, no real mentorship, and no real product culture.

What they learned was survival, not craft.

They learned how to ship features under pressure without a PRD. How to conduct "discovery" by asking their CEO what to build. How to define success by whether the founder was happy, not whether the user was retained. They left those companies with job titles and stories, but without the depth of practice that comes from working inside a functioning product organisation.

When they walk into an international interview and are asked how they prioritise a roadmap, or how they define a metric that matters, they give answers that sound rehearsed — because the environment that trained them never demanded anything better. The experience was real. The learning environment was broken.

Lesson four — build your MVP fast, and build it to be validated, not just shipped — is the antidote to this exact pattern. Environments that produce that discipline produce different people.

The second problem is hiding in plain sight.

Banks and large Nigerian corporations are among the biggest employers of tech-adjacent talent in this country. They absorb thousands of graduates every year and put them through structured programmes, clear hierarchies, and formal processes. On the surface, that sounds like exactly what builds global-standard talent.

In practice, it builds something else entirely.

Nigerian banks operate on outdated product thinking. Products are defined by compliance requirements, not user needs. Roadmaps are driven by what the MD saw at a conference in Singapore, not by data or discovery. "Product managers" are often project coordinators with a fancier title — tracking delivery timelines, attending steering committee meetings, and writing status reports nobody reads.

The people who come out of these environments have discipline. They have process literacy. They know how to work inside a corporate structure. But they have almost never been asked: what problem are we actually solving? They have never built a hypothesis, designed an experiment, and made a product decision based on the result.

When they enter the global job market — or even a company like Moniepoint that aspires to global standards — they collide with a completely different way of working. And the gap feels enormous, not because they are not smart, but because the environment that trained them never demanded global thinking.

This connects directly back to lesson one. A fundamental and viable direction requires someone who can think from first principles about the customer. Banks, as training grounds, have largely produced people who think from compliance and hierarchy. That is not a character flaw. It is a consequence of the environment.

Here is the uncomfortable truth that the salary argument on Twitter was circling around without landing on directly.

There is a version of Nigerian product talent that absolutely meets global standards. These are people who have worked with international teams remotely, gone through rigorous product interview processes at companies like Stripe, Deel, or Andela-placed organisations, shipped products that compete internationally, and built the kind of portfolio that holds up anywhere in the world.

Those people exist. I have met them. I have trained some of them.

They are not applying to Moniepoint.

Not because they are disloyal to Nigeria, but because the market has already found them and priced them accordingly. A mid-level PM with genuine international-grade experience is earning in dollars — often between $3,000 and $7,000 a month — working remotely for companies that also offer flexibility, trust, and a healthy product culture.

If Moniepoint's compensation is not indexed to that reality, then what they are actually describing is: we want global-standard talent at below-global-standard cost. That is not a talent gap. That is a compensation strategy gap dressed up as a skills conversation.

Lesson five speaks to this directly: hire Spartans and give them equity. Spartans know what they are worth. The companies that attract them are not necessarily the ones paying the highest base salaries. They are the ones offering ownership, growth, mission, and the kind of product culture where excellence is actually recognised. If you cannot compete on cash, you have to compete on everything else — and most companies have not done that work.

This is the part of the conversation nobody wants to have — so I will.

Over the last three years, Nigeria has seen an explosion of people who call themselves product managers without having ever shipped a meaningful product. Many of them are now training others.

I do not say this to be unkind. I say it because I have seen its consequences directly. In interviews, I have met candidates who can recite every PM framework — RICE, JTBD, the double diamond, north star metrics — and cannot tell me a single coherent story about a product decision they made and why it worked or failed.

The PM training market in Nigeria has a real problem: too many instructors are teaching from content, not from experience. They took a course, read a few newsletters, watched some Product School videos, and built a curriculum. They use terminology correctly. But they have never managed a sprint, navigated a difficult stakeholder, or fought for a user insight in a room full of executives who had already made up their minds.

Then there are the "get ready with me" creators — people whose entire PM brand is aesthetic. The laptop, the Notion dashboard, the morning routine. Thousands of followers watching someone prepare to be a PM, indefinitely. Content without output. Performance without craft.

The people consuming this content are not learning to be product managers. They are learning to perform product management on social media. And when they walk into an actual interview, or sit down with an actual engineering team, the gap between performance and competence becomes visible almost immediately.

This is a real part of why companies like Moniepoint are struggling. The candidate pool looks large, because the PM community looks active. But a significant portion of that community is running on borrowed vocabulary, not earned experience. Tosin's seven lessons — specifically the emphasis on pragmatism, on fast validated learning, on hiring people with real commitment — describe exactly the kind of operator this environment is failing to produce.

---