Proc

What needs you, when it needs you.

Prototype. Designed end to end.

Design render with invented data: a Mac desktop with a planning document open. Proc shows a call starting in two minutes at the top, three messages waiting for a reply down the right, a timer top left, two blocked items and a summary of the day bottom left, and recent actions bottom right. — The resting state: asks with a wait ring, a call countdown, who's blocked on you, and what you closed. Concept view of the prototype with invented data, a fictional company, people and deals. Not a screenshot.

The problem

Notifications treat every message the same. The cost isn't the message, it's working out whether it needs you, and when.

How it decides

Three lanes. A request from a system arrives as data. A short ask shows as written. A long message is condensed to its one ask, with the exact sentence it came from.

Quiet by default

The same desktop in Proc's louder style, with invented data: two messages waiting, harder card edges, and the recent actions bottom right set in heavy italic capitals. — Concept view of the prototype with invented data, a fictional company, people and deals. Not a screenshot.

Most of the time it stays quiet. For a moment after you act, it marks what you did, not what arrived. Never during a call, never for backlog.

Shadow before drive

The model runs alongside plain rules first. Users' real actions are the ground truth, and the model only takes over once it beats the rules on the same events. If it errors, the rules take over; it never silently hides anything. Message text stays opt-in, telemetry is counts only.