Design studio approvals without long email chains

A CRM for designers is mainly there so that every client approval is recorded next to the project, with the name of the person who approved and the date. In a graphic design studio you get there by requesting the approval as a task assigned to the right person at the client, sharing only the version they need to review and keeping internal comments within the team. The email chain still exists for conversation, but the decision lives in the project.

Picture a five-person studio preparing a clinic's corporate brochure. They are on the third round. The clinic's marketing coordinator replies to an email titled "RE: FW: RE: brochure v3" saying she prefers option B. Two days later, the medical director writes in another thread that the final version is A, with a change on the cover. The designer worked from the last comment she read. Now an afternoon of work has to be redone, and someone has to explain to the client why the delivery is late.

Where an approval gets lost

In a studio, review rounds are short and intense, and comments arrive by email, by WhatsApp and on calls. None of those channels says which reply is the decision. The typical risk is a designer acting on the most recent comment while the actual approver believes a different version is final. There are plenty of messages, and none of them counts as an approval.

Who approves, settled before the first round

The first step happens before any design work: writing down in the client record who decides. In AgentticCRM each client has their contacts, and you can give each person who needs it their own portal access, one per person.

With that settled, the approval is requested from that person and nobody else. In the project you create a task such as "Approve the final cover design" and assign it to that person at the client, or to the client as a whole. They get a notice in their portal and an email with a link to confirm the task, even without an account. When they respond, the task closes with their name and the project moves on. If instead of confirming they ask for changes by email or on a call, the account lead notes it as a comment on the task and opens the next round.

Each round, a project phase

Organizing the project in phases helps everyone know where it stands: brief, first round, second round, final artwork. Each phase has planned dates, actual dates and a person in charge. A phase with a blocked task shows as blocked even if everything else is done, so nobody mistakes "almost ready" for "ready".

You decide what the client sees. Their portal shows the project's progress and only what you marked as visible, plus the files you share. Task comments are internal by default: the team can discuss the typeface or the tone of an image without the client reading that conversation. If you want to show them a specific comment on a project task, you choose it. And the client notice for every project change is off until you turn it on.

The client also sends you what you ask for from there: the copy, the high-resolution logo or the photos, up to 25 MB per file, and your team gets a notice.

When the client asks for something outside the budget

Halfway through, the clinic asks for a social media version of the brochure. That was not in the proposal. The accepted proposal is kept exactly as it was, with the name of the person who accepted it and the date, and nobody rewrites what the client approved. For the new work, you duplicate the proposal and prepare a draft for that round, or build a new proposal from your catalog. The client accepts or rejects it in their portal, and the decision is again recorded under their name.

The same goes for repeat commissions. If next year the clinic asks for event materials based on the earlier campaign, you open a new project, and the approval trail of the previous one stays in the client record for reference.

What stays in your design software

AgentticCRM manages the client record and the operation around design work. It does not replace your illustration or layout software, color management, prepress, print proofing, licensing or a specialist digital asset library. Working files stay where they always were; the CRM keeps what was requested, who approved it and what was invoiced. The CRM for graphic design studios page sums it up.

If this is the first time you will open a portal for your clients, client portal: what your client handles on their own explains what they can do there. And if your studio uses ChatGPT or Claude, a connected assistant can create the approval task and hand it to the client when it depends on them; we explain what that connection is in MCP explained for business owners.

Frequently asked questions

Does my client need an account to approve?

No. The tasks you assign them are answered from a private link they receive by email. If they have portal access, they also see them there, under What we need from you.

Does the client see what the team says about their design?

No. Task comments are internal by default. They only see a comment if you choose to show it to them on a project task.

Can someone other than the person who accepted the proposal approve?

Yes. You assign the task to the person at the client who decides on that deliverable, who may be different from the person who accepted the proposal.