Before the Multiyear Grant: A Term Sheet for a Ninety-Day Cameroon Pilot
Photo by Photo by Vincent Lockhart on Unsplash on Unsplash
US-based foundations, diaspora groups, and companies often arrive at a Cameroon partnership with a multiyear vision already sketched: a grant schedule, a program of work, a reporting calendar. The community organization may be equally eager to show what it can do. Yet the most useful first document is often smaller than either side expects. It is a term sheet for a bounded pilot—long enough to reveal how the partners make decisions, short enough to correct course without a public reckoning.
In 2026, that discipline matters. Travel is easier in some respects and still uneven; exchange rates move; community calendars fill with obligations that do not appear in a US logic model. A pilot should not be treated as a probationary test of one partner’s worth. It should be a structured first season in which both sides learn how the other works under real conditions.
Start with a Charter, Not a Promise
A pilot charter should state four things plainly: the problem the partners intend to address, the activities included, the activities explicitly excluded, and the period of performance. Ninety days is a practical starting point for many community projects, though a wet-season calendar may argue for a different window. The point is a definite end date, not an open-ended arrangement that drifts into a full program by inertia.
The charter should also say what the pilot is not. It is not a commitment to future funding. It does not create an entitlement to renewal. It does not make one partner the permanent supervisor of the other. Language of that kind may feel cautious, but it protects both sides from assumptions that harden before evidence arrives.
A useful clause describes the pilot as a joint learning period. That framing matters in Cameroon, where community organizations may have experienced funders who arrive with a fixed template and leave when the reporting becomes inconvenient. A charter that names mutual obligations—not only grantee obligations—signals a different posture.
Indicators That Fit the Work
Success indicators should be few, observable, and agreed before the pilot begins. A common mistake is to import a long list of metrics from a larger program design. A ninety-day pilot cannot credibly measure every outcome that a three-year grant might pursue.
Instead, the term sheet can separate indicators into three groups. The first covers delivery: for example, the number of community meetings held, the number of local suppliers paid, or the number of participants who complete a training cycle. The second covers process: whether decisions were made within agreed timeframes, whether funds reached the implementing account without avoidable delay, and whether documentation was complete enough for both partners to understand what happened. The third covers relationship quality: whether the check-ins occurred, whether problems were raised early, and whether both sides would recommend continuing.
Qualitative evidence deserves a place alongside counts. A short joint note after each check-in can record what worked, what created friction, and what each partner wants to adjust. For US audiences accustomed to dashboards, the term sheet should explain that these notes are not decoration. They are the record from which a renewal decision will be made.
A Pilot Budget with Room to Breathe
A pilot budget should be small enough to approve quickly and complete enough to avoid hidden costs. The usual temptation is to fund activities and leave coordination, transport, communications, and closeout to goodwill. That approach tends to burden the community partner most.
The budget can include a modest coordination stipend, reasonable local travel, mobile money or bank charges, data and communications costs, local procurement, a small contingency, and a closeout allocation. If the US partner requires an external audit, the cost should be stated rather than absorbed quietly by the community organization. If the pilot will use community labor or meeting space, the term sheet should say whether those contributions are valued in kind or treated as the community’s share.
A line for a short learning product is also worthwhile: a two- to five-page joint note, not a glossy report. The purpose is to capture decisions while they are fresh and to give both boards something concrete to review.
Check-Ins on the Calendar, Not in the Inbox
Mutual check-ins should be scheduled at the outset and treated as obligations, not optional calls. For a ninety-day pilot, three check-ins are often sufficient: an early operational call, a midpoint review, and a closing conversation. Each should have a short agenda, a named convener, and a written note circulated within a few days.
Time-zone governance deserves explicit attention. A standing slot that is convenient in Washington may be unreasonable in Yaoundé or Buea. Alternating meeting times, or rotating the convening partner, can distribute the burden. The term sheet should also identify who may speak for each organization and who must approve a change in scope.
Check-ins are not the same as formal decision gates. They are the working rhythm that makes the gates meaningful. If a problem emerges in week four, the partners should have a place to discuss it before it becomes a reason to end the pilot.
Decision Gates and a Graduation Standard
A decision gate is a scheduled moment when the partners decide whether to continue, adjust, or close. For a ninety-day pilot, a midpoint gate and a closing gate are usually enough. The term sheet should specify what evidence will be reviewed at each gate and who will make the decision.
A graduation standard can be simple: the pilot met its core delivery indicators, both partners completed their process obligations, and both sides agree that the working relationship is worth extending. That standard should be written before the pilot begins, when neither side is lobbying for a particular result.
If the answer is to continue, the partners should treat renewal as a new decision, with a revised scope and budget. If the answer is to adjust, the term sheet can allow a short extension for a defined purpose. If the answer is to stop, the exit terms should already be clear.
An Exit That Leaves the Relationship Intact
A no-blame exit option is not a sign of weak commitment. It is a sign that the partners have thought about risk honestly. The term sheet can state that either party may decline to proceed at a decision gate without penalty, provided that outstanding invoices are settled, assets are accounted for, data are handled according to the agreed rules, and a short learning note is completed.
The exit clause should also address public communication. Neither partner should describe the pilot as a failure or as a victim of the other. A neutral statement—that the pilot concluded and the partners are considering next steps—is usually sufficient. In small communities, reputational language travels quickly; the term sheet should protect the dignity of the local organization as carefully as it protects the funder’s board.
What the Pilot Should Produce
At the close of a well-designed pilot, the partners should have more than a report. They should have a tested decision-making rhythm, a clearer view of real costs, a record of what the community valued, and a shared answer to whether a larger program is warranted. They should also have a relationship that can survive a negative answer.
A pilot is not a trial of one partner by another. It is a bounded piece of joint work with written terms, scheduled reflection, and a dignified way to stop. For US–Cameroon partnerships in 2026, that modest structure may be the most useful grant of all: a short season of evidence before a long commitment.