Nuxsol
Start a conversation

Worknuxsol.eu/work/sendfirst/

A first invoice in the first session.

A studio project. An invoicing app for freelancers that asks one thing first: who the invoice is for.

Sendfirst: Send first. Set up later.
Sector
Financial software
Year
2026
Project
Sendfirst
Client
Self-initiated

Sendfirst is a studio project in product design: the first minutes of an invoicing app for freelancers, built around a single idea. Send a real invoice first, and set up the rest afterwards.

In the project

  • Name and wordmark
  • Palette of four tones
  • First-run screen
  • Sent screen with checklist
  • Component set

The case

The problem

A freelancer opens an invoicing app because a client is waiting to be billed. The app answers with setup: company details, tax settings, bank verification. Each step is reasonable. Together they stand between the user and the only thing they came to do.

Setup is also where doubt begins. A tax question the user cannot answer on the spot is a reason to close the tab and write the invoice in a document instead.

What we made

The name, a wordmark, a dark violet palette, and the two screens of the first run on a phone. Both screens use one set of fields, buttons and messages.

The first run on a phone: who the invoice is for, then what is still missing.

Who it is for

  • The new freelancerHas one client and one invoice to send today. Needs it sent before learning the app.
  • The freelancer who is switchingComes from another tool. Needs proof in the first minute that this one is quicker.

What we did

By service: what was used in this project, and the steps of execution.

Product design

Complex products, made to feel simple.

UI and UX that make complex products feel simple. We balance what users need with what the business needs, so the product just works.

  • User interface
  • User experience
  • Mobile apps
  • Design systems
  1. 01

    Find the first question

    The client and the amount: the two facts every user knows.

  2. 02

    Design the flow

    Send first, then a short list of what is missing.

  3. 03

    Draw the screens

    Two phone screens made from one set of parts.

  4. 04

    Set the components

    Fields, buttons, labels and status rows.

Development

The design, built exactly.

Clean code that brings the design to life: fast, responsive and exact on every device, with a back end you can rely on.

  • Front-end
  • Astro
  1. 01

    Build the screens in code

    Both phone screens are built in HTML and CSS inside Astro components. They are not exported images.

  2. 02

    Make them scale

    Every size is relative to its container, so one drawing works as a card, a cover and a figure.

  3. 03

    Check on a phone

    The same drawing is checked at 390 pixels wide.

Design decisions

Each with the reason for it, and what we chose not to do.

  1. 01

    Ask who it is for, first.

    The first screen has two fields: the client and the amount. They are the two facts every user knows without looking anything up.

    Instead ofStarting with the user’s own company details.

  2. 02

    Send before setup.

    The invoice goes out with what the app has. The user gets the result they came for, and a reason to come back.

    Instead ofBlocking the send button until the profile is complete.

  3. 03

    Show what is missing as a short list.

    After sending, the second screen lists what remains, with the finished item ticked. Two open items look finishable.

    Instead ofA progress bar in percent. It says how far, not what.

  4. 04

    “Finish later” is a real button.

    Leaving is allowed and visible, so the checklist does not feel like a trap.

    Instead ofHiding the exit behind a small link.

The identity: mark, colours, type and voice.
The component set, in Sendfirst’s own colours and words.

The system

Four tones, each with one job. Contrast is measured, not judged by eye.

  • Ground#15131FNear-black violet: the app at rest.
  • Ink#F5F3FFCool white: all text.
  • Signal#8B7CFFViolet: the send button and the ticked item.
  • Soft#221E33A lighter violet: the area around the phone.
Contrast ratios of the palette
PairContrastPasses
Ink on ground16.7 : 1AAA
Ink on soft14.7 : 1AAA
Label on signal5.6 : 1AA
Signal on ground5.6 : 1AA
Type
Geist 600, tightly spaced, for the wordmark and the questions. Geist Mono for small labels such as “New invoice”.
Voice
One question per screen. No jargon about tax.

How it works

  1. 01

    One question

    The first screen asks who the invoice is for, and how much.

  2. 02

    Send

    The invoice goes out before any setup.

  3. 03

    Then the rest

    What is missing appears as a short checklist: tax number, bank account.

The principle

Ask for one thing first: who the invoice is for.

The first question, and the list of what is still missing.

What it is built to change

  • Invoices sent on day oneThe share of new accounts that send an invoice on the day they sign up.
  • Where people stopThe flow is two screens, so the step at which a session ends can be counted screen by screen.
Next case A parts catalogue anyone can search.

Show us the page you want machines to understand.

Send us one URL. On the first call we tell you, for free, what a person and an agent each find there, and roughly what it would take to fix.