A Public-Benefit Technology Initiative

Technology for good,
in practice.

Helpful Tech helps mission-driven people and organizations use accessible, ethical technology for public benefit — expanding access, agency, creativity, and community power.


Context

Mission-driven teams are outpaced by their tools.

Nonprofits, schools, artists, and public-interest teams need better technology support — but lack the capacity to implement it safely and accessibly.

  1. Technology moves faster than governance and training.
  2. Accessibility is treated as an afterthought.
  3. Small organizations lack technical staff.
  4. Community innovators lack infrastructure.
  5. Public-interest tech depends on unstable grants.
"The opportunity is not just to use new tools. It is to help communities shape technology around their own needs."
What Helpful Tech Does

Six practice areas, one mission.

Education, strategy, pilots, and implementation support — built around the people the technology actually serves.

01 / Education

Technology Literacy

Responsible technology adoption for mission-driven teams.

02 / Design

Accessibility-First Systems

Treat access as infrastructure, not a feature flag.

03 / Inclusion

Creative Technology

Inclusive tools at the intersection of art, accessibility, and code.

04 / Pilots

Public-Interest Tech

Prototypes that solve real community problems.

05 / Practice

Community TA

Hands-on technical assistance, not consulting decks.

06 / Knowledge

Documentation & Training

Reusable playbooks, open to the field.

Who Helpful Tech Serves

Communities the commercial tech market underserves.

Organizations and communities that need technology — but cannot rely on standard commercial tech models alone.

Nonprofits Schools & Universities Cultural Orgs Deaf & Disabled Public Agencies Under-Resourced Communities Community Orgs Public-Interest Tech
Why Helpful Tech Is Different

Accessibility, ethics, and implementation — together.

Typical Tech Support The Helpful Tech Approach
One-off workshops with no follow-through Sustained technical assistance built around real workflows
Accessibility as a compliance checkbox Accessibility as a design principle from day one
Tools chosen for the vendor, not the community Open-source and community-governed options prioritized
Capacity building separated from implementation Education and delivery integrated in every engagement
Expertise extracted from community, not shared back Playbooks, documentation, and models open to the field
Track Record — Completed Projects

Completed projects. Real deployments.

Evidence, not promises — each shipped with a partner and a real user base.

Project 01 · delivered

Audiolux

Open-source hardware that translates audio into light and vibration so sound can be seen and felt.

  • Deployed at festivals and venues
  • Open-source, rentable, and DIY kits
  • Spawned Audiolux Devices & CymaSpace
Project 02 · delivered

PixelBoop

An instrument that feels like a game, disguised as a toy — teaching music through color, no theory required.

  • iOS & web app in TestFlight beta
  • Color-coded chord system
  • PJCE partnership & community jams
Project 03 · delivered

Universal Music Design

A Deaf-led research program reimagining music as an immersive, tangible encounter.

  • GeLu gestural bracelets
  • SubPac mixing for Deaf producers
  • OR Community Foundation funded
Portfolio

Two programs. A handful of projects. Two stakeholders.

One shared practice — public-interest technology, built with the people it serves.

Programs · ongoing Technology Literacy for Good · Public Interest Systems Lab
Projects · start + finish UMD Continuation Pathway · DAO Pilot — Transparent Governance (in flight). Delivered: Audiolux · PixelBoop · Universal Music Design.
Stakeholders · own governance Universal Music Design · surfaces.live

Program · ongoing

Technology Literacy for Good.

Practical technology education for mission-driven teams — built around real workflows, real risks, and real accessibility constraints.

Program · ongoing

Public Interest Systems Lab.

A lab for designing and testing systems that solve real community problems — open-documented, shared back to the field.

Stakeholder · partner entity

Universal Music Design.

A Deaf-led partner entity with its own leadership and governance. Audiolux is the product line we build with them — accessible sound, music, light, and haptic technology, classroom- and stage-ready.

Stakeholder · allied surface

surfaces.live.

The successor to our decentralized-intelligence work — a semantic transport layer that routes intent, not messages. Independently governed; Helpful Tech is a participant.

surfaces.live is a transport + trust layer, not a federated-compute cooperative — it carries forward DI-Coop’s decentralization intent under a model that actually ships.

Project · start + end

Universal Music Design continuation pathway.

Helpful Tech may provide a future continuation pathway for Universal Music Design, subject to stakeholder, grant, board, and IP review.

"Move carefully, transparently, and with respect for the existing history of the work."

Gate 01

Stakeholder & Grant Review

Align with existing funders, partners, and program stakeholders before any transition.

Gate 02

IP & Documentation Map

Inventory all intellectual property, assets, and institutional knowledge held in UMD.

Gate 03

Governance & Board

Establish appropriate governance structures and board review before any formal move.

Gate 04

Future Program Home

Determine the long-term home for the work — inside or alongside Helpful Tech.

Project · start + end

DAO Pilot. Governance in the open.

Definition

DAO = Decentralized Autonomous Organization — A member-run organization where rules, money, and decisions live on a public ledger. Anyone with a stake can propose, vote, and audit — no closed-door committee, no hidden books.

A small, time-boxed pilot to test transparent governance, on-chain finances, and stakeholder voting as a working model for Helpful Tech itself and the communities it serves.

Practice the governance we recommend — before we recommend it.

Operating Model

Begin fiscally sponsored.

Faster to launch. Lower administrative burden. Charitable from day one — without forming a new nonprofit too soon.

Layer 01

Fiscal Sponsor

Layer 02

Helpful Tech Governance Layer

Layer 03

Programs

Layer 04

Community Impact

Why this

Fiscal sponsorship means Helpful Tech can accept tax-deductible donations and grants immediately, without the overhead of forming and maintaining a standalone 501(c)(3).

What it enables

Rapid launch, focus on program work over compliance, access to foundation and government funding from day one, and a clear path to independence when the time is right.

What it earns

Trust with funders, community credibility, and institutional legitimacy — while keeping the operational model lean and the governance transparent.

Revenue Model

Two pillars. Mission-aligned.

Charitable funding underwrites public-interest work; earned program revenue keeps the practice grounded in real client needs.

Pillar 01

Charitable Support

  • Foundation grants (technology & public benefit)
  • Government and municipal contracts
  • Individual major donors
  • Crowdfunding for specific programs
  • In-kind contributions and partnerships
  • Fiscal sponsor pass-through grants
Pillar 02

Mission-Aligned Earned Revenue

  • Organizational technology literacy workshops
  • Accessibility consulting engagements
  • Technical assistance retainers
  • Licensing of open-source tools & kits
  • Community technology audits
  • Training program licensing to field partners
Governance & Trust

Guardrails from day one.

Helpful Tech must be built with clear, written boundaries — so that mission, money, and method stay separable and reviewable.

Fiscal sponsor oversight
Separate bookkeeping
Written agreements
Conflict-of-interest review
IP documentation
Transparent program budgets

"Advisory circle in place before any board is formed."

First 12 Months

A staged launch, measured by trust.

0 – 90 Days

"Stand it up."

  • Identify and engage fiscal sponsor
  • Establish governance documents and agreements
  • Form initial advisory circle
  • Open project bank account and books
  • Define first-year program scope and budget
  • Launch Helpful Tech public web presence
3 – 6 Months

"Run real work."

  • Launch Technology Literacy pilot workshop series
  • Begin Systems Lab first project cohort
  • File first grant applications
  • Begin UMD stakeholder conversations
  • Publish first open documentation
6 – 12 Months

"Decide forward."

  • Assess first-year program outcomes
  • Review fiscal sponsorship model
  • Decide: stay sponsored or incorporate
  • Set second-year program priorities
Impact Goals

How Helpful Tech measures success.

Outcomes for the people and organizations Helpful Tech serves — not vanity metrics for the initiative itself.

01

Organizations that can implement technology responsibly without dedicated technical staff

02

Public-interest tech projects that include accessibility from the first design decision

03

Disabled and Deaf community members as active co-designers, not just end users

04

Open playbooks published and reused by field partners outside of Helpful Tech

05

Community pilots that move from prototype to deployment within the first year

06

Grant-funded programs that generate matching earned revenue from community partners

07

Program participants who go on to train others in their own organizations

Community members who experience technology as something they shape — not something done to them

The Ask

Approve Helpful Tech as the public-benefit umbrella for accessible, ethical, community-centered technology work.

01 — Launch

Launch under fiscal sponsorship.

Identify a fiscal sponsor, establish governance documents, open books, and stand up Helpful Tech as a recognized initiative with charitable status from day one.

02 — Portfolio

Fund the programs, projects & stakeholders.

Back the two ongoing programs and the in-flight projects; partner with our stakeholders — Universal Music Design and surfaces.live.

03 — Govern

Create governance & IP guardrails.

Form the advisory circle, establish conflict-of-interest policies, document IP ownership, and publish transparent program budgets before any board is formed.

04 — Review

Move UMD work with care.

Begin the four-gate stakeholder and IP review process for Universal Music Design — carefully, transparently, and with respect for the existing work and relationships.

Helpful Tech

Helpful Tech turns emerging technology into practical public benefit.

Powerful tools — usable, ethical, accessible, and community-owned.

Helpful Tech / Vision Brief — 2026

View Full Presentation →