Keep the client notes with the work they lead to.

A practical way to organize client notes, project tasks, and follow-ups when your team is small enough that everyone wears a few hats.

You finish a client call with three different kinds of information: something worth remembering, something someone needs to do, and something to ask about later. Put all three in a meeting note and the actions can disappear into the paragraph. Turn everything into a task and the context gets lost.

Give each kind of information a home, then connect them through the client and the project.

Keep the relationship longer than the project.

Start with a record for the client company and the people you work with. Keep ongoing context there: who approves the work, how someone likes to communicate, and what matters to them. A new project should not mean starting the relationship from scratch.

Write notes that another teammate can understand without having been on the call. Include the decision and why it was made. "Sarah prefers the warmer palette because the shop should still feel familiar" is more useful than "Talked colors."

Pull the next actions out of the conversation.

Make a separate task for a concrete piece of work. Give it an owner and, when there is a real commitment, a due date. Keep related tasks in a named list inside the project. A list called "Ready for the first look" tells the team what those tasks add up to.

Separate work you owe from replies you're waiting for.

"Send the concepts" and "Ask whether the concepts are approved" are different commitments. The first belongs on the project's to-do list. The second is a follow-up with a person. Keeping that distinction makes it easier to see what you can move forward today.

When someone replies, add the useful outcome to their history and finish or reschedule the follow-up. Avoid leaving an old reminder open just because the broader project is still running.

Leave enough context for the next person.

Connect the client to their active projects. Before a call, look at their recent notes, open follow-ups, and project activity. After the call, update the decision and next action while they're still fresh.

This also helps when a teammate takes a day off. They should be able to hand over a project and a few clear next steps without forwarding their entire inbox.

What this looks like in tgethr

tgethr is being built around this connection between CRM and project management. People and companies have notes and follow-ups. Projects have to-do lists, messages, and files. Linked contacts connect the two, while shared activity shows what's changed.

We're preparing the first hosted version. The homepage includes a fictional studio workspace you can explore now.