Angel Investor Overview

Emergency
Coordination
App

When roads close, signals drop, or risk changes fast, people need each other.

Lee Hill Labs / Colorado Front Range and Foothill Communities
The Moment

Emergencies rarely arrive as clean instructions.

During a wildfire, flood, storm, evacuation, or outage, most people are not calmly reading official bulletins. They are trying to answer immediate questions.

What People Need to Know
  • Is my family safe?
  • Is my road open?
  • Who nearby needs help?
  • What do I need to do now?
  • Which updates are verified?
  • What did I already agree to do for my neighbors?
Why Now

Longer fire seasons and more severe weather are making local coordination a year-round need.

  • Western communities: wildfire, smoke, evacuation, red flag conditions
  • Mountain and foothill communities: fire, flood, snow, wind, limited road redundancy
  • Coastal communities: hurricanes, storm surge, flooding, power outages
  • Plains and Midwest communities: tornadoes, derechos, hail, flash floods, grid interruptions
  • Urban and suburban communities: smoke, heat, flooding, fast-moving local incidents

ECA starts with wildfire. But the product category is broader: community-scale emergency coordination.

Stylized North America hazard context map
Source

NOAA/NCEI billion-dollar disaster dataset, NIFC wildfire statistics, FEMA preparedness resources

The Gap

Official alerts tell people something happened. Communities still need to coordinate what happens next.

Current tool What it does well What it does not solve
Official alerts Public safety notices, evacuation orders, warnings Household and neighborhood coordination
Watch Duty-style maps Fire visibility, incident tracking, perimeter awareness Private group plans, tasks, family status, neighbor support
Text chains Fast, familiar, informal Chaos, duplication, misinformation, no structure
Social groups Broad local discussion Hard to verify, hard to act on, noisy
Phone trees Human fallback Fragile, slow, not data-aware
01
Alert
02
Context
03
Coordination
04
Action
Product Thesis

ECA turns a neighborhood into an organized response network.

A mobile coordination app for families, households, and trusted local groups during active emergencies and preparedness windows.

  • Create private household and neighborhood groups
  • Receive and organize emergency context
  • Share verified status updates
  • Coordinate tasks, roles, supplies, and check-ins
  • Understand local map conditions
  • Preserve access to critical information when connectivity is degraded
  • Run mock drills and test plans before an actual incident
9:41 ECA
Boulder Heights
Incident Escape Route Fire
12/14Checked in
! 2 requests !
🚨 Evac zone expanded 🧯 Wind shift update 📡 Sheriff briefing live
Offline plan cachedReady
User Story: Wildfire First

A foothill neighborhood gets a fire alert. ECA helps them move faster without creating more noise.

Without ECA
  • Group texts split into multiple threads
  • People repeat the same questions
  • Rumors mix with official updates
  • No one knows who checked on elderly neighbors
  • Road status, pets, door codes, and task ownership are scattered
With ECA
  • The group receives a structured alert view
  • Members check in: Safe, Away, Need Help, Unknown
  • Tasks are assigned and marked complete
  • Critical household details are visible only to approved people
  • A map view shows relevant hazard context
  • The group can reference its offline plan if cell service degrades
Wildfire-First MVP

MVP focuses on the smallest set of tools that can prove coordination value.

01
Private Groups
Households, neighbors, family members, and trusted contacts
02
Status Check-Ins
Safe, Away, Need Help, Unknown, Evacuating, Sheltering
03
Structured Alerts
Alert cards that connect incident context to group action
04
Task Coordination
Assign and track preparedness or incident tasks
05
Critical Info Access
Secure sharing for pets, gates, utilities, door codes, and contacts
06
Map Context
Hazard-aware map layer for incident proximity and area status
07
Offline-Ready Plan
Cached group plan and critical info for limited connectivity
08
Simulation Mode
Test with mock coordinates inside an active ZIP code, no physical presence required
Product Principles

The product has to be calm, useful, and trusted under pressure.

No Panic UI
Severity should be clear without making people spiral
Private by Default
Sensitive household data should never become neighborhood gossip
Verified Where Possible
Separate official sources, group updates, and unverified observations
Action Over Noise
Every screen should help someone decide, coordinate, or confirm
Local First
Communities have different roads, risks, resources, and norms
Offline Matters
Emergency tools cannot assume perfect connectivity
Mock Testing is First-Class
The app must be testable before people rely on it
Built for the moment people stop browsing and start acting.
Prototype Screens

Early design will focus on the flows that prove whether people understand and trust the app.

ECA
Create Group
Boulder Heights
Household Neighbors Emergency partner
Onboarding & Group Creation
Boulder Heights
Escape Route Fire
Group chat
! 2 requests ! 🚨 Evac zone expanded
🧯 Wind shift update
📡 Sheriff briefing live
Group Coordination
Group Status
12 of 14 Safe
86%
2 need reply 1 needs pickup
Group Check-In
Boulder Heights
My Household
Address 442 Ridge View Door code 0719 Animals barn + mudroom Supplies shovel, fire ext., water
My Household
Coordination
Open Requests
! Horse Trailer ! ! Jumper Cables ! ! Dogs in house !
Task Assignment
Offline Plan
Cached
Updated 8:42 AM
Contacts saved Routes saved
Offline Plan
Platform Scope

The same coordination pattern applies across regions and hazards.

Mountain Towns
Snow, fire, road closures, limited access
Midwest / Plains
Tornadoes, derechos, hail, flash floods, grid interruptions
Urban / Suburban
Smoke, heat, flooding, outages, fast-moving local incidents
California WUI
Wildfire, smoke, power shutoffs
Colorado Foothills
Wildfire, smoke, snow, wind, access issues
Gulf / Atlantic Coast
Hurricanes, flooding, power outages, post-storm coordination
Prepare
Alert
Check In
Act
Recover
Improve

The incident changes. The coordination problem repeats.

Who Uses It

ECA starts with households and trusted local groups, then expands toward organized community partners.

Initial Users
  • Homeowners in high-risk or high-consequence areas
  • Families with shared emergency responsibilities
  • Neighborhood pods and informal mutual-aid groups
  • Rural and foothill residents with limited road redundancy
  • People caring for elderly family, pets, livestock, or second homes
Regional Ecosystem
Community Partners
Neighborhood
Trusted Group
Household
Business Model Hypotheses

We are not locking the revenue model before we validate who feels the pain most clearly.

Model Buyer Why it could work What we need to validate
Consumer subscription Household / family Direct value, simple adoption Will households pay for preparedness and incident utility?
Group subscription Neighborhood pod / HOA Shared cost, strong local relevance Who owns setup, payment, and admin?
Community license Municipality / district / local org Public resilience and preparedness Procurement path, liability, support burden
Insurance / risk partner Carrier / broker / mitigation partner Risk reduction and preparedness alignment Incentives, data boundaries, privacy requirements
Freemium + paid features Individual and power users Low friction adoption Which features create paid conversion?
Preparedness toolkit Households / groups / orgs Revenue before full incident automation Packaging, support, and repeat use

MVP is designed to validate product behavior first, then sharpen the buyer motion.

Roadmap: Formation to MVP

The first phase is about proving the product, not pretending we are already a scaled company.

Spring 2026
Company Formation
Entity, founder roles, legal setup, bank and accounting readiness
Spring 2026
Seed Tooling
Tool stack, shared workspace, roadmap, design system start
Spring 2026
Product Definition
MVP requirements, data assumptions, privacy model, user stories
Late Spring / Early Summer
Design Prototype
Clickable iOS prototype, core flows, investor and advisor demo
Summer 2026
MVP Build
Working app: group, alert, check-in, task, map, offline plan
Summer 2026
UAT + Mock Testing
Test with simulated active hazard area in Colorado Front Range context
Late Summer / Fall 2026
Post-MVP Path
Validate buyer model, refine data integrations, prepare larger raise
Operating System

We are building the product and the company operating system at the same time.

Asana
Roadmap, boards, tasks, dependencies, timeline, and owner tracking
Google Drive
Founder notes, meeting docs, research, product decisions, and investor materials
GitHub
Code repository, issues, documentation, and version control
Claude / Codex
Design planning, product documentation, code support, and engineering acceleration
Figma / Design Tools
Wireframes, prototype, design system, and investor visuals
Data / API Research
Wildfire and hazard feeds, geospatial assumptions, alert source evaluation
Admin Agent Layer
Agentic layer that reads working docs, supports Asana tasking, summarizes updates, creates follow-ups, and reduces founder admin load

We are not just buying subscriptions. We are buying speed, coordination, and reduced execution drag.

Use of Funds

Small checks help us get from concept to credible MVP without overcapitalizing too early.

Angel participation in $5,000 increments.

Category What it supports Estimated cost
Entity, legal, and finance Formation docs, basic agreements, bank and accounting readiness TBD
Product and design tools Figma, prototyping, asset creation, design system setup TBD
Engineering tools GitHub, hosting, app dev tooling, test environments, code support TBD
AI / tooling stack Claude, Codex, agent support, documentation automation, task acceleration TBD
Data / API exploration Hazard feeds, map layers, geospatial assumptions, alert-source evaluation TBD
MVP build support Contract help, technical support, integrations, QA support TBD
UAT and mock testing Test plans, simulated active-area testing, neighborhood feedback loops TBD
Contingency Unplanned setup, data, legal, or technical costs TBD
Total TBD

Budget is designed for pre-raise proof, not production-scale operations.

What This Funding Unlocks

The first dollars create proof points.

MVP Scope Document
Defined MVP scope and product requirements document
Clickable iOS Prototype
Investor, advisor, and user feedback-ready prototype
Product Roadmap
Working roadmap through summer 2026 UAT
Privacy Model
Documented privacy and permissions architecture
Data Assumptions
Wildfire-first data-source assumptions and integrations
Simulation Testing Plan
End-to-end mock hazard testing plan and method
Technical Architecture
Lightweight MVP build plan and cost basis
Early Community Feedback
Buyer model recommendation and next-stage raise clarity
John Elliot
John Elliot
CEO / CMO
Owns
  • Outreach and relationship development
  • Community and partner strategy
  • Marketing narrative and positioning
  • Investor and stakeholder conversations
  • External validation and market feedback
Randall Fransen
Randall Fransen
CPO / COO
Owns
  • Product strategy and roadmap
  • UX, design direction, and prototype quality
  • Technical planning and build oversight
  • Operating system, tooling, documentation, and workflow
  • MVP definition, UAT planning, and execution discipline
Mission / Operating Belief

Community resilience is built before the emergency.

The communities most exposed to changing weather, fire risk, and infrastructure strain cannot rely on information alone. They will need guided preparation, trust, and when the moment of crisis comes, the ability to coordinate.

  • Safe Neighbor status
  • Locating / protecting family and pets or livestock
  • Knowing which neighbor has helpful items: tractors, trailers, vehicles, water
  • Sharing access info securely
  • Local incident reporting / verification
  • Focused chat/help/coordination, less noise
9:41 ECA
Boulder Heights
Preparedness Hub
Emergency partner view 4 neighborhood roles active
Check on Maple Drive Confirm pet transport Share generator access Run evacuation drill
The Ask

We are looking for aligned early supporters to help us reach a credible MVP and summer test cycle.

Angel support in $5,000 increments to fund the pre-raise path from planning to prototype to MVP validation.

  • Early angel capital
  • Strategic advisors
  • Emergency management and preparedness conversations
  • Data and mapping guidance
  • Community testing partners in Colorado Front Range
  • Introductions to aligned investors or civic partners
We are building this because the gap is real, local, and repeatable. The first version starts here. The need does not stop here.
9:41 ECA
Boulder Heights
Group Ready
86%
Wildfire Watch Route A cached
Plan available offlineReady
Appendix A MVP Validation Questions
  • Do users understand the difference between official alerts, group updates, and observations?
  • Will households enter critical emergency information before an incident?
  • What information are users willing to share, and with whom?
  • Which check-in statuses are intuitive under pressure?
  • Do groups need one admin, multiple admins, or role-based access?
  • Which map layers are useful versus overwhelming?
  • How much offline functionality is required for trust?
  • Does simulation mode make testing more realistic and useful?
  • Who is the most natural buyer: household, group, HOA, civic org, insurer, or partner?
Appendix B Early Technical Considerations
  • Native iOS / Android paths may require platform-specific design and behavior decisions
  • Data-source reliability matters as much as interface design
  • Map overlays must be legible, useful, and not overpromise precision
  • Permissions should be designed before sensitive data is introduced
  • Offline mode must distinguish cached information from current live updates
  • Notification logic must avoid fatigue while still surfacing urgent changes
  • Simulation mode must allow end-to-end testing without requiring physical presence inside an active hazard area
Appendix C App Visual System
Design Direction
  • Clean iOS-first wireframes, white and warm gray base
  • Calm green for safe / check-in status
  • Orange for watch / prepare
  • Red only for evacuation / urgent alerts
  • Blue sparingly for official information or map context
  • Rounded cards, large readable labels, low visual noise
Avoid
  • Tactical or military styling
  • Fear-based red-heavy screens
  • Overly complex emergency dashboards
  • Dense government-style interfaces
  • Prepper visual language
  • Anything that feels like social media chaos