The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
If you invoice at the end of a project, you have already given away your leverage.
By delivery the hours are spent and the client has seen the work. Nothing on your side is still owed, so nothing on your side still creates urgency. Eleven week payment cycles are almost never a client problem — they are a structure problem, decided months earlier.
Three things that changed our cash flow, none of them adversarial:
→ Split into three. Deposit at signature, milestone at first presentation, balance at delivery. Nothing starts before the deposit clears.
→ Make every trigger observable. "On client approval" is a permission slip the client can decline to sign for months. "On presentation of three directions" either happened or it did not.
→ Never tie the final payment to a launch date. Campaigns slip. Use "thirty days after final delivery, launch or no launch".
Write all of it during scoping, in the same document, while the relationship is warm and nobody is negotiating it line by line.
Full breakdown, including how we price the licence as a separate line: https://supadark.com/notes/invoicing-a-sonic-branding-project
supadark.com
How to Invoice a Sonic Branding Project Without Chasing the Payment
Deposit, milestone, balance. How to structure payment on a sonic branding engagement so the invoice is a schedule you designed at scoping, not a request you send at the end.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Accounts payable is one of those jobs where the work is dull and the mistakes are expensive. Someone types the invoice in, checks it against the purchase order, chases the right person for approval, and posts it before the terms run out. Do that a thousand times a month and something slips: a duplicate payment, a missed early payment discount, a unit price that quietly went up in March.
So I built Ledgerpilot, an accounts payable system that handles the routine invoices end to end and asks for a person only when it should.
An invoice arrives by email, supplier portal or EDI. The system reads it, checks every line against the purchase order and the delivery note, looks for duplicates across the last six months, then applies the company rules before it goes into the accounting system.
Three things I cared about while building it.
The person gets evidence, not a verdict. When an invoice needs review, the screen shows the scanned document with every field the AI read marked on it, how sure it was about each one, the line by line comparison against the order, and a note on what it recommends and why.
Policy comes before confidence. Rules like "over $10,000 goes to the controller" or "new supplier, first three invoices" run first. A confident read never lets an invoice skip the person who is supposed to sign it.
You can change the rules and see the effect before you save. Move a threshold and the screen tells you how many of the last 30 days of invoices would have gone through on their own.
The front end is React and TypeScript. The backend is designed around .NET and Node.js services, RabbitMQ, PostgreSQL and AWS, with queue depth, worker health and cost per document visible in the app.
I built this as a portfolio project with realistic sample data, not a client system, so the thinking is mine to show: the flow, the screens and the checks around the AI.
If your finance team is buried in invoices and you want automation your auditor will be happy with too, I am glad to talk it through.
It runs 23 characters over 2,000. Cut the words "and the mistakes are expensive" from the first line and it lands at 1,993. I left it in because it earns its place in the hook, and most feeds allow more than 2,000.
Most editing problems don’t actually start in the timeline.
They start before the project even gets opened.
A clear script, organised footage, solid references, and a bit of context around what actually matters can save a ridiculous amount of time on both sides.
No 14-page brief needed.
Just please don’t make me search through final_final_REALfinal_v7.mp4 to find the actual final. 😭
#VideoEditing #VideoEditor #FreelanceEditor #ContentCreator #YouTubeEditor #PostProduction #VideoProduction #ContentCreation #Freelancing #CreativeWorkflow #EditorLife #AdobePremierePro #ContentStrategy
Good reminder that editing starts before the timeline.
In Uzbekistan most brand deals still happen in DMs. No brief, no terms, no idea when the money arrives.
For the past months I've been designing BETWEEN — a two-sided marketplace that connects businesses with local creators.
The hardest decision wasn't a screen. It was what to leave out.
BETWEEN doesn't hold the payment. Businesses and creators agree the price in chat. A guarantee the app cannot enforce is theatre — and a formal approval cycle would push creators straight back into DMs. So the product promises one thing and delivers it: a good match.
What shipped:
• 957 screens, light and dark, mobile and desktop
• 254 components, 230 variables, 31 text styles
• Business and creator apps on one system
Full case study in the comments. 👇
#uiux #productdesign #designsystem #creatoreconomy
