Skip to main content
UI Coach Logo
Back to challenges
Hard

Freelance Income Cashflow Forecast

Design a cashflow forecast that turns irregular invoices, expected payment dates, recurring costs, and tax set-asides into transparent scenarios.

Responsive web, Mobile

The brief

Understand the problem

Background

Freelancers often know how much they invoiced but not when clients will actually pay. Forecasts become misleading when tentative work, overdue invoices, taxes, and personal withdrawals are treated as equally certain.

User context

Camila runs a small photography practice. Two clients usually pay late, equipment insurance renews next month, and she wants to test whether she can replace a camera without using tax reserves.

Product problem

Camila needs a forecast that communicates timing and confidence rather than presenting one optimistic balance as fact.

Objective

Create forecast setup, timeline, scenario comparison, and invoice-detail states that support a near-term cash decision.

What to design

Define the experience

Required experience

  • Connect invoices, recurring costs, and current balances
  • Set expected dates and confidence for uncertain income
  • Compare a baseline with a delayed-payment scenario
  • Inspect which events create a projected shortfall

Screens and states

  • Forecast setup
  • Cashflow timeline
  • Scenario comparison
  • Invoice and assumption detail

Core user flow

Follow the critical path

  1. 01

    Camila imports open invoices and confirms recurring costs

  2. 02

    She marks one client as likely to pay fourteen days late

  3. 03

    The delayed scenario shows a shortfall before insurance renewal

  4. 04

    She postpones the camera purchase and exports the assumptions used

Product rules

Requirements and constraints

Requirements

  • Separate received, invoiced, expected, and tentative income
  • Show every forecast assumption with an editable source
  • Include tax reserves without presenting tax advice
  • Use ranges or scenarios when payment timing is uncertain
  • Pair charts with a chronological table

Constraints

  • The product cannot guarantee client payment or tax liability
  • Connected bank balances may be delayed
  • Multi-currency invoices need an explicit exchange-rate assumption

Reality check

States worth considering

A client partially pays an invoice
One invoice becomes overdue
A recurring cost changes mid-period
A personal withdrawal is not categorized
The user has no historical payment behavior

Ready-to-use content

Mock data

Use this content to test hierarchy and realistic data states. You can expand it when the concept needs more depth.

Forecast events

  • Current available cash: $9,600
  • Client North: $4,800 expected 9 September
  • Client Field: $2,100 expected 22 September with low confidence
  • Insurance: $3,200 due 18 September
  • Tax reserve: $4,000 protected

Finish line

What to deliver

  • Four responsive screens comparing baseline and delayed-payment scenarios
  • An assumptions panel with confidence and data-freshness states

If you want more

Optional extensions

Add a client payment-pattern view
Create a safe-to-invoice reminder rather than an automatic collection message

Optional direction

Visual resources

Use these as a starting constraint if you want one. They are not part of the required solution.

Color palette
#79674F
#EDE6D2
#090C0F
#B7B7B7
#A7A7A7
Font pairing
Mr De HavilandNeuton

Mr De Haviland & Neuton

Clear interface writing gives people the confidence to understand what changed and decide what to do next.

Icons
Illustrations

Theory to review

UX principles for this brief

Use these as decision lenses, then validate the design with the people and context in the brief.