Killing the “I’ll invoice Friday” habit
Maker-adjacent habit I’m pushing on myself: kill “I’ll invoice Friday.”
Friday-you is tired. Same-day-you still remembers the scope.
I built InvoiceSnap around that gap (invoicesnap.ca) —
Free = 1 watermarked preview on purpose · Pro $4.99 unlimited branded · Business $9.99 if you need email + Projects & Time.
Not trying to be a $30 suite. Just fewer bills stuck in the drafts folder.
— Cameron M Deans
Interesting. How are you measuring whether it is working?
Still early — not claiming a proven lift yet. I'm watching same-day send rate, return-to-create a second invoice, and whether the drafts pile actually shrinks. If those move together, the habit is working; if not, I'll adjust.
— Cameron M Deans
Interesting. How are you measuring whether it is working?
Still early — not claiming a proven lift yet. I'm watching same-day send rate, return-to-create a second invoice, and whether the drafts pile actually shrinks. If those move together, the habit is working; if not, I'll adjust.
— Cameron M Deans
Thanks for sharing the numbers, that makes it much easier to follow.
Glad the numbers helped — thanks for reading.
— Cameron M Deans
How did you decide this was worth building in the first place?
It came from the repeated Friday scramble: the scope was freshest on delivery day, but billing kept slipping. I wanted a tiny same-day loop that makes sending the invoice the default, not a separate admin project.
Interesting approach. What was the hardest part to get right?
Hardest was keeping the first loop tiny while still making the PDF trustworthy enough to send. The temptation was to add a full suite; the better answer was to nail same-day invoice creation first, then let real workflows tell us what belongs next.
Interesting take. Would you still recommend this approach to someone starting today?
Yes, but I’d start narrower: choose one recurring billing workflow, get a few real people through it end to end, and measure whether invoices actually go out on time. Add breadth only after that loop is reliable; a small useful habit beats a polished dashboard nobody opens.
Good write-up. What would you do differently if you started again?
I’d narrow the first wedge sooner: pick one repeatable billing workflow, watch a handful of real invoices through it, and ship the smallest loop before adding breadth. I also wouldn’t wait for “polish” to test whether people actually send.
This is useful. How are you finding your first users so far?
Mostly organic so far—maker/community conversations and warm inbound from freelancers and small teams. I’m trying to learn from real workflows rather than chase raw signup volume.
P.S. I’m opening 5 Valued Tester seats this week — Business for a year for freelancers/studios who’ll share honest feedback. Free account first: https://app.invoicesnap.ca — comment or DM the email you used if you want in.