Partner Brief · June 2026 · US Park Pass · Atlas
The pass is one transaction. The trip is twenty decisions — where to stay, which trail, what permit, which town, what to pack. Atlas captures the traveler at the decision point, does their thinking for them, and earns across every layer of the trip. One audience, captured once, monetized many times over.
The same search that powers the header, the parks hub, and the map — try it:
No matches. Try a state name, park name, or city.
Searching…
Search unavailable. Try again or browse the map.
01 · The thesis
Every other park site sells one thing and sends the traveler back to Google for the rest. We do the opposite: we capture the planning intent, eliminate the decision fatigue, and earn across the whole trip. Each turn of the cycle funds the next and lifts every park alongside it.
01 — Capture
We already rank for the planning queries — the root domain carries DR 57 and ~1,600 referring domains, and the map ranks for ~50K monthly searches. Atlas converts that attention into a captured relationship: an email, an account, a saved trip — feeding the 211K-engaged list that is itself the launch channel. The cycle starts from an audience we already own.
02 — Serve the decision
Park-contextual aggregation plus the authored why — this basecamp for this kind of trip, because X — takes someone from “I want to visit Zion” to a confident, executed decision without bouncing to a forum or ChatGPT. Delivered value is what earns the engagement everything downstream is priced against.
03 — Monetize the intent
Qualified intent converts at higher ROAS, CR, and AOV than cold traffic ever will. The pass is the anchor; lodging and experience commissions, premium guides, and email commerce all layer onto the same captured audience — each click terminating in an executable action while the traveler is still deciding.
04 — Reinvest & compound
The margin feeds the engine: more pages, better targeting, conversion values pushed back into Smart Bidding. Cross-linked parks compound each other's rankings, and the audience compounds with every trip — so the next turn of the cycle starts from a higher base than the last.
02 · What the traveler sees
The surface is a trip-planning decision engine. Park pillars, entity cards for trails and lodging and experiences, a federal-lands map, premium guides, and one universal search — every screen ends in an executable action. These are live; click through.
Park pillar
The pillar pattern — hero, getting-there, trails, lodging, tips, pass CTA — composed from reusable components and themed to the park's biome. One template, every park.
Open Zion →Entity satellite
A trail that earns its own page — fit-check, season table, gear, the permit reality, Plan-B variants. Cards for trails, lodging, and experiences carry the why, not just a list.
Open the trail →Corridor
A multi-park road trip as a first-class entity, aggregating its parks in route order — the shape a real Utah trip actually takes, not five disconnected pages.
Open the corridor →Interactive map
A Mapbox surface of federal recreation sites with agency tiers and progressive disclosure — the live geographic context for any trip, lazy-loaded so it never taxes the page.
Open the map →Premium guides
Field-tested, fact-checked PDF guides sold through the same Shopify checkout as the pass. Mighty 5 is live; the catalog is the template every future guide inherits.
Open the catalog →The hub
64 parks in the data layer, four full suites live and scaling. The parks hub and header both run on the same universal entity index — nearly 2,000 searchable entities.
Browse the parks →One search index, every surface — parks, corridors, gateways, trails, guides:
No matches. Try a state name, park name, or city.
Searching…
Search unavailable. Try again or browse the map.
03 · The moat
The product is the surface; the pipeline is how it scales. One operator plus LLM pipeline-operators produce and maintain hundreds of pages across 63 parks — the labor that would take a five-person editorial team. The pipeline is the thesis, and it is the defensibility.
Fetch
Entity MCPs
AllTrails · Viator · LiteAPI — the agent pulls real entity data; nothing is fabricated.
Stage
Producer-cache
Raw fetch results land in a cache the canonical producers consume.
Normalize
Canonical producers
One producer per entity type — no freelanced scripts — emits the substrate.
Store
D1 + flat-JSON
Structured metadata in D1; editorial prose in slug-keyed JSON twins.
Render
Astro pages
The build-time LLM composes components by slug — it operates the pipeline, never redesigns it.
Running alongside, on every build:
Sources, crops, and focal-points every image through the catalog — never a raw R2 URL, never a hand-placed file.
Flags missing or broken images as labelled GitHub issues that bridge to the project board — gaps surface, they don't rot.
Four independent gates enforce tokens, layout, copy discipline, dead links, and decision-value. A page that drifts never reaches production.
Every structural decision passes a dialectical rig before it ships; every build cycle runs a dual-swarm against settled architecture. The pipeline only ever tightens — that self-iterating discipline is what makes “one operator at the scale of a team” hold.
04 · Go to market
This is an email-first launch, not an SEO bet. The Klaviyo Engaged-90 segment — 211K subscribers active in the last 90 days — is day-zero distribution we own outright. Four to six segmented sends put an estimated 15–30K sessions on the platform in month one: more traffic than a conservative year of SEO, delivering the first guide sales, the first affiliate clicks, and the behavioral data the smarter features need — all before Google has even indexed the surface.
The launch channel
The launch is sends, not spend: segmented waves to the 211K-engaged Klaviyo base, each wave landing on monetized pages instead of dead ends. Capture is wired live on the platform, so every wave also grows the list it launched from — the first P&L proof lands before Google does.
Platform
Retire the Wix surfaces onto the Astro platform — one data layer, one design system, pages that compound instead of four content islands that don't talk to each other.
Authority
Everything moves under usparkpass.com/parks/* via a Cloudflare path-router, concentrating ~1,600 referring domains on one root instead of stranding content on a low-authority subdomain.
Organic · the second act
63 pillars × clusters × satellites = thousands of indexed, cross-linked URLs compounding underneath while email carries the launch. Each new park lifts the others — an acquisition engine that grows while we sleep.
Revenue
Lodging, experiences, and gear resolve to partner links where they ARE the executable decision — CJ (Booking), Viator, Impact (REI / Backcountry), Amazon — never thin “Wirecutter for parks.”
Already live
Analytics in every page (GA4 + Clarity), the full UTM attribution scheme, and a working /guides → Shopify checkout path are built and verified. Supply is no longer blind — every revenue action is measured.
05 · The path
Today the business is split across three surfaces — the Shopify shop, the Wix content, and the Atlas dev domain. The endgame is a single unified usparkpass.com where shop and content share authority, cookies, and a brand frame. The cutover is staged behind a hard rank-rollback gate.
Phase 1 · Done
Astro pipeline, D1 data layer, universal search, the analytics + attribution + checkout demand side — built and verified. Four park suites live.
Phase 2 · Now
Replace the Wix subdomain, scale park suites toward the launch set, and run owned-channel sends to the engaged base — first revenue proof before Google arrives.
Phase 3 · Next
The Cloudflare path-router moves usparkpass.com/parks/* off Wix once rank monitoring has a baseline — guarded by a DNS-level revert if the map's ranking slips.
Phase 4 · Later
One domain, shared consent, programmatic expansion beyond the 63 national parks. The cycle runs on its own base and the moat widens with every park.
06 · How it pays
No single layer carries the business — each one earns from the same captured intent, and they stack. The pass anchors; affiliate and guides and email commerce build on top; trip-intelligence is the paid tier the behavioral data unlocks later.
The $8M anchor — America the Beautiful passes at ~$86 AOV. Atlas feeds it qualified, lower-CAC demand and displaces paid spend.
Lodging, experiences, gear — earned on bookings the traveler was making anyway, surfaced exactly where the decision happens. Validated post-stay, compounding with traffic.
$20+ field-tested digital guides, sold through checkout attach and the email engine. Each guide is also a load-bearing SEO asset — it sells AND ranks.
211K engaged subscribers, segmented by the trip they're planning — campaigns and flows that land on monetized pages instead of dead ends.
Live, trip-specific re-planning, permit alerts, and offline export — the per-trip paid tier the captured behavioral signal unlocks. Sequenced behind real usage, not guessed.
07 · The channels
The channels aren't three equal budgets — they're sequenced. Email is the launch engine and stays the highest-trust channel; the content surface compounds organic reach underneath it; paid spend gets sharper and smaller as owned demand displaces it. All three deposit into the same captured audience.
Owned · leads the launch
The Engaged-90 base is the engine: segmented launch waves, then Klaviyo flows keyed to the trip being planned — welcome, trip tips, intent-based drips. Every send lands on a monetized page, and every captured planner makes the next send bigger. The cheapest, highest-trust channel, and the one we own outright.
Earned · compounds underneath
The 63-park surface is an organic acquisition engine — and an LLM-discoverability play, structured so ChatGPT, AI Overviews, and Perplexity cite Atlas when someone asks about a park. It feeds the list email launches from.
Paid · shrinks as owned grows
Google Ads Smart Bidding fed by the CM2 profit pipeline — real conversion values, not proxy clicks. Every order email and organic win displaces a paid one, shrinking the 77% paid dependency.
Email proves the model in month one; content makes it compound; paid fills the gaps at better and better margins. That's the difference between buying traffic and owning demand — the flywheel gets heavier, and momentum carries it.
08 · The trajectory
The pass business is the foundation and it keeps its $8M. Atlas is a new, compounding revenue layer on top of it — and the readout of the value we deliver. The goal isn't a one-time lift; it's a curve that bends upward on its own as the cycle compounds.
Today
$8M
Pass business, healthy and growing — the anchor. Atlas demand side live; revenue layer switching on.
Near term
+$8K/mo
The email launch lands: segmented sends to the engaged base drive the first guide sales, the first affiliate clicks, and a list that's already bigger than when we started.
Year one
+$20K/mo
Root cutover done, a guide catalog, displaced paid spend, paid dependency trending from 77% toward ≤65%.
Year two+
$40K+/mo
Full park coverage, the paid trip-intelligence tier, partnerships — a self-reinforcing growth machine, not a campaign.
The numbers are the readout, not the point. Revenue-per-user is the readout of value-per-user — when the cycle delivers a genuinely better way to plan a park trip, the revenue follows, and it compounds.
One audience, captured at the decision point. Monetized across the whole trip. Compounding every turn.
Atlas