← WORK
PRODUCT DESIGN · 2026

Custom Fields

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

Custom Fields
PROBLEM_

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.

MY 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.

RESEARCH_

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 structure was already there. It was just sitting in a text box where nothing could reach it.

KEY INSIGHT_

CHALLENGE_

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.

PROCESS_

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.

SOLUTION_

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.

LIVE PROTOTYPE_

The working prototype is embedded below.

This is the real exploration, not a mockup. Open the Alfie nudge to create a Project field, then accept or edit what it fills in.

MOBILE PREVIEW_
Custom Fields prototype on mobile

Desktop-scale prototype — open on a larger screen to try it.

OUTCOMES_

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.

← PREV

Swipey Admin

NEXT →

Get Started