By Trayo

GTM apps worth showing the team

The design system behind Trayo, for the tools you build on top of it. Accounts, people and signals render with real faces, real logos and tables that hold up under dense pipeline work — so what you ship looks like part of the product, not a side project.

React 19 · Tailwind v4 · light and dark · free and open source

Why it matters

Looks finished, because it is

It looks like it came from Trayo

The same design system the Trayo app is built from — the colours, the type, the surfaces, the density. What you build reads as part of the product your team already uses, not as a separate thing bolted on beside it.

Credible before anyone clicks

Most internal tools are judged on the first screenshot, in a thread, by people who will never open them. This is the difference between something that gets adopted and something that gets politely ignored.

The hard parts are already right

People and companies are what a GTM screen is full of, and they are fiddly: faces, logos, fallbacks, dense tables that stay legible. Those are solved here, so the quality does not depend on how much time you had.

Consistent across everything you build

The second tool matches the first, and the fifth matches both — without anyone maintaining a style guide. Colour, type and dark mode all come from one token set.

Live demo

See it running, right here

The real components on this page — not a video, not a screenshot. Flip it to dark with the switch in its header.

Install

Copied in, not installed

The components go into your project rather than into your dependencies — so they are yours to read, edit and keep, with nothing to rely on afterwards.

  1. 1. Copy the components into your project

    The library is vendored, not installed — the files become yours, with no dependency on this site. degit pulls the directory without any git history.

    npx degit trayoai/ui/src src/trayo-ui

    No npx? Grab the tarball instead:

    mkdir -p src/trayo-ui
    curl -L https://ui.trayo.ai/trayo-ui.tar.gz | tar xz -C src
  2. 2. Install the real dependencies

    Ordinary public npm packages. Requires Tailwind CSS v4 and React 19 (React 18 is not supported).

    npm install react@^19 react-dom@^19 clsx tailwind-merge lucide-react \
      class-variance-authority tailwindcss @tailwindcss/vite \
      @radix-ui/react-avatar @radix-ui/react-checkbox @radix-ui/react-dialog \
      @radix-ui/react-dropdown-menu @radix-ui/react-label @radix-ui/react-popover \
      @radix-ui/react-scroll-area @radix-ui/react-select \
      @radix-ui/react-separator @radix-ui/react-slot @radix-ui/react-switch \
      @radix-ui/react-tabs @radix-ui/react-tooltip
  3. 3. Wire up the CSS

    Tailwind first — the stylesheet extends its theme. No @source directive is needed: the components now sit in your own source tree, which Tailwind v4 already scans.

    @import "tailwindcss";
    @import "./trayo-ui/styles/trayo-ui.css";
  4. 4. Build something

    Light is the default; add class="dark" to <html> for the dark palette. The whole token set flips — no component changes.

    import { AppShell, PageContainer, PageHeader, Person, CompanyCard, Button } from './trayo-ui'
    
    export default function App() {
      return (
        <AppShell>
          <PageContainer>
            <PageHeader title="Target accounts" actions={<Button>Import</Button>} />
            <CompanyCard company={{ name: 'Ramp', domain: 'ramp.com', industry: 'Fintech' }} />
            <Person person={{ id: 'p-1', name: 'Dana Whitfield', title: 'VP RevOps',
                              company: 'Ramp', companyDomain: 'ramp.com' }} />
          </PageContainer>
        </AppShell>
      )
    }

Documentation

Everything, documented beside the code

The full component reference — every prop, every variant — lives in the README, so it travels with the copy you take. Read it on GitHub →

Components

Entities
Person (variants row, inline, stacked, lead), PersonCard, PersonBanner (tones solid, soft, plain; size compact), PersonContactLinks, Company, CompanyCard, CompanyMeta, PostCard (a post and its author), EntityList (a spaced, divided list of Person or Company rows), FactList and Fact (labelled points: why now, fit, evidence), JobMove (left one company, joined another), PersonAvatar, CompanyLogo, ToneAvatar
Tables
DataTable (sortable, selectable, paged via `pagination`, skeleton loading; `variant="simple"` or `"large"` and `hideHeader` for a short list in a card), Pagination + usePagination, and the raw Table primitives
Page scaffolding
AppShell (with brand / nav / actions top bar), AppShellNavLink, PageContainer, PageHeader (size default / large / lead; eyebrow, icon, stats; variant plain / card / band), Split (a main column and an aside), Surface (title / description / icon / actions for a framed panel), IconTile, Well, StatGrid
Summaries
HeroStat (one headline figure with a reading, a chart and supporting figures), StatBand (figures on one sheet; `headed` for titled cells), EntityStack (a pile of logos or faces with +N), Funnel, SplitBar, Meter (a score against a pass mark), MethodNote (how the data was made, as steps or sources)
Breakdowns and small charts
BreakdownTiles (a tile per company, usable as a filter), DistributionList, ShareTicks, ShareRing, DivergingColumns, ColumnChart, Sparkline, Ring
Decorative
BrandMesh, GradientText
States
EmptyState, StatTile, Callout (tones; leave `texture` unset and the brand picks one for the app), Skeleton, Progress
Type
PageTitle, SectionTitle, CardTitle, EntityName, Body, Meta, Eyebrow, SectionLabel, DataLabel
Controls
Button, Input, Textarea, Select, Checkbox, Switch, Label, Tabs, SegmentedControl
Display
Badge, TagChip, Card, Separator, Tooltip, ScrollArea
Evidence
EvidenceItem (tags in the brand tint, a headline, a source line, the explanation, a footer; `media` for a person or a job move), EvidenceList (titled, with a count)
Overlays
Dialog (with DialogBody for content that scrolls), PersonDialog (a dialog about one person: banner, body, footer actions), Popover, DropdownMenu
Feedback
Toaster, toast() — variants default, success, warning, destructive, preview
Charts
ChartLegend, DataLabel, CHART_COLORS, CHART_SEQUENTIAL, CHART_MUTED, chartColor(i), chartSequential(t)

Working with Trayo data

Pass an API response straight to a component — it reads what is there and leaves out what isn't.

const { data } = await fetch('/v1/people?limit=25').then(r => r.json())
return data.map(p => <Person key={p.id} person={p} showContact />)

A person’s photo has two names

GET /v1/people returns profileImageUrl, but a POST /v1/find contacts result carries photoUrl — which is also the field you send when creating a person. <Person> reads both (plus imageUrl / avatarUrl), so pass the API object straight through rather than remapping it.

For coding agents

Building this with an agent?

Point it at ui.trayo.ai/llms.txt — the same library, written as instructions it can follow. Generated from the repo on every deploy, so it never drifts from the code.

Read https://ui.trayo.ai/llms.txt and follow it. Use the Trayo GTM UI
components for all UI in this app.