← All work
CRM & Enterprise · SHIPPED

Watch Box

Custom Salesforce Lightning pages built around how the sales team actually worked.

Watch Box Salesforce design

Watch Box needed new custom pages added to its Salesforce CRM — not a generic Lightning template, but pages built around how its specific sales team actually worked.

01
Discover & define

I worked directly with the PMs to translate their user stories into concrete requirements for Sales Cloud, rather than starting from Salesforce's default page layouts. That began in Object Manager: which standard objects the team actually used, which custom fields had accumulated, and which of them belonged on a page a rep looks at fifty times a day.

02
Design

I produced multiple Salesforce Lightning page-layout options in Figma for the team to evaluate against their actual sales workflow.

Design sample · demo data
Watch Box inventory search with keyword and brand filters over a tabbed results table
Inventory search. Results are tabbed by object — Inventory, Models, Deals — so one query answers the three different questions a rep asks. The columns are the operational ones the team sorted on daily, days in status and inventory age, rather than the record fields Salesforce lists by default.
Design sample · demo data
Point of sale order page with line items on the left and account plus order summary on the right
Point-of-sale order. Line items hold the left column while the customer’s account and the running total stay pinned to the right, so a rep never leaves the order to check a balance before checking out.
IN THE PLATFORM
OM
Object Manager

Audited objects, custom fields, and record types before proposing layouts. Several fields the team assumed were essential turned out to be unused, which is what made a shorter page defensible.

AB
Lightning App Builder

Delivered each layout option as an App Builder composition — regions, components, and visibility rules — so the PMs could evaluate them against the real sales workflow and an admin could assemble the winner directly.

Design sample · demo data
Add origination form sectioned into model information, watch information and negotiation information
Add-origination intake, sectioned into model, watch condition, and negotiation. Keeping the offer amounts in their own section at the end separates the pricing conversation from the cataloguing work that has to happen first.
Design sample · demo data
Market pricing table with saved views as tabs and colour-coded price change columns
Market pricing. The saved views sit across the top as tabs instead of inside a filter panel, because the team came back to the same five questions every day. Change and % change carry the only colour on the page.
OUTCOME

The PMs selected and shipped from the layout options that best fit how the sales team worked day to day.

SAMPLE DESIGN ATTACHED
All work
GET IN TOUCH

Open to senior product design roles

Remote, US hours — full-time or contract. Happy to walk through the decisions behind any case study here.

Email betayards@gmail.com →