Redesigned Linea's home screen. The bit i care about most is the signals panel, the system watches every run and flags anything that looks wrong: "hallucination suspected", "tool error", last seen, how often. you catch it before a user does.
Each execution shows its cost. the support assistant's about a cent a run. Second shot is the canvas where the flows get built.
Is the home page enough at a glance, or would you pull executions higher?
Agent products resist normal product marketing. There's no single interface to screenshot and the category vocabulary has gone generic, so a feature list communicates almost nothing.
We built Heron's explanation as a four-beat scroll that runs the agent's actual loop. The model appears and is watched. Violations surface with plain language and a real IBC clause. An edit is applied after approval. The system learns the firm's standards.
Pacing was the main design problem. Each beat needed enough scroll distance to register as a separate action, without the section becoming so long that people bail before the payoff. The sequence carries the technical detail that would otherwise sit in a spec table.
The four-beat scroll is a smart way to make the agent’s loop feel tangible—much clearer than a static feature list. The restrained visual system gives the interaction room to breathe.