UXXRAY · facts, not opinions
◉ All x-rays
Above-the-fold capture of neon.tech
their above-the-fold, as captured

UXXRAY · Teardown dossier

neon.tech

neon-tech-2026-07-09-desktop

content · desktop · 2026-07-09

30 /100

Sparse ★☆☆☆☆ 3 measured categories

Score breakdown

  • Action path 0/7
  • Friction reduction 6/6
  • Value reinforcement 0/7

The funnel, frame by frame

see their whole funnel without clicking through it — scored step by stepmeasured
Homepage / Lander
01

Homepage / Lander

3 tactics
Trust badgesLogo wallDemo / docs
Unify
02

Unify

3 tactics
Sticky CTAFAQDemo / docs

Why it scores what it does

the score explained category by category — expand any for the on-page language they usemeasured

Neon scores 30/100 — sparse evidence coverage. Strong on friction reduction; thin on action path and value reinforcement. Expand any category for the on-page language.

Friction reductionhighFAQ / objection handling
  • FAQ / objection handling
Action pathnoneno signals detected

Not detected — proof above the fold.

Value reinforcementnoneno signals detected

Not detected — us-vs-them comparison.

Their design system

palette by on-page usage · type rendered live · the radius scalemeasured
full palette ordered by on-page usage %
primary#e4f1eb
accent#e4f1eb
bg#e4f1eb
surface#ffffff
text#797d86
accent

Body copy in their text role, on a surface card.

the roles, doing their job
The quick brown fox48px
Jumps over the lazy dog44px
A subheading in their voice40px

Body copy set at their measured paragraph size. This is how their product reads to a first-time visitor — same family, same scale, same weight.

  • List item one, at body scale
  • List item two
  • List item three
4px
50px

Build brief — copy for your agent

the whole teardown as one grounded spec: tokens · proof language · detected tactics · funnel facts
neon.tech · 1/3 tactics · 0 proof templates · tokens ✓ 
# Agent Brief — build in the style of neon.tech

> Machine-extracted from a live funnel teardown (2026-07-09). 100% facts — measured
> tokens, detected patterns, harvested proof strings. No LLM interpretation.
> Tokens: `tokens.json` / `tailwind.css`.

**Category (label):** —
**Funnel:** Homepage / Lander → Unify

## Palette (area-weighted from live CSS)
| Hex | Usage | Likely role |
|-----|------:|-------------|
| `#e4f1eb` | 28.7% | background |
| `#ffffff` | 26.6% | background |
| `#fafafa` | 22.9% | background |
| `#151617` | 9.9% | support |
| `#000000` | 6.8% | support |
| `#111315` | 2.7% | support |
| `#18191b` | 1.1% | support |
| `#ebf5f0` | 0.7% | background |

Curated roles: `primary=#e4f1eb` · `accent=#e4f1eb` · `bg=#e4f1eb` · `surface=#ffffff` · `text=#797d86`

## Type
- Display: `Inter`
- Body: `Inter`
- Size scale (px): 10, 12, 13, 14, 15, 16, 18, 20, 24, 40, 44, 48
- Radius (px): 4, 50

## Patterns detected (fact-based) — 1/3
- **FAQ / objection handling** — An accordion / FAQ block answering objections. _(p2: FAQ/accordion)_

## Proof language (harvested strings → templates)
- _(none extracted)_

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

## To replicate
Match the palette + type tokens above, deploy the detected patterns at the same funnel positions, and reuse the proof-language templates with your own numbers.