Context

Verso is a self-initiated concept product: an internal operations platform that runs a team's requests and approvals end to end, from a marketing spend sign-off to vendor onboarding to time off. It was designed and built as a working demo on fictional Northgate data, spanning a home dashboard, triage, queues, a request detail with its full audit, a visual workflow builder, and settings. It is the plumbing every company rebuilds badly in a ticketing tool, done as a clear, single system.

Problem

Approval tools fail on two fronts: people cannot tell where a request stands, and the audit of who did what and when is either missing or buried. An earlier version of Verso also failed a plainer test, it did not say what the product was or what you could do with it. The design problem was accountability made visible, plus a front door that orients a stranger in one line.

Approach

Every request is built around a step chain, an SLA clock, and an exportable audit trail sharing one screen, so state, timing, and history are always together. The workflow builder lets you rebase the approval chain by inserting conditional gates, and publishes versioned. Triage proposes a route and a reply as an editable draft, never an auto-send, carrying the same preview-before-send discipline. Home was rebuilt as an orienting front door.

Outcome

A request-to-approval flow that runs end to end, submit through triage, step chain, and publish, with an audit trail you can export on any request. The workflow builder handles conditional branches and versioned publishing. Home now teaches the product in a sentence and routes you straight into the three things you can do. The visual system was kept exactly and the product clarity was fixed.