Skip to main content

About Backed

SMALL TEAM.LONG MEMORY.

Backed was built on a simple premise: the administration around a funding decision should never be the reason a good decision is slow, inconsistent or hard to defend. We build for the people who have to answer for the money.

See the platform →

Who we are

Grants software is not a CRM with different labels.

A grant is not a deal and an applicant is not a lead. The record has to survive an audit, a change of government, a change of staff and a request under Freedom of Information, sometimes all four in the same year. That is a different shape of system, and adapting a sales tool to it produces exactly the compromises funders have learned to live with.

So Backed was specified before it was built. The requirements, the data model, every screen and every acceptance criterion were written down first, traced to each other, and reviewed. It is a slower start and a much shorter middle: the arguments happen on paper, where they are cheap, rather than in a release, where they are not.

We are Australian, our records are held in Australia, the trust page names every place data goes, and we say plainly what the product does today rather than what it is scheduled to do. Where something is specified but not yet shipped, we will tell you that in the first conversation rather than the fourth.

What we protect

THE STANDARDSDO NOT MOVE

The work changes from programme to programme. These do not.

Evidence

Every action attributable, every change timestamped, every decision holding its reason. If the system cannot show how a decision was reached, it has not done its job.

Restraint

A feature that does not earn its place makes every other feature harder to find. We would rather ship six things that are finished than twenty that are nearly.

Plain words

The product uses your terminology, not ours, and this site says what the software does without a layer of language between you and the answer.

The record

SPECIFIED BEFOREIT WAS BUILT

These are artefacts of this repository, not customer outcomes. They are here because they are checkable, and because a funder deciding whether to trust a platform with a decade of grant records is entitled to know how carefully it was put together.

215
Screens specified
314
Tables designed
2,231
Requirements traced
4,081
Acceptance criteria

Where the data lives

Records in Australia. Every store named.

Records are held in Australia (AWS Sydney) (aws-ap-southeast-2). Some processing and mail delivery happen outside Australia, and the trust page names every store with its provider and region. The subprocessor list is published rather than supplied on request, retention and deletion are configured by you, and an export of your own data is available at any time in a format you can actually use.

Privacy Act 1988 · CGRPs aligned · WCAG 2.1 AA

WORK WITH PEOPLEWHO WROTE IT DOWN FIRST.

Start a conversation →