The platform

One engine for the whole housing lifecycle

HomesMatrix models the decisions your programs are accountable to — not just contacts and tasks. Homeownership and home repair run on the same engine, configured to each program, with every determination role-stamped and traceable from first inquiry to lasting stewardship.

One connected record

One source of truth, not many systems

People, properties, funding, and cases live in one connected record — so staff never re-enter the same information twice, and leadership sees the whole picture without asking anyone to build a report.

People & households

Constituents and households, with the roles they play across your programs.

Properties

The homes being built, repaired, or stewarded — with their condition and history.

Funding

Grants and funding sources, with the eligibility rules they carry.

Cases

Each case links its household, property, funding, decisions, and documents.

The lifecycle engine

A role-stamped, eight-stage case engine

Every case moves through the same defensible sequence. Each stage carries its evidence forward, and nothing advances without the record to back it up.

  1. 1
    Application & EligibilityIntake the household and make an income and program-eligibility determination.
  2. 2
    AssessmentDocument the household or property condition and capture the supporting evidence.
  3. 3
    ValidationAn independent reviewer validates the evidence against the versioned ruleset.
  4. 4
    Eligible activitiesDetermine which activities qualify under the program and its funding sources.
  5. 5
    SpecificationsDraw scope from a standards-based specification library.
  6. 6
    ScopeAssemble a traceable, line-item scope of work tied back to the specs.
  7. 7
    ExecutionBuild or repair, tracked to completion with inspections along the way.
  8. 8
    CloseoutFinal inspection and closing, then hand-off into long-term stewardship.
Validation enforces separation of duties — the person who assessed a case can never be the one who validates it — and every decision is stamped with the exact ruleset version it was judged against. Anything that doesn’t cleanly pass routes to an exception queue for review.

Two programs, one engine

Configured, not custom-built

Each program runs on its own versioned ruleset and role map. Adjusting a policy is a new ruleset version — a configuration change on a record, not a code rewrite — and past decisions keep the version they were made under.

Homeownership

Eligibility ruleset

Income within policy, demonstrated housing need, and willingness to partner — evaluated as explicit, auditable criteria.

Home repair

Standards ruleset

Condition measured against a deficiency threshold and program standards — so what qualifies for repair is consistent and defensible.

Finance

Finance that reflects the mission

Affordability isn’t an afterthought bolted onto a CRM — it’s modeled directly, with the guardrails your funders and your charitable purpose require.

Affordability underwriting

From a household’s income and obligations, model an affordable payment, the maximum affordable mortgage, and the affordability subsidy needed to close the gap.

Income-ceiling gates

Area Median Income eligibility ceilings are built in as machine-checkable gates, so cases stay inside the limits your funding sets.

Charitable-purpose checks

A charitability safe-harbor check helps keep assistance defensibly within your nonprofit’s exempt purpose.

Accountability

Isolation and accountability by design

The controls that make decisions defensible are built into the platform, not bolted on.

  • Per-organization workspacesEach organization’s data is isolated at the database layer with row-level security.
  • Separation of dutiesGranular role authorities, enforced where it matters — the person who assesses a case can’t validate it, and resale and refinance decisions can require a second, different approver.
  • Accountable decisionsStamped with who, when, and the ruleset version — recorded as new, attributed entries the app never edits or erases.
  • Verified at startupThe platform checks that tenant isolation is intact when it starts, and won’t run if it can’t be proven.
  • Encryption in transit & at restTLS in transit; documents kept in a private object store, encrypted at rest by managed cloud infrastructure.
  • Least-privilege accessSign-in lockout, security headers, and least-privilege database roles.

See our full security approach →

See the engine on your programs

A short, tailored walkthrough — homeownership, home repair, or both.