You've got a great idea. You've found a technical co-founder who can build it. You shake hands, agree to split everything 50/50, and you're off to the races.
Six months in, things get messy.
Your technical co-founder has stopped responding to messages. You've realized you have no idea who actually owns the code. You're not sure what you own versus what they own. Your business is running on infrastructure that's tied to their personal account. And you have no written agreement to back up any of the promises made at the beginning.
This scenario plays out more often than you'd think. Non-technical founders — product visionaries, business development experts, operators — often gloss over the legal and contractual side because it feels like paperwork getting in the way of real work. It's not. It's the thing that determines whether your business survives a co-founder conflict or disappears entirely.
Why This Matters More Than You Think
Here's the hard truth: a business built on a handshake and assumptions is one conflict away from collapse. And conflicts happen. Co-founders disagree on direction. Cash runs out. Someone gets a better offer. Life circumstances change. Someone has to leave.
When you're unprepared, that conflict doesn't just slow you down. It can destroy the entire company. Especially when IP — your product, your code, your customer data — is unclear who owns it.
For African businesses operating in regulatory environments like Nigeria's CAMA 2020 framework, this isn't just a startup formality. It's foundational to how your company will operate, how you'll raise capital, and how you'll protect yourself if things go wrong.
The Three Critical Areas
1. Equity — Who Owns What and When
This sounds simple. It's not. Equity gets complicated fast, and most founders misunderstand the fundamentals.
Founder equity is not free. When you and a co-founder agree to split the company 50/50, you're not splitting it immediately. You're agreeing to earn it over time. This is called vesting. Typically, equity vests over four years, with a one-year cliff. That means if a co-founder leaves after six months, they don't take their 25% of the company with them. The company remains whole, and that equity stays unallocated.
Why? Because equity is meant to reward people who actually stay and build. If you split everything equally at day one, your co-founder can walk away in month two with a 25% stake in your company, which they had nothing to do with after they left. The vesting schedule prevents that.
The cliff is non-negotiable. If your co-founder leaves before the cliff (usually one year), they typically get nothing. This is standard. It's not punitive; it's protective. It's saying: "You need to be seriously committed to actually build something with us."
Everyone should vest the same way. This is where non-technical founders often get burned. A technical co-founder might push for different terms — faster vesting, a smaller cliff, more equity — because they feel their contribution is immediate and technical while yours is "just business." Don't accept this. If you're both co-founders doing the work, your vesting schedules should be identical.
Dilution will happen. When you raise funding, your stake will get diluted. If you own 50% and raise Series A, you might own 40%. Understand this in advance. It's normal and acceptable, but you need to know it's coming.
Your vesting schedule should be in writing. Not in an email. Not in a message. In an actual co-founders' agreement signed by both parties.
2. IP — Who Owns the Code, the Product, the Ideas
This is where things get genuinely murky for non-technical founders, and it's also where conflicts cause the most damage.
Ownership of the code is not obvious. If your technical co-founder wrote the code, they might believe they own it. You might believe the company owns it. Nigerian law, under the Copyright Act and CAMA 2020, has provisions about work-for-hire and employee-created IP, but these can be interpreted different ways depending on how your business is structured. Without a clear agreement, this becomes a fight.
Your agreement needs to assign all IP to the company. Both founders should agree that any code written, any designs created, any processes developed — as part of the company — belongs to the company, not to individuals. This seems obvious until your technical co-founder is walking out the door and threatening to take their code with them.
It includes things beyond code. IP assignments often need to cover not just software but customer lists, business processes, documentation, trademarks, and methodologies. If you're building a product that depends on proprietary algorithms or specific integrations, these need to be covered.
Side projects and personal work need clarity too. If your technical co-founder is working on the company during the day but maintaining an open-source project on the side, whose time is that? What if they're advising another startup? What about work they did before joining? These boundaries need definition.
Future IP should be assigned in advance. Any IP created during their tenure as a co-founder — not just what exists today, but everything they create going forward — should belong to the company. This is standard in proper founder agreements.
3. Contracts — The Written Proof You Actually Discussed This
This is the part most founders skip because it feels expensive and slow. It's not. An undone contract isn't cheap; it's a bomb waiting to explode.
A co-founders' agreement is not optional. It's the document that says who owns what, what happens if someone leaves, what the roles and responsibilities are, and how disagreements get resolved. If you don't have one signed before you start, you're gambling.
It should cover vesting, IP assignment, and decision-making. You need to know: What happens to equity if someone leaves? Who decides on major business decisions? What requires agreement from all founders versus what one person can decide alone? When can someone be forced out? What happens to their equity if they're forced out for cause versus if they leave voluntarily?
Roles and time commitment matter. Your co-founder agreement should specify what each founder is responsible for. This prevents the situation where a founder is half-checked-out but still owns 50% of the equity and gets a vote on everything.
Non-compete and non-solicitation clauses are standard. Your agreement should include provisions preventing a founder from leaving and immediately starting a competing company or poaching your team. Again, this is standard and reasonable.
Get the details right the first time. You don't need a 40-page agreement. But you need one that addresses the core issues: equity structure and vesting, IP ownership, roles, what happens if someone leaves, decision-making authority, and how disputes get resolved.
Common Mistakes Non-Technical Founders Make
Assuming handshakes are binding. They're not. Not legally, not practically, and not when memory gets fuzzy. Write it down.
Letting a co-founder set all the terms. If your technical co-founder drafts the agreement, it's going to be skewed in their favor. Either hire a lawyer (worth it), or have both parties review and negotiate the terms. Equal founders should have roughly equal protection.
Not thinking about failure. It's awkward to discuss what happens if the partnership doesn't work out. Discuss it anyway. In writing. When things are still friendly. The moment to define these terms is before conflict, not during it.
Treating IP casually. "We'll figure out who owns what later" is a disaster waiting to happen. A technical founder walks away and claims they own the code. You try to hire a new technical founder, but they won't touch a codebase with unclear ownership. You're stuck.
Forgetting that regulations exist. In Nigeria, under CAMA 2020 and the Copyright Act, there are statutory requirements about how companies should handle IP and employee-created works. Your agreement should be consistent with these.
Doing too little or too much. An agreement that's too vague is useless. An agreement that's so rigid it requires a legal team to make any decision is paralyzing. Find the middle ground.
What You Actually Need to Do
Step one: Get a template or hire a lawyer. There are founder-friendly resources online, but for African businesses, it's often worth getting a Nigerian lawyer to review any agreement. The cost (often ₦150,000–₦500,000 for a co-founders' agreement) is trivial compared to the cost of a poorly structured partnership.
Step two: Have the hard conversations. What if one of you wants to leave in year two? What if you disagree on a major decision? What if one founder stops pulling their weight? Discuss these scenarios and get agreement on how they'd be handled.
Step three: Document everything. Write it down. Have both co-founders sign. Keep copies. And update it if circumstances change (new funding round, new co-founder joining, business pivot).
Step four: Continue communicating. An agreement isn't a set-and-forget document. Regular check-ins between co-founders — about how things are working, whether terms need adjusting, how equity is vesting — keep everyone aligned.
The Real Cost of Getting This Wrong
We've seen it happen. A company with a great product and real traction gets derailed because the founders can't agree on who owns the IP. A technical founder leaves and claims the code is theirs. A business development founder realizes they're not vesting at the same rate as the technical co-founder. A new investor wants to understand the cap table but can't because there's no documentation.
These aren't legal edge cases. They're common founder scenarios that derail otherwise viable companies.
Getting this right isn't about distrust. It's about clarity. It's about saying: "I trust you, and I want us both to be protected." The founders who do this early build stronger partnerships because they've actually talked through the hard stuff and written it down.
For Non-Technical Founders Specifically
If you're non-technical and partnering with a technical co-founder, you have leverage in these discussions. You're adding real value — vision, business development, fundraising, operations. Don't diminish that. A 50/50 split with identical vesting and equal protection is reasonable. You shouldn't accept anything less just because they're writing the code.
And if your technical co-founder resists putting a co-founders' agreement in place, that's a red flag. If they're confident in the partnership, they'll be happy to document it.
This isn't fun work. It's not the exciting part of building a company. But it's foundational. The businesses that survive co-founder transitions, conflicts, and pivots are the ones that handled the paperwork when things were still friendly.
Get it done early. Get it in writing. Get a second set of eyes on it. Your future self will thank you.
Easy World Techs Limited (RC: 1874001) has worked with founders building complex partnerships across African tech. If you're navigating co-founder agreements, IP concerns, or other foundational business questions, we can help.
