What we build

Five module shapes, combined per engagement to fit the program.

Public-facing community portals

Applicant portals, resident-facing service finders, multi-village resource hubs. Role-aware logins, Section 508 / WCAG 2.1 AA conformant, low-bandwidth-friendly.

Intake, eligibility & referral workflows

Structured intake forms, eligibility logic, role-based admin review, cross-agency referral with explicit consent. Iñupiat / multi-language ready when programs require it.

Program & reporting dashboards

Funding-by-community visualizations, grant performance rollups, AI-summarized program narratives reviewed by program staff before release.

White-label / re-skinnable platforms

Same platform shape, new brand + content + local knowledge base per deployment. Olen Hub is the canonical re-deployment template.

If we built it for your program

Three shapes we keep coming back to because they save real staff hours and clear real audit deadlines. Each one adapts to your program — the screenshots are sketches, not templates we’d try to ram into your context.

Member-facing

One door to every program in every village

Right now finding a service means a printed binder, a photocopied flyer, or a “call this number” phone tree. Replace it with one directory that knows what each village offers and who qualifies — for both members and your front-desk staff.

  • Filter by village — staff stop fielding “is that offered in Anaktuvuk?” calls
  • Multilingual when programs require it — Iñupiaq, Diné, or others, side-by-side with English
  • Low-bandwidth render — works on field tablets and slow Arctic links, not just on a fast metro connection
Staff-facing

Keep ICWA cases in your control — not buried in a state spreadsheet

Tribal social services sees open cases, court dates, and placement status in one queue. Generate the BIA Quarterly Report in one click instead of three weeks of cross-referencing PDFs. The state still gets what they need; the data ownership stays with the Tribe.

  • ICWA-preferred placement tracking built in, not bolted on after audit findings
  • One-click BIA Quarterly — pulls from approved records, no re-keying
  • Tribal-state CCWIS exchange without ceding data ownership or rebuilding your records in a state system
Compliance-facing

Quarterly GPRA without three weeks of staff time

GPRA (the Government Performance and Results Act) reporting metrics pull from program records you already keep. AI drafts the narrative paragraph; your clinical lead edits the first draft instead of writing from a blank page. Same numbers IHS already wants — just produced in a Tuesday afternoon instead of a Friday-night marathon.

  • Target vs. actual on every measure, every quarter, automatically
  • AI narrative draft — staff edits, doesn’t write from blank; every paragraph traceable to source data
  • IHS CRS-compatible — works with the IHS Clinical Reporting System (CRS), feeding the numbers IHS already collects rather than fighting your existing reporting

Common RFP shapes we respond to

If your procurement language looks like this, we ship that. Each shape below is a real RFP form we’ve seen from Tribal Health, Tribal Government, or Native-serving foundation buyers — with the deliverable and a price band.

Grant management platform

RFP language: “Online grant application portal with reviewer workflow, awardee reporting, and impact dashboard for a Tribal or regional foundation.”

What we ship: Applicant portal · admin/review queue · award workflow · impact dashboard · AI navigator chatbot.

Reference: ASCF deployment, 8 villages →

Community resource portal

RFP language: “Multilingual community-facing portal with searchable services directory, eligibility info, and admin CMS.”

What we ship: Resource directory · search + filter · eligibility info · multilingual content · admin CMS · low-bandwidth render.

Reference: Olen Hub white-label template →

ICWA / Tribal-state coordination tool

RFP language: “ICWA case-tracking system with Tribal-state CCWIS data exchange and court reporting workflow.”

What we ship: ICWA case workflow · CCWIS-compatible data exchange · court report generator · audit log.

Maps to: State HHS shape →

GPRA / 638 reporting dashboard

RFP language: “Program performance dashboard with GPRA metric tracking and AI-assisted narrative report drafting for IHS / BIA reporting.”

What we ship: Reporting dashboard · GPRA metric inputs · AI narrative draft · staff review + sign-off.

Maps to: Document-to-Dashboard pipeline →

Member portal + intake workflow

RFP language: “Member-facing portal with intake forms, eligibility checking, and referral coordination for Behavioral Health or Social Services.”

What we ship: Member login · structured intake · eligibility logic · review queues · referral handoff with consent.

TERO database / member services

RFP language: “TERO certified-member database with jobs board, employer registration, and compliance reporting.”

What we ship: Member directory · employer registration · jobs board · TERO compliance reports.

Deployed proof

Arctic Slope Community Foundation

First integrated grant management platform serving all 8 North Slope Iñupiat villages. Applicant portal + admin/review dashboard + AI navigator chatbot + impact reporting layer. Multi-year operating agreement.

See the full case study →

Olen Hub

White-label community resource platform combining local knowledge-base chatbot, AI auto-aggregation pipeline, cross-agency intake workflow, resource directory, and aggregated calendar. Re-skinnable per deployment.

See the full case study →

Programs and frameworks we work within

We design around the regulatory and cultural context that already governs your program — not around generic civic-tech assumptions.

Indian Health Service (IHS) program work

Software that supports IHS Division of Grants Management, IHS Area Office program reporting, and Tribal Health Programs running under P.L. 93-638 (the Indian Self-Determination and Education Assistance Act) self-determination contracts. CUI-aware. Aligned with the IHS Health IT Modernization Program (PATH EHR) integration patterns — module-shaped, not enterprise-replacement.

BIA / BIE program work

Software for BIA Grants Management, BIE school-system data, and Tribal governments operating under self-governance compacts. Native preference, TERO-aware, ICWA-aware where workflows touch family services.

638 self-determination contracts

We work with Tribes and Tribal organizations operating IHS / BIA programs under PL 93-638 self-determination contracts and self-governance compacts. Our engagement model fits the 638 environment: configuration over customization, GPRA-aware reporting continuity, tribal data ownership at engagement exit, MOA/MOU-light operational posture.

Indigenous data sovereignty principles

We design with OCAP (Ownership, Control, Access, Possession — First Nations Information Governance Centre) and CARE (Collective Benefit, Authority to Control, Responsibility, Ethics — Global Indigenous Data Alliance) principles as defaults, not afterthoughts. Data ownership stays with the Tribe; cross-agency sharing requires explicit consent.

How an engagement runs

Typical engagement shape. Tailored per program.

  • Discovery sprint (3–6 weeks) — community-facing program review, data-flow map, stakeholder interviews, clickable prototype
  • Build sprint (4–12 weeks) — production-grade module delivery, fixed scope or T&M
  • Cultural & community review — co-design checkpoints with program staff and community representatives where the program requires it
  • Operations support — optional multi-year operating agreement (hosting, support, iteration) for sustained platforms like ASCF and Olen Hub
  • Section 508 / WCAG 2.1 AA baked into the build, not bolted on at the end
  • Tribal data sovereignty principles applied before requirements — consent, ownership, retention, cross-agency sharing

Have a program-software need or RFP?

Tell us the program, the buyer, and the timeline. We respond to direct-client inquiries within two business days.