Three years ago I worked with a founder named Priya who wanted a full redesign of her scheduling app, Loom Hours (no relation to the video tool), inside four weeks. We signed a scope document, a proper one, eleven pages with wireframe counts and revision limits. By week two she had added a referral flow, a dark mode, and a request to ‘just look at the onboarding again.’ The document sat in a shared drive, unread. What finally stopped the drift wasn’t a conversation. It was the invoice.
Why scope documents get ignored
Scope documents are written in a language clients don’t use day to day. They talk about deliverables and milestones. Clients talk about money and dates. A twelve-page PDF describing three rounds of revisions feels abstract until someone tries to request a fourth round, and by then the document has already lost its authority.
An invoice doesn’t have that problem. It’s the one artifact in a project that everyone reads carefully, every time, without being asked.
What the invoice actually contains
Line items instead of phases
Instead of billing ‘50% on kickoff, 50% on delivery,’ I now write invoices with six to nine line items before any design work starts: homepage layout, settings redesign, onboarding flow, two rounds of revisions, one async Loom walkthrough per week. Each line has a number next to it. Seeing ‘$1,400: settings redesign’ makes a client ask a very different question than reading ‘Phase 2: Core Screens.’ They ask what’s included. That question is the whole point.
Pricing the boring parts separately
I learned to price empty states, error messages, and loading screens as their own line, usually $300 to $600 depending on complexity. For years I folded these into ‘feature design’ and watched them get deprioritized every single time. Once they appear on an invoice with a dollar figure, they stop feeling optional.
The three invoices I’ve thrown away
Not every attempt worked. One client, a logistics startup called Harrow Freight, pushed back hard on an invoice that itemized ‘stakeholder alignment calls’ at $150 each. He felt nickel-and-dimed. I rewrote it as a flat weekly rate and kept the line-item structure only for design deliverables. The lesson wasn’t to abandon the approach, it was to itemize things people can see, not things they merely sit through.
Another time I itemized ‘creative direction’ as its own $2,000 line and got the same confused reaction. Vague nouns don’t survive on an invoice any better than they survive in a scope document. If a line item can’t be pointed to on a screen, it probably shouldn’t be its own line.
An invoice is the only document in a project that both people actually read on the same day.
What this changes about the first call
Now, before a kickoff call, I send a draft invoice instead of a proposal. It has placeholder numbers next to a guessed list of screens: ‘Dashboard: $1,200,’ ‘Settings: $500,’ ‘Mobile nav: $400.’ I ask the client to cross out what’s wrong. This single exercise surfaces disagreements about scope in the first twenty minutes instead of the third week.
With a furniture retailer named Oslin & Birch, this draft invoice revealed that their ‘simple product page redesign’ actually meant rebuilding the entire filtering system. That would have been a three-week surprise under the old process. Under this one, it was a five-minute correction on a shared screen.
A short list before I price anything
- List every screen or flow by name, not by category
- Attach a number to each one, even a rough one
- Separate revisions from original design work
- Price the unglamorous screens on their own line
- Send the draft before the call, not after
None of this requires new software. I use the same invoicing tool I’ve used for six years, Bonsai, and the only change is sequence: price first, then design, instead of the reverse.
What it costs me
There’s a real cost to this approach. Drafting a detailed invoice before a signed contract takes an extra ninety minutes I used to spend sketching. Some prospective clients find the specificity off-putting and go quiet. I’ve lost at least two projects this way, both of which, in hindsight, probably would have been difficult regardless.
What I’ve gained is fewer midnight emails asking why the onboarding flow ‘still isn’t done’ when onboarding was never on the invoice to begin with. The document does the uncomfortable conversation for me, before the relationship has any tension to protect.
