Family on the Ground Is Not an Operating System
Davinia | Founder, Build From Abroad · 14 September 2026
When you tell people you want to build a business in Nigeria from abroad, one of the first questions is usually:
“Who do you have on the ground?”
It is a sensible question. A reliable relative in Nigeria can solve problems quickly, understand the local context and notice things that are difficult to see from London, Toronto or Atlanta.
But “I have family on the ground” is not an operating plan.
A relative can be honest, capable and deeply committed to your success. They can still misunderstand the job because the job was never written down clearly.
That is how an ordinary business problem becomes a family problem. The founder hears carelessness. The relative hears mistrust. Both people begin defending their character when they should be examining the role.
Working with family is not automatically the risky part. The risky part is asking somebody you love to run a role that depends on interpretation.
The hidden risk is interpretation
Imagine your cousin is coordinating supplier deliveries for the business.
You expect every short delivery to be recorded on the day it arrives. Your cousin believes only serious shortages need to be mentioned because small discrepancies can be corrected with the supplier later.
At the end of the month, the stock count and the cash position do not match your expectations.
You feel information was withheld. Your cousin feels unfairly accused after spending weeks fixing problems without bothering you.
Nobody needed to be dishonest for the arrangement to fail. The two of you simply never agreed what counted as an exception, what had to be recorded or when the founder needed to know.
Good intentions cannot resolve an instruction that was never made explicit.
Build a one-page family operator agreement
Before the work begins, write down four things on one page.
1. Outcome
State the result the person owns.
“Manage stock” is vague.
“Record every delivery, update the stock sheet and flag any difference on the day it arrives” is something both people can recognise.
The outcome should describe what good work produces, not simply list activities.
2. Boundary
Write down where the role begins and ends.
This is not about creating a complicated policy. It is about removing the decisions most likely to cause confusion.
The boundary might cover the maximum amount they can spend, the changes they can make to an order or the promises they can make to a customer.
It should also state what remains outside the role.
3. Proof
Agree what makes the work visible.
This may include payment records, a dated stock sheet, delivery confirmation or a short list of exceptions.
The goal is not to demand constant evidence. It is to decide in advance which facts the founder needs in order to understand the business without chasing for updates.
4. Escalation
Define the problem that must reach you and how quickly.
A late delivery may belong in the Friday update. A missing payment or safety issue may need an immediate call.
Escalation is not failure. It is part of the job. The operator should not have to guess which problems the founder would consider urgent.
Make the weekly update predictable
A useful update can be brief. What matters is that it arrives at the same time and shows the same essential information every week.
A five-line Friday update might cover:
- sales received;
- money spent;
- stock or delivery problems;
- customer issues;
- the decision that needs the founder.
Use the same order every week.
A predictable format makes changes easier to spot and makes it harder for an important exception to disappear inside a long WhatsApp conversation.
Separate correction from character
Family relationships carry history, loyalty and expectations that do not disappear when business begins. That makes clear feedback more important, not less.
When something goes wrong, return to the written agreement before judging the person.
Was the expected result clear?
Was the boundary understood?
Was the required proof agreed?
Did the issue meet the escalation rule?
Clear instructions do not excuse poor performance. They help both people distinguish poor performance from poor instruction.
That distinction protects the founder from avoiding a necessary conversation. It also protects the relative from being blamed for expectations they were never given.
Ask these questions before they start
Before a relative joins the business, ask:
- What result will they own?
- Where does their authority begin and end?
- What proof will make the work visible?
- Which problems must be escalated?
- When and how will you review the arrangement together?
If those answers feel uncomfortable to discuss, that is useful information. The business should surface the difficult conversation before money, customers and family expectations make it harder.
Family support can be a genuine advantage. Give it a role clear enough to protect the work and a reporting rhythm strong enough to protect the relationship.
The Build From Abroad Book + Starter Kit helps diaspora founders turn ideas, roles and risks into a practical plan before the commitment becomes expensive.
