railway.app

# Funnel Teardown — railway.app

> An evidence-based read of railway.app's live conversion funnel, captured 2026-07-10.
> Every claim is measured from the page; each detected tactic carries the exact
> on-page string it fired on. Deterministic extraction — no LLM opinion. Read this
> to understand WHY this funnel converts (or leaks) — the persuasion principles it
> uses and the ones it's missing. It is a report to learn from, not a template to clone.

**Funnel type:** saas
**Evidence Coverage Score:** 70/100 (Partial)
**Path captured:** Homepage / Lander → Pricing → Features

## Scorecard — where the points come from
| Category | Earned |
|----------|-------:|
| Offer clarity | 0 / 8 |
| Action path | 17 / 20 |
| Trust & proof | 11 / 11 |
| Friction reduction | 4 / 10 |
| Value reinforcement | 10 / 10 |
| Risk reversal & urgency | 0 / 0 |

## What's working — tactics in play, with proof
Each is a persuasion mechanism the funnel actually deploys; the quoted string is the on-page evidence.
- **Us-vs-them comparison** — A comparison table framing the brand against alternatives.  
  _Proof:_ `p2: Compare features`
- **Free trial / freemium** — A free trial, free tier, or "no credit card" entry offer.  
  _Proof:_ `p2: free trial`
- **Trusted-by logo wall** — Customer/company logos or a "trusted by / used by" claim.  
  _Proof:_ `home: logos: TripAdvisor, Cognizant, Mercado Libre, G2X, Reducto`, `p2: logos: HIPAA_BAA, HIPAA_BAA, LOG_HISTORY, LOG_HISTORY, ENTERPRISE_SUPPORT`, `p3: logos: Deploy, Deploy, docker logo, helm logo, heroku logo`
- **Usage / adoption proof** — A count of developers / teams / companies / stars using the product.  
  _Proof:_ `home: 2M+ developers`, `p3: 2M+ developers`
- **Demo / docs entry** — A "book a demo" or documentation / API entry point.  
  _Proof:_ `home: Book a demo`, `p2: Book a demo`, `p3: Book a demo`
- **Lead-capture form** — An on-page form collecting contact details (email / name / phone) outside a checkout.  
  _Proof:_ `p2: name, email, Select an option, Select an option`

## What's missing — gaps for a saas funnel
Conversion tactics that apply to this funnel type but weren't found — the openings a competitor could exploit:
- **FAQ / objection handling** — not detected. An accordion / FAQ block answering objections.
- **Proof above the fold** — not detected. Social proof rendered within the first viewport on at least one step.
- **Pricing tiers** — not detected. Named plan tiers with per-month / per-seat pricing.

## Proof language observed
The exact phrasing this funnel uses to build credibility — study the *mechanism* (specific numbers, named counts, guarantees), not the wording:
- _(none extracted)_

## Measured design signals (facts, not a style to copy)
- Palette, area-weighted from live CSS:

| Hex | Usage | Likely role |
|-----|------:|-------------|
| `#13111c` | 34.7% | support |
| `#181622` | 22% | support |
| `#ffffff` | 21.1% | background |
| `#1b2132` | 7.5% | support |
| `#1f2b2e` | 7.5% | support |
| `#0d0c14` | 2.6% | support |
| `#1c1a28` | 1.1% | support |
| `#1e132a` | 0.9% | support |

- Type: display `IBM Plex Serif`, body `Helvetica` · size scale (px): 11, 12, 13, 14, 16, 18, 20, 36, 40, 54 · radius (px): 6, 8, 10, 12, 16

## Funnel facts
- Depth reached: 3 steps
- Proof points: 0 across 0 steps
- Free-gift line items (max on a step): 0
- Discount/anchor pricing: no · Countdown: yes · Subscription: yes
- Price continuity lander→checkout: not detected

---
_Full machine data: `tokens.json`, and the JSON bundle at api.uxxray.com. The value here is the analysis of a real competitor's funnel — what it does, what it doesn't, and the evidence for each._