JOBR icon mark
JOBR Market mark
JOBR Trade mark
JOBR Drive mark
JOBR Wallet mark
JOBR Checkout mark
Home Work JOBR Business Ecosystem
JOBR logo
Case Study · Founding Designer

JOBR Business
Ecosystem

One token-based design system powering a growing multi-vertical commerce ecosystem — Market, Trade, Drive, Wallet, and Checkout — each its own sub-brand, all built on a single, disciplined foundation.

Company
JOBR LLC · Miami, FL
Duration
Mar 2022 – Present
Role
Founding Product Designer
Platforms
Web · iPad · iOS · Android
Adoption Rate
68–77%
5+
Sub-Brands Designed
77%
Platform Adoption
40%
Faster Delivery
4
Platforms (Web/iPad/iOS/Android)
3yr
Sole Designer → Led Team of 3
Overview

A business ecosystem
built on one system.

JOBR set out to build a multi-vertical commerce ecosystem — not a single SaaS product, but a family of interconnected experiences serving merchants, consumers, drivers, and traders, each carrying its own sub-brand under one parent identity.

I joined as the founding and sole designer in March 2022, when there were no screens, no components, and no system. My first decision — the one that shaped everything that followed — was to build the design foundation, an 8-step color system, a full typographic scale on Roobert, and a token library, before shipping a single product screen. That bet paid off across every vertical that followed.

Today the JOBR design system powers the core ecosystem: JOBR Market (commerce marketplace), JOBR Trade (C2C trading), JOBR Drive (fleet & delivery), JOBR Wallet (payments), and JOBR Checkout — each with a distinct mark built from the same geometric diamond motif, instantly recognisable as part of the family. Adoption sits at 68–77% (nearly double the industry average of 40%), and feature delivery is 40% faster than before the system existed. I have since grown and lead a team of three designers.

Every sub-brand mark, every color step, every type size traces back to one Figma foundation file — Foundations → Color System and Foundations → Typography — so that as the ecosystem keeps expanding, new verticals inherit years of decisions for free.

My Responsibilities
🧱
Design System Architecture
8-step color ramps, type scale, spacing, and motion — built from zero for cross-platform, multi-brand use.
🎨
Sub-Brand Mark System
Designed the modular diamond-motif mark language used to identify each vertical within the JOBR family.
🗺️
0→1 Product Strategy
Shaped scope, IA, and UX direction for every new vertical from discovery through launch.
🔬
User Research & Testing
Merchant interviews, usability tests, heatmaps via Hotjar, and funnel analytics via Amplitude.
🤝
Developer Handoff & DesignOps
Storybook + Zeroheight documentation, Figma variables, annotated specs, and QA sign-off.
Accessibility (WCAG 2.1 AA)
Every color pairing carries a contrast rating (AA/AAA) baked directly into the token spec.

"The design system wasn't a support function. It was the product strategy — the thing that let five sub-brands feel like one company without nine times the headcount."

At a Glance

Why design infrastructure
came before product screens.

Problem
No shared foundation for five sub-brands.

Market, Trade, Drive, Wallet, and Checkout were each being scoped independently, with one designer. Without shared color, type, and component rules, every new vertical risked fracturing the JOBR identity, duplicating design work, and shipping inconsistent accessibility — slowing delivery as the ecosystem grew.

Fractured Identity Duplicated Work Accessibility Debt Slowing Velocity
Solution
One token-based foundation, inherited by every vertical.

An 8-step color system, a single typographic scale, and a modular diamond-motif mark language — built before any product screen — let each new sub-brand inherit years of decisions for free. Every vertical shipped faster, more consistently, and with zero post-launch accessibility regressions.

77%
Platform Adoption
+40%
Delivery Speed
0
A11y Regressions
The Challenge

Three constraints,
one foundation.

01
One Designer,
Many Sub-Brands

As the sole designer, I had to define an identity flexible enough to spawn distinct marks for Market, Trade, Drive, Wallet, and Checkout — while keeping every one of them legible as "JOBR" at a glance.

02
Four Platforms,
One Language

Web, iPad POS, iOS, and Android all needed to feel unmistakably JOBR while respecting platform conventions. An 8-step color ramp and a single typeface (Roobert) had to bridge that gap without fracturing.

03
Accessible by
Default, Not Audit

Rather than retrofitting contrast fixes late, every single color step in the system — Primary, Complement, Neutrals, Extra, Error, Warning, Success — ships with its WCAG rating attached at the token level.

Design System

The stack that
compounds everything.

JOBR mark JOBR Design Foundation
↓ Tokens flow into every sub-brand and surface ↓
Deep Ocean
8 Steps
Iceberg
8 Steps
Moon / Black Ocean
8 Steps
Aa
Roobert
5 Weights
↓ Components built on tokens → consumed by every sub-brand ↓
JOBR Market
JOBR Market
Commerce · Live
JOBR Trade
JOBR Trade
C2C · Live
JOBR Drive
JOBR Drive
Fleet/Delivery · Live
JOBR Wallet
JOBR Wallet
Payments · Live
JOBR Checkout
JOBR Checkout
Payments Flow · Live
+
Next Vertical
Designed in Days, Not Months
Sub-Brand Verticals

Five marks.
One family.

Every sub-brand mark is built from the same modular diamond and rounded-square motif — recolored and recomposed per vertical, instantly legible as JOBR. Click any vertical to expand the detail.

JOBR Market mark
JOBR Market
Web + iOS + Android · Commerce
The consumer-facing marketplace — discovery, browsing, cart, checkout, and order tracking. The primary window into the JOBR merchant ecosystem.
● Live 2022–Present
Key Screens
Discovery feed & personalized home
Product detail & merchant pages
Cart, checkout & address management
Order status & delivery tracking
Design Focus
Mobile-first, native-feeling interactions
iOS + Android platform parity
Conversion-optimised checkout
Delight in empty states & onboarding
Mark Language
4-diamond grid, Iceberg + Deep Ocean split
Reads as "marketplace grid" at a glance
68–77% adoption tied to onboarding quality
JOBR Trade mark
JOBR Trade
Web + App · Peer-to-Peer
A consumer-to-consumer trading experience layered on top of Market — listing creation, offer & counter-offer negotiation, secure payment, and mutual review.
● Live 2023–Present
Key Screens
Seller listing builder (multi-step)
Buyer browse & search with filters
Offer / counter-offer negotiation
Secure payment & escrow status
Design Focus
Trust signals throughout the flow
Reducing friction in listing creation
Dual-sided experience parity
Mark Language
Diamond grid inverted: Deep Ocean dominant
One Iceberg accent — signals "exchange"
~80% component reuse from Market
JOBR Drive mark
JOBR Drive
Android · Fleet & Delivery
Fleet-side delivery management — route optimisation, order queue, delivery confirmation, earnings dashboard, and real-time communication between drivers, merchants, and operations.
● Live 2022–Present
Key Screens
Live order queue & acceptance
Route map & navigation handoff
Delivery confirmation & proof
Earnings & shift dashboard
Design Focus
One-hand use while mobile
Glanceable real-time status
Minimal cognitive load under pressure
Mark Language
Forward-motion triangle + bracket form
Reads as direction / dispatch at a glance
Low-data environments considered
JOBR Wallet mark
JOBR Wallet
Web + App · Payments
Stored balance, transaction history, payouts, and cross-vertical payment methods shared by Market, Trade, and Checkout — the financial backbone of the ecosystem.
● Live 2023–Present
Key Screens
Balance overview & quick actions
Transaction history & filtering
Payout / withdrawal flow
Linked payment methods
Design Focus
Financial clarity — never ambiguous balances
Security-forward interaction patterns
Cross-vertical embed (used inside Market/Trade)
Mark Language
Rounded card form + pill accent
Echoes a physical card / wallet shape
Iceberg accent signals "available balance"
JOBR Checkout mark
JOBR Checkout
Embedded · Payments Flow
The shared checkout component embedded across every vertical — cart review, payment method selection, promo codes, and order confirmation, built once and reused everywhere money changes hands.
● Live 2022–Present
Key Screens
Cart review & order summary
Payment method selector
Promo / discount code entry
Confirmation & receipt
Design Focus
Friction-minimal, conversion-first flow
One component, embedded across 5 verticals
Consistent payment trust signals
Mark Language
Overlapping rotated squares = "transaction"
Most reused component in the entire system
Next Vertical
Designed on the Existing Foundation
The system is built to keep expanding. Every new vertical starts with the same 8-step color ramps, the same Roobert type scale, and the same diamond-motif mark language — turning months of foundational work into days.
▲ Ready to Extend Ongoing
What's Already Built
3 full color families × 8 steps each
Extra (Twilight/Bright), Bases, and Status ramps
13-size Roobert type scale, 5 weights
What a New Vertical Needs
A new mark composition (recolor + recompose)
~20% net-new component work
Vertical-specific flows only
Outcome
40% faster delivery vs. pre-system baseline
Brand-consistent from screen one
The Control Layer

One Admin Panel.
Every Vertical.

● Live · Core Product

The dashboard that
runs the entire ecosystem.

Every JOBR vertical — Market, Trade, Drive, Wallet, Checkout — reports into a single Admin Panel: one place for merchants and operators to manage products, services, orders, bookings, inventory, payroll, marketing, and analytics across the whole business, not just one app.

📊
Unified Key Metrics
Gross sales, net sales, average net sales, and transactions — one glance, every vertical rolled in.
🧭
Full Operational Sidebar
Products, Services, Orders, Bookings, Inventory, Wallet, Taxes, Payroll & Staff, Marketing — every function of the business in one nav.
📈
Cross-Vertical Analytics
Customer growth, payment-type breakdowns, and order status — segmented by channel, rolled up across the ecosystem.
admin.jobr.com/home
JOBR Admin Panel dashboard — Key Metrics, Net Sales chart, Total Customers, Payment Types, and Total Orders
Admin Dashboard

The business
command centre.

The most complex surface in the ecosystem. SMB owners manage their entire operation here — from a 50,000+ product catalogue to multi-channel orders, staff payroll, and real-time analytics. The challenge was depth without overwhelming non-technical users.

Admin Dashboard — Main View
Dashboard Overview
Real-time analytics, order pipeline, revenue, and key metrics at a glance
Web · B2B
Product Catalogue
Product Catalogue
Managing 50,000+ SKUs with AI-powered categorisation and variant management
Inventory
Order Management
Order Management
Multi-channel orders from all surfaces unified and actionable in one view
Orders
Point of Sale

One app.
Three surfaces.

The POS had to work on iPad behind a counter, on mobile for market stalls, and on web for back-office processing — each with different user roles. The core challenge: one coherent experience across three fundamentally different form factors.

iPad POS — Checkout
iPad Checkout
Counter POS — fast product selection, cart management, and payment
iPad
Mobile POS
Mobile POS
Adapted for market stalls and pop-ups — same features, thumb-first navigation
iOS · Android
Market App & Driver App

Consumer storefront meets
last-mile delivery.

Market App — Browse
Market — Browse & Discover
Consumer storefront for local SMBs — live inventory, pickup & delivery options
B2C · iOS · Android
Driver App — Active Delivery
Driver App — Active Delivery
Route, order details, and proof of delivery — designed for drivers in motion
iOS · Android
Wallet & Trade

Payments and wholesale,
fully integrated.

JOBR Wallet — Dashboard
JOBR Wallet
Balance, transactions, and payouts — keeping money visible without a separate tool
Web · Mobile
JOBR Trade — B2B Orders
JOBR Trade
B2B wholesale — bulk ordering, custom pricing, and supplier relationship tools
Web · B2B
Design System

The actual
foundation file.

JOBR mark JOBR Design System · Foundations → Color, Type, Components
Foundations → Color
One Color System.
Five Sub-Brands.
100%
of color tokens ship with a documented WCAG rating

Every ramp and weight was picked to keep five sub-brands feeling like one company — accessible, consistent, and built to scale across web, iOS, and Android.

AAA#FFD74B
AAA#263682
Primary
2.0#58C2E8
Secondary
AAA#E4EBF1
Foundations → Typography
Roobert,
One Family
13×5
sizes × weights, zero secondary typeface

A single typeface — Roobert — carries the entire product across 13 sizes (10–72px) and 5 weights, Light through Bold. Headings and body text share the same family, differentiated by weight and scale rather than a second typeface, keeping every screen visually unified.

Specimen Character Set
Aa Bb Cc
Roobert · 5 weights · 13 sizes (10–72px)
ABCDEFGHIJKLMNOPQRSTUVWXYZ
abcdefghijklmnopqrstuvwxyz
0123456789 !@#$%^&*()
Weights Light → Bold
Aa Light300
Aa Regular400
Aa Semibold600
Aa Bold700
Foundations → Components
A Complete
Component Library
40%
faster feature delivery vs. pre-system baseline

Every component below is built directly on the token layer — no one-off colors, no one-off radii. Every primitive, from buttons to inputs to cards, is fully rounded — a deliberate, consistent pill-and-circle language across the entire system. From primitives through composites, the library covers what five live sub-brands actually ship with. These are real, rendered with the system's tokens, not icons standing in for them.

Foundations → Buttons
7 Variants · 4 States · 4 Sizes · Fully Rounded
Primary
Secondary
Tertiary
Link
Underlined
Alternate A
Alternate B
Default Hover Disabled
Primitives Forms Feedback Data Display Navigation
Inputs
Checked option
Unchecked option
Controls
Enabled
Disabled
68% complete
Badges & Status
● Active ● Pending
● Failed ● In Review
JOBR Verified
Chips & Tags
Electronics × Same-day ×
Verified seller ×
Tabs
Active
Pending
Closed
List Cards
Order #JB-30214
Iceberg Sneaker Co.
Marcus T.
Driver · 4.9 rating
Avatar Group
+12 team members
Alerts
New payout method added to your Wallet.
Data Table
OrderVerticalStatusAmount
#JB-3021MarketLive$84.00
#JB-3022TradePending$212.50
#JB-3023DriveReview$19.00
40+ components documented in Storybook and Zeroheight, each mapped 1:1 to its Figma source — covering every screen across Market, Trade, Drive, Wallet, and Checkout.
100%
Tokens Rated
Accessibility isn't an audit — it's a token property. Every step in every color ramp ships with its WCAG rating already calculated, so the cost of a color choice is visible before it ships, not after.
WCAG 2.1 AA Contrast-rated tokens
Process

How I worked.

01 — Discovery

Research & Strategy

User interviews with SMB owners, competitive analysis, and Jobs-to-be-Done mapping. Built a deep understanding of how small businesses actually operate before designing anything.

02 — Architecture

System Before Screens

Information architecture and user flows for all six products. Mapped how users would move between products. Built the design token and component foundation before any UI work.

03 — Design

Wireframes to High-Fi

Iterative design process from low-fidelity wireframes through usability testing to pixel-perfect high-fidelity prototypes. Every edge case, empty state, and error message designed intentionally.

04 — Delivery

Handoff & QA

Detailed developer handoff specs in Figma, design QA sessions with engineering, and WCAG 2.1 AA accessibility review on every feature before ship.

Design Process

How each vertical
goes from zero to live.

🔍
Step 01
Discovery & Context

Stakeholder interviews, competitive audit, user archetype definition, and business model mapping before any wireframe is drawn.

🗺️
Step 02
IA & Flow

Information architecture, user journey maps, task flows, and screen inventory — documented in FigJam before moving into Figma frames.

🧱
Step 03
System Extension

Identify which existing tokens and components to reuse, which need extension, and which require net-new creation.

🧪
Step 04
Test & Iterate

Unmoderated usability testing via Maze, Hotjar heatmaps post-launch, and Amplitude funnel analysis to track drop-offs.

🚀
Step 05
Handoff & QA

Annotated Figma specs, Storybook component mapping, Zeroheight documentation, and design QA sign-off before release.

Where research
time actually went.
Step 01 — Discovery — splits across three activities every time a new vertical is scoped.
Step 01 · Discovery & Context
45
%
Merchant & Stakeholder Interviews
0% 25% 50% 75% 100%
Understanding workflows across Market, Trade, Drive, and Wallet — the pain points a color ramp alone couldn't fix.
35
%
Competitive & Platform Audit
0% 25% 50% 75% 100%
Studying multi-vertical commerce platforms and cross-checking 8-step ramps against WCAG before locking any token.
20
%
Pattern Library & Heuristic Review
0% 25% 50% 75% 100%
Evaluating component libraries and accessibility heuristics to decide what the foundation file needed to own outright.
DesignOps

Design that engineers
can actually build.

📐
Annotated Figma Specs

Every shipped screen has complete redline annotations: spacing values in tokens (not px), component names matching Storybook IDs, and state coverage for every interactive element.

Token references Component IDs State coverage
📚
Zeroheight Documentation

A living design system site covering every component and color ramp with usage guidelines, contrast ratings, and do/don't examples. Engineers never have to guess intent.

Usage guidelines Contrast ratings Changelog
⚙️
Storybook Integration

Design components are mapped 1:1 to Storybook stories. Engineers verify visual implementation against the source-of-truth component before it reaches production.

1:1 mapping All variants Viewport testing
🔬
Design QA Sign-off

Formal QA at three milestones: component build, integration, and pre-release. Each pass checks spacing fidelity, color token usage, and responsive breakpoints.

3-stage QA Token fidelity Responsive checks
📊
Analytics & Feedback Loops

Amplitude funnels, Hotjar heatmaps, and Maze usability scores are reviewed at every sprint retro, directly informing which components need iteration.

Amplitude Hotjar Maze
👥
Cross-Functional Rituals

Weekly design critique, bi-weekly design/engineering sync on implementation parity, and monthly system health reviews to deprecate stale components.

Weekly critique Eng sync System health
Measured Impact

Numbers that
tell the story.

0%
Platform Adoption
JOBR Market — industry average is 40%. Nearly double, driven by onboarding quality and consistent token-level polish.
0%
Faster Feature Delivery
Measured against pre-system baseline. Components designed once compound across every sub-brand without rework.
0
Sub-Brands Shipped
Market, Trade, Drive, Wallet, and Checkout — all powered by one token-based design system and mark language.
0
Platforms Covered
Web, iPad, iOS, Android — all sharing the same color ramps, type scale, and component names.
0
Sole Designer Tenure
Three years as the only designer before growing the team — every foundational decision traced back to one person.
0%
Color Tokens with WCAG Ratings
Every step across all seven color families ships with a documented AA/AAA contrast rating.
0%
Component Reuse Rate
Average across new verticals. Each new sub-brand requires only ~20% net-new component work.
0
Team Grown to 3
Scaled the design function from a solo contributor to a three-person team, with the system as onboarding material.
Learnings

What three years
building a brand family teaches.

01
The System IS the Strategy

I initially framed the design system as infrastructure — necessary but separate from product work. That framing was wrong. The 8-step color ramps and the Roobert type scale weren't just visual cleanup; they were the single largest product decision JOBR made. They enabled five sub-brands to exist as one company.

02
Accessibility at the Token Level Pays Forward

Annotating contrast ratings directly on every color step — instead of running audits after launch — meant no vertical ever shipped an accessibility regression. The 5 minutes spent labeling "AA 5.8" on a swatch saved hours of post-launch fixes, every single time.

03
A Modular Mark Language Scales Identity

Designing one geometric motif — diamonds and rounded squares recomposed per vertical — meant every new sub-brand could get a distinct, ownable mark in days, not a multi-week brand exercise. Family resemblance was built into the system, not bolted on after.

04
One Typeface Forces Discipline

Committing to Roobert alone — no secondary display face — forced every hierarchy decision to be made with weight and scale instead of typeface-switching as a crutch. The constraint produced a calmer, more confident product across all five verticals.

Up Next
Tiko · Public Transport SaaS →
View Case Study ← All Work