Scope
A new user of "Billsend," a specimen invoicing tool for freelancers, signs up and sends a first invoice. Five states reviewed: pricing page → signup → first-run dashboard → new-invoice form → send confirmation. Walked as a first-time user with one client to bill, no tour taken, no prior account.
Where is this flow losing clarity, trust or momentum before the first invoice goes out?
Product, usability, trust and interaction. Each observation names what is visibly happening, why it matters, and the action the evidence supports. No research, no redesign: an expert review, bounded on purpose.
Four of the Seven Observations
Observation 1 · First-run dashboard — the empty canvas
Observation: after signup the dashboard shows zero-state charts ("Revenue: $0", "Outstanding: $0") and a "+ New" button in the corner. Nothing names the one thing a new user came to do.
Why it matters: the drop happens before the product has shown any value. The user has to guess that "+ New" is the invoice, and a user who leaves here never learns what they were leaving.
Recommended action: replace the zero-state charts with one task in the user's language — "Send your first invoice" — and make it the single visible move. Keep the charts for the second visit.
Observation 2 · New-invoice form — a number with no basis
Observation: next to the due-date field the form says "Usually paid within 7 days." Nothing says where the figure comes from, whose invoices it describes, or how sure the product is.
Why it matters: trust that is not calibrated breaks all at once. When the first client pays late, the user re-rates every earlier number the product showed them.
Recommended action: show the basis or show the uncertainty — "based on invoices sent through Billsend" — or drop the line until there is data of the user's own to base it on.
Observation 4 · Signup — the error that names the problem, not the way out
Observation: a business name containing an ampersand returns "Invalid characters" under the field. The message does not say which character, what is allowed, or what to do next.
Why it matters: every dead end is an exit. The message confirms to the user that the product has run out of ideas, at the second screen of the flow.
Recommended action: name the way out in the message ("Use letters, numbers and spaces — & isn't accepted yet"), or better, accept the character.
Observation 6 · Send confirmation — the money controls in a different voice
Observation: the send screen explains itself warmly until the "Payment terms" and "Late fee" controls, where the copy drops to terse labels with no line about what the client will see.
Why it matters: users conclude the quiet parts are the dangerous parts and leave them untouched — and these are the controls that decide when they get paid.
Recommended action: bring the centre's voice to the edges: one sentence per control saying what the client sees and when.
The Three Actions to Take First
- Give the dashboard one job. Replace the zero-state charts with "Send your first invoice." Smallest effort, largest effect on first-session completion. (Observation 1.)
- Fix the signup dead ends. Rewrite every validation message to name the way out, starting with the business-name field. (Observations 4 and 5.)
- Explain the money controls in the product's own voice. Payment terms and late fee get one sentence each, and the "usually paid" line goes until it has a basis. (Observations 2 and 6.)
What the Other Pages Hold
A full diagnostic runs 5–10 observations in this format, in priority order, followed by the three actions above and a short note on what was out of scope and why. It is a concise annotated report delivered by email, with screenshots or frames where they help. No meeting and no revisions — the point is a decision-ready answer the next business day.
Client reports are confidential — showing you a real one would tell you exactly how I'd treat yours. The format, depth and honesty above are real; "Billsend" is a composite assembled from patterns that recur across shipped products, the same shapes described in the five leaks I look for first. When the report about your flow lands, it looks like this — about things only your product does.