Freelancers run a whole business alone. Their tools should act like one.
A web app for independent designers, developers and writers in India that brings tasks, client conversations, projects, invoices and time into one calm dashboard.
A client approves in chat, but the invoice goes out a week later, and unpaid invoices are chased by hand.
Framed the problem and my assumptions, then designed the product behind a marketing page: 30 screens and one system for both.
Design the money loop first. An approval in the project thread becomes an invoice, with GST or LUT wording picked from the client's country.
01The problem
A typical freelance week is spread across a notes app for tasks, WhatsApp for approvals, Google Drive for files, a Word template for invoices and memory for hours worked. Nothing connects, so things slip.
It also handles what Indian freelancers deal with every month: GST, export invoices under LUT and clients who pay in pounds or dollars.
02Who it's for
This was a self-initiated concept, so I didn't run interviews. Meera is a proto-persona: my assumptions about a typical Indian freelancer, written down so every decision traces back to someone specific. Testing her with real freelancers is the first thing I'd do next.
6 active clients, 2 overseas. Bills per project and per hour. Uses Notes, WhatsApp, Drive and Word today.
03Decisions
Tasks, messages, files and invoices hang off the same client and project, so context never has to be copied between apps.
Unpaid, overdue and unbilled amounts appear wherever decisions happen: the dashboard, the client, the project and the timesheet.
A white canvas, one accent per meaning and quiet states. Colour only shows up when something needs attention.
GST, LUT export wording, rupees and foreign currencies are handled for her.
ChoseAn approval in the project thread offers "Create invoice" with the milestone and amount filled in.
ReplacedA Word template, filled in a week later.
WhyThe approval is the moment the money is owed. Meera's goal is to invoice the moment work is approved.
ChoseThe editor picks GST or LUT from the client's country and adds the declaration.
ReplacedWording she has to look up.
WhyIndian clients in her state get CGST and SGST at 9% each, clients in other states get 18% IGST and overseas clients get no GST, under LUT.
ChoseEvery invoice goes out with its reminder schedule: a friendly nudge before it's due, on the day and after.
ReplacedFollow-ups by hand.
WhyChasing late payments feels personal. A schedule set when you send makes it the tool's job.
ChoseThe timesheet calls out unbilled hours and turns them into an invoice in one step.
ReplacedHours from memory.
WhyTracked time is only useful if it becomes money. She forgets to bill hours she worked.
ChoseOne accent per meaning: blue is time, green is clients, amber is tasks, purple is money.
ReplacedColour as decoration.
WhyRed and amber tints stay free for priority and overdue states, so they read as alerts.
04The money loop
The flow I cared about most. Approval, invoice and payment used to live in three different places. Here each step hands off to the next, and the overdue path runs by itself.
The approval sits where the work was discussed, and the invoice for £1,200 to Hatch Money is one tap away.
Milestone and amount come from the approval. The tax wording comes from the client's country: an overseas client gets the LUT declaration.
A friendly nudge before it's due, on the day and after, so chasing is the tool's job.
Tom opens the invoice from a link and pays it there.
The invoice is marked paid. Had it gone overdue, the reminder timeline would have run by itself.
05The product
Clients and projects are the spine. Tasks, messages, files, time and invoices attach to them.
Sign up, say what kind of work you do, set up how you get paid, then add a first client.
The project started as a single marketing page. To make the promises on that page real, I designed the product behind it, then turned both into one system. Its stats are marketing copy.
06The system
I kept the calm black and white of the original landing page and gave each accent one job. The type scale is SF Pro, from a 48px display down to a 12px caption, and components are built with auto layout.
07How I used AI
08What I would do next
Five or six interviews with Indian freelancers who bill overseas clients would confirm or break the proto-persona before anything else is built.
Automatic reminders help cash flow but can strain a relationship. I'd test wording and timing with people who have chased payments themselves.
GST, LUT and export wording are modelled on how they usually work. A chartered accountant should review every rule before it ships.
Timers and approvals happen away from the desk. A small mobile app for those two jobs is the natural next surface.
Tinted badges and small captions need contrast checks, and every flow needs a keyboard-only run-through.
Days from approval to payment is the one number that would show whether ClarityFlow actually works.
The complete ClarityFlow case study is on Behance.