Your Client Info Is Scattered Across Ten Apps
A freelancer's client info, briefs, logins, and preferences, ends up scattered across email, Slack, WhatsApp, Notion, and Drive. The detail you need is always in the app you didn't check. The fix is one place to save it and ask for it late…

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 in 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 the thing they already sent you, which makes you look like you are not on top of it. Each client lives in a slightly different combination of apps, so there is no single move that finds anything.
The information exists. You were sent all of it. It is just spread across ten places, none of which can see the others, and remembering which place holds which detail is its own unpaid job.
Why freelance client info scatters by default
This is not disorganization. It is the natural result of how freelance work actually arrives. The scatter is built in.
The client picks the channel, not you. One emails, one only uses WhatsApp, one lives in Slack, one drops everything in a shared Drive. You do not get to standardize. You absorb each client's habits, and they do not match.
Information arrives mid-conversation. The staging login is dropped in the middle of a thread about something else. The real brand color is corrected in a passing message. The important detail is rarely in the document labeled "brief." It is in the chat, three weeks ago, between two other topics.
There is no single place that holds it all. Email holds threads. Slack holds chat. Notion holds docs you maintain. A password manager holds some logins but not the ones a client texted you. The full picture of a client lives nowhere. You assemble it from memory every time.
Memory is doing the index. What actually ties it together is you remembering "the API key is in that one Loom" or "her real deadline was in a voice note." That index lives in your head, degrades over time, and does not transfer when you take on the next client.
The result is a tax on every client interaction: before you can do the work, you have to find the work.
What "client info" actually means
When you say you need the client's info, you mean a specific, scattered set of things that almost never live together.
- The brief and the scope, including the version that is actually current.
- Logins and access, staging, CMS, analytics, the shared folder.
- Brand details, exact colors, fonts, voice notes, do-not-use list.
- Preferences and quirks, how they like feedback, their real deadline versus the stated one.
- The decision history, what you already agreed, so you do not relitigate it.
These are the things a client expects you to have at your fingertips. They are also the things spread across the most apps. The mismatch is the whole problem.
One place to put it, plain words to get it back
This is where dEssence helps. As each detail arrives, you send it into one place, the Chrome extension, the Telegram bot, or the web app at dessence.ai. Forward the email, screenshot the Slack message with the brand colors, drop in the brief, paste the staging note. dEssence reads each one and holds the meaning, no matter which app it came from.
Later, you ask in your own words. What were the brand colors for the Henderson site? Where is the staging login for the bakery client? What did the agency say about the deadline, the real one, not the stated one? The answer comes back from across all of it, because you saved the detail without first deciding which folder or doc it belonged in.
That is the point: no folders, no tags, no organizing. You save it, forget it, and ask for it later. The login dropped in a Tuesday chat is still findable in three months, in the words you would actually use. Your client knowledge becomes memory you don't have to maintain, instead of a scavenger hunt across ten apps you run before every call.
Honest about Notion, password managers, and dEssence
If you run a tight Notion client database or a disciplined password manager and you keep them current, that beats any tool you would abandon. Those tools are stronger than dEssence at structured records, shared workspaces, and team access. Keep them for what they do well.
dEssence is for the messier reality, the brand color buried in a chat, the deadline in a voice note, the brief that has three versions. And it has clear limits. It is in beta, so expect changes and rough edges. There is no native iOS app yet, so you save by forwarding into Telegram or using the web app rather than a polished share sheet. The free archive has a cap, which a freelancer juggling many clients can reach. And it is not a vault built for high-security secrets, so a dedicated password manager remains the right home for sensitive credentials. Worth knowing before you put a whole client roster in.
Frequently asked questions
Q: Do I have to set up a project or database per client?
No. There are no folders, no tags, no organizing. You send each detail as it arrives and ask for it later by client name or by what you remember.
Q: It came in WhatsApp, Slack, and email. Can one search cover all three?
Yes. Once you have sent those details into dEssence, you ask in plain words and the answer comes back regardless of which app it originally arrived in.
Q: Should I store client passwords in it?
For sensitive credentials, keep a dedicated password manager. dEssence is in beta and is not built as a high-security vault, so treat real secrets accordingly.
Q: I have a lot of active clients. Will the free tier hold everything?
The free archive has a cap, so a large roster may reach it. That is a real limit to weigh while dEssence is in beta.
If finding the client detail takes longer than using it, the thing to change is not how carefully you file things across ten apps. It is having one place that holds whatever arrives and hands it back in your own words. Keep your client info somewhere you can ask, not search. dEssence does this at save-time, free during beta, no card.
A client detail you cannot find on the call is a detail you do not have. Save it so future-you can simply ask.