# 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.

- Sector: Financial software
- Year: 2026
- Project: Sendfirst
- Client: Self-initiated
- Services: Product design, Development

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 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.

## Who it is for

- The new freelancer: Has one client and one invoice to send today. Needs it sent before learning the app.
- The freelancer who is switching: Comes from another tool. Needs proof in the first minute that this one is quicker.

## What we did

### Product design

Used: User interface, User experience, Mobile apps, Design systems.

1. Find the first question: The client and the amount: the two facts every user knows.
2. Design the flow: Send first, then a short list of what is missing.
3. Draw the screens: Two phone screens made from one set of parts.
4. Set the components: Fields, buttons, labels and status rows.

### Development

Used: Front-end, Astro.

1. Build the screens in code: Both phone screens are built in HTML and CSS inside Astro components. They are not exported images.
2. Make them scale: Every size is relative to its container, so one drawing works as a card, a cover and a figure.
3. Check on a phone: The same drawing is checked at 390 pixels wide.

## Design decisions

1. 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 of: Starting with the user’s own company details.
2. 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 of: Blocking the send button until the profile is complete.
3. 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 of: A progress bar in percent. It says how far, not what.
4. “Finish later” is a real button. Leaving is allowed and visible, so the checklist does not feel like a trap. Instead of: Hiding the exit behind a small link.

## How it works

1. One question: The first screen asks who the invoice is for, and how much.
2. Send: The invoice goes out before any setup.
3. 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.

## What it is built to change

- Invoices sent on day one: The share of new accounts that send an invoice on the day they sign up.
- Where people stop: The flow is two screens, so the step at which a session ends can be counted screen by screen.
