Kite

Freelancers do not think in budgets. They think in invoices: what is owed, by whom, and how late it is. Kite started from that observation, after forty conversations with designers, translators and photographers who were all running small businesses out of a phone they also used for everything else.

The interface is a sentence

The core screen is not a dashboard. It is a short, plain-language forecast: “You have ¥12,400. Two invoices land this week. You are fine until the 28th.” Numbers live underneath the sentence, not instead of it. The forecast is generated from the user’s real payment rhythm, and it is honest when it does not know.

Splitting money without splitting attention

Group expenses for trips and shared projects were a constant source of friction. We designed splitting as a thread of messages — a receipt, a comment, a nudge — because the money was never the hard part; the awkward conversation was. Reminders are drafted for you, soft by default, firmer only after the second week.

Trust is a material

Onboarding was where we spent the most design time and the least interface. Instead of asking for bank credentials on the first screen, we let people explore with a demo wallet, then connected accounts one permission at a time, each with a plain-language explanation of what it unlocks. Verification drop-off fell by a third.

Every motion was slow enough to be legible — a balance that counts rather than jumps, a confirmation that waits for your thumb to leave the screen.

What the numbers hid

Activation rose 42%, and support tickets about payments fell by more than half. The metric I am prouder of is quieter: the number of people who used Kite for three months and never opened the settings screen. A financial tool that stops demanding attention has earned a kind of trust that surveys cannot measure.