Return Circle

A returns platform for Shopify merchants, designed from first principles — starting with whether the problem was even real.

Years: 2022 — 2023
Scope: Web app · Product strategy
Role: Product Designer

Overview

Return Circle started as a bet, not a brief: that Shopify merchants were quietly losing money and goodwill on returns, and that a better returns flow was worth building a company around. The work began before any screen — with the question of whether the problem was even real.

Early-stage design is less about pixels than about reducing uncertainty. The riskiest thing to get wrong wasn't a layout — it was building the wrong product beautifully.

Product Designer from zero — merchant interviews and hypothesis testing through the first shippable web app, working directly with the founders.

Selected work

Flagship

Validation — a problem worth building on

Decision

I ran interviews with Shopify store owners and mapped how returns actually happen — the emails, the spreadsheets, the refunds issued on trust. The goal was to separate the loud complaints from the expensive ones.

Alternative

We could have taken the founding hunch at face value and started designing the app we imagined. Fast to start, expensive to unlearn.

Why

Talking to merchants first reshaped the product: the pain wasn't the return itself, it was the uncertainty and manual work around it. That insight decided what the MVP had to solve — and what it could ignore.

Artwork pending

Deep dive · 01

The MVP — deciding what not to build

Decision

I scoped the first version around a single loop — request, approve, refund — and consciously left everything else out until real usage argued for it.

Alternative

A fuller launch — analytics, automations, multi-store, custom rules — would demo well and delay the only thing that mattered: putting it in front of real merchants.

Why

In a zero-to-one product, shipping is how you keep learning. A tight MVP got the loop into merchants' hands quickly, so the roadmap could be written by evidence instead of guesswork.

Artwork pending

Deep dive · 02

Money movement — KYC without the cliff

Decision

Handling refunds meant handling money, which meant KYC and banking partners. I designed verification to collect what regulation demands in the order a merchant could actually supply it.

Alternative

The simplest engineering path is one long compliance wall up front. It satisfies the bank and loses the user on step two.

Why

I broke verification into staged, resumable steps tied to what each merchant was trying to do, so security requirements arrived as context rather than a gate — the bank's rules met without making anyone feel interrogated.

Artwork pending

The first build

The surfaces that made up the MVP — the smallest set that let a merchant run a return end to end.

Merchant dashboard

The operator's home — open returns, what needs a decision, and what's owed, in one glance.

Returns

The core loop — request, review, approve or decline — written so a busy shop owner can act in seconds.

KYC

Identity and business verification, staged so merchants clear it without hitting a wall.

Payouts

Refunds and settlements laid out plainly — amounts, timing and status, no surprises.

Notifications

The nudges that keep a return moving — for the merchant, and downstream for the shopper.

Outcome

Turned a founding hunch into a validated problem through direct merchant research.

Defined an MVP scope tight enough to launch and learn from quickly.

Designed KYC and payout flows that satisfied banking partners without stranding users.

Reflection

Return Circle reframed what I think design is for at the earliest stage. Before product-market fit, the most valuable thing a designer produces isn't a polished interface — it's reduced uncertainty. Every interview, prototype and deliberately-cut feature was a way to make the team less wrong about what to build next. The interface mattered; being right about the problem mattered more.

Let's talk

Have a role or a product in mind? I'm one message away.

Write me an email→Message on Telegram Connect on LinkedIn