Freelance designer in his home studio, phone next to the keyboard, with a concentrated expression

Use case: a freelance designer and the client who changes the scope on WhatsApp

8 min read

Simulated case: a freelance designer whose client keeps widening the job on WhatsApp. What was agreed, what is pending and how to prepare the payment talk.

by Equipo Memchats

Table of contents
  1. A simulated case: Dani and the client who "adds one little thing"
  2. Before: what was agreed, scattered across a chat
  3. What matters in a situation like this
  4. After: Tomás's record
  5. Preparing the payment conversation
  6. The limits
  7. How each option on the market handles it

A simulated case: Dani and the client who "adds one little thing"

This is a simulated case. Dani and his client, Tomás, are fictional characters built from situations many freelancers will recognise. We tell it to show what a relationship with a difficult client looks like when everything lives in a chat, and where what Memchats can do ends.

Dani is 34 and a freelance designer. A few months ago he agreed with Tomás, who owns a small chain of bike shops, a brand identity and a five-page website. There was a quote as a PDF, a proposed schedule and a promise of "two rounds of changes". After that, as so often happens, the relationship moved to WhatsApp: it is fast, it is comfortable and nobody dreads opening it.

Tomás is not a bad person. He is a client in a hurry, who thinks out loud and remembers something new every day.

Before: what was agreed, scattered across a chat

The quote said one thing. What happened afterwards, in messages, was this:

  • One Tuesday, Tomás writes: "hey, while you're at it, could you also do an English version of the site? It's a small thing". Dani replies "no problem, I'll look into it".
  • A week later: "the shop signs could come from the same identity, right?". Dani answers with half a "sure" and does not come back to it.
  • Tomás says he loves the logo. Two days later he asks for "one more pass, something more modern". That is already the third round, and nobody has called it that.
  • Dani asks for the page copy. Tomás says "I'll send it this week". Six weeks have gone by.
  • The second invoice is still unpaid. Tomás says "once everything is closed", and nothing closes because every week there is something new.

Each message on its own is reasonable. Together they are a scope that has grown without anyone deciding it, a schedule that has slipped because of copy that never arrives, and an invoice nobody wants to mention. Dani suspects he has been saying yes for too long. He does not know how many times, or to what. And if he raises it, he fears looking like the one who gets petty over one little thing.

Studio wall with printed mockups, colour swatches and illegible sticky notes

What matters in a situation like this

To talk about money with a client without it turning into a fight, Dani needs three things, and none of them is a clever line. Knowing what was agreed at the start and where it is written down. Knowing what has been added since, when, and how he reacted (whether he accepted it, postponed it, or never answered). And knowing what the client owes: copy, approvals, payments. With that you can propose something clear. Without it, you argue from memory and tone.

After: Tomás's record

Dani exports his chat with Tomás from WhatsApp (the guide is in Import WhatsApp chats in 60 seconds) and imports it into Memchats. Memchats works with what you import: whatever was agreed on a call or in person will only be there if Dani writes it down afterwards.

From the history, Memchats builds and maintains a record of Tomás. Among other things it picks up:

  • Each party's commitments, with a date and the message that supports them: the proposed schedule, the copy Tomás promised to deliver, the two rounds of changes.
  • The threads left open: the shop signs, the English version, the invoice.
  • A pattern, with the quotes that show it: Tomás tends to introduce changes as "one little thing" or with a "while you're at it", and he almost always does it right after approving something.

What separates this from pasting the chat into an assistant is that the record stays up to date with every import and always points to the message it comes from; we explain that in Memory is not context. Dani can correct anything that is not right, because a model can misread a tone or a joke.

Hands holding a phone with the screen turned away, on a wooden table with coffee and a notepad

Preparing the payment conversation

Dani asks Alma, in her business area (how she picks an area is covered in One counsellor with four areas), what he should bring to that conversation. This is an illustrative example of the kind of summary he might get, not a real screenshot:

What is on record as agreed: brand identity and a five-page website, with two rounds of changes (message of 10 September). What was added later: English version (asked for on Tuesday the 23rd; your reply: "no problem, I'll look into it"), shop signs (asked for on the 30th; your reply: "sure", with no follow-up) and a third pass on the logo (asked for on the 5th). Pending from Tomás: the page copy (promised for "this week" six times) and payment of the second invoice. Note: for two of the three new requests, your reply is on record as acceptance.

That last sentence is the uncomfortable part, and the most useful. Alma does not take Dani's side: she shows him that in two cases he said yes and did not make clear it had a cost. It would be unfair to claim now that those were out of scope, as if Tomás knew. The honest conversation is a different one: acknowledge what was accepted, put a price on things from now on, and ask for what has already been delivered to be paid.

From there comes something like this, which Dani adapts and writes in his own words (Memchats is a prompter, it does not send or write for you, as we explain in Assistant or prompter):

  1. A three-line summary of what was agreed on 10 September.
  2. The three added items, with their dates, and a clear proposal: what comes in as an extra and what waits for a second phase.
  3. What he needs from Tomás to close: the copy, with a date, and payment of the second invoice.
  4. A rule for what comes next: any change of scope is confirmed in writing before work starts.
Designer standing by a window with a mug in hand, calm at the end of the afternoon

The limits

  • It is not legal advice. A chat is not necessarily a contract, and its value as evidence depends on each case and on how it is submitted (the general case is told in When a WhatsApp message ends up in court). If the non-payment gets complicated, a lawyer is the one to assess it. Memchats helps you arrive with the chronology in order, not to say what to claim.
  • It does not collect for you. No record makes Tomás pay. What changes is that Dani raises the conversation with facts and without guilt.
  • It cannot see what was not written. What was said on the phone or in a meeting is not in the chat, and the record does not know it.
  • It can be wrong. A misread tone or a message without context can produce a wrong conclusion. Every item carries its quote so Dani can check it before using it.
  • It does not turn the client into an enemy. If you use a record to catch someone out, the conversation will go worse. It is for preparing, not for winning.
  • Another person's data is involved. Tomás has not consented to his conversation being analysed; the database is on servers in Germany, the original files go to Cloudflare R2 (with Western Europe as the preferred location), and it can be exported or deleted, and the other party can ask for their data to be deleted (we explain it in European data sovereignty).

The reason we built Memchats as a record and not as an assistant that talks for you is in Why Memchats was born.

How each option on the market handles it

  • A general chat assistant: it helps you draft a payment message if you paste in all the context first; as far as we have been able to check, its memory is about you and not about each client (ChatGPT, Claude, Gemini).
  • A chat analyser: it can accept exported chats and read the tone of a one-off conversation; it is not designed to keep a client record over time (Lucen).
  • An AI companion: it is for chatting with you, not for remembering your clients (Replika).
  • Memchats: a persistent record per client, with commitments, open threads and dated quotes, and a counsellor who reads it.

The full picture, with sources and access dates, is in the market for AI memory about people.

If you have a client like this, you can create an account for free and import just that one chat to see what record comes out.

Start with your own chats

Import one conversation and Alma builds that person’s profile in a minute. Free to start.

Create my free account

Keep reading