A family foundation, a pooled fund, a community foundation and an intermediary funder all manage many partners at once. They need to decide, monitor and learn across them without burying anyone in reporting. This playbook helps you find your model, the information your team needs and the smallest useful system to begin with.
Many organisations combine two or three. Start with the closest match, then borrow only the parts that solve a real problem.
You fund a portfolio of nonprofits through open calls or invitation, and manage each grant through its lifecycle.
You fund toward a defined goal across several partners, places or themes, and judge the portfolio as a whole.
Several funders put money into one vehicle, and a lead or intermediary manages the grantees.
You receive funds and pass them to smaller organisations, often with capacity support and compliance checks.
You manage donors' funds and help them give, locally or across borders.
You fund against results, through loans, equity or payments tied to outcomes.
Not sure which one you are? Bring one tracker and describe a normal month. The model usually becomes clear quickly.
These come up in almost every first conversation we have with foundation teams.
"Our grantees send us forty different reports."
Each grant has its own template, so comparing two partners means rebuilding both by hand.
"A programme officer left, and so did the history."
Why we funded them, what we promised and what went wrong sat in one person's inbox.
"The board wants one number for the portfolio."
Grantees count different things, so the total adds up to something we cannot defend.
"Our grantees spend more time reporting than doing."
We ask for everything because we do not yet know what we will use.
Funding models differ, but most grants follow this path. Use it to see where your records should connect and where they usually break.
Open calls, invitations and referrals, then a first screening.
Check legal status, governance, finances and safeguarding.
Grant agreement, budget and tranche schedule.
Reports, calls, site visits and capacity support.
Compare grantees, themes and strategies.
Decide on renewal, scale-up or closeout.
Choose the parts that match how your foundation actually works. Most funders need a focused combination, not every module.
One profile per organisation across calls, grants and years, with due-diligence status.
Budgets, conditions, instalments, approvals and amendments.
Due dates, reminders and templates sized to the grant, with grantees reporting in one place.
Grants by theme, place and strategy, with indicators linked to outcomes.
A shared dictionary, with what grantees report kept apart from what has been verified.
Multi-currency grants, foreign-funds rules and per-contributor reporting where funds are pooled.
A foundation, a pooled fund and an intermediary all manage many partners at once. These short reads cover what to collect and protect, what to connect to, what goes wrong and what success means for funders.
Rule of thumb. A foundation needs to see across many partners without making each one report on everything. Collect what a decision needs, agree definitions with grantees, and keep what grantees report apart from what you have verified.
Rules differ by country and by the source of the funds. We confirm what applies to you in the first conversation, and we use the equivalent in your country.
What goes wrongEvery grantee fills a different long form and nobody reads most of it.
How it is designed outA short core template, extra fields only where a decision needs them, and grantees can see what happened to their reports.
What goes wrongUnlike indicators are summed into one impact figure.
How it is designed outRoll-ups only for agreed definitions. Everything else is shown side by side, with context.
What goes wrongA co-funder or consultant receives raw partner data.
How it is designed outSharing rules set for each grant, contributor-specific views in pooled funds, and an access log.
What goes wrongA programme officer leaves and the reasons behind a grant go with them.
How it is designed outDecision notes, conversations and visit records sit on the grantee's record, visible to the team.
Funders at the same table ask different things of the same data. Start from the question the person will ask.
Which grantees need a call this month, and what did we agree last time?
Watch outA dashboard of grants says little about the relationship.
Is the portfolio moving us toward our goal, and what should we change?
Watch outSumming unlike indicators gives a number nobody can interpret.
What do you need from us, why, and what happens to it?
Watch outHeavier forms for smaller organisations make funding less fair.
Foundations set their own cycle. Many run an open call once or twice a year, with board decisions a quarter later. We map yours at the start.
Most AI projects stall because the records underneath are messy. So we work in a fixed order.
Every field has to earn its place by helping someone decide something. If nobody uses it, we don't collect it.
A system people avoid is worse than a spreadsheet. We design around the grant officer, the finance lead and the grantee.
On clean, connected records, AI can read long documents, draft summaries and flag what needs attention. A person always checks.
Where you start depends on where you are. If your records are already in good shape, we can move to AI quickly. If they are in spreadsheets and inboxes, we start there, and we don't start from zero.
Most systems launch in three to four months. The timeline moves with the number of programmes and roles, how messy the old data is, and how many tools need connecting.
Tell us where the work gets stuck today. Spreadsheets, notebooks, WhatsApp groups, all of it.
You show us how the programme runs. We'll tell you straight if you need a new system, a better workflow or nothing at all.
We map how your programme works, talk to the people who'll use it, review the tools you use today and hand you a System Blueprint, a clear plan of what we'll build.
Working screens every 2 to 4 weeks, tested by your field team in your own terms. We clean up your old spreadsheets and move them across.
Field training and launch, then 30 to 60 days of close support. After that, the system keeps changing as your programmes do.
We connect to your survey app (SurveyCTO, ODK or Kobo), BigQuery or Postgres, WhatsApp, your accounting software, grant portals and CRM, rather than replacing what already works. Zoho licences sit in your organisation's name, and everything exports whenever you want it.
The questions your finance head and IT lead will ask, answered before the call.
Zoho licences are bought in your organisation's name and hosted in the Zoho data centre region you choose, including India. We work inside your account.
Every record exports to Excel or CSV whenever you want, including the day you stop working with us. You're not locked in to us for support either.
Each person sees only the records their role needs. Applicant due-diligence files and bank details are visible only to the team that decides and the finance lead. Pooled-fund contributors see their own reports, never each other's.
Edits are logged with who made them and when, so an audit or a funder query doesn't start from memory.
Consent is recorded for each purpose, and we agree up front how long data is kept and when it's deleted. ZolaShield, our DPDP platform, shows where you stand.
AI features run on your records under your account's controls. Partner and beneficiary records never go into public AI tools.
We'll map how grants move through your team today, identify the smallest useful first version and show where reporting, learning and decisions can share the same information, without forcing your foundation into a generic template.
Four short questions. Plain language is perfect; you do not need to have the solution worked out.
The same approach, shaped to each kind of work.
