Relay borrows FlowFunds' structure: a misty light ground, one giant headline, and the logo itself rendered as a glass object behind the work. The content is a handoff instead of a bank balance, and the colours are Relay's own.
I studied 12 frames from the recording and your dashboard screenshot. These are the moves I'm carrying over.
Their dashboard hero uses the FlowFunds petal mark extruded in dark green glass with chrome edges, cropped off the top right. Nothing else is 3D.
Relay: the Return Path R, rendered live in the same material.A pale sage-grey field with a soft green glow behind the object. White panels sit on it, so the panels read as paper on a table.
Relay: #EDF1EF ground with a forest glow; white working panels."Today's priorities" is set enormous and light-weight, with a one-line subtitle. Everything else on the page is small and calm.
Relay: "Today's handoffs" in Urbanist 400; Geist for the work.In "Needs attention", the most urgent item is a glossy dark-green gradient card; the rest are pale. Tags are small pills.
Relay: the handoff due today gets the glass card.Stat tiles put a large light numeral next to a plain-language unit ("6 upcoming deadlines").
Relay: "4 open questions", "3 decisions to verify".Timeline blocks run from a colour into near-black, with an avatar on the right edge.
Relay: each handoff's week, coral for today, green for this week.The top nav is a translucent bar; the active item is a white pill. The account is a dark pill on the right.
Relay: same pattern, Incoming · Sent, plus a New handoff button.Their AI panel ends in a striped mint risk meter and quick chips.
Relay: a "Context check" meter showing how much of a handoff is confirmed. No AI is implied.Relay speaks in soft clay. Each object stands for one part of a handoff, in the brand's own colours: forest, mint, lime and coral, with a fine speckle like printed matte clay. They are rendered from simple rounded forms, so the whole set stays consistent and new objects are easy to add.
The Incoming hero, the stat tiles, the section headers on a handoff, empty states, and the two moments of transfer: sent and accepted.
Carry information on its own. Every object sits beside a label or number, so the screen still reads without it.
The emerald glass Return Path stays as the logo's hero render, for the launch film and marketing stills. The clay set is the product's everyday voice.
Relay's four colours already sit very close to FlowFunds' (deep green, mint, coral-orange), so I kept them. Forest becomes the glass and the urgent card. Lime only appears on dark surfaces or as the meter. Coral marks today and blockers. Lime and coral each get a darker ink for text, because the originals fail contrast on light grounds.
| Role | Light | Dark | Used for |
|---|---|---|---|
| Primary action | #173D32 | #C8F169 | Accept, Send, New handoff |
| Surfaces | #FFFFFF / #F3F6F4 | #0F1B17 / #14221D | Panels / inner cards, inputs |
| Muted text | #5C6964 | #9BAAA3 | Rationale, metadata |
| Confirmed | #2A7047 on #DFF0E2 | #86D3A0 | Confirmed decisions, accepted |
| Assumption | #7A5208 on #F7E8C2 | #EDC56E | Unverified, awaiting review |
| Proposed | #345A79 on #E0E9F0 | #9CC0DD | Proposals, dependencies |
| Blocker | #A33D27 on #FBE2DA | #F39B85 | Blockers, due today |
Urbanist stands in for FlowFunds' round geometric display face and is used only for page headlines and big numbers. Geist carries all the working text; Geist Mono carries timestamps and counts.
Kept for behaviour rather than looks: status as a small pill with a dot, and lists you can scan without opening anything.
Both build their 3D from the brand's own form and reuse it, which confirms the FlowFunds approach of making the logo itself the object.
Product-first marketing: the hero image for a Relay landing page should be this dashboard, not an illustration.
A line goes out, turns, and comes back carrying something, and the whole shape reads as a lowercase R. The coral dot marks the moment the work changes hands.
Relay is built on a survey of 48 people on product teams and six interviews with people from design, engineering, product and research. The survey measured how big the problem is; the interviews showed why it happens. Each finding below maps to something in the product.
Survey: 48 people on cross-functional teams at mid-sized SaaS and tech companies (22 engineers, 14 product designers, 12 product managers). Interviews: six semi-structured sessions of 30–45 minutes, coded with thematic analysis and grouped into five affinity clusters.
One line from each participant. Between them, they describe the same gap from both sides of a handoff.
“The file is usually there, and the ticket is usually there. What isn't obvious is which version we agreed on after the review, or why we moved away from the first idea.”
“I don't know whether it was considered and rejected, or whether nobody got to it.”
“The decision makes sense if you were in the meeting. A week later, someone sees the ticket and assumes the original scope is still the plan.”
“People grab a single quote from my slide deck to justify a UI choice, completely ignoring the caveats we noted in the report.”
“I need to know what's done, what's blocked, what could break if I change it, and who can answer the one thing I'm unsure about.”
“A handoff isn't complete just because somebody posted a link.”
Each finding and what Relay does about it. “See it” opens it in the prototype.
Every decision has a Why, shown directly under it.
Decisions are Confirmed, Assumption, Proposed or Out of scope.
How strong is it? and What this doesn't prove on each decision.
Where it stands comes first. Next actions have an owner and a due date.
A What could break section, separate from blockers.
A source can be marked as the Agreed version.
Not opened yet, Clarification requested and Accepted states.
Questions show Open N days after three days.
People wanted more context, and also less paperwork. So only four things are required: what the work is, who takes it, the project, and where it stands. Everything else is optional, and appears only when it's filled in.
Relay has two homes, one for each side of a handoff: Incoming for the person inheriting work, Sent for the person passing it on. Everything else hangs off a single object, the handoff, so every path leads to the same detail screen.
Built from the prototype as it stands. Green chips show where a screen links to another one.
The four journeys the prototype supports end to end. Diamonds are decisions; the lanes after them are the branches.