FIGR / UI TEMPLATE

Freelancer Earnings

Track freelance earnings across contracts, hourly and milestone income, marketplace fees, pending funds, payouts, forecasts, and tax documents.

This analytics reference covers talent marketplaces. Its sample screen includes Product redesign and React migration and the Withdraw funds action. Adapt its workflow to your product and design system.

Freelancer Earnings

BUILD ON THIS

Make it yours in Figr.

Explore this screen, then bring in your own product and design system to shape the next version.

Use this template ↗

At a glance

Screen

Analytics

Primary action

Withdraw funds

Pattern

Freelancer Earnings analytics

State

Default, loading, empty, error, permission, success

Design system

Adaptable product UI theme

What this screen helps with

The freelancer earnings screen supports “Withdraw funds” while keeping earnings and contracts in view. It should show the current state even when data is missing or access is restricted.

What to look for

  • Primary action: Withdraw funds
  • Main area: Earnings brings the user to the relevant workflow
  • Related area: Contracts keeps nearby context accessible
  • Earnings MTD: 18.4k in the sample screen
  • Pending: 4.8k in the sample screen
  • Example 1: Product redesign
  • Example 2: React migration
  • Input: Reporting period

States to consider

  • Default: Show the main workflow and its available next step
  • Loading: Keep chart labels and time range visible while metrics refresh
  • Empty: Explain the chosen date range or filter has no data
  • Error: Identify missing or stale metric sources without implying zero activity
  • Access: Show which actions require a role or permission
  • Success: Confirm the result after Withdraw funds and say what happens next

Where it fits

Earnings → Contracts → Withdraw funds → Review result

Patterns in this screen

Freelancer Earnings analytics, Earnings, Contracts, permission handling, error recovery

UX choices to review

Keep metric definitions, chart periods, and filter context visible together

In this example, Product redesign is one of the records worth checking. Keep the sample data clearly separate from a live system.

Show why numbers changed; distinguish delayed data from genuine zero values

Make a useful drill-down available before teams export or share findings

Try a similar screen in Figr

Design a freelancer earnings screen for an existing talent marketplaces product. Use our actual design system, components, and content rules. Cover Earnings and Contracts, include believable records such as Product redesign, and make "Withdraw funds" easy to find. Map empty, loading, error, permission, and success states. Keep the result editable in Figma.

Open Figr

KEEP EXPLORING

More ways to approach your next screen.

Browse other product UI examples, compare patterns, and pick the direction that suits your product.

Explore all 500 templates ↗