Consulting that leaves
the capability with you.
Advisory and capacity building for NGOs, government bodies and development banks. We build the method inside your team, write it down so it survives staff turnover, and deploy the system in your own accounts from day one.
The last platform we built for a client had its build toolkit published, code included.
If nobody on your side has time to receive it, we will tell you on the call.
What the engagement gives you. Programme volume and client names sit further down, where they evidence capability instead of opening with our own output.
The engagement closed.
Nothing moved.
Three shapes of failed handover. Each ends with a satisfied final report and an organisation that cannot do the thing on its own.
The deliverable nobody can run
Two hundred pages of strategy, correct in every particular, and no answer to the only question your team has: what do I do on Monday. A method is a set of decisions someone has to make under pressure. A document that describes the decisions without stating the rules is a description of a capability rather than the capability.
The workshop that was a demonstration
Your team watched experienced people do the work well for three days. Everyone left impressed and nobody left able. Watching a thing done and having done a thing are separated by the part where you do it badly first, in front of someone who can correct you — and that part takes longer than a workshop.
The system in somebody else's name
The platform runs beautifully, on a licence held by the supplier, with hosting in their account and credentials in an inbox. Nothing was withheld deliberately. It just never got moved, and the day you need to move it is the day you are least able to negotiate.
The pattern underneath all three: transfer was treated as the last phase, and the last phase is the one that gets compressed when a programme runs late. Anything that has to happen at the end mostly does not happen.
Four things leave with you.
Only one of them is a document.
Each item below exists because a specific client kept it and used it after we had gone. Nothing here is a category of deliverable we could produce if asked.
We published the build,
including the code.
At the end of the World Bank programme the team prepared a practical toolkit describing how to build the platform — coding and technical details included — and made it publicly available so that anyone could create a similar one, or a better one.
That is in the client's own published report. It is also the most complete answer available to the question this page exists to answer.
Why we do it anyway
Publishing a build is commercially irrational in the short run and it is the only version of this promise that cannot be quietly walked back. A supplier who has published the method has no lever left to pull.
It also produces better work. Knowing that the technical detail will be read by strangers changes what gets written down, and what gets written down is the thing your team actually inherits.
What it does not mean
Your data, your participants and anything commercially sensitive stay yours and stay closed. What gets published is the method and the build, and only where the client agrees — on the Jedad programme that agreement is recorded in the report itself.
Where a client would rather nothing were published, nothing is. The handover is identical; it just stops at degree two.
Audit the last handover
you received.
Twelve checks, in the four places transfer usually fails. Think of the most recent engagement that closed on your side and tick what you actually got. Nothing is sent anywhere — the whole thing runs in this page.
0of 12
Tick what you were actually left with. Most engagements land between three and six, and the two that go missing first are almost always the system and the people.
Twelve checks, and we would not score twelve on every engagement we have run either. The list is what we contract against, which is a different claim from having always hit it.
Everyone says
“knowledge transfer.”
Ask what arrives.
Four ways to buy advisory work, sorted by what is on your side of the table when the contract ends.
Strategy consultancy
A document, and a good one.
Rigorous analysis, board-ready, and genuinely useful for a decision. What arrives is a recommendation. The capability to produce the next one stays with the firm, which is the business model rather than a failing.
Choose it if you need a decision made well once, and the next one is years away.
Staff augmentation
Hands now, nothing after.
Contractors sit inside your team and do the work. Fast, flexible and entirely dependent — when the contract ends, the throughput ends with it, and nothing was written down because nobody was paid to write.
Choose it if the constraint is genuinely capacity rather than capability.
Training provider
Knowledge without the system.
Your team learns the concepts on a course and returns to an organisation with no process, no templates and no time. The knowledge is real; the setting it needs is missing, which is why so much training evaporates in a quarter.
Choose it if the process already exists and the gap is genuinely individual skill.
Umbrella500
The method, the materials, the system, the people.
We do the work with your team rather than beside them, write the method down as we go, put the system in your name from the first deployment, and have one of your staff deliver before we leave.
Choose us if you will have to do this again and would rather do it yourselves.
The first three are honest businesses and we have been the fourth column on programmes where one of the other three would have been cheaper. If a decision is genuinely one-off, buy the document.
Handover starts
in week one.
Every phase below produces something your team keeps. There is no closing phase called transfer, because a closing phase is the one that gets compressed when the programme runs late.
A capability your team has never used under pressure is a document with your logo on it.
Four cases where
this fails.
Three of the four are about you rather than us, which is why they are worth reading before the call.
- Nobody on your side has the time. Capability transfer costs your team real hours during delivery rather than after it. If those hours are not protected in writing, you will pay us to build something excellent and inherit a dependency anyway.
- The decision is genuinely one-off. A merger, a one-time market entry, a single regulatory response. Buy the analysis from a firm that does it constantly and do not pay a premium to learn a method you will never use again.
- You need a name for the board. Some decisions need the cover of a brand the board already trusts. That is a legitimate thing to buy and we are not it.
- The real problem is that a decision has not been made. No amount of capability building substitutes for a leadership decision nobody wants to take. We have been hired into this twice and it does not work; the engagement becomes a way of postponing the meeting.
Throughout the collaborative process, Umbrella500 has demonstrated a keen understanding of the unique needs and requirements of SPARK's young entrepreneurs. Their receptiveness to feedback and their proactive approach to incorporating suggestions have been instrumental in refining the curriculum.
Halil Can EmreProject Manager · SPARK TürkiyeRead what he is actually describing: their feedback changing our curriculum, repeatedly, during the build. That is what co-design looks like from the client's side, and it is the mechanism by which the method ends up in their hands rather than ours.
Two people, and why
it is them.
Tareq Malas
Co-founder & COO · AI and strategySix years of senior consulting at McKinsey and a PhD in AI and data science. Tareq leads the advisory work and is responsible for engagements being grounded in data rather than opinion — which on a capacity-building engagement means the method has decision rules somebody can follow, and the measurement still runs after we leave.
Asmaa Baghdadi
Financial & operations managerFinancial reporting and operations management since 2019. Asmaa runs programme finances and coordinates delivery teams across countries — which is the unglamorous half of capacity building, and the reason a multi-country programme reports accurately and on time rather than accurately and late.
Where this has run: the World Bank in Jordan, SPARK in Türkiye and across MENA, and the Social Development Bank with MakanE in Saudi Arabia. The SPARK Innovation Hub engagement became a three-year partnership after launch, which is the only durable evidence that a handover held.
The ones that decide it.
How much of our team's time does this actually cost?
More than a supplier who is only delivering, and the difference is the point. Expect the named receiver to spend a meaningful share of a working week on it through the build phase, and expect at least one other person to deliver something live before we leave.
We put that in the proposal as a number, because the engagements that fail are the ones where it was implied and never budgeted.
What if the person we name leaves?
It happens, which is why the method is written for a stranger rather than for them. The test we apply to every handover document is whether someone who was not in the room could act on it. That test is also why the documents are duller than a consultancy deck and more useful six months later.
Will you really publish our method?
Only if you want it published. The World Bank toolkit was published because the client wanted the initiative to outlive its funding, and that decision was theirs. Your data, your participants and anything commercially sensitive stay closed in every case.
Can you do this remotely?
Partly. The method, the materials and the system transfer well remotely. The phase where your staff deliver and we correct them does not, in our experience, and we would rather concentrate the travel budget there than spread it across status meetings.
We have an existing supplier. Can you work alongside them?
Yes, and it is often the right shape — they keep delivering while we build the capability underneath. It needs saying out loud at the start, because a supplier who discovers midway that the engagement reduces their future scope becomes an obstacle, reasonably enough.
Do you work in Arabic?
Arabic is where we start. The team is in Amman, and handover documents are produced in the language the receiving team works in rather than translated once at the end.
How do we start?
A thirty-minute call, and the first question is who the receiver would be. If that name does not exist yet, finding it is worth more than anything we could sell you in the same month.
Tell us what your team
should be able to do.
Send the mandate and, if you know it, the name of the person who would own it afterwards. We answer in a day, usually less.
Or write directly: saleem.najjar@umbrella500.com