PRODUCT DESIGN · 2026

Custom Fields

People were already tracking projects. Just not anywhere the software could see.

ROLE

Design intern at Swipey, a corporate card and spend platform for Malaysian SMEs. I did the interaction model and the AI layer, and built the prototype with AI agents.

THE GAP

Finance teams needed columns Swipey didn't have: Project, Client, Billable. They improvised in the notes field, where nothing can be filtered, grouped, or reported on.

Two things already existed. Project names in the notes field, and Alfie, the receipt reader people trusted to file their expenses. The work was connecting them.

The transactions table has no Project column, while Alfie reports that projects were mentioned in the notes of 14 transactions

THE DECISION

Custom fields are org-wide. One person deleting a column destroys everyone's reporting, so management is admin-gated and deletion takes a typed confirmation.

Manage fields, restricted to admins, listing every org-wide field with its visibility and required toggles beside Alfie's suggested fields

Alfie read receipts. I gave it notes to read rather than introduce a second assistant. Suggestions land as dashed pills carrying the note they came from, so accepting eight at once is still informed.

A new Project column filled with dashed Falcon, Atlas and Orbit suggestion pills, with Alfie offering to accept all eight values at once

WHAT SHIPPED

A field you create in one click from a nudge that cites its evidence, filled by Alfie, confirmed by a human, filterable the moment it exists.

NOW PLAYING

WHAT STUCK

A new column landed off screen — one of eleven findings I only caught by using the prototype as the admin who'd live in it. Next, the same lens on the mobile table.

Product DesignData UXAI InteractionDesign Systems