A 501(c)(3) nonprofit serving Arizona

Applications built around real needs. One platform built on consent.

Nexus for Hope builds applications for publicly funded community programs, each one shaped by the people who run and use that program. The Nexus (with NavigatorConnect) serves homelessness response. PEEPS is our application for a PEEPS-like program: publicly funded preschool scholarships spread across many providers and funders. Both run on one platform, so every application starts with the same guarantees: consent that can be revoked, a record that follows a person across handoffs, and results measured by someone independent.

See the applications What the platform provides
Application
The Nexus (with NavigatorConnect)

Homelessness response: beds, services, referrals, outreach, and outcomes across agencies.

Application
PEEPS

Our application for a PEEPS-like program: enrollment, attendance, a record that follows each child, and independent evaluation.

both run on
One shared platform
  • Consent, item by item, revocable
  • Each organization keeps its own data
  • One record across handoffs
  • Role-based access
  • Every access logged
  • Independent measurement
  • Works alongside systems of record
The Nexus (NavigatorConnect) dashboard showing shared resource availability and client actions across agencies

Two applications. Each starts with a need.

Every application is built around what a specific program needs to know and who needs to know it. The data of one application never touches the other's.

Homelessness response

The Nexus (with NavigatorConnect)

A shared operational view for the agencies serving people experiencing homelessness.

The need

Response is spread across dozens of agencies with separate records. Outreach teams can't see which beds and services are open, referrals go untracked, and contacts made before enrollment never make it into the data.

Who uses it

Outreach navigators, shelters and service providers, agency administrators, local government, and funders.

What it does

  • Live bed, shelter, and service availability across agencies
  • Referrals tracked from first contact to placement
  • Outreach and encampment mapping
  • Contacts and declined services recorded before formal enrollment
  • Outcome tracking that connects referrals, services, and results
  • Runs alongside HMIS, not in place of it
The Nexus (NavigatorConnect) map showing clustered outreach locations across the Tucson area
In demonstration with southern Arizona agencies.
Early childhood education

PEEPS

Our application for a PEEPS-like program: publicly funded preschool scholarships spread across many providers and several funders, like Pima County's.

The need

A program like PEEPS reaches about 2,000 children a year at more than 100 provider sites, with several public and philanthropic funders. Enrollment and attendance reach administrators weeks late, no record follows a child into kindergarten, and the program's long-term results can't be shown.

Who uses it

Preschool providers, program administrators, school districts, families, and an independent evaluator.

What it does

  • Enrollment and attendance logged at the provider site, in real time
  • The permanent state student ID assigned at preschool intake, so no child is lost at kindergarten
  • A family portal for consent, and later for finding open scholarship slots
  • A current view of enrollment, utilization, and provider capacity for administrators
  • A consented, de-identified cohort for an independent, pre-registered evaluation using state third-grade reading results
  • Adopted by funders as a condition of scholarship funding, so the record is complete
In development, 2026 to 2027, in conversation with program administrators, school districts, providers, and families in Pima County.

One platform underneath both.

Every application inherits the same foundation. That is what makes the second application faster to stand up than the first, and what lets partners trust either one.

✓Consent first. People and families decide what is shared, item by item, and can revoke it. Every access is logged.
✓Each organization's data stays its own. Sharing happens by agreement and by consent, not by merging databases.
✓One record follows a person across providers, funders, and handoffs.
✓Role-based access. Each user sees what their role allows and nothing more.
✓Independent measurement. Evaluators who don't work for us receive de-identified, linked records they don't have to build.
✓Complementary to systems of record. HMIS and student information systems stay in place.
✓Year-round visibility. Inflow, engagement, connection, and results as they happen, not in an annual report.
Platform resources page showing available beds, services, organizations, and capacity

What we won't do.

The value of shared data depends on trust. These are the lines we hold, in writing, with every partner and in every application.

Ask us about governance
We are not the system of record. HMIS and student information systems stay where they are.
We do not grade the programs we support. Independent evaluators do.
We collect the minimum data needed, and less for children.
Consent can be withdrawn, and withdrawal is honored by every organization that received the data.
No organization sees another's data without an agreement that names what is shared and why.
Results are reported whether or not they are favorable, including when early gains fade.

About Nexus for Hope.

Nexus for Hope is a 501(c)(3) nonprofit organization co-founded by Kevin Daily and Josh Jacobsen. It was formed to close the gap between what communities spend on the programs they fund and what they can show those programs achieved. We build the applications, convene the partners, hold the agreements, and steward the data governance each one requires.

Co-founder

Kevin Daily

Co-founder of Nexus for Hope. Kevin is a systems engineer with three decades in hardware and software integration and functional safety, and a longtime school board member in Pima County. He leads strategy, partnerships, and technical execution.

Co-founder

Josh Jacobsen

Co-founder of Nexus for Hope and CEO of Trusted Role Solutions. Josh leads the organization's work to make coordination and outcome measurement a practical daily reality for community programs.

How the technology relationship works

Both applications run on WorldbyMe, a platform developed by Trusted Role Solutions, a separate technology company co-founded by Kevin Daily and Josh Jacobsen. Nexus for Hope is an independent nonprofit. Any work between the two organizations is approved by Nexus for Hope's board with both founders recused, and is disclosed to funders and partners.

The programs are funded. The proof should be too.

If you administer, deliver, fund, or depend on one of the programs above, we would like to talk. And if you run a different publicly funded program with the same gaps, an application can be configured for it on the same platform, with the same consent rules and the same independent measurement.

Start a conversation