What "paid" should mean
When should a one-person AI agency count a payment as paid? Why a client saying it's paid isn't confirmed money, and the simple rule we recommend.
"Paid" sounds like the simplest word in running an agency. When we sat down to decide how Volant should treat payments, it turned out to be one of the slipperiest.
Think about how many different things a web designer might hear as "paid" in a single week. A client texts "just sent it!" A client forwards a screenshot of a bank transfer. An invoice gets marked paid by hand because the client said so on a call. A card payment shows up as processing. A deposit clears on Monday and is disputed two months later. Each of those can look like "paid". Only some of them are.
The rule we recommend is short: a payment counts as paid when the place the money arrives confirms it. Everything else is a message.
Why the difference matters
Most of the time, "it's sent" and "it's arrived" end in the same place, a day or two apart. The trouble is the time in between, and what you do with it.
If you start a website on "it's sent", you're working on credit you didn't agree to give. If the transfer bounces, or the client sent it to an old account, or "sent" meant "tonight, probably", you've spent a weekend on a project that hasn't begun as far as the bank is concerned. If you mark a care plan month as paid because the client said so, your notes say one thing and your bank says another. Working out which months are really covered then becomes an evening of detective work.
None of this is about distrust. Nearly every client who says they've paid has paid, or will. The rule isn't for them. It's for the version of you who's reading three months of payments and trying to work out what's true.
What "confirmed" looks like
The confirmation comes from where the money lands, not from the person sending it.
Payment providers are clear about this. Stripe's documentation, for example, describes a payment moving through stages. Some payment methods, such as bank debits, sit in a "processing" state and can take up to a few days to confirm, and Stripe notes that until then the payment isn't certain. Only when a payment reaches "succeeded" does Stripe say the funds are in your account and the order can be fulfilled.
Even then, a card payment isn't beyond question. Stripe's documentation on disputes explains that card networks typically let a cardholder dispute a payment within 120 days, and in some cases longer. For a one-person AI agency with a clear agreement and a happy client, that's rare. But it's another reason to keep what was agreed and what was delivered next to the payment. If a question ever comes, the answer should already be written down. If you take payments through Stripe, the guide to Stripe invoicing for freelancers covers how invoices, fees and payouts fit together.
So we think in three states, not two:
| State | What it means | What you do |
|---|---|---|
| Offered | You've sent a quote or invoice | Wait, then follow up |
| Said to be paid | The client says they've paid, or sent a screenshot | Thank them, and wait for confirmation |
| Paid | Your bank or payment provider confirms the money | Start the work, or mark the month covered |
The middle state is the one most spreadsheets skip. It's also where most of the confusion lives.
Where this shows up in practice
Deposits. Work starts when the deposit is confirmed, not when it's promised. Say so on the quote, in plain words, so it's a rule of the business rather than a judgement about the client. The guide to a web design deposit goes further on amounts and timing.
Care plans. Each month is either paid or waiting. If a card expires, the month shows as waiting, and you have a friendly reason to get in touch before the work piles up.
Final payments. A site goes live when the final payment is confirmed, or on the date you both agreed in writing. Either is fine. What matters is that you decided before launch day.
Approvals. The same thinking applies to sign-off. A client saying "looks good" in passing isn't the same as approving a named version, which is why client approval of a website version has to point at one exact version. Money and approval are the two places where "they said so" and "it's confirmed" need to stay separate.
Why we care about this one
When we worked out what Volant should be, we kept coming back to one idea. A one-person agency runs on promises, and every promise needs a clear state: offered, agreed, done, paid. If any of those is fuzzy, you carry it in your head, and a head is a poor place to keep money. The story of why Volant exists is mostly about removing that kind of fuzziness.
"Paid" was the first word we wanted to make exact, because it's the one that decides when work begins. If you're starting a one-person AI agency, it's worth deciding your own rule now, before the first "just sent it!" arrives.
Where Volant fits
Clients pay through your own Stripe account, and Volant marks a payment as received only when Stripe confirms it. When the deposit is confirmed, the job shows as started and the website work can begin. A text saying it's paid stays a text. The page on quotes, deposits and payments in one place shows how it looks with real client work.