Studio Scale
Let's Talk

The paths found too late

Plan for what goes wrong.

We plan permissions, empty states, errors, interrupted tasks, alternate roles and other paths that usually turn up too late in development.

Example
You don’t have accessAsk an admin to add you to this project.Request accessRequest sent ✓
Payment didn’t go throughYour card was declined. Nothing was charged.Update cardCard updated ✓
You’re offlineYour changes are saved and will sync later.Try againSynced ✓
Session expiredLog in again to pick up where you left off.Log inSigned in ✓

The work

The moments we design

The paths we design so nobody has to improvise them in code.

Book a call

The problem

Sounds familiar?

If 2 or more of these ring true, the hard paths need designing too.

Tick the ones that sound like you

Selected work

Selected edge-case work

Screens on Dribbble and Behance

# Revisual / Sync failed

Calendar list with published, unpublished and disconnected statuses, and a banner: Last sync failed

ScreensErrors

When a sync fails

A clear banner when a calendar sync fails, with what it means for the data and where to fix it, plus a status for every calendar.

View on Dribbble

# Influencer Marketing AI / Locked insights

Unlock insights modal on desktop, tablet and mobile

ScreensLimits

When a feature is locked

A locked-insights modal that explains what’s behind the limit and how to unlock it, on every screen size.

View on Dribbble

# Trending Influencers / Email code

Confirm your email screen with a 6-digit code and a timer before a new code can be requested

ScreensVerification

A code that expires, and a way to retry

Email confirmation with a 6-digit code and a visible timer before a new code can be requested.

View on Dribbble

# Revisual / No events yet

Calendar leaflet editor with event filters and a hint: No events to display? Go to the Setup tab

ScreensEmpty data

When there’s nothing to show

A calendar editor that tells people what to do when no events appear, instead of leaving a blank page.

View on Dribbble

Proof

“We went hunting for somebody who would care about every tiny detail, every workflow, every edge case, and be able to take a complex and novel idea and convert it to a specific design and plan.”

James Pursey · Founder & CEO, Replicate Labs
Upwork Job Success
100%
Regular clients
10+
Recognized by
Dribbble Select

Ways to start

2 ways to start

Plan edge cases before the build, or fix the ones you’ve found.

  • # Before the build

    Plan the hard paths

    Permissions, errors and interrupted tasks, designed before development.

    • Edge-case inventory
    • Flows for each path
    • Screens and copy
    • Handoff in Figma

  • # Live product

    Fix the gaps

    Find the paths nobody designed, then design them properly.

    • Review of the current product
    • Missing paths by impact
    • Redesigned screens
    • Handoff in Figma

FAQ

Questions founders ask

Book a call See all questions

Permissions and roles, empty states, errors, interrupted tasks, offline, expired sessions, limits and anything specific to your product.

It depends on the scope. Once we’ve seen the full picture, we’ll share a rough timeline.

Yes. Every error gets a clear message and a way to recover.

Yes. Engineers are welcome early, and they often know edge cases we should plan for.

Complete states cover how each screen looks in every state. Edge-case flows cover the paths between screens when things go wrong.

Related capabilities

Explore all capabilities

Complete states

Empty, loading, error and success states, designed before they ship.

User and screen flows

Every step, decision and failure point, mapped before the screens.

UX writing and content design

Words in the interface that say exactly what happens next.

Accessibility design and WCAG reviews

Contrast, focus, labels and touch targets designed in, not bolted on.

2 client slots open

Show us the path nobody planned.

A rough idea is a fine place to start. We’ll get back to you within 24 hours.

Book a call Let's talk