Remote work for African startups: pay, taxes, time zones

You've just hired a brilliant backend engineer in Kano. Two weeks later, your finance person asks whether you're supposed to register them as a contractor in Nigeria, Ghana, or your own country. Your HR tool doesn't support NGN payroll. And nobody's agreed on meeting times yet. This is the reality most African startup founders face when they go remote — and it's fixable, but only if you plan ahead.

Building a distributed engineering team across Africa is cheaper than hiring in San Francisco, faster than waiting for local talent in any single city, and often better quality than outsourcing to agencies. But the compliance, tax, and operational friction is real. This guide walks you through the actual decisions you need to make: which payment platforms work, how to structure employment correctly, what your tax obligations really are, and how to stop 9am standups happening at midnight for half your team.

We've worked with dozens of founders at LaunchPad building remote teams across Lagos, Accra, Nairobi, and Kigali. Most of the mistakes are preventable. Most of the platforms actually work. The tax situation is less clear than you'd like, but it's navigable.

The payment platform question: Deel, Wise, or local rails

You need to move money to your team every month. Your options are narrower than they look.

Deel Africa is the obvious choice for most startups. They handle payroll for 150+ countries including Nigeria, Ghana, Kenya, and Uganda. You pay Deel in USD or GBP (they take a cut — typically 2–8% depending on volume), and they disburse in local currency to your team members' bank accounts. They handle tax withholding in some jurisdictions, though this varies by country. The platform integrates with your HRIS, supports both employees and contractors, and the dashboard is actually usable. For a team of 5–20 people, this costs £50–£150 per month in fees on top of the payroll itself. Most founders we speak to start here.

The catch: Deel's tax handling in Nigeria is incomplete. They'll withhold PAYE (Pay As You Earn) if you're registered as an employer with the FIRS (Federal Inland Revenue Service), but you still need to file your own returns. They don't handle state taxes in Nigeria, which technically exist but are rarely enforced for remote workers. This is a grey area — more on that below.

Wise for Business (formerly TransferWise) is cheaper for the actual transfer but requires you to handle payroll yourself. You move money to Wise, they convert it at real rates, and you distribute to local accounts. No withholding, no compliance handling. This works if you're small (under 5 people) or if you're genuinely treating people as independent contractors and they're handling their own tax. The transfer fees are genuinely low — typically 1–2% — but you're doing the admin yourself. Wise is solid infrastructure; the problem is it puts all the compliance burden on you.

Local payment rails — Paystack Payouts, Flutterwave Payouts, or direct bank transfers — are worth considering if your team is entirely in one country and you have a local bank account there. Paystack and Flutterwave both offer bulk payout services. The rates are competitive (1–2% per transaction) and the money arrives same-day or next-day. The downside: you need a local entity or bank account to send from, which most early-stage foreign founders don't have. If you're a Nigerian founder paying Nigerian engineers, this is genuinely the cheapest option.

For most distributed teams, Deel is the pragmatic choice because it centralises the compliance questions (even if it doesn't answer all of them) and it's designed for exactly your use case. Wise works if you're disciplined about tax withholding on your end.

Employment vs. contractor: the legal structure that matters

This is where most founders get stuck, because the answer depends on three things: your country, their country, and how much you want to sleep at night.

Nigeria's position is unclear. There is no explicit law prohibiting remote work or remote employment. The Employment and Wages Act, 2019 doesn't distinguish between local and remote workers. In practice, if you employ someone in Nigeria (even if you're based abroad), you have employer obligations: PAYE withholding, pension contributions (8% employer, 8% employee to the PENCOM scheme), and theoretically registration with the FIRS. The CBN has not published specific guidance on remote work taxation, which means you're in a grey zone. Most startups we know are doing one of two things: (1) treating remote Nigerian staff as regular employees, registering with FIRS, and withholding taxes through Deel or manually, or (2) treating them as contractors and hoping the FIRS doesn't audit. Neither is ideal.

Ghana, Kenya, and Uganda have similar ambiguity. Ghana's tax authority (GRA) is relatively hands-off on remote work. Kenya's KRA has been more aggressive about tracking digital economy income. Uganda is unclear. The practical answer: if you're hiring people in these countries as employees, you should assume you have tax obligations. If you're treating them as contractors, get a written contract that says they're responsible for their own taxes, and ideally have them register as self-employed with their local tax authority.

The safest approach: treat remote hires as employees if they're working full-time for you, structured as if they were local. Use Deel or a similar platform to handle withholding. This costs a bit more but eliminates the audit risk. If someone is part-time or project-based, contractor status is more defensible, but still document it properly.

One more thing: check whether your own country (if you're foreign) has tax treaties with the countries where your team is based. Most do. These treaties usually prevent double taxation and clarify where employment income is taxed. The US-Nigeria tax treaty, for example, says employment income is taxed in the country where the work is performed. This means a Nigerian remote worker pays tax in Nigeria, not the US, even if their employer is American. This actually simplifies things — you're not trying to navigate two tax systems simultaneously.

Tax withholding and compliance: what you actually owe

Let's be concrete. You're a founder in London. You hire an engineer in Lagos at ₦1.2m per month (roughly £600). What do you owe.

PAYE withholding: If they're an employee, you must withhold PAYE tax. In Nigeria, PAYE rates are progressive, ranging from 1% to 24% depending on income. For ₦1.2m per month, the rate is roughly 12–14%. So you withhold ₦150–170k and remit it to the FIRS. Deel will do this automatically if you're registered, or you can do it manually and file monthly returns.

Pension: If they're an employee, you contribute 8% to their PENCOM account (they contribute 8% from their salary). That's ₦96k per month from you, ₦96k from their salary.

VAT: If you're a service company (software, consulting, etc.), you may owe VAT on services rendered, but this is complex and depends on your own jurisdiction and whether you're VAT-registered. Most early-stage startups ignore this until they're larger.

State tax: Nigeria has state income taxes in theory, but they're rarely enforced for remote workers and Deel doesn't handle them. Don't stress about this unless you have 20+ employees.

Your own tax: You also owe corporate tax on the profit you make. This is separate from payroll tax. If you're a UK company, you owe UK corporation tax on worldwide income. If you're a Nigerian company, you owe Nigerian corporation tax. Again, tax treaties prevent double taxation, but you need to file in both places if you're operating across borders.

In practice: Most startups use Deel, which handles PAYE and pension withholding in Nigeria if you're registered with FIRS. You still need to file your own corporate tax returns. If you're not registered with FIRS yet, Deel can help you register, or you can do it yourself online (the FIRS has an online portal). The process takes a few weeks.

The honest answer: tax compliance for remote teams is a grey area in most African countries, and you should talk to a local accountant before you hire your first person. A good accountant in Lagos or Accra costs £50–150 per month and will save you from expensive mistakes. This is not optional if you're serious.

Time zones: the operational reality

You're in London. Your engineer is in Lagos (5 hours ahead). Your designer is in Nairobi (3 hours ahead). Your QA is in Kigali (2 hours ahead). How do you actually work together.

The answer is: you don't have synchronous overlap on everything, and that's fine if you structure for it.

Synchronous time (real-time collaboration):

• Lagos and Nairobi overlap by about 2 hours: 1pm–3pm Lagos time, 3pm–5pm Nairobi time. This is your window for standups, pair programming, and urgent meetings.
• If you're in London, you have zero overlap with Lagos in the morning and a 1–2 hour window in the afternoon (4pm–6pm London time is 9pm–11pm Lagos time, which is rough but doable for important meetings).
• Kigali and Lagos have 1 hour overlap. Kigali and London have no morning overlap.

Asynchronous work (the bulk of it):

• Document everything. Decisions, architecture, design specs, deployment procedures. Written English. This is non-negotiable.
• Use GitHub issues, Slack threads, and Loom videos for code review and feedback. Don't expect real-time responses.
• Have a daily standup in written form (Slack thread or Asana) that people fill in async. No 9am call.
• Plan for 24–48 hour turnaround on feedback, not 1 hour.

Practical schedule:

• Morning (London): You work on strategy, planning, async feedback to the team. They're asleep or just waking up.
• Midday (London): Your Lagos team is online and productive. Nairobi is online. This is your overlap window.
• Afternoon (London): You're in meetings or deep work. Your team is in their afternoon, still productive.
• Evening (London): You're done. Your team is in their evening, wrapping up or already offline.

This actually works better than you'd think. The constraint forces you to be more deliberate about communication, which makes you better.

Practical tools:

• Slack for async communication and quick questions. Set expectations: no expectation of immediate response.
• GitHub for code review. Async by design.
• Loom for video explanations. Much faster than writing 500 words.
• Figma for design collaboration. Real-time or async, both work.
• Notion or Confluence for documentation. Single source of truth.
• Zoom for the 1–2 hour overlap window. Use it for standups, architecture discussions, and relationship-building.

The mistake: trying to run synchronous standups across time zones. If your standup is 9am Lagos time, it's 4am London time or 11pm Nairobi time. Someone is always miserable. Don't do this. Write standups instead.

Compensation: paying fairly across regions

You want to pay fairly. But "fair" is complicated when you're hiring across Lagos, Nairobi, Accra, and Kigali, all of which have different costs of living, salary expectations, and talent density.

The common mistake: paying everyone the same USD amount. This is actually unfair. A senior engineer in Lagos earning $2000/month is earning more than 95% of the population and is probably overcompensated. The same engineer in Nairobi might be undercompensated. You need a regional approach.

The framework:

1. Define your role and seniority level clearly. Junior backend engineer. Senior full-stack. Staff engineer. Be specific.
2. Research local market rates. Look at job boards (LinkedIn, Andela, Toptal), ask founders, check /resources/engineering-comp-2026 for 2026 benchmarks. Rates vary: Lagos senior engineers typically command ₦1.5m–₦2.5m per month (roughly $1000–1700 USD). Nairobi is similar. Kigali is lower, around $800–1200 for senior roles.
3. Set a band, not a fixed number. For a senior backend engineer: Lagos ₦1.5m–₦2m, Nairobi KES 150k–180k, Kigali $900–1100. This gives you flexibility and accounts for experience.
4. Pay in local currency. This removes FX risk for your employee and shows you're serious about the region. If you're paying in USD, you're essentially asking them to manage currency risk.
5. Include benefits. Health insurance, laptop, internet stipend. These matter more in Africa than in the US. A ₦15k/month internet stipend is cheap for you and meaningful for them.

For more detailed guidance, read /resources/engineering-comp-2026 and /resources/hire-engineers-naija.

Equity: If you're offering equity, be aware that most African countries don't have mature secondary markets for startup equity. It's less of a draw than cash. Some founders are explicit: "We're paying 20% below market rate but offering 0.5% equity." This is honest. Others try to sweeten equity without being clear about the tradeoff. Be clear.

Building and retaining your remote engineering team

Hiring is one thing. Keeping people is another.

Remote work in Africa has a specific retention challenge: your team members are constantly getting poached by better-paying companies, often foreign. A senior engineer in Lagos who's proven they can work with a distributed team is suddenly attractive to US startups willing to pay 2–3x more. This happens fast.

What actually keeps people:

1. Clarity about growth. Can they become a staff engineer? A tech lead? A manager? Remote work can feel like a dead end if there's no ladder. Be explicit about career progression.
2. Autonomy and interesting work. Remote engineers often have more autonomy than office engineers. Use this as a draw. "You'll own the entire payment system" is more powerful than "You'll work on the backend team."
3. Competitive pay, not maximum pay. You don't need to pay San Francisco rates, but you need to pay top of market locally. If you're 30% below market rate, you'll lose people.
4. Predictable, calm work. Startups are chaotic. Remote startups are even more chaotic because communication is harder. If you can offer a team that ships regularly, has clear priorities, and doesn't have all-hands crisis meetings every week, you retain people.
5. Genuine remote culture. Some founders hire remote but still expect people to be online 9–5 their time. This defeats the point. If you hire someone in Lagos, respect that they're in Lagos. Flexible hours, async communication, trust-based management.

For a deeper dive, see /resources/engineering-team-naija.

The infrastructure: tools and processes

You can't run a distributed engineering team on Slack and email. You need systems.

Version control and CI/CD:

• GitHub or GitLab. Non-negotiable. Make sure your CI/CD pipeline is solid so that engineers don't have to wait for manual deploys. Fast feedback loops matter more in remote setups.

Monitoring and observability:

• Datadog, New Relic, or similar. If something breaks at 3am, you need to know immediately, and your team needs to be able to debug without being in the same room.

Documentation:

• Confluence, Notion, or Gitbook. Document your architecture, deployment procedures, onboarding, and decision-making. This is your institutional memory.

Project management:

• Asana, Linear, or Jira. Depends on your preference. The key is that everyone knows what's being worked on and why.

Communication:

• Slack for daily communication. Consider Slack channels by time zone so that people in the same region can have focused conversations.
• Email for anything that needs a record.

Hiring and onboarding:

• Lever or Greenhouse for recruiting. Notion or a wiki for onboarding. First week should be fully documented and asynchronous.

Common mistakes and how to avoid them

Mistake 1: Hiring without a written contract. You think it's informal, they think it's permanent. Write a contract that specifies: role, compensation, benefits, notice period, confidentiality, IP assignment. Use a template from a local lawyer, not from the internet.

Mistake 2: Not registering with tax authorities. You think it's too complicated. Then you get audited and owe back taxes plus penalties. Spend a weekend registering with FIRS or your local equivalent. It's not that hard.

Mistake 3: Mixing time zones without a system. You end up with 9am standups that are 4am for half your team. Write standups instead.

Mistake 4: Paying in USD without a plan for currency fluctuation. The naira devalues, your engineer's salary drops 20% in real terms, they leave. Pay in local currency and absorb the FX risk yourself.

Mistake 5: Hiring fast and onboarding slow. You bring someone on, they wait a week to get access to GitHub, another week to understand the architecture, and they're already considering other offers. Have an onboarding checklist ready before day one.

FAQ

Q: Do I need to register my company in Nigeria if I'm hiring remote engineers there? A: Not necessarily. If you're a foreign company hiring Nigerian employees, you technically need to register with FIRS and withhold PAYE. If you're treating them as contractors, the rules are less clear. Use a platform like Deel that handles this, or talk to a Nigerian accountant before you hire.

Q: Can I pay my remote team in USD? A: Yes, but it's risky for them. If the naira devalues 15%, their salary drops 15% in local purchasing power. Most teams prefer local currency. If you must pay in USD, make it explicit in the contract and consider a cost-of-living adjustment clause.

Q: What's the cheapest way to pay a remote team across Africa? A: Wise for Business if you're handling withholding yourself, or local payment rails (Paystack, Flutterwave) if your team is in one country. Deel if you want compliance handled for you. The difference is usually 1–2% in fees, so the choice depends on your comfort with tax compliance.

Q: How do I handle time zones with a distributed team? A: Async communication is your friend. Write standups instead of calling. Use Loom for video explanations. Have a 1–2 hour overlap window for important meetings. Respect that your team is in different places.

Q: How much should I pay a senior engineer in Lagos vs. Nairobi? A: Lagos and Nairobi are roughly equivalent: ₦1.5m–₦2.5m per month in Lagos, KES 150k–200k in Nairobi. Both are around $1000–1700 USD at current rates. Kigali is lower: $800–1200. Use local job boards and ask other founders for current rates. See /resources/engineering-comp-2026 for benchmarks.

What to do next

1. If you're about to hire your first remote engineer: Read /resources/hire-engineers-naija for specific sourcing and negotiation tactics. Then set up a Deel account and talk to a local accountant about tax registration.

2. If you're scaling a remote team: Check /resources/engineering-team-naija for retention strategies and team structure. Make sure your compensation is competitive by reviewing /resources/engineering-comp-2026.

3. If you're unsure about compensation: Use /resources/engineering-comp-2026 to benchmark your offers. Pay top of market locally, not San Francisco rates, and you'll retain people longer.