GetOut Weekly  ·  The Parent Network

The Local
Weekend
Network

AI-powered, human-curated local weekend media — one operator, N cities. Pittsburgh is the proof. The area-code namespace is the network.

Action-Driven Locals-First Curated Picks Weekend Energy Get Out. Do More.
Live Network

Three Cities. One Machine.

Every GetOut city runs on the same AI-native pipeline. Each is a locally-branded, independently-hosted edition with city-specific curation, color, and voice.

412
Flagship · Live
GetOut
412
Pittsburgh, PA

The origin city and proof-of-concept. Black and gold heritage editorial style. First newsletter sent, subscriber list growing, full pipeline running nightly.

Pipeline: ~940 events/night
Status: Phase 1 · Audience Growth
Est.: July 2026
Visit getout412.com →
216
Live
GetOut
216
Cleveland, OH

Guardians navy and red. Great Lakes energy. Metroparks, the Flats, Cedar Point region. Cloned from Pittsburgh in days, not months — the machine proving its scale thesis.

Pipeline: 1,229 events/night
Status: Phase 1 · Audience Growth
Est.: July 2026
Visit getout216.com →
614
Live
GetOut
614
Columbus, OH

OSU scarlet. Short North arts scene, Cbus food culture, Hocking Hills daytrips. Third city in the network — shipped concurrently with Cleveland on the same infrastructure.

Pipeline: 1,116 events/night
Status: Phase 1 · Audience Growth
Est.: July 2026
Visit getout614.com →
The Machine

Investor-Grade Infrastructure

The GetOut pipeline collapses the labor cost of curated local media to under one hour per week per city — without automating away the human judgment that makes it worth reading.

01
AI Ingestion

Nightly multi-source pull: Ticketmaster API, Google Calendar feeds, local venue iCal endpoints, TMDB film data, Humanitix event listings. Deduplication, normalization, confidence scoring.

Scale: 3,000+ events/night across the network
Cost: API quotas only — no scraping labor
02
AI Pick Analyzer

Claude AI scores each candidate 0–100 against the operator's documented taste using past picks as few-shot context. Suggests vibes, daypart, and best-bet flag. Pre-sorts the curation queue.

Cost: ~$0.09/night across the network
Asset: Every override trains the dataset
03
Human Curation

The operator reviews a pre-sorted, AI-scored queue and selects 8–12 picks. Best Bets and editorial blurbs are written by hand — this is the trust layer and the product's competitive moat. Zero-date-error policy.

Time: 30 min/week at steady state
Output: The weekly newsletter draft, ready to send
04
Auto-Publish

On operator approval: newsletter sends via Resend, static site rebuilds (~1,500 pages), calendar feed updates. Full city presence maintained with one click. No CMS. No agencies. No headcount.

Channels: Email · Web · iCal feed
Rebuild time: Under 60 seconds per city
Marginal Cost / City / Month
<$50
Infrastructure, APIs, and AI processing. Hosting shared across the network; incremental cost per city is config, not capex.
Founder Time / City / Week
≤1 hr
The design center of the model. Curation is the only non-automatable function — and it stays that way by intent.
Events in Network Pipeline / Night
3K+
Across Pittsburgh, Cleveland, and Columbus. Scales linearly with city count; the pipeline is the durable asset.
Owned Namespace · Coming Cities

14 Markets. One Network.

The area-code domain system is the moat. Every target metro has a matching [area-code]do.com domain owned and reserved. Clone speed means the pattern is provable at scale before anyone notices.

All domains are owned. Expansion order is governed by TAM, whitespace, tourism index, and cluster synergy — not by date. No launch dates are promised; the Ohio Valley cluster (513/317/502) may ship as a batch ahead of the top-ranked individual markets. City 4 is gated on Pittsburgh reaching its Day-90 audience threshold and at least one existing city reaching a repeatable growth loop.

412
Pittsburgh, PA
Live · Flagship
216
Cleveland, OH
Live
614
Columbus, OH
Live
#1
313
Detroit, MI
Owned · In Dev
#2
615
Nashville, TN
Owned · In Dev
#3
513
Cincinnati, OH
Owned · In Dev
#4
317
Indianapolis, IN
Owned · In Dev
#5
502
Louisville, KY
Owned · In Dev
#6
901
Memphis, TN
Owned · In Dev
#7
314
St. Louis, MO
Owned · In Dev
#8
312
Chicago, IL
Owned · In Dev
#9
704
Charlotte, NC
Owned · In Dev
#10
407
Orlando, FL
Owned · In Dev
#11
410
Baltimore, MD
Owned · In Dev
For Investors

The Business

GetOut Weekly is an early-stage media infrastructure company. We are in Phase 1 — building audience. The model is designed for honest, phased revenue with hard go/no-go gates between stages.

Phase Model

Phase Name Revenue Model Gate to Advance
1 AudienceCurrent Affiliate ticket links; zero marginal cost Day-90: 500 subscribers · 40%+ open rate. Kill criteria: <300 subs or <30% opens with consistent weekly publishing.
2 Sponsorship $150–$500 per newsletter send; one sponsor slot per issue; quarterly lockout contracts 2,000 subscribers + first paid sponsor signed
3 Network 10 cities × $2–8K/month; network buy packages across all cities; pipeline licensing to local publishers and tourism boards City 2 or 3 at ≤2 hrs/week founder time; repeatable acquisition loop proven

Structural Moats

Moat #1
Cost Structure
Under $50/month marginal infrastructure per city. A competitor entering this market faces payroll costs we never incur. The unit economics are asymmetric by design: each city we add increases revenue capacity; the cost curve barely moves.
Moat #2
The Taste Dataset
Every pick, rejection, and editorial override trains the AI analyzer. A competitor can copy the site in a weekend. They cannot copy 52+ weeks of labeled curation decisions across three cities. The dataset compounds with every issue published. Best Bets are human-touched by policy — the trust layer is not automatable.
Moat #3
Area-Code Namespace
14 metro-area domains owned across the target expansion map. In local media, the [area-code] is the identity — locals already call their market by its code. A locked namespace is a structural barrier to branded competition in each market.
Moat #4
Compounding SEO
Each event published creates a permanent indexed page. The pipeline rebuilds nightly — fresh content, compounding domain authority, zero incremental labor. Tourist and visitor search terms ("things to do in Pittsburgh this weekend") are served by pages that auto-regenerate from the same data that runs the newsletter.

Fastlane CENTS Analysis

Control
6
→ 8
Entry
4
→ 7
Need
7
→ 8
Time
8
→ 9
Scale
7
→ 8

Baseline composite: 32/50  ·  Achievable path documented: 40/50 with namespace lock, taste dataset compounding, venue-direct revenue rails, and quarterly sponsor contracts. Full analysis: internal CENTS framework (Fastlane discipline; Unscripted, MJ DeMarco).

"AI ingestion collapses the labor cost of curated local media to ~1 hr/week/city, making a one-person, multi-city 'worth the drive' events network viable. Pittsburgh is the proof; the [area-code]do pattern is the network."

— GetOut Weekly Business Model Doc · July 2026

Talk to the Founder

We are an early-stage business building in public. If the thesis resonates — the cost structure, the moat stack, the namespace play — reach out directly. No deck required to start a conversation.

Send a Note
This page contains forward-looking statements about the business model, revenue projections, and expansion plans of GetOut Weekly. All revenue figures are targets based on industry benchmarks and internal modeling — not historical results. GetOut Weekly is an early-stage company in Phase 1 (Audience Growth) as of July 2026. No guarantee of future performance is implied. Subscriber counts and growth rates are not disclosed on this page. Investor conversations are subject to a separate disclosure process.