Scope creep shows up on the invoice
Scope creep shows up on the invoice if you don’t name it.
Extra work → short written note → its own line. Don’t bury it in the original lump.
InvoiceSnap: Free = 1 watermarked preview (no logo). Pro $4.99 unlimited branded. Business $9.99 when email + client log + Projects & Time matter.
Honest Free. Focused invoicing. Not a suite.
— Cameron M Deans
https://app.invoicesnap.ca
Writing the out-of-scope list into the offer before work starts has saved me more than any invoice rewrite later. Buyers accept boundaries more easily at purchase than after delivery. The separate invoice line then just confirms something the client already agreed could happen. Do you put change pricing in the original offer, or only negotiate when creep appears?
I put a short change-order rate in the original offer whenever I can — even one line like “out-of-scope work billed at $X after written approval.” Buyers accept the boundary easier at purchase. When creep shows up later, the separate invoice line is just confirming what was already agreed, not opening a brand-new pricing fight.
If you’re testing invoicing this week: free account at https://app.invoicesnap.ca — try one real client invoice. Ping me if something blocks you.
— Cameron M Deans
The “not a suite” positioning is refreshingly clear. I’d watch whether one watermarked preview lets a freelancer reach the real aha moment, though the value may be recovering an extra charge that would otherwise disappear into scope creep. A free first sent invoice or one client with unlimited previews might demonstrate that outcome more convincingly while still keeping Pro simple. Have you tested preview limited versus client limited free plans?
Good challenge. I’ve stuck with one watermarked preview (no logo) so Free proves PDF quality without becoming a permanent substitute. A “one client, unlimited previews” path is a fair hypothesis if the aha needs more than one send — I’m watching second-invoice / return intent before widening Free.
If you want to pressure-test the current boundary: free account at https://app.invoicesnap.ca — send one real client invoice this week and tell me where it felt too tight. I’ll help.
— Cameron M Deans
The separate line is a useful forcing function. I’ve found it helps to tie each extra to a timestamped approval and leave it untouched until the client says yes; otherwise the invoice becomes the first pricing conversation. For repeat clients, a short weekly scope check can bundle small requests while keeping the approval trail clear.
Agree — the invoice line works best when it points back to a yes that already happened. Timestamped approval (even a short email/thread) keeps the extra line from becoming the first pricing conversation. For repeat clients, a weekly scope check is a good way to bundle small asks without losing the trail.
— Cameron M Deans
One detail I would want in that workflow is a link from the extra invoice line back to the exact change the client approved. If the note is edited later, the invoice could otherwise point to different wording. I’m working on amendment tracking in an agreement prototype, so this is a design question I’m wrestling with too. Does your written note stay fixed once approved, or can people keep editing it?
I treat the approved note as fixed once the client says yes — if wording changes later, that’s a new amendment, not an edit of the original. Ideal state is a stable reference (message / change order id) the invoice line can point back to so the PDF and the agreement don’t drift.
— Cameron M Deans
This is great work — what's the biggest thing you'd do differently if you started over?
Naming extra work as its own line is so underrated. The earlier version of this that helped me: a clear scope written from the client's own intake answers at kickoff. When the change request comes, you can point to what they originally asked for, and the conversation stays calm.
Yes — writing scope from the client’s own intake answers is the calm version of this. When the change request lands, you’re pointing at what they asked for originally, not inventing a new boundary after the work. The separate invoice line then just confirms the delta.
— Cameron M Deans
This tracks with something I've been running into too — by the time scope creep shows up on the invoice, it's already too late to have the pricing conversation calmly. What's worked better for me is flagging the extra cost the moment the request comes in, before any work starts on it, so there's a number attached to it right away instead of a surprise line item weeks later. Curious if you've found a way to get clients to actually engage with that flag in the moment, vs. just discovering it at invoice time?
That’s the better sequence: number attached at request time, before any work starts. I’ve found a short written flag (“this is out of scope — $X if you want it”) gets more engagement than a surprise line weeks later. The invoice line is the receipt for that earlier yes, not the first negotiation.
If you’re testing the send side this week: free account at https://app.invoicesnap.ca — one real client invoice is the signal. Ping me if anything blocks you.
— Cameron M Deans
Good question. I think of those as two different signals: scope changes are often the trigger to make the invoice clearer, while branded invoices and email + client log + Projects & Time are the reasons to go beyond the Free 1-invoice preview. I’m watching for the point where the workflow saves enough follow-up that the upgrade is obvious, rather than adding features just to add them.
If you’re testing invoicing this week, create a free account at https://app.invoicesnap.ca and send one real client invoice. Ping me if anything blocks you and I’ll help.
Have early users shown what actually drives the upgrade decision—handling scope changes, branded invoices, or the client/project features?