Funding-to-impact operating system

One record of funded work, from the opportunity to the final report

AwardBase is not a grant finder and not a proposal generator. It is the system the whole life of funded work runs inside — discovery, the decision to pursue, the proposal, the award, the project, the money, the obligations and the report — so the joins between them are already made rather than reconstructed at a deadline by a person.

Request a demoHow it works

The lifecycle, as one system

Most organisations run this across a finder, a proposal tool, a spreadsheet, an accounting system and a folder of PDFs. The work is continuous; the tools are not.

  1. CONNECTBring in the funding sources, the documents and the systems you already work with, under terms you have actually agreed to.
  2. DISCOVERFind the funding you are genuinely eligible for, with the eligibility reasoning attached rather than a relevance score.
  3. DECIDEMake a go/no-go a person is accountable for, against a recorded eligibility position that cannot move underneath it.
  4. BUILDAssemble the proposal against the funder’s actual requirements, with every claim traced to an approved fact.
  5. SUBMITSubmit once, deliberately, with a package that refuses to be built over an unresolved defect.
  6. EXECUTERun the funded work: projects, work packages, milestones, budget baselines and the cost that accumulates against them.
  7. COMPLYHold the obligations the award actually created, read from the notice by a person rather than inferred by a model.
  8. REPORTReport on the funded work from the same records the work was executed against, not a spreadsheet assembled afterwards.
  9. RENEWCarry what you learned into the next cycle, with the history of what happened still attached to it.

What you would use it for

The part that is genuinely different

Software about funding is full of numbers nobody can trace and green ticks nobody earned. AwardBase is built so that cannot happen.

  • Nothing unknown becomes a zero. A check that has never run reports as never run. A figure with no records behind it does not render as a figure. What the system does not know is the thing it is most careful to say.
  • People decide; models draft. Approving, certifying, submitting, awarding, attesting and waiving require a human, enforced in the domain layer rather than by policy. A model-produced claim can never be recorded as observed fact.
  • Decisions bind to an exact version. An approval is made against a specific version of a specific record, so it cannot quietly survive a material edit to what was approved.
  • Evidence is a by-product, not a project. The audit trail is written as the work happens, because that is the only moment it is cheap to write.

Where AwardBase actually is

Stated plainly, because the alternative would contradict everything above. AwardBase is pre-production: there is no production deployment, no customer, no certification and no independent security assessment. Substantial parts of the platform are built and tested; others are designed and not yet implemented. Every page on this site labels which is which, and those labels are checked against the codebase by an automated test.

Security and trust, including what is not claimed

Explore the platform

AwardBase — Find funding. Build partnerships. Drive impact.