Most of what is written about building teams was written for environments that bear little resemblance to the operating reality of African ventures. The standard advice assumes that talent is abundant, that capital is plentiful enough to compete for it on compensation, and that the founder’s main task is to design hiring processes that filter the abundant talent into the venture at the right pace. The advice is technically correct for the contexts in which it was developed. It is the wrong advice for African founders, who operate in environments where talent is unevenly distributed, capital is scarce, and retention cannot be purchased through top-of-market compensation alone.
I have built teams across four ventures under these constraints, in roles ranging from React Native developers to operations managers, hospitality staff, designers, and senior commercial leaders. The teams have been built in Harare, in Sandton, with remote contributors across multiple African jurisdictions, and across categories from B2B SaaS to hospitality to ride-hailing to consulting. The framework I have arrived at is not original to me; pieces of it appear in management traditions across decades. What I want to argue is that the framework is meaningfully different from what is taught in the dominant founder writing, and that founders who absorb the dominant writing without recognising its assumptions about abundance build teams that fail in characteristic ways.
This piece is the cornerstone of the Teams and Governance pillar of this site. The supporting pieces go deeper into specific aspects: the substance of leadership, the hiring decision’s asymmetric cost, the structural role of team culture in the venture’s market position, the breakthrough positioning that small teams can achieve. This piece is the umbrella under which all of those sit.
The structural realities the dominant writing does not acknowledge
Before getting into disciplines and tactics, I want to name five structural realities about African team-building that the dominant writing does not address, because every subsequent decision flows from them.
The first reality is that talent in African markets is unevenly distributed in ways that make hiring fundamentally different from hiring in mature markets. The talent pool for almost any specialised role in any African market is smaller than the equivalent pool in a mature market would be. The pool is also less standardised; the credentials, training, and prior-employer signals that a founder in San Francisco might use to evaluate candidates are weaker indicators in many African contexts because the credentialing infrastructure is younger and less consistent. The implication is that founders cannot run the standard “post the job, screen the applicants, hire the best fit” process and expect to find the right person; the right person often is not in the application pool because they have not been incentivised to apply, or because they are in a relationship-based career path where they would not respond to public job postings, or because the role’s signals do not match what they would search for.
The second reality is that capital constraint shapes every compensation decision in ways that the dominant writing does not address. The standard advice on compensation assumes the venture can pay market rates, with adjustments for performance and tenure. African founders operating under capital constraint cannot pay market rates for senior roles, often cannot pay market rates for mid-level roles, and have to design compensation structures that compete on dimensions other than base salary. Equity, autonomy, learning, mission, the founder’s own personal investment in the team member’s development, and the venture’s eventual upside are all parts of the compensation conversation in ways that they are not at well-funded ventures. Founders who try to compete on base salary alone lose the talent fight; founders who design multi-dimensional compensation structures recruit and retain meaningfully better than their constrained budget should allow.
The third reality is that retention is structurally harder in African markets than in mature ones because the alternatives for talented people are weighted toward leaving. A talented developer in Lagos has options that include large international companies hiring remotely, diaspora migration to mature markets, freelancing for international clients, and positions at better-funded competitors. The retention question is not “how do we keep this person from going to another local company”; it is “how do we keep this person from leaving this market entirely.” The compensation, work environment, autonomy, and mission of the venture all have to be calibrated against the brain drain pressure, and most founders under-calibrate because they are reasoning about retention as a local-competition problem rather than as a structural-environment problem.
The fourth reality is that the founder’s personal investment in team development is more consequential in African contexts than in mature ones. In a mature-market venture with full HR infrastructure, talent management, formal training programmes, and middle management depth, the team member’s development happens through institutional structures that the founder is largely outside of. In an African early-stage venture without those structures, the founder’s personal involvement in team development is the substitute, and the team’s growth depends substantially on whether the founder is investing the time. Founders who delegate team development to intermediaries who do not yet exist, or to formal processes that the venture is too small to operate, watch their teams stagnate and eventually leave for environments where the development they need is happening.
The fifth reality is that the team’s relationship with the venture’s mission carries more of the retention weight than it does in mature markets. In a mature market, a team member can have a moderate connection to the venture’s mission and still stay because the compensation, infrastructure, and career path are themselves sufficient. In an African early-stage venture, where the compensation cannot fully compete and the infrastructure is being built, the team member’s connection to the mission is what holds them through periods when the other dimensions of the offer are stretched. Founders who recruit team members whose connection to the mission is shallow find that those team members leave at the first stress; founders who recruit team members whose connection is deep find that those team members stay through periods that should have lost them, and the staying is what produces the venture’s continuity.
These five realities shape everything that follows. They are not exceptions to the standard playbook; they are a different operating environment in which a different playbook applies.
The four disciplines that work under constraint
When the time comes to actually build the team, the founder’s job is to apply a small set of disciplines that fit the constrained environment. The disciplines are unglamorous, demand significant founder attention, and produce teams that punch dramatically above what the venture’s resources should allow.
The first discipline is to hire slowly, deliberately, and from your relationship-based network rather than from public application pools. The talent that will actually transform the venture is rarely in the public application pool; it is in the founder’s extended network, the network of senior practitioners the founder has cultivated, the network of operators the founder has worked with at prior ventures. The discipline is to spend significantly more time on candidate sourcing than the dominant writing suggests, to make hires from warm connections rather than cold applications wherever possible, and to defer hiring rather than hire someone weakly aligned with the venture’s needs. A bad hire in a small team is structurally more damaging than a bad hire in a large team; the constraint amplifies the cost. The discipline is to refuse the time pressure that produces wrong-fit hires, even when the venture genuinely needs the role filled, because the cost of the wrong hire is paid for years.
The second discipline is to design compensation as a multi-dimensional package rather than as a salary number. The package includes base compensation, of course, but also includes equity (for senior roles where it makes sense), autonomy (the team member’s actual control over their work), learning (the explicit investment the venture is making in their development), recognition (the way their contribution is acknowledged), and the founder’s personal accessibility (the team member’s actual relationship with the founder over time). Each of these dimensions is real compensation, with real value to the team member, and a venture that designs all five thoughtfully can recruit and retain talent who would not be available at the same base salary alone. The discipline requires the founder to understand each team member individually well enough to know which dimensions matter most to them, because the dimensions are not interchangeable; some team members weight learning heavily, others weight autonomy, others weight equity. The package has to be calibrated to the person.
The third discipline is to invest founder time in the team’s development at a rate that mature-market founders would consider excessive. The substitute for full HR infrastructure is the founder’s personal involvement: weekly one-on-ones with senior team members, quarterly career conversations, deliberate exposure to challenges that develop the team member’s capability, explicit feedback on performance and growth. This is hours of founder time per week that mature-market founders would have delegated. The discipline is to hold the time even when the calendar pressure makes it tempting to skip, because the team’s growth is the venture’s capacity, and the founder’s investment is what makes the growth happen. Founders who skip this work end up with teams that stagnate and leave; founders who hold it have teams that develop into senior contributors over years, and the senior contributors are the venture’s most consequential asset.
The fourth discipline is to make the venture’s mission specific, visible, and recurringly reinforced. The team member’s connection to the mission carries retention weight; the founder’s job is to make that connection vivid and continuous rather than implicit. Specifically: the venture’s purpose articulated explicitly and frequently, the customers being served made tangible to the team, the impact of the work made visible through stories and outcomes, the founder’s own commitment to the mission demonstrated through how time and attention are allocated. This discipline is not slogan-making or vision-statement work; it is the cumulative pattern of founder behaviour that makes the venture feel like something worth participating in, and it is what holds the team through periods when the compensation and infrastructure dimensions are stretched.
The specific African challenges, named
There are three challenges that recur in my experience of building teams across African contexts, and each has a specific operational response.
The first is the diaspora pull. Talented African operators often have credible options to leave the continent for mature-market roles paying significantly more in dollar-denominated terms. The pull is structural and not personal; it is a function of the global compensation arbitrage. The response is to acknowledge the pull honestly, rather than pretending it does not exist, and to design the team member’s situation in ways that compete on dimensions where the diaspora option is weaker. Specifically: meaningful work that they could not do in a junior role at a foreign company, autonomy that they would not get for years in a hierarchical foreign organisation, ownership of outcomes that would be diluted in a large team, and the personal connection to a place and a mission that the diaspora option does not offer. Some team members will leave anyway; the response is not to prevent every departure but to ensure that the ones who stay are doing so for substantive reasons that the venture can sustain.
The second is the currency tension. Compensation discussions in African markets often involve a currency dimension. Some team members want dollar-denominated compensation to insulate against local-currency volatility; others are comfortable with local currency. The venture’s revenue mix may not match the compensation request structure. The response is to design compensation transparently, to denominate at the level the venture can sustainably afford, and to communicate openly about the trade-offs each currency choice involves. Hidden complexity in compensation produces resentment when the volatility hits; explicit complexity that the team understands produces stable expectations.
The third is the founder-team gap that emerges as the venture scales. In the early years, the founder is in daily contact with every team member. As the team grows, the founder’s direct relationship with junior team members thins, and the team begins to see the founder primarily through senior intermediaries. The transition is structurally necessary but operationally risky. Junior team members lose their direct connection to the venture’s mission; senior intermediaries become the bottleneck for everything; the founder loses visibility into the team’s actual condition. The response is deliberate ritual: all-hands meetings where the founder is genuinely present and listening, structured opportunities for junior team members to interact with the founder, transparent communication that flows in both directions across the senior layer rather than through it. The work of maintaining founder-team connection across scale is unglamorous and recurring; it is also what prevents the venture’s culture from fragmenting into the layers that scale produces.
The Kose and Cafe Oldrock observations, briefly
I want to give two personal observations because grounding the abstract in real experience makes it actionable.
When the Kose driver app was being built, the team was small enough that I was personally involved in every architecture decision and every weekly sprint review. As the team has grown, my involvement has had to evolve: I am not in every code review, but I am in the strategic decisions about what the team is building and the conversations about who is being hired into senior roles. The discipline has been to remain meaningfully present at the right level rather than to either remain present at every level (impossible at scale) or to disappear entirely from team-level work (the typical founder mistake). The presence has had to evolve, and the evolution has required deliberate decisions about what to delegate and what to retain.
At Cafe Oldrock, the constraint has been different: the talent pool for hospitality staff in the relevant Harare market is genuinely small, and the staff turnover patterns of the hospitality industry are difficult. The discipline has been to invest in the staff’s development, to make Cafe Oldrock a place where staff who join develop their craft over years, and to accept that the venture is partly a training operation whose graduates may eventually go elsewhere. The investment in development costs the venture in immediate operational terms; the return has been a team whose tenure is meaningfully longer than the industry average, and whose competence in the work is one of the venture’s distinguishing assets.
In both cases, the disciplines are not original to me. The framing of “team-building under constraint” is what makes the disciplines feel different from generic team-building advice; the constraint itself shapes which disciplines matter, and the disciplines that work in a constrained environment are different from the disciplines that work in an abundant one.
The closing observation
The team you build is the venture you build. The Stay-Up phase ventures all share a particular team-building pattern: a founder who has invested years of personal attention in developing a small core team, designed multi-dimensional compensation that competes beyond base salary, made the mission specific and recurringly visible, and held the team through periods of pressure that should have lost them. The cumulative effect is a team whose capacity exceeds what the venture’s resources should allow, and the excess capacity is the venture’s strategic advantage.
If you are an African founder reading this and thinking about your team’s current state, the most useful diagnostic is to examine which of the four disciplines you are running consistently and which you have been neglecting. Most founders are running one or two well and skipping the others, and the skipped disciplines are the source of the team-related problems they are currently experiencing. The fix is rarely a single dramatic change; it is the steady investment in the discipline that has been undermaintained, sustained over months until the team’s condition shifts.
Build the team you can build. Hold the disciplines that produce the team that compounds. The constraint is real, the disciplines are demanding, and the ventures that emerge with thriving teams are the ones whose founders did the unglamorous work of building people, year after year, with the same patience that the rest of the venture’s compounding requires.
That is the framework. The team is not what you find through HR; the team is what you build through disciplines that the dominant writing does not adequately describe and that African founders have to develop largely without external models. The supporting pieces in this pillar go deeper into specific aspects of the work. This piece is the umbrella that connects them.
For the framework that explains why early-stage learning is the asset team-building should be developing, see The Sprouting Curve. For the cornerstone on the African capital realities that constrain team-building specifically, see Raising Your First Round in Africa. For the related fiduciary posture that connects how the founder treats the team to how the team treats customers, see The Founder’s Fiduciary Posture.
