⚠ Confidential · Business Plan · Not for Public Distribution
Moonlit Social Labs

Fault Line
Business Plan

Community infrastructure accountability — for the next 36 months

v1.0 · 2026 · Michael Wylde · moonlit-social-labs@proton.me

Table of Contents

  1. Executive Summary
  2. The Problem & Why It Persists
  3. The Solution & Product Vision
  4. Market Analysis & Sizing
  5. Competitive Landscape
  6. Business Model & Pricing
  7. Operations & Cost Structure
  8. Go-to-Market Strategy
  9. Financial Projections
  10. Team & Org Structure
  11. Risk Analysis & Mitigation
  12. 12 / 24 / 36 Month Milestones
  13. Use of Funds & Capital Plan
  14. Exit / Sustainability Strategy
01 · Executive Summary

The accountability layer for America's broken infrastructure system.

Fault Line is a free mobile and web app that turns one-tap photos of infrastructure problems — potholes, broken streetlights, sidewalk hazards, water main breaks, and 20 other categories — into community-verified, GPS-stamped, legally significant reports that automatically escalate to the responsible government authority.

The product is built around a simple insight: cities ignore problems they're not legally documented as knowing about. Every state in America has a "notice of defect" statute that creates legal liability when a municipality fails to fix a hazard it has been formally notified about. For 30 years, almost no one has used those statutes — because almost no one had the documentation. A 311 phone call is not documentation. A timestamped photo with GPS coordinates, a community of corroborating witnesses, and an auto-generated demand letter citing the specific state statute is.

Fault Line is the documentation infrastructure. The 10-second photo is what users see; the legal pressure is what cities feel.

$3B
Annual pothole damage
$786B
US deferred maintenance
$30/mo
Operating cost at launch
300 DAU
Break-even point

The product is fully built and ready to ship. The mobile app (React Native + Expo) has 11 screens and 43 service modules. The web app (Next.js 15) has full reporting, magic-link auth, and a Leaflet map. The backend (Supabase + Postgres + 5 Edge Functions) is production-ready with row-level security, server-side rate limiting, and AI-powered photo analysis via Claude. 42 government authorities are pre-loaded for Massachusetts, Rhode Island, and New Hampshire. Operating costs are projected at under $30/month at launch and break-even at 300 daily active users via banner ads alone.

We seek $50K–$150K in pre-seed grant capital to fund a 12-month runway covering app store fees, AI inference, professional brand identity, founder stipend, and municipal pilot kickstarting.

02 · The Problem & Why It Persists

America's infrastructure is failing — and the system designed to fix it is structurally broken.

The visible problem

The American Society of Civil Engineers gives US infrastructure an overall grade of C-. The Federal Highway Administration estimates a $786 billion deferred maintenance backlog. AAA reports Americans spend $3 billion a year on vehicle damage from potholes alone. Add liability lawsuits, property depreciation, healthcare costs from cyclist/pedestrian injuries, and fuel waste — the real annual cost of infrastructure neglect exceeds $30 billion.

The invisible problem

The system designed to address this — 311 — was launched in 1996 and has not been meaningfully upgraded. Its five fatal flaws:

  1. No tracking. A 311 call typically generates no ticket, no confirmation, no GPS, no photo. The city receives an oral description and the resident never knows what happened.
  2. No aggregation. When 15 people call about the same pothole, the system may create 15 separate records — or zero, depending on the operator. Severity is invisible to leadership.
  3. No accountability. Response time data is internal. Citizens cannot compare their city to neighbors or hold individual departments accountable.
  4. No legal evidence. A phone call is not documentation. There are no GPS coordinates, no photos, no timestamped proof of notification.
  5. No community. Each resident's frustration is siloed. There is no shared view, no collective action, no momentum.

The structural problem

The reason 311 has not been fixed is that the incentives are wrong:

Until a tool exists that aggregates citizen frustration into legally and politically significant data, the cycle continues forever.

03 · The Solution & Product Vision

Make the documentation effortless. Make the consequences automatic.

Fault Line is built around three principles, in order of priority:

Principle 1: Friction is the enemy.

Every second between "I see a pothole" and "I've reported the pothole" is a second the user can change their mind. We obsess about it. The Quick Report flow is one screen. No account. No login. No form fields except "tap the photo" and "tap submit." AI fills in everything else.

Principle 2: Aggregation creates power.

One person yelling about a pothole is easy to ignore. Three people pointing at the same pothole creates "community verification." Ten people creates an automatic legal escalation event. The math is the user's superpower.

Principle 3: Consequences are mandatory.

The app does not just report problems — it generates legal pressure. Auto-generated demand letters cite state-specific statutes. Insurance claim packages bundle GPS evidence with notification timestamps. Fiscal impact projections show authorities the math: "Fix this for $75 today, or face $12,000 in liability next year." Inaction becomes the expensive option.

What the product actually does

The product spans ~50 individual features documented exhaustively at features.html (plain + technical). The headline capabilities:

For the complete technical architecture (database schema, edge functions, AI routing, security architecture, cost analysis), see ARCHITECTURE.html.

04 · Market Analysis & Sizing

Three concentric markets — each meaningfully large on its own.

TAM — Total addressable market

Every American with a smartphone who experiences infrastructure problems. Functionally, this is approximately 240 million US adults, of whom roughly 95% carry smartphones. The actionable subset — people who would download a free, frictionless app to report local problems — is harder to size but conservatively numbers in the tens of millions.

SAM — Serviceable addressable market

People in jurisdictions where Fault Line has authority routing pre-loaded. Today this is Massachusetts (~6.9M residents), Rhode Island (~1.1M), and New Hampshire (~1.4M), totaling ~9.4M. With each new state added (~3 weeks of authority research and seeding), SAM expands by the state's adult population.

SOM — Serviceable obtainable market

Realistic adoption in the next 36 months, given marketing budget, app store competition, and word-of-mouth dynamics. Civic-tech apps with a clear consumer benefit (Citizen, NextDoor, etc.) regularly reach 1–5% penetration in their target metros within 2 years. Targeting 1% of SAM by month 24 = ~94,000 installs, with a stretch goal of 250,000 by month 36 as additional states come online.

Adjacent markets

05 · Competitive Landscape

The category has incumbents — none of them are doing what we do.

CompetitorAudienceStrengthsGaps
SeeClickFix (CivicPlus)Sold to citiesEstablished, integrated with city back-officeNo consumer brand, no legal pressure features, no public grades, no AI photo analysis, no community verification incentives
Open311 (protocol)CitiesOpen standard, allows interoperabilityJust a protocol — not a product. Doesn't generate consumer value
Boston 311 / NYC 311 (city-specific)City residentsDirect integration with that city's systemsSiloed, no cross-city visibility, no accountability layer, English-only
Citizen / NextDoorLocal communitiesBrand recognition, social engagementNot designed for infrastructure reporting; no escalation; no legal tools
City contact forms (default)AnyoneFree, ubiquitousNo tracking, no accountability, no community, no data, no legal weight

The competitive moat for Fault Line is not a single feature — it's the combination. Any one of these competitors could add legal demand letters or photo AI tomorrow. None of them will build the entire stack: 10-second reports + AI + community verification + auto-escalation + legal letters + insurance packages + public grades + predictive analytics + multilingual accessibility + bidirectional Open311 sync, all in one consumer-facing free app.

The reason none of them will is that the incentives don't align. SeeClickFix's customer is the city, so they will never build features that publicly embarrass the city. Boston 311 will never build cross-city comparisons. Citizen monetizes engagement, not problem-solving. The category is wide open for a citizen-aligned tool that takes the city's side only when the city is right.

06 · Business Model & Pricing

Free at the top of the funnel. Multiple monetization tiers below.

Fault Line is and will remain free for individual users. The product's social mission depends on universal access. Monetization is layered and additive:

LayerMechanismStageStatus
1. Banner adsGoogle AdSense (web), Google AdMob (mobile). $1–3 eCPM.From day 1SDK installed; placeholder IDs; awaiting AdSense + AdMob approval
2. Ko-fi donationsOptional voluntary supportFrom day 1Live (ko-fi.com/moonlitsociallabs)
3. Ad-free subscription$2.99/mo or $19.99/yr via RevenueCat (mobile) + Stripe (web)Month 3+Scaffolded behind a feature flag; activates after store approval
4. Municipal licensingWhite-label dashboards, custom routing, predictive analytics exports. $5K–$25K/year per city.Month 6+Pilot conversations TBD
5. Data licensingAnonymized, aggregated infrastructure data sold to insurers, journalists, academic researchersYear 2+Future
6. Personal injury referralsRouting damage-claim users to attorneys on a referral fee. Highly regulated, requires state bar review.Year 2+Future

Why this stack works

Every layer is additive and non-cannibalizing. Banner ads keep the lights on. Donations build identity. The ad-free subscription monetizes the most loyal users without locking out new ones. Municipal licensing is the largest opportunity but takes months to close, so it's never the foundation. By year 3 the revenue mix is roughly 30% ads, 25% subscription, 35% municipal, 10% data/referrals.

Pricing rationale

The $2.99/mo ad-free price is anchored to comparable utility apps (weather, news, podcast players) and is below the threshold where most users will cancel after a month. It's not priced to maximize ARPU — it's priced to maximize the conversion rate among people who genuinely don't want ads but want to support the project. The annual price of $19.99/yr (44% discount vs. monthly) is designed to capture loyalty.

Municipal licensing pricing follows a tiered model: $5K/yr for a city under 50K residents, $15K/yr for 50K–250K, $25K/yr for 250K+. This is well below SeeClickFix's reported pricing, deliberately positioning Fault Line as the affordable consumer-friendly alternative.

07 · Operations & Cost Structure

Built deliberately to operate near zero — until success forces growth.

Most civic-tech projects die from cost overruns long before they die from lack of users. Fault Line was architected from day one to be durably cheap. Every infrastructure choice optimizes for the free tier first.

ServiceFree tierMonthly cost (launch)Triggered upgrade
Supabase500MB DB, 1GB storage, 50K MAU, 500K edge invocations$0$25/mo at 50K MAU
Anthropic Claude APIPay per use (no free tier)$5–20Scales linearly with photo upload volume
Resend (email)3,000 emails/mo$0$20/mo at 3K+
Apple DeveloperNone$8.25Fixed
Google Play$25 one-time$0Already paid
Domain (fault-line.dev)None$1Fixed
GitHub Pages (marketing site)Unlimited (public repo)$0Never
Vercel (Next.js web app)Hobby tier$0$20/mo at moderate scale
Sentry (errors)5K errors/mo$0$26/mo at 5K+
Upstash Redis (rate limit)10K requests/day$0$10/mo at heavy use
Expo EAS (builds)30 builds/mo$0$15/mo at 30+
AdMob / AdSenseN/AGenerates revenue
TOTAL$14–29/mo

The cost structure is unusually favorable for a consumer app. $30/month operating costs. Break-even at ~300 daily active users via banner ads alone. Every additional user beyond break-even is contribution margin. The business does not need venture-scale growth to be self-sustaining; it just needs honest organic adoption.

Where costs grow

The two cost lines that scale with usage are Anthropic AI (pay-per-photo) and Supabase storage (photos and videos). Both have aggressive caching strategies in place — the AI cache table stores results so identical analyses are not re-run, and the photo pipeline downsamples and compresses before upload. At 10,000 daily reports, projected AI cost is approximately $100/month, easily covered by ad revenue at that volume.

08 · Go-to-Market Strategy

Earned distribution. Local press. Accountability content.

Fault Line is not a category-creation play; it's a category-replacement play. The category already exists (city-specific 311 apps, SeeClickFix). Customers already feel the pain. The job is to be the better answer — and to get in front of people at the moment they're frustrated.

Phase 1 — Launch (months 1–3)

Phase 2 — Content engine (months 3–9)

Phase 3 — Municipal pilots (months 6–18)

Phase 4 — Network effects (months 12+)

09 · Financial Projections

Conservative base case — break-even by month 9, profitable by month 18.

MetricMonth 3Month 6Month 12Month 24Month 36
Total installs2,00010,00040,000120,000250,000
Daily active users3001,5006,00018,00040,000
Reports / month1,5009,00040,000140,000320,000
Ad revenue / month$50$300$1,200$3,600$8,000
Subscription revenue$0$150$900$3,000$8,000
Municipal revenue$0$0$5,000$30,000$80,000
Total monthly revenue$50$450$7,100$36,600$96,000
Operating cost / month$30$50$150$500$1,200
Net contribution / month$20$400$6,950$36,100$94,800

Assumptions: 1 daily active user per ~7 installs, 5 reports per DAU per week (5% are heavy reporters who account for 80% of volume), 3% conversion rate to ad-free subscription at month 12+, 1 municipal pilot signed by month 6 and 1 per quarter thereafter. These are conservative — civic-tech tools with strong product-market fit have shown installs growing 2–3× faster.

Sensitivity

The plan is not dependent on any single revenue line. If municipal licensing is slow, ads + subscription alone reach $19,600/month by month 36 — still net-positive. If subscription conversion is lower (1.5% instead of 3%), total revenue at month 36 drops to ~$80K/month, still durable. The downside scenario is "no traction at all," which is bounded by the $30/month operating cost; even with zero revenue, the project can run for years on a small grant.

10 · Team & Org Structure

Today: one person who builds fast. Tomorrow: a small senior team.

Today

Michael Wylde — Founder, Engineer, Designer, Writer

Solo developer who built Fault Line from concept to production-ready in [n months]. Operates Moonlit Social Labs, an independent civic-tech studio. Reachable at moonlit-social-labs@proton.me.

The lean structure is a feature for early-stage civic tech: low burn, fast decisions, no committee paralysis. Solo founders do not scale forever, but they ship faster and waste less capital than venture-padded teams.

Year 1 hires (in priority order, when funding allows)

  1. Designer / Brand — accessibility-conscious illustrator and brand identity. Likely contract, ~$5K–10K.
  2. Mobile engineer — additional React Native + Swift/Kotlin capacity for store-specific issues, dashcam mode, routing engine.
  3. Partnerships lead — handles municipal sales and grant applications. Quarter-time at first.

Year 2+ hires

Civic engagement specialist (community management, local press), data engineer (predictive analytics), legal counsel (state bar reviews for personal injury referrals).

11 · Risk Analysis & Mitigation

Honest accounting of what could go wrong.

1. Adoption risk

The biggest risk is that nobody installs the app. Civic-tech apps notoriously struggle with cold-start problems. Mitigation: aggressive local PR strategy, comparative city report cards as press hooks, and an extremely low-friction onboarding (no account required) that maximizes conversion of any traffic we can generate.

2. Authority hostility

Cities may resent being publicly graded and may attempt to discourage use of the app, intimidate users, or refuse to acknowledge reports. Mitigation: every report is anonymized when escalated; we never share user identities with authorities; the public health grades are based on the city's own response data and so are factually defensible; legal demand letters cite real statutes.

3. Legal liability

The legal demand letter feature could expose Moonlit Social Labs to claims from cities arguing that we misrepresent legal standing. Mitigation: every demand letter explicitly states "this is not legal advice" and recommends users consult an attorney for actual claims. The letters are templates citing real statutes, not legal opinions.

4. Defamation / abuse risk

Users could submit fake reports, defamatory descriptions, or photos of private property. Mitigation: server-side rate limiting (max 10 reports/hour/user), bot honeypot, content moderation queue for cluster-escalations, RLS-enforced ownership, ability to flag and remove reports.

5. AI cost runaway

If Anthropic raises Claude pricing significantly, AI costs could become a meaningful line item. Mitigation: AI cache table (identical analyses are not re-run), photo downsampling before upload, ability to swap AI providers (Gemini, OpenAI, local model) via the centralized AI service abstraction.

6. App store rejection

Apple or Google could reject the app for unspecified reasons. Mitigation: the product is conservatively designed (no novel APIs, no controversial content, no in-app purchases on launch), the metadata is professional, and we have multiple submission pathways (ad-supported, ad-free, web-only fallback).

7. Founder bus factor

One developer is the entire engineering team. Mitigation: code is well-documented (ARCHITECTURE.html), open-source where possible, commit history is public, secrets are managed in Supabase Vault and recoverable. A new engineer could ramp in days, not months.

12 · 12 / 24 / 36 Month Milestones

Concrete checkpoints — what we promise vs. when.

Month 0 (today)

Month 3

Month 6

Month 12

Month 24

Month 36

13 · Use of Funds & Capital Plan

$50K–$150K covers a 12-month runway with everything we need.

Line itemYear 1Notes
Founder stipend (12 mo, part-time)$36,000$3K/mo — modest. Enables full-time focus on the project.
Apple Developer Program$99Required for iOS App Store
Google Play Console$0Already paid one-time fee
Domain & DNS$120fault-line.dev + email routing
AI inference (Claude)$300Conservative estimate at projected scale
Supabase + Resend scale-up$700For when free tiers are exhausted at ~10K MAU
Professional brand identity$5,000Logo, app icon, color system, brand guidelines
Design contract work$3,000App store screenshots, marketing graphics, accessibility audit
Marketing & PR$8,000Press kit, paid local-press placements, podcast sponsorships
Conferences & travel$3,000Code for America Summit, civic-tech conferences for partnerships
Legal & accounting$2,500LLC setup, contractor agreements, basic IP
Reserve / contingency$10,000~10% buffer for the unknown
TOTAL (Year 1)$68,719Mid-range case

The mid-range Year 1 budget of ~$70K is the realistic minimum for credible execution. The lean case (~$50K) cuts the founder stipend in half and trims the marketing line. The aggressive case (~$150K) doubles the founder stipend, adds a part-time mobile engineer for the second half of the year, and triples marketing.

Capital sources we are pursuing in priority order: Knight Foundation civic-tech grants, MacArthur Award for Creative & Effective Institutions, Ford Foundation civic engagement, Code for America grants, local/state civic innovation programs, and finally impact-focused angel investors if grant capital is insufficient. We are not pursuing traditional venture capital because the company structure (long-term sustainability, low burn, no high-growth obligations) is misaligned with VC return expectations.

14 · Exit / Sustainability Strategy

Built to last, not built to flip.

Most startups optimize for an exit. Fault Line is built for the opposite: indefinite sustainable operation on lean revenue, with no acquisition pressure. The cost structure, the funding sources, and the founder mission all push in the same direction.

That said, a few realistic outcomes:

  1. Long-term sustainable independence. The most likely outcome. Lean operation, organic growth, multiple small revenue streams, no equity dilution. The founder retains creative and political independence indefinitely.
  2. Acquisition by a civic-tech company. CivicPlus (which owns SeeClickFix), Tyler Technologies, Granicus, OpenGov — any of these could find Fault Line strategically interesting if it reaches meaningful adoption. An acquisition would be considered only if the acquirer commits to the free consumer tier in writing.
  3. Acquisition by a media or insurance company. Local news chains (Gannett, Lee Enterprises) could use Fault Line data as a content engine. Auto insurers could use the claim-evidence packaging as a customer perk.
  4. Spin-off into a nonprofit. If the project succeeds and the founder eventually steps back, the natural transition is to a 501(c)(3) civic-tech nonprofit with a board of advisors. The product would continue under public-interest stewardship.

Whatever the path, the design constraint is the same: the consumer-facing app must remain free and uncompromised. Every other commercial decision is downstream of that.

Confidential — for the recipient only.
© 2026 Moonlit Social Labs. All rights reserved.
← back to pitch