Stop Waiting for the Tender: Why African Enterprises Should Build Tech Capability Through Staff Augmentation and Their Own GCCs

A note before I start: my company, Redian Software, provides IT staff augmentation and helps enterprises set up Global Capability Centres. I have a stake in this debate, so weigh my arguments accordingly — and I've tried to be honest about when these models are the wrong choice.

It's a pattern anyone who has sold to, or worked inside, a large African enterprise will recognise.

A bank, insurer, telco or government agency decides it needs something important — a new mobile app, a modern core system, a data platform, an AI capability. A committee is formed. Requirements are written. A request for proposals goes out. Vendors respond. Evaluations, clarifications, negotiations and approvals follow.

Nine, twelve, sometimes eighteen months later, a contract is signed. By then the requirements have changed, the budget has been squeezed by currency movements, and the market has moved on. The vendor's team arrives, spends months learning how the business works — and when the contract ends, that knowledge walks out of the door with them.

Meanwhile, a short drive from head office, thousands of talented young engineers are looking for work.

My argument in this post is simple: African enterprises should stop treating technology capability as something they buy through tenders, and start treating it as something they build — using IT staff augmentation to move fast, and their own capability centres (GCCs) where the talent is, to build lasting strength.

Three ways to get technology work done

Before going further, it's worth being precise about the options.

	Project outsourcing (tender)	IT staff augmentation	Captive centre / GCC
What it is	A vendor delivers a defined project, often fixed-price	Skilled engineers join your team, managed by you, supplied by a partner	Your own technology centre, with your own employees, in a talent-rich location
Time to start	Months (procurement, contracting)	Weeks	3–9 months to set up; faster via a partner
Who controls the work	The vendor	You	You
Where knowledge stays	Largely with the vendor	With your team and processes	Fully in-house
Flexibility	Low — changes mean change requests	High — scale up or down	Medium — built for a long-term roadmap
Best for	Well-defined, non-core, one-off work	Speed, specialist skills, variable demand	Core, long-term, strategic capability

None of these is always right or always wrong. The problem is that many African enterprises default to the first column for almost everything — including work that is core to their future.

Why the tender-first model is failing

1. Procurement is slower than technology

Technology now changes in months. Procurement cycles in large organisations are often measured in years. The World Bank's own evaluations of the projects it finances show how deep this problem runs: in Western and Central Africa, about half of projects sign their first procurement contract only at the end of their first year, and around 45% run into significant processing issues along the way. Common bottlenecks include low-quality tender documents, slow bid evaluation and late contract signing.

Private enterprises aren't immune. Long RFP cycles, multiple approval layers and board-level sign-offs mean that the gap between "we need this" and "someone is working on it" is often longer than the life of the technology itself.

2. Knowledge leaves with the vendor

When an external vendor builds and runs your systems for years, it learns your business — your processes, your customers, your data and your weaknesses. As one recent analysis of African telecom operators put it, telcos risk handing vendors "the blueprint to their business."

At the end of the contract, you are left with software you don't fully understand and a choice between renewing with the same vendor or paying someone new to learn it all again. That's not a partnership; it's dependency.

3. Fixed scope doesn't fit a moving target

Fixed-price, fixed-scope contracts make sense when you know exactly what you need. For digital channels, AI, data and customer experience, you rarely do. Every change becomes a change request, every change request becomes a negotiation, and the relationship slowly becomes adversarial.

4. Money leaves the continent while local talent waits

Large technology contracts often go to foreign vendors, priced in dollars or euros, with delivery teams based abroad. Currency swings in recent years have made those contracts far more expensive in local terms. At the same time, Kenya alone sees 500,000 to 800,000 young people enter the labour market every year, and training programmes such as Nigeria's 3MTT and Ghana's One Million Coders are producing tens of thousands of newly skilled people who need work.

What leading enterprises are already doing

The most ambitious African companies have already started to change course.

Safaricom said in 2022 that it aimed to develop 70–80% of the technology it uses in-house, and hired around 400 developers that year. Its flagship M-PESA and mySafaricom apps are built and maintained by internal teams.
Banque Misr in Egypt built its digital bank in-house rather than through a partnership — keeping control of the customer relationship.
Standard Bank runs large engineering teams across the continent and in global hubs, building platforms rather than just buying them.

Look further afield and the scale of the model becomes clear. According to the Nasscom–Zinnov India GCC Landscape Report, India now hosts 2,117 Global Capability Centres employing around 2.36 million people, generating close to US$98 billion in revenue. More than 500 of the Forbes Global 2000 companies run operations there. Many of these centres began as cost-saving back offices. Today, many lead their parent companies' engineering, data and AI work.

Here's the point that is often missed: global companies went to India, Egypt, Morocco and South Africa because that's where the talent was. African enterprises can do exactly the same — within Africa.

The African GCC opportunity

Research firm Mordor Intelligence estimates the Middle East and Africa capability centre market at around US$20 billion in 2026, growing to over US$31 billion by 2031. Most of that is global multinationals setting up in Egypt, South Africa, Morocco and, increasingly, Kenya.

What's still rare is African enterprises building capability centres for themselves. Imagine:

A Nigerian bank running an engineering centre in Nairobi or Accra, drawing on talent it can't hire fast enough in Lagos.
A South African insurer building its data and actuarial technology team in Kenya.
A pan-African telco consolidating its digital engineering from a dozen country vendors into one captive centre that serves every market.
A group of regional banks sharing a GCC for common platforms such as payments, fraud and compliance.

The African Continental Free Trade Area — whose Digital Trade Protocol was adopted in 2024 — makes this kind of cross-border arrangement more realistic every year.

Staff augmentation: the fast lane

Building a GCC takes time. Staff augmentation doesn't.

With staff augmentation, a partner provides vetted engineers — developers, testers, data engineers, cloud and security specialists — who work inside your team, follow your processes and report to your managers. You keep control of the roadmap and the knowledge; the partner handles recruitment, employment, payroll and replacement.

It works best when you need to:

Start in weeks, not months, on a priority initiative.
Add skills you don't have, such as AI engineering, cloud migration or cybersecurity.
Flex capacity up for a launch and down afterwards.
Test a location before committing to a full centre.

The best staff augmentation relationships also transfer knowledge deliberately — pairing augmented engineers with your own staff so that capability grows inside the organisation, not outside it.

From augmentation to your own GCC

For most enterprises, the smartest path isn't choosing one model. It's a sequence:

Augment: bring in a small, high-quality team through a partner to deliver an urgent priority and learn what works.
Build a pod: grow that team into a stable, cross-functional unit with its own leads, working on core systems.
Build–Operate–Transfer (BOT): have a partner set up and run a dedicated centre under your brand — handling entity, office, hiring and compliance — with a clear option to take it over.
Own the GCC: transfer the centre, its people and its knowledge to your own organisation once it reaches scale.

This approach gets you moving immediately, reduces the risk of setting up in a new location, and ends with a capability you fully own.

When outsourcing is still the right answer

To be fair, traditional outsourcing still has its place. It makes sense for:

Commodity services such as infrastructure management, help desks or standard software licences.
Genuinely one-off projects with a clear, stable scope.
Highly specialised work you'll need only once, such as a specific regulatory implementation.
Organisations too small to manage an engineering team well.

And staff augmentation and GCCs come with their own risks: they need strong internal technology leadership, clear governance, careful data protection (under laws such as Kenya's Data Protection Act and Nigeria's Data Protection Act), and a plan to retain good people. An enterprise that can't manage engineers will struggle with any model.

Fixing procurement, not abolishing it

Good procurement protects organisations and taxpayers. The goal isn't to remove it; it's to design it for how technology actually works. A few practical changes make a huge difference:

Framework agreements and pre-qualified panels. Run one rigorous selection to approve a small panel of partners, then call off capacity in days rather than running a new tender each time. Modern procurement rules, including those based on the UNCITRAL Model Law, allow for this.
Rate cards instead of fixed scopes. Agree transparent rates for roles and skills, and pay for capacity and outcomes rather than guessing the full scope up front.
Multi-year capacity contracts with exit clauses. Give partners the stability to invest in your team, and yourself the freedom to leave if quality drops.
Knowledge-transfer obligations. Make documentation, pairing and handover measurable parts of every contract.
Delegated authority for small teams. Allow technology leaders to add or replace a few engineers without returning to the board.

What governments can do

Governments shape this market in two ways: as the biggest buyers of technology, and as policymakers.

Modernise public technology procurement with framework agreements, agile contracting and capacity-based models, so that ministries and state agencies can build digital services at the speed citizens expect.
Extend GCC and export incentives to domestic and intra-African enterprises, not just foreign multinationals. A Kenyan or Nigerian company building a capability centre that serves several African markets creates the same high-quality jobs.
Make cross-border talent mobility easier within Africa, through faster work permits and recognition of professional certifications, in line with the AfCFTA's goals.
Provide clear, stable rules on employment, tax and data protection for staff augmentation and GCC arrangements, so that enterprises can use them with confidence.
Link national skills programmes to employers, so that graduates of initiatives like Ajira, 3MTT and One Million Coders move directly into augmentation pools and capability centres.

A practical checklist for CEOs and CIOs

If you lead an African enterprise and want to move from buying capability to building it, start here:

Map your technology work into core (build it), important (augment it) and commodity (outsource it).
Pick one priority initiative and staff it with a small augmented team within 30 days.
Hire or appoint strong engineering leadership — the single biggest success factor for any in-house model.
Set up a framework agreement with two or three pre-qualified talent partners.
Choose a location strategy based on where the talent is, not just where head office is.
Plan a BOT or GCC roadmap for the capabilities you'll need for the next five years.
Measure what matters: time to start, delivery speed, quality, retention and knowledge retained — not just day rates.
Build a learning pipeline with universities and skills programmes so your centre grows its own talent.

Final thought

For decades, global companies have built their technology capability in places where talent was plentiful and ambitious. Africa's enterprises now have the same opportunity on their own doorstep.

Every month spent waiting for a tender to close is a month a competitor spends building. Every contract that leaves knowledge with a vendor is capability that could have stayed at home. And every young African engineer who can't find work is talent that an African enterprise could have used.

The future belongs to organisations that own their technology capability. Staff augmentation is the fastest way to start. A capability centre where the talent is — in Nairobi, Lagos, Accra, Cape Town, Cairo or Casablanca — is the way to make it last.

How is your organisation approaching this? Are you still tender-first, or are you building in-house? I'd like to hear what's working — and what isn't — in the comments.

Sources: World Bank Independent Evaluation Group, Making Procurement Work Better; Nasscom–Zinnov India GCC Landscape Report (FY2026); Mordor Intelligence, Middle East and Africa Global Capability Centers Market (2026); reporting on Safaricom's in-house engineering strategy by Business Daily and Techweez; Briter on Banque Misr's in-house digital bank; BusinessDay (Nigeria) on African telcos and vendor dependence; Kenya National Bureau of Statistics and national labour-market reporting; Nigeria's 3MTT programme and Ghana's One Million Coders programme; UNCITRAL Model Law on Public Procurement (2011); African Union, AfCFTA Protocol on Digital Trade (2024).