← → or click to navigate
A Map-Native Group Messaging App
Your Group’s Coordination Canvas
a@mobileflow.ai
1
Summary
Problem: Real life is already coordinated in group messages. Friends decide where to go, when to meet, who is coming, whether plans changed, and what happened after, all inside the thread. The group chat is already the default operating surface for social coordination. The problem is that group messaging was never actually built for coordination.
Solution: Hytch makes the group thread executable with map-native coordination tools that help small groups decide faster, move together, and actually follow through. It is a coordination engine built to turn “What’s the move?” into action.
2
Product Spine
Hytch is a messenger-first coordination engine. One spine: map-native group messaging. On top of that:
- Messenger: Geo-aware group chat; messaging and media first-order.
- Geo primitives: Project a Plan, Plan Polls, time-boxed location, place threads.
- Group Quests: Shared goals (e.g. 7 walks in 10 days, go to a Tennessee Titans game); plan pins and polls to complete them.
- Action verification: GPS + motion fusion; opt-in, time-boxed. Confirms arrival, dwell, safe rides.
- Rewards & carrots: Unlock only after verified outcomes. Reward Capacity Packs for sponsors.
- Sponsor console & analytics: Outcome rules and caps; aggregated dashboards.
3
How the GeoSocial Messenger Works: Users
- Project a Plan: Place + time in the group thread; everyone sees where and when.
- Plan Polls: “Who’s coming?” “Where next?” Turn chat into decisions.
- Plan a Carpool: Coordinate who’s driving and who needs a ride in the thread.
- Drop Location: Share your location or a place in the chat; time-boxed, group-only.
- Need a Ride: Request a ride from the group; ties into SafeRide and carpool coordination.
- Dangle a Carrot: Fund a small reward to nudge friends to show up; unlocks after verified arrival.
- Create Group Quests: Set shared goals (e.g. 7 walks in 10 days, go to a Tennessee Titans game); use plan pins and polls to complete them.
Core: map-native group messaging. Coordination, verification, rewards.
- Privacy-first location: Time-boxed, group-only; you control it.
- Verified actions: Opt-in verification for arrivals, dwell, safe rides. Rewards unlock only after verification.
4
How the GeoSocial Messenger Works: Sponsors
Sponsors don’t buy ads. They fund verified outcomes.
- Reward Capacity Packs: Sponsors pay a fixed amount; Hytch distributes up to a set limit in verified rewards. Campaigns pause when capacity is exhausted.
- Rules Engine: Set outcome rules (who/where/when). Pay only for verified outcomes.
- Reporting: Aggregated, privacy-preserving. No sale of personal data.
Outcomes: arrivals, off-peak visits, safe rides, group behaviors.
5
Business Model & Monetization
- Reward Capacity Packs: Sponsors pay fixed amount; capped distribution. No runaway spend.
- Premium group tools (optional): Subscriptions for templates, admin, enhanced recaps.
- Peer carrots: Micro-spend inside coordination; rewards unlock after verification.
- Data products (at scale): Privacy-preserving dashboards, reports, APIs from verified outcomes, never raw personal traces.
Settlement: prepaid capacity and programmatic distribution; avoids leakage of traditional incentive programs.
6
SafeRide
Sponsor-driven program on the same product spine: map-native group messaging. Groups plan the night in the messenger (Project a Plan, Plan Polls, “who’s driving?”, “who needs a ride?”). When a verified safe ride happens, sponsors fund rewards. Targets bars, campuses, events.
How it uses the GeoSocial Messenger
- Group chat & Project a Plan: “Tonight’s plan” and ride coordination in the thread.
- Opt-in verification: Same stack confirms ride from designated driver (friend, rideshare, taxi).
- Rewards on verified outcomes: Same Reward Capacity and rules engine. Non-profits (e.g. MADD, state safety councils); venues get “Responsible Drinking Partner” branding, insurance benefits, campus integrations.
7
Market & Opportunity
Hytch turns coordination and movement into verified, auditable outcomes that sponsors pay for. Not estimates. Proof.
- Buyers (venues, non-profits, agencies) already spend on incentives; they want verified behavior, not self-reported data.
- Regulation and insurers increasingly demand proof over estimates.
- SafeRide alone: non-profits against drinking and driving fund rewards; venues get safety narrative and insurance upside; campuses get verified designated-driver data.
Win condition: Weekly Active Groups and repeat rituals.
8
Roadmap
- Phase 1: Platform (Nashville and SafeRide): Group messaging core, geo primitives, ritual engine, trust controls (time-boxed location, privacy modes, safety and moderation tools). Initial sponsors and Reward Capacity Pack flow.
- Phase 2: User growth: Anchor groups, rituals (Tonight’s Plan, Next Stop, Weekly Recap). Peer carrots and sponsor pilots (verified arrivals, off-peak, SafeRide). Prove group density.
- Phase 3: Regional Expansion & LA/NYC Launch: Pre-funded outcome pools in LA/NYC; dynamic multipliers and templates.
- Phase 4: National: City playbook; sponsor dashboards; data-exchange APIs.
- Phase 5: Global: OECD metros; localized compliance; regional payments and partners.
9
Positive Outcomes
- Increase social connection and use of third spaces
- Help small businesses
- Minimize drinking and driving
- Reducing congestion
- Reducing carbon emissions (tracked in-app)
- Action-oriented communication saves time
10
Team
Andrew Grinde: CEO
5+ yrs as a business owner leading two companies he founded and now exited. Received a Bachelors Degree from Yale University.
Demetre Gostas: COO
4+ years C-level in Web3 with focus on Operations, L1 & L2 blockchains and DeFi protocols.
Nasos Lentzas: Full Stack Engineer
Senior Reliability Engineer at Allwyn Lottery Solutions and OpenBet. PhD from Aristotle University of Thessaloniki in Analytics and Data Visualization.
Samuel Harrison: Advisor
Advisor on product strategy, scaling operations, and go-to-market for early-stage mobility and consumer apps; background in technology and growth.
11
Use of Funds
- Cloud costs (infrastructure, hosting, tooling, etc.)
- AI subscriptions (for rapid software and BD development)
- Team Salaries (to focus full-time on growth and development)
- Customer Acquisition
- Hyper-targeted, data-driven campaigns to spur user growth (through which we can attract paid sponsors)
12
Contact and More Information
Company Legal Name: MobileFlow Inc.
State of Filing: Delaware
Office: Music Row, Nashville
Contact us
13