01 · Setup
Built by programme staff, not developers
Big ideasbackedthe right way
Why it exists
01 / 04
Funders spend more time on spreadsheets, inboxes and version control than on the decisions only they can make. The administration is not the work. Done badly, it becomes the work, and the programme quietly starts serving the process instead of the other way round.
02 · Assessment
A conflict removes access, it does not warn
03 · Decision
The reasoning sits beside the decision
04 · Delivery
The tranche waits for the report
Open to acquittalEND TO END
One record
Not seven systemsONE RECORD
Who it is for
Five kinds of funderone set of obligations
01 / 05
The seven phases
One round, end to end
Every phase hands the next one a complete record. Nothing is re-keyed, and nothing is reconstructed at the end from files.
Underneath every phase
The record they all share
The seven phases only work because one entity record, one permission model and one audit trail run beneath all of them. Change any of those in isolation and the lifecycle stops being a lifecycle.
The entity recordWho you fund
Reporting and dataWhat you can prove
IntegrationsWhat it connects to
Security and administrationWho can see what
1 / 4
215
Screens specified
314
Tables designed
2,231
Requirements traced
4,081
Acceptance criteria
Questions
What Funders Ask First
Can we run more than one programme?
Yes. Funding categories carry their own branding, forms, assessor pools and approval limits, and reporting can hold them apart or roll them together. A council running four community rounds and a department running forty use the same mechanism.
What happens to an application after the round closes?
Nothing is deleted. Records are deactivated, archived or retired, and the audit trail keeps the history either way. Retention periods are configurable, because the answer to "how long must we keep this" is set by your obligations, not by us.
Who can see an applicant’s answers?
Only the people whose permissions and data-access rules allow it. Assessors see the applications assigned to them and nothing else, and an assessor with a declared conflict loses access outright rather than seeing it with a warning attached.
Does it work on a phone?
Yes. Applications autosave on every field, so an applicant can start on a phone at a community meeting and finish on a laptop that night without losing anything in between.
What does implementation actually involve?
Configuration rather than development: your forms, your eligibility rules, your assessment framework, your templates and your delegation limits. Most of the elapsed time is decisions your team makes, which is why the first workshop is about the programme and not the software.
Can we get our data out?
At any time, in a format you can use. There is a report builder with CSV export across every stage of the lifecycle, and a read-only, versioned API using OAuth 2.0 client credentials for anything that needs a live feed.
Get started
Show us your next round
Bring a real round. Not a demo dataset.
Thirty minutes
We will walk your own round through the platform: your form, your criteria, your decision process, your delegation limits.
Most teams know inside half an hour whether this is the right shape for their programme. If it is not, we will say so. A bad fit costs us both more later than it does now.
Request a walkthrough
Or email contact@backed.giving. We answer within one business day.