Stop running client work on WhatsApp: what to use instead

WhatsApp is a good place to talk to clients and a poor place to run their projects. Keep it for conversation, and move the scope, files, approvals and invoices to a system that stores them where you can find them.

This is an opinion piece, and I know the objection before you raise it: your clients live on WhatsApp, and that is how business gets done where you work. True. The problem is not that you use it. The problem is that you run the whole job on it.

Scope creep gets written into the chat

A quick question becomes a "while you are at it" request three messages later. Nothing marks where the agreed scope ended and the extra work began, so the question "is this included?" gets answered by tone.

A written scope is easy to point to. A chat thread three weeks deep, mixed with jokes, voice notes and a shipping address, is not. There is a legal edge too, in places where messages can serve as evidence. A Chambers article on UAE practice says electronic correspondence counts as electronic evidence with the same effect as written evidence, and that its weight depends on reliability, integrity and traceability. A messy thread is exactly where those three are hardest to show.

The fix is boring. Put the scope in a quote or contract, and when a request falls outside it, answer with a line like "I will add that to the project and confirm the cost first." Our post on stopping scope creep has scripts for it.

Boundaries dissolve

Email has rhythms. Most work chat apps have channels you can mute. WhatsApp is the same app where your family writes to you and your group chat sends memes, and also where a client asks for one more revision at 11pm on a Saturday.

You end up either always available or inconsistent. Always available wears you down. Inconsistent looks careless. A separate place for work, with its own notifications, is the simplest way out.

Files disappear

Every owner has the story. A client sends a logo in March. In November you need it for a follow-up job. You scroll through thousands of messages, work and personal mixed together, hunting for one small image. You give up and ask the client to resend, and it takes three days.

Chat is not a file system. You cannot reliably search it by project, version or date, and a file you cannot find might as well not exist. Large deliverables are worse. Sending a finished video or a design package through chat means compression, size limits and no record of which version the client downloaded.

A thumbs-up is not an approval

A "yes looks good" reaction is a mood. Six weeks later, when the client says "I never approved that version", all you have is a small icon next to a meme.

An approval should be an action with a name and a timestamp attached to a specific version. Click to approve, a signed contract and a logged invoice are all approvals. A reaction on a message is not. Our guide to documented client sign-off explains how to set it up.

Invoicing turns into chasing

The usual WhatsApp invoice flow runs like this. You send a PDF. The client sees it and does not open it. You send three reminders. Eventually they say "oh, I missed it, sending now."

A link that opens an invoice with a pay button removes most of that loop. Stripe describes payment links as pages you can share by email, text or social media where customers pay in their own language and currency, and the point holds for any tool: the closer payment is to one tap, the sooner it happens.

The numbers back up the frustration. In a 2026 survey of 397 freelancers reported by ContentGrip, 54% waited more than a week to be paid after sending an invoice, and 24% waited two weeks or longer. The same survey puts admin and paperwork at about 204 hours a year. Not all of that is WhatsApp, but a good share of it starts in a chat window.

"But my client only wants WhatsApp"

Mostly, clients want low friction. They do not care about the app. They care that it does not need a long login, a password reset and a verification code to see a file.

So test it, starting with a new client rather than an old one. Send a project link on day one with a short note: "I put your files, approvals and invoices here so nothing gets lost in chat. You do not need an account, just open the link." Many clients will use it without comment. Some will prefer it once they see the file is always in the same place. A few really do need chat, and for them the hybrid works: keep chat for talking, and use the link for anything that needs a record.

The objection is often about your fear of looking too formal. A clean link looks organised, and clients read organised as reliable.

What leaving WhatsApp looks like

You do not quit it. You demote it. The shift is from "WhatsApp is where the work happens" to "WhatsApp is where we chat, and the portal is where the work lives."

In practice:

• Quick questions and friendly check-ins stay in chat.
• Files, deliverables and approvals go to a portal.
• Quotes, contracts and invoices go to a document and payment tool.
• Any message that changes scope gets the same reply: "Good idea, let me add that to the project and confirm the cost."

None of this takes special talent. It takes deciding that the app the client opened first does not get to decide how the work runs.

What to switch to

Pick the one you will actually use. Here are some options at different prices:

• A shared folder in Google Drive or a Notion page. Cheap and fine for under five clients, but you build and maintain it yourself, and it cannot take a payment or record a signature.
• HoneyBook, which starts at $29 a month billed yearly and includes invoicing, proposals, contracts and a client portal.
• Dubsado, whose Starter plan is $335 a year.
• Delivvo, which has a Free plan and a client portal that needs no password. More on it below.

For a broader comparison, see our roundup of the best client portal software.

How Delivvo takes the work out of the chat

Delivvo gives the client one link where the quote, contract, files, approvals and invoice live, so WhatsApp can go back to being a chat.

1. Put an inquiry form link in your WhatsApp bio or auto-reply. The inquiry lands as a card on your lead board instead of in a thread you have to scroll for.
2. Send a quote and a contract on one link. The client signs and pays the deposit there.
3. Share files in the client portal with versions, so version one, two and three are one click each. Files up to 50 GB on Pro and above, uploaded in a way that resumes if the connection drops.
4. Ask for approval on a specific file. The client clicks approve, and the approval is stored with a name and a time.
5. Send the invoice with a pay button. A reminder goes out at 7, 14 and 30 days if it stays unpaid, and stops when it is paid.

Everything stays on one project, so when a client writes "where is the final file?" you answer with a link and not a search through old messages. Chat still works for the quick stuff, and you can paste the portal link into WhatsApp whenever you like. The client opens the portal with a one-time code, with no password and no account. They pay through your own gateway, and Delivvo takes 0%. The Free plan costs $0 with no card and covers 3 clients, so you can test it on the next new client without risking an existing relationship. Read more on the client portal page.

Delivvo is a CRM and client portal for service businesses. See Delivvo for teams.

FAQ