Design First or Local Partner First? Reflections on Proposal Architecture
By Lucy Njue
Where Does Local Partner Engagement Belong in Proposal Design?
In one recent multi-country proposal, the language strongly emphasised localisation and locally led delivery. Yet, at the point of submission, the organisations expected to deliver that vision had only just been brought into the conversation!
Because in large institutional funding processes, technical design receives intense scrutiny. We refine indicators. We debate assumptions. We pressure-test risk matrices. We negotiate budgets to the decimal.
Yet, one question often receives far less deliberate attention:
At what point – and how – should partners be meaningfully engaged in multi-country, multi-partner proposals?
This question has become particularly real for me through multiple complex, multi-country proposal processes I have been involved in over the years, in different roles.
Often, funding windows are anticipated. Internal concept discussions may already be underway. Country teams might begin shaping draft budgets. Elements of the logframe can begin to take shape.
In some cases, consortium roles among lead organisations are clarified early, while the identification of local implementing partners in each country context comes later in the process.
Engagement with those local actors may occur only in the final stretch before submission.
By that point, elements of the technical and financial architecture can already be largely pre-structured, including indicative staffing models and operational assumptions, before substantive co-design conversations take place.
This can create an important tension: proposals may emphasise localisation and locally led delivery, yet the local actors who will ultimately carry implementation responsibility may not have had sufficient opportunity to shape the design from the outset.
The intention is often not exclusion, but efficiency. Teams want coherent, competitive submissions.
But the experiences left me reflecting on something deeper:
If partnership is central to delivery, when should it truly begin?
The Practical Tension
In highly competitive funding environments, there is understandable pressure to:
- Protect technical coherence.
- Move quickly once calls are released.
- Control narrative alignment.
- Avoid complex coordination too early.
A sequencing logic I have seen is:
- “Design first. Then identify the best-fit partners.”
- And in some contexts, that may work.
But in predictable funding ecosystems, where calls are cyclical and thematically anticipated, I increasingly question whether this sequencing serves long-term delivery.
What I Observed in Practice
When partners enter late into an already structured proposal, several dynamics can surface:
1. Budget Assumptions That Need Reworking
Even when developed with good intentions, centrally drafted budgets may:
- Underestimate contextual salary realities.
- Constrain administrative cost recovery.
- Overlook operational nuances.
- Create cash flow pressure once implementation begins.
Time pressure at submission stage often limits meaningful recalibration.
2. Log frames That Require Adjustment Post-Award
If partners were not involved in early indicator selection and activity sequencing, post-award revisions may be required to align with contextual realities.
These are sometimes framed as “implementation adjustments.”
But they often reflect design that was not jointly shaped.
3. Compressed Governance Conversations
Due diligence, safeguarding alignment, financial systems reviews, procurement harmonisation — these require more than days to do well.
When timelines are tight, governance checks can become procedural rather than strategic.
4. Subtle Power Imbalances
When partners join a largely fixed framework, the implicit question becomes:
“Can you deliver this design?”
Rather than:
“How should we design this together?”
That distinction influences ownership, accountability, and long-term institutional strengthening.
So When Should Engagement Begin?
In my view, particularly in multi-country mechanisms where calls are predictable, meaningful engagement should begin at the concept exploration stage, not after the technical architecture is complete.
This does not mean drafting full proposals months in advance.
It means:
- Early ecosystem mapping.
- Pre-call dialogue about comparative advantage.
- Preliminary conversations on cost structures and indirect recovery.
- Joint reflection on risk appetite and governance expectations.
- Co-shaping an outline theory of change before submission pressure intensifies.
When the call is finally released, the consortium is refining a jointly shaped concept and not retrofitting partnership into an existing structure.
Reflection
It is important to acknowledge that many organisations are already investing deeply in equitable partnership models and early engagement processes. There is no single universal approach.
The pressures of donor timelines, competitiveness, and internal coordination are real. This reflection is not about assigning fault. It is about asking a structural question:
If we believe partnerships are central to delivery, resilience, and sustainability, why do we sometimes treat them as final-stage alignments rather than foundational architecture?
A Sustainability Lens
Institutional sustainability is not built at the implementation stage. It begins at design.
Resilient programmes require resilient institutions. Resilient institutions require equitable partnerships. Equitable partnerships require time and intentional sequencing.
Perhaps the more important question is not whether we engage partners.
It is whether we engage them early enough to shape what we are asking them to deliver.
(Lucy Njue is a Kenyan fundraising and sustainability strategist, and Founder and Executive Director of Realtime Insights)
