INTERNAL — OAHE DATA
Oahe Data

Intelligence Brief

HaloRRS — Halo Response & Recovery Solutions, LLC
Date: 2026-04-19 Entity Type: Private Audit Type: Public Index Reconnaissance

Contents

Entity Profile


Budget Signals

HaloRRS itself doesn't spend federal money — but their entire client portfolio does, and they exist to advise that spending. The money they touch flows through:

Where Oahe could help them spend better: the firm's central pain (see Pain Points) is evidence assembly for FEMA Project Worksheets and CDBG-DR applications. Damage extent, demographic-impact analysis, longitudinal recovery indicators — these are FP-STAN-style problems and they currently depend on whatever data the impacted district's administrators can scrape together themselves.


Technology Gaps

Where Oahe could help: if the Halo Recovery Responder™ is actually a product, it almost certainly needs (a) a real backend with audit-grade logging, (b) a data layer that integrates FEMA/USGS/NWS/EPA reference data, and (c) an evidence-assembly workflow for FEMA PA Project Worksheets. Three things Oahe builds.


Decision Makers

Name Role Why they matter Outreach lever
Jennifer Huff CEO / Owner Holds the woman-owned credential; legal owner; signs contracts LinkedIn + 417-450-0624 main line
C.J. Huff, Ed.D. Director, BD The brand. Former Joplin Schools Supt. 2008-2015. Three speaker bureaus actively booking him through 2026 cjhuff.com; easier to reach via speaker-bureau channels than corporate
Teresa Huff Chief Grants Officer Owns the $75M-grants-secured headline. Technical buyer for grants-data tooling Direct LinkedIn
Seth Spencer Advisor, CDBG Funding HUD/CDBG technical credentialed; would evaluate a CDBG-data or recovery-indicators tool Direct LinkedIn
Michele Gay Senior Advisor, School Safety Sandy Hook mom; co-founder Safe and Sound Schools — gives access to the K-12 safety conference circuit, not HaloRRS contracts directly Conference channel

Family ownership shape: four Huffs on the roster (Jennifer, C.J., Teresa, Ryan). Decisions concentrate inside that family unit. Persuasion is family-trust work; not enterprise-procurement work.


Pain Points

  1. Evidence assembly under deadline — FEMA PA Project Worksheets, CDBG-DR applications, insurance claims all require quantitative damage and demographic context that a small district administrator does not have time to compile in the 60-180 days after a disaster. HaloRRS sells this assembly as a service. Right now they likely build it by hand.
  2. Multi-state expansion without a multi-state knowledge base — they've worked MO, AR, TX, CA. Each state has its own emergency management agency, CDBG-DR allocation, and procurement portal. As they grow, the cost of "remembering AR" or "remembering CA" goes up. No public knowledge base or playbook visible.
  3. Sales cycle is conference-and-relationship-driven, not search-driven — zero PR wires, light press, no SEO investment, no thought-leadership content cadence. This works at their current size; it caps growth.
  4. No trademark protection on flagship product — first business-risk lawsuit they encounter could be a trademark dispute they brought on themselves by not filing.
  5. No SAM.gov visibility — even if registered, they are not discoverable to federal contracting officers searching for woman-owned disaster-recovery vendors. If they want CDBG-DR direct contracts (not just sub-recipient advising), this is a gap.

Competitive Landscape

Direct competitors (FEMA PA / CDBG-DR consultancies serving K-12 and county clients):

HaloRRS competes on superintendent-to-superintendent trust (C.J. Huff), not on size, federal prime status, or technology. Their wedge is small districts traumatized by a disaster who don't want to talk to a 500-person consultancy.

Implication for Oahe: we are not competing with HaloRRS — we could equip HaloRRS. They are the relationship; we could be the data layer that makes their evidence assembly faster than a Tidal Basin/IEM team could match.


Timing Opportunities


Position Oahe as the data/evidence-assembly layer that makes HaloRRS's superintendent-trust premise scale. Don't sell to them as a grants-tooling vendor (Teresa already does grants); don't sell to them as a software vendor (they have Wix for marketing and aren't ready to be a SaaS company). Sell as a disaster-recovery evidence partner — the team that can assemble the FEMA PA / CDBG-DR data package faster than any large competitor can.

Entry point: C.J. Huff via the Joplin alumni / superintendent network, or via a co-attended Safe and Sound Schools event. The Joplin-tornado case study already in this repo gives us conversational ground that we are taking the same disaster seriously, from a different angle.

Pitch frame: "You are the recovery superintendent in the room. We are the evidence team behind you. Together you outrun Tidal Basin in any district small enough to choose people over volume."

What NOT to do: do not approach as a competitor (we are not), do not approach as a SaaS vendor (they will pattern-match to grants software), do not lead with the Halo Recovery Responder™ trademark issue (it is a real issue but it is not how relationships start).


INTERNAL — OAHE DATA — NOT FOR EXTERNAL DISTRIBUTION