When you’re working with a client, how do you keep the agreement, messages, feedback, approvals, requests, and project details together?
I’m curious what everyone is using right now, especially when you’re handling multiple clients or working with a team.
I’ve been exploring a simpler way of keeping all of that connected, and I’d love to hear how you guys currently do it.
I would say that this depends on the client, the request, the project, timeline and other things!
Yeah, that makes sense. I guess that’s exactly what makes it difficult when every project ends up being handled a little differently.
For you, what do you usually use to keep everything together when a project gets more complicated?
Just in 3 words:: Discipline, Patience and Organization.
I try to keep the project communication and approvals in one place as much as possible. For each client, I usually separate the scope, deadlines, feedback, and final approvals so there’s a clear record of what was agreed.
The biggest improvement for me has been keeping revision requests structured instead of having important changes scattered across email, chat, and random messages. It saves a lot of time when managing multiple projects.
Yeah, this is pretty much what I was getting at. When you’re managing multiple projects, what does your process usually look like from start to finish Like what tools do you use and how do you keep everything together?
This is something we’ve been working on because the communication itself usually isn’t the problem — it’s keeping the request connected to the actual work.
For website projects, we use a flow where the client points directly to the element on the staging site, the team gets the request with its page/element context, assigns it to the developer, and the developer can take that context into Cursor or Claude through MCP.
After the fix, the client reviews it in the same loop and the request can be closed.
It has made the client → team → developer → approval process much easier to keep track of.
Curious — do you currently keep this in one project tool, or does it still happen across email/chat/project management tools?
Good question — and honestly the tool matters less than the process around it. A few things that changed client work for me:
1. Get it in writing before you design anything. A simple brief or agreement covering scope, timeline, deliverables, revision rounds, and payment terms. Most client headaches come from mismatched expectations, not bad design.
2. Structure your revisions. Two or three defined rounds works well. Clients giving feedback across email, calls, and chat is where things get lost — ask them to send consolidated feedback in one place after each round, and confirm approvals in writing before you move to the next stage.
3. Show work in stages, not one big reveal. Early checkpoints (concepts before details) save you from spending hours polishing a direction the client never wanted.
4. Get paid in milestones. A deposit up front plus payments tied to approvals protects both sides and keeps projects moving.
The goal is a paper trail and a clear approval loop. Once you have that, you can run it with a spreadsheet and email — the fancy tools just make the same process faster.
When you’re managing multiple projects, what do you usually use to keep the brief, revisions, approvals, and payment milestones together?
The concrete version of what I described earlier: one folder per client, with subfolders for brief, assets, rounds, and finals. The brief is a single doc — scope, deliverables, revision rounds, deadlines, payment milestones — and everything else hangs off it.
For revisions, I have clients mark up a PDF export or use in-file comments (Figma for web work, annotated PDFs for print) so feedback lands on the design itself instead of scattered across chat threads. One consolidated feedback round at a time — no drips between calls and messages.
Approvals and payments stay in email as a written trail, and I track milestones in a simple spreadsheet: project, stage, invoice sent, paid. Tools honestly matter less than the rule “if it isn’t written in the project folder, it didn’t happen.” When a client questions a scope change, you just point at the brief doc rather than scrolling through six weeks of chat.
Does this ever get messy when you’re handling multiple projects at once, or does it work pretty well for you?