The portfolio nobody can see whole
Each programme officer knows their own grantees deeply. Nobody can answer which relationships across the portfolio have gone quiet, because the answer lives in four inboxes and three tracking sheets.
For grant-making foundations
Portfolio-wide visibility, without taking the relationship away from the person who holds it.
Foundations rarely have a data problem at the individual grant level. The gap is one level up: no single view of which relationships across the whole portfolio are healthy, which are stalled, and which reporting cycle is about to embarrass someone.
- Best fit
- Foundations and large development teams
- Views
- Programme, finance, board, administrator
- Tier
- Foundation, with custom workflows
Portfolio health5 of your bed
Renewedin bloom
Activeon cycle
Activeon cycle
Stalled11 months
At riskreport late
What breaks at portfolio scale
Four failures that only appear above a certain number of relationships.
Reporting cycles that arrive as surprises
Interim reports, disbursement conditions and renewal windows are known individually and tracked collectively by nobody. The late one is discovered by the grantee chasing it.
Relationships owned by individuals, not the institution
When a programme officer moves on, five years of context about a grantee goes with them. The replacement starts from the application file, which is the least honest document in the relationship.
Cultivation treated as informal work
Foundations that also raise money run major gift cultivation on relationships and instinct. It works until the person carrying it is on leave during a decision window.
What HOPEAQUE adds
One portfolio view, four role-shaped readings of it.
The same underlying pipeline, presented differently depending on whether you are managing a programme, signing off a disbursement, or sitting on a board.
Programme officer
Their own grantees, stage ageing on each, the next date that belongs to them, and the full relationship history including notes from whoever held it before.
- Stage ageing per grantee, not just current stage
- Every promise made to a grantee, with who made it
- Site visit and call history in one thread
Head of programmes
The whole portfolio by stage, by programme area, and by owner load, with the stalled relationships surfaced rather than buried in an average.
- Portfolio-wide health, ranked by what is deteriorating
- Owner load, so cultivation is not concentrated on one person
- Cross-programme duplication of the same grantee
Finance
Disbursement schedules, conditions attached to each tranche, and reporting requirements tied to payment release, with variance visible before a payment run.
- Conditions and milestones against each tranche
- Outstanding reports blocking a disbursement
- Committed against disbursed, by programme area
Board and trustees
A read-only summary by stage and expected value with the assumptions shown, and portfolio health without individual grantee detail they should not need.
- Stage summary with conversion assumptions stated
- Portfolio health trend across periods
- No access to sensitive relationship notes
Institutional memory
The handover problem, which is really the whole problem.
Foundation relationships outlive the people who manage them. A system that only records decisions loses the reasoning, and the reasoning is what the next officer needs.
- Decisions with their reasoning
- A decline records why, in the words used at the time, not only the outcome. A grantee reappearing in three years arrives with that context rather than a blank file.
- Attributed, dated notes
- Every note carries an author and a date. Sensitive notes can be restricted to the relationship owner and the head of programmes without being deleted.
- Ownership transfer
- Reassigning a relationship moves the dates and the obligations with it, and flags anything promised but not yet delivered so it does not vanish in the handover.
- Cycle memory
- Funder and grantee cycles persist across staff changes, so a window that opens every October keeps opening every October in someone's list.
Handover checklist, generated
Open commitments3 outstanding, 1 overdue
Promised but not sent2 items, both site visit notes
Next dates in 90 days4, including one renewal window
Restricted notes1, transferred with approval
Unlogged contact gapsflagged for 2 grantees
Illustrative handover summary, showing structure rather than any real portfolio.
On foundation-scale requirements
Foundations usually arrive with constraints that a product page cannot answer honestly: an existing grants management system, a specific approval chain, data-residency preferences, or an audit requirement with its own vocabulary. Those conversations are worth having directly rather than through a feature list, which is why the Foundation tier includes custom workflow configuration and why the contact form asks what you are actually working against.
No programme officer loses a grantee relationship. Portfolios lose them, in the space between officers.
Which is an institutional memory problem long before it is a software one.