# Gravity AI Pitch Deck v6
**Updated: July 21, 2026**  
**Approval Rails / Ledger / Agentic Payments Edition**

---

## 1. Title Slide

**GRAVITY**  
*Turn scattered accounts into a governed action engine.*

User-governed approval rails, ledger integrity, and agentic payment infrastructure for recurring expense management.

---

## 2. The Problem

### Recurring spend is fragmented, but decisions still need owners

People do not lack another dashboard. They lack a system of record for who can approve recurring expenses, what can auto-run, and how actions get executed across subscriptions, insurance, service bills, and family accounts.

- Fragmented across merchants, portals, cards, and inboxes
- Informal approvals handled through memory, texts, and cleanup
- No execution layer between insight and money movement

---

## 3. The Insight

### Visibility is not enough

Users do not want more passive monitoring. They want:

- explicit approval tiers
- clear thresholds and exceptions
- a durable ledger of actions
- AI that can execute within user-defined rules

---

## 4. Our Solution

### Approval rails plus ledger plus agentic execution

1. **Connect** — ingest accounts, payment methods, and recurring records
2. **Govern** — apply approval logic, thresholds, and routing rules
3. **Execute** — let the agent pay, pause, switch, renegotiate, or escalate
4. **Ledger** — record every approval, override, action, and rationale

---

## 5. Customer Value Proposition

### Positioning

For busy professionals and high-complexity households managing fragmented recurring spend, Gravity is user-governed expense operations infrastructure that centralizes approvals, preserves context, and executes actions on their behalf.

Unlike bill trackers, dashboards, and generic AI assistants, Gravity owns the layer between intent and money movement.

---

## 6. Target Customer

### Primary user

- Busy professionals and households with 12+ subscriptions and multiple service accounts
- Already trying to stay organized with notes, card reviews, inbox search, or spreadsheets
- Need clearer control, less manual coordination, and lower spend leakage

---

## 7. Product

### What the engine does

- Unified ledger for recurring accounts and actions
- Approval routing for auto-run vs review vs escalation
- Agentic execution for payment-adjacent actions
- Auditability and action history
- Preference learning and exception handling

---

## 8. Why Now

### The infrastructure moment is now

- Account sprawl keeps rising
- AI agents can finally execute multi-step work
- Users will trust automation when control and auditability are explicit

---

## 9. Market Opportunity

### Sized bottom-up from the wedge, not the vision

| Metric | Value | Basis |
|--------|-------|-------|
| **TAM** | ~$20B | ~110M US subscription-holding households + UK/CA/AU, at $12–15/mo for recurring-spend control |
| **SAM** | ~$4B | 20–25M US high-complexity households (busy professionals 30–55, 12+ subscriptions, already self-tracking, validated WTP) |
| **SOM** | $8–10M ARR (Year 3) | ~50K paying households × $13–15/mo blended (individual + family plans) ≈ 0.2% of SAM |

### Why the market is real

- Average American spends **$219/mo across 8.2 subscriptions** but estimates only $86 — a 2.5× perception gap (C+R Research, 2026)
- Category proof: Truebill hit ~$100M annualized revenue and a $1.275B acquisition (now Rocket Money) on visibility and cancellation alone
- The $182B global AI-productivity market is the **expansion story** as Gravity becomes the governed action layer — it is not the wedge math

---

## 10. Business Model

### Free to start, premium where execution saves time

- Core access: low-friction approvals and baseline control rails
- Premium execution: deeper workflows and more hands-off operations
- Aligned economics: monetize after measurable time savings and lower leakage

---

## 11. Competitive Landscape

### The gap is between insight and money movement

- Bill monitors categorize or alert, but do not govern execution
- Budgeting apps explain spend after the fact
- Generic AI assistants recommend but do not serve as a system of record
- Autopay lacks approval policy, review thresholds, and durable rationale

---

## 12. Moat

### Trust, policy, and execution compound together

The moat is the governed action layer:

- approval logic
- ledger history
- execution traces
- revocable permissions
- user-owned context

---

## 13. Go-to-Market

### Start with recurring expense workflows that already hurt

1. Land in expensive subscriptions and recurring bills
2. Prove control and lower manual overhead
3. Expand into insurance, utilities, and service accounts
4. Compound into broader recurring financial workflows

---

## 14. Roadmap

### Three phases

1. **Approval proof** — recurring subscriptions and accounts
2. **Ledger plus execution** — payment actions, negotiation flows, vendor handling
3. **Payment operating layer** — broader recurring expense operations

---

## 15. Team & Traction

### Built lean, with core infrastructure already in hand

- Solo technical founder
- Browser automation, telemetry, and agentic product work already underway
- Public website, deck sources, and PDF generation now wired directly in repo

---

## 16. The Ask

### Raising a $250k–$1M seed

Use of funds:

- ship v1 control rails
- prove trusted execution
- extend payment actions and vendor handling
- add first product and growth hires