Back to blog
7 min readJune 14

Every client's brand rules live in a different app and you keep mixing them up

One client's brand colors are in a PDF, another's are in a Slack thread, a third's are in your head. Here is how to keep each client's rules in one place you can actually ask.

Keep each client's details in one memory per client instead of scattering them across folders, chats, and email. Forward every brand guideline PDF, asset link, logo file, and feedback message into that one place as it arrives. Then ask in plain language, "what is this client's primary hex," and get the exact answer back before you start work.

You knew this client's rules cold three months ago. Their coral was #E2503B, headings were always set in their licensed serif, and the founder hated drop shadows with a quiet intensity. Then you onboarded two more clients, each with their own palette, their own fonts, their own list of things never to do, and the lines started to blur.

Last week it almost cost you. You sent client A a social set in client B's blue because both files were open and you grabbed the wrong swatch. You caught it before they did, this time. But the brand PDF was buried in an email from the kickoff call, the logo files were in a shared drive folder you could not remember the name of, and the "please never use the old logo" note was in a Slack message from February. The rules existed. They were just in five different apps, and your memory of which client owned which was the only thing tying them together.

Why your folders and apps do not actually solve this

The 2026 advice for freelancers is sound on paper: keep a centralized client record, store the brief, contracts, assets, and brand guidelines location per client, add custom fields for things like preferred channel and asset folder, and provide a shared folder with logos, templates, and font files. Good client-management tools do real work here, holding contact records, project history, and invoices linked to the right client.

The gap is not whether the information is stored somewhere. It is that the answer you actually need, the primary hex, the font name, the one rule the client cares about most, is split across the storage. The hex code is a swatch inside a 40-page brand PDF. The font is a license email. The "never do this" rule is a line in a feedback thread. To answer a five-second question you are opening three apps and skimming, and when you are mid-project juggling several clients, you do not skim, you guess.

So the details split across tools. The structured stuff lives in the client folder. The real, in-the-weeds rules live in PDFs, chats, and your head, and the question you actually ask yourself, "wait, what does this client allow," has no single place to land.

What freelancers actually do to keep client rules straight (and where it breaks)

The habits are good. The storage is the problem.

Many freelancers make a folder per client and drop the brand kit, logos, and fonts in it. Some keep a one-page cheat sheet with each client's colors, fonts, and dos and don'ts. Plenty save the feedback that matters, the message where the client said "we always capitalize the product name" or "the founder hates stock photos," by starring an email or pinning a Slack message.

Every one of those is the right instinct. They each create a fragment, and the fragments never end up in the same place. The brand kit is in a drive folder. The cheat sheet is a doc you forgot to update after the rebrand. The pinned rule is in whichever chat app that client uses. When you need the answer fast, you cannot find it, so you fall back on memory, and memory is exactly what mixed up the two blues in the first place.

Put each client's rules somewhere you can ask, not just store

The fix is not another folder to keep tidy. It is one place per client that takes whatever you already receive and lets you ask it back later in plain language.

That is the idea behind a tool like dEssence. It is a personal memory app, not a project tool and not a client-management system, so it stays out of your way and just holds things. You save it, forget it, and ask for it later. The point for a freelancer is that the brand PDF, the logo link, the font email, and the one-line rule from a chat all finally land in the same spot, sorted by which client they belong to.

Here is what that looks like across a few clients at once.

A new client sends their brand guidelines PDF on the kickoff call. You forward it in. They share a drive link with logos and fonts; that goes in too. A week later the founder writes "please never put our wordmark on a photo," and you forward that straight from your inbox. There are no folders, no tags, no organizing. Each thing attaches to that client.

Then, the morning you open their next project, you ask in your own words: "What is this client's primary hex and heading font, and what are the rules I keep forgetting?" You get back #E2503B, the licensed serif, the no-wordmark-on-photos rule, and the no-drop-shadows note, pulled from a PDF, a link, and an email you would have spent ten minutes hunting for. You start the work knowing the brand, not guessing at it.

The three save surfaces match how a freelancer actually works

You receive client material everywhere: email, chat, browser. dEssence has three co-equal ways to capture, and they line up with where your client comms actually arrive.

The Chrome extension is the desk tool: save a brand portal page, a font license page, or a drive link straight off the tab without breaking flow. The Telegram bot is the on-the-go tool: forward a logo file or fire off a voice note about a client's verbal rule the moment a call ends. The web app is where you sit down and ask the synthesis question before you open a project. Same memory underneath all three, so it does not matter which one you reach for first.

This is memory you do not have to maintain. You are not building a knowledge base of clients. You are dropping things in as they pass and trusting that you can ask later.

Honest about dEssence

A client-management or project tool and dEssence are different tools, and you will likely keep both. Your project tool runs the business: contracts, invoices, deadlines, deliverable handoff. dEssence does none of that and is not trying to. It holds the messy per-client rules and answers questions about them. If you want one system that also manages your projects and billing, dEssence is not that system.

A few honest limits. dEssence is in beta, so expect rough edges and changing features. There is no native iOS or Android app yet, so on the go you are working through the Telegram bot rather than a dedicated mobile app. It also has no team workspace, so it is your personal memory, not something a whole studio shares. For a solo freelancer keeping their own clients straight, that fits. For an agency that needs shared, role-based access to brand assets, a dedicated brand platform still owns that job.

Frequently asked questions

Is dEssence a project or client-management tool?

No. It is a general personal memory app that happens to work well for keeping each client's brand rules and assets in one place. It does not manage contracts, invoices, or deadlines. Keep your project tool for that and use dEssence for the in-the-weeds details those tools do not surface fast.

How do I keep one client's brand rules from mixing with another's?

You forward each client's PDFs, links, and feedback in as they arrive, and when you ask later you name the client. The answer pulls from what you saved about that client. There is nothing to file or tag.

Can it actually give me back an exact hex code?

If you saved the brand guidelines that contain it, yes. You ask in plain language for the primary color or heading font, and it answers from the document you forwarded in, so you do not reopen a 40-page PDF to find one swatch.

What if I already keep a folder and a cheat sheet per client?

That instinct is right, the problem is only that the folder, the cheat sheet, the email, and the chat rule never sit together. Sending them into one memory per client means the answer is in the place you will actually ask.

dEssence is free during beta with no card required, so you can run two or three of your active clients through it for a week and see if you start their next project actually knowing the rules. It will not replace your project tool, and it is early software with no mobile app yet, but for the brand details that scatter across PDFs, drives, and chats, it gives you somewhere to put them and a way to ask for them back.