Proptech · TC

Reidy: TC

TC is the surface every action on Reidy has to pass through. Thirty-two ticket types, one month. The only version that ships is the one where nothing gets designed twice.

Role
Design engineer · dashboard, components, package
Timeline
Jun–Jul 2026 · one month
Package
@reidyai/ds · designed and shipped
Shipped
Internal · live

42 components carrying 32 ticket types

The shape of the problem

Every action on Reidy becomes a ticket: registering, listing, editing a loan product, pausing one. A coordinator has to read each one and decide.

Subtract until it's buildable

Figma Make gave me a full screen set in days. It also decided every treatment fresh, on every screen.

Every colour needs a job

Colour count was a speed decision first. Every extra hue is a choice a developer has to get right on every screen.

A third verdict, placed last

Every generated screen offered approve or reject, in the header, above the evidence.

Where the chassis bent

One class of ticket refused the chassis. Listing and loan product edits aren't approvals of a thing. They're approvals of a change.

What the build surfaced

TC is live internally. I shipped the components as @reidyai/ds, and the developers built TC from it under the same names. Five tickets have run through it; one took the full action required path.

Deep Adalja · Next case study