Find scattered client info across apps and chats

Your Client Info Is Scattered Across Ten Apps

The brief is in email. The logins are in a WhatsApp voice note. The brand colors are in a Slack message from March. The feedback is split between a Notion page and a Loom. A client asks a simple question and you cannot answer it, because the detail you need is always in the app you did not check.

So your day fills with searching instead of working. You grep your inbox for “staging password,” scroll a WhatsApp thread for the logo file, reopen the Notion page that may or may not be the current brief, and ask the client, again, for something they already sent. It makes you look as though you are not on top of the work, even when the actual work is going well.

Each client lives in a slightly different combination of apps. There is no single move that finds everything. The information exists; you were sent all of it. Remembering which place holds which detail has become its own unpaid job.

Why freelance client info scatters by default

This is not necessarily disorganization. It is the natural result of how freelance work arrives. The scatter is built in before you decide how to manage it.

The client picks the channel

One client emails. Another only uses WhatsApp. Another lives in Slack. Another drops everything in a shared Drive. You absorb each client's habits, and those habits do not match.

A system that depends on every client sending every detail through the same channel asks you to change how they work. The more practical change is on your side: give the details you need a consistent destination after they arrive.

Information arrives mid-conversation

The staging login appears in the middle of a thread about something else. The real brand color is corrected in a passing message. The important detail is rarely confined to the document labeled “brief.” It is in the chat, three weeks ago, between two unrelated topics.

That matters because a tidy brief can still be incomplete. You might have the official document open and still miss the correction that changed what you were supposed to do. Finding the document and finding the current instruction are different tasks.

No single source holds the whole client

Email holds threads. Slack holds chat. Notion holds the documents you maintain. A password manager holds the credentials you have actually put into it, but not necessarily the login a client just texted you.

The full picture lives nowhere. Before a call, you assemble it from several places. During the call, you try to remember which piece came from which one.

Your memory becomes the index

What ties the information together is often a thought such as “the API key is in that one Loom” or “her real deadline was in a voice note.” That index lives in your head, gets less reliable over time, and has to be built again for the next client.

The result is a tax on every interaction: before you can do the work, you have to find the work. The problem is not that you lack the information. It is that retrieving it requires remembering its route to you.

What “client info” actually means

You are rarely looking for everything about a client at once. You are looking for one particular detail, and you need enough context to know what it means.

The brief and scope: what you agreed to deliver, including the version that is actually current.
Logins and access: staging, the CMS, analytics and the shared folder. Sensitive credentials belong in a dedicated password manager.
Brand details: exact colors, fonts, voice notes and the do-not-use list.
Preferences and quirks: how the client likes feedback, and their real deadline versus the stated one.
Decision history: what you already agreed, so the next conversation does not reopen a settled question.

These are the things a client expects you to have at your fingertips. They are also the things spread across the most apps. That mismatch is the problem to solve.

For example, “the brand colors” might mean the palette in the original brief or the corrected color in Slack. “The deadline” might mean the date in the document or the different expectation expressed in a voice note. Saving the useful detail means keeping the instruction you will need, rather than relying on your memory of the conversation around it.

One place to put it, plain words to get it back

This is where dEssence helps. As each detail arrives, you choose what to send into one place using the Chrome extension, Telegram bot or web app at dessence.ai. You manually forward or save the material. There are no connections to your email, Slack, Notion, calendar or school apps doing this in the background.

Forward the relevant email, screenshot the Slack message with the brand colors, or drop in the brief. For staging access, keep sensitive passwords in your password manager; the useful client note can be the non-sensitive context about what access you need. dEssence reads the material you save so you can ask about it later, regardless of the app it originally came from.

The questions can sound like you: What were the brand colors for the Henderson site? What did the agency say about the deadline, the real one, not the stated one? If your question is Where is the staging login for the bakery client?, the credential itself should still live in your dedicated password manager.

The point is that you do not have to decide which folder or tag a saved client detail belongs under before keeping it. You save it and later ask by client name or by the part you remember. A passing Tuesday message does not have to depend entirely on your recollection of Tuesday's chat when you need it three months later.

There is still a boundary: an answer can draw on what you have saved. If the correction remains only in Slack, saving the original brief does not bring that correction along. The habit is to capture the useful change when it arrives, not to assume the whole conversation is already present.

Keep the tools that already work

A tight Notion client database or a disciplined password manager that you keep current beats a tool you would abandon. Structured records and shared workspaces have a different job from remembering a stray client detail. Team access also matters when someone else needs to work from the same information.

You do not need to replace those strengths to address the scatter. Keep Notion for the structured client record you actually maintain. Keep the password manager for sensitive credentials. Use dEssence for the messier material: the corrected brand color, the deadline in a voice note, or the brief whose versions are otherwise hard to keep in mind.

Change the retrieval habit, not every client's workflow

If finding a client detail takes longer than using it, more careful filing across ten apps may leave you doing the same work in ten places. A common destination gives you a different starting point: the detail itself, described in the words you would use on the call.

Start with the information that actually interrupts your work. The corrected color. The current scope. The preference you keep asking the client to repeat. Save each useful detail as it arrives, and keep the structured systems that already earn their place.

A client detail you cannot find on the call is not much help in that moment. The aim is to make the next question easier to answer, without making your memory responsible for the entire route back.

Frequently asked questions

Do I have to set up a project or database per client?

No. You can save details without creating folders or tags, then ask by client name or by what you remember. The useful habit is capturing the relevant material as it arrives, including the corrections that change the original brief.

Can one search cover information from WhatsApp, Slack and email?

Yes, once you have manually sent those details into dEssence. Their original channel does not have to determine how you ask for them later. This does not mean dEssence connects to or searches your live accounts: material you have not saved remains outside that saved collection.

Should I store client passwords in it?

Keep sensitive credentials in a dedicated password manager. dEssence is not a high-security vault. A non-sensitive note about the client's staging access and the actual password are different things with different storage needs.

Which plan makes sense for a lot of active clients?

Compare how much you save each day. Free is $0 forever and allows up to 20 saves a day, with no card required. Pro is $10 a month and allows up to 150 saves and 200 messages a day. The number of clients alone does not tell you how many details you will save.

Can I save from my phone?

You can use the Telegram bot or web app. There is no native iOS or Android app. The Chrome extension is another saving surface, so choose among these available routes rather than relying on a native mobile share sheet.