Skip to content

Company

It started with a donor who left, and a system that never noticed.

HOPEAQUE was built after watching an organisation discover, in the middle of preparing an annual report, that a supporter of eleven years had stopped giving nine months earlier. Nobody had been careless. There was simply nothing in the way they worked that could have noticed.
Company
Hopeaque Private Limited
Focus
Donor and volunteer relationships
Built for
Nonprofits, NGOs and foundations

The gift had not stopped because anything went wrong. It stopped because after the last field visit, nobody sent the note they had promised, and eight months of silence answered a question the donor had never been asked.

Three reads of the same relationship, over eight months.

Why this product

The gap we kept finding.

Nonprofits are not short of software. They have a donation page, a payment gateway, an email tool, a spreadsheet for volunteers and another for the appeal, and every one of those was a sensible decision on the day it was made. What none of them do is hold the relationship, because a relationship is exactly the thing that falls between tools.

The general-purpose CRMs that could hold it are built around a sales pipeline, where a contact moves forward until they either buy or are disqualified. A donor does not behave like that. A donor gives, then volunteers, then goes quiet for a season because their circumstances changed, then comes back further in than before if somebody noticed. Ask a sales pipeline to model that and you get a stage list nobody in the organisation is willing to update.

So the structure came first. One record for a person, holding both the money and the time they give. Then the scoring, built on behaviour instead of the calendar, because the calendar is what made the eleven-year donor invisible. Then the suggested action, because a flag without an instruction is just a new source of guilt for a team that is already stretched. Then the reporting, because the report is what would have prevented the whole thing.

The visual language of the product came out of the same argument. A donor base is not a funnel and it is not a deal board. It behaves like a planted bed: things grow when they are attended to, they wilt quietly when they are not, and the wilting is visible long before the plant is gone if anyone is looking at the bed rather than at the total.

Principles

Four commitments that decide what gets built.

These are not values on a wall. Each one has ruled a feature out at some point, which is the only test of whether a principle is real.

01

Every supporter should feel seen, not just solicited

The test we apply to every feature: does this make a supporter more likely to hear something other than an ask? If a capability only makes soliciting faster, it does not get built. This is why suggested actions are held back when the only recorded contact since the last gift was a solicitation, and why report sending is treated as retention work rather than administration.

02

Engagement scored honestly, not just by recency

Recency-based scoring is easy to build and flattering to look at, and it systematically misreads the annual giver, the seasonal donor and the supporter whose bank mandate failed. We would rather ship a score that is harder to compute, show its five signals and their weights, and let a fundraiser overrule it with a reason.

03

Impact reporting should not cost a week, every time

The reason donors are not told what happened is almost never indifference. It is that the giving data and the programme data live in different places, so telling one supporter the truth means reconciling two files by hand. Fix the join once and the honest report becomes the cheap option instead of the expensive one.

04

Say what the product does today

No roadmap dressed as a feature, no certification implied that we do not hold, no accuracy figure borrowed from somebody else's donor file. Our security page names what we have not done. That is deliberate, and it is the version we would want if we were the ones migrating a donor file.

How we work

Where credibility is supposed to come from.

Not from a testimonial wall or a customer-logo grid. From two things you can inspect yourself.

One

The demo on the homepage runs on your own number

Enter your supporter count and the bed is planted at that scale, with the engagement mix most donor files settle into. It is labelled as illustrative because it is, and it is still more informative than a screenshot of somebody else's dashboard.

Plot your own garden

Two

The donor-engine pages go deeper than a feature list

Signal weights, flag triggers, what suppresses a flag, how attribution is calculated, what the score cannot see. If a claim on this site cannot survive that level of detail, it should not be on the site.

Read the Donor Engine

Where we are

Hopeaque Private Limited is an early company, and the honest reading of that is a trade: you get direct access to the people building the product and real influence over what gets built next, and in exchange you are adopting something younger than the alternatives. If that trade does not suit your organisation right now, a well-kept spreadsheet and a calendar reminder is a perfectly respectable answer. Our registered office details are on the contact page.