CRM vs Project Management for Agencies: Where Should Client Follow-Ups Live?

CRM, project management and client follow-ups solve different problems. Here's a simple way for small agencies to decide where each type of work belongs.
Jun 4, 20267 min read
Short answer: use your CRM for deals and your project tool for delivery. Client follow-ups, promises and approvals are a third thing, and neither tool is really built to tell you what a client needs from you next. You don't have to replace either one.It's easy for a small agency to end up with three tabs open all day. The CRM has the deal. The project board has the work. The inbox has what the client actually said. And somewhere between them sits the question nobody owns: what do we need to do *with* this client next?

What each tool is actually for

A CRM is built around people and money. Who is this, where do they work, what's the deal worth, what stage is it at, when did we last talk?A project management tool is built around work. What needs delivering, who's on it, when is it due, what's blocked, what's done?Both are great at their jobs. Neither is great at: what does this client need from me next?

What goes where

ItemBest home
Implement checkout flowProject management
Deal worth $15,000CRM
Ask client to approve checkout flowClient next action
Contract renewal dateCRM
Send Friday progress updateClient next action
Bug: mobile menu overlaps logoProject management
Follow up on missing product imagesClient next action
Pipeline stage: proposal sentCRM
A simple test: is it something you're *building*, something about the *deal*, or something about *talking to and following through* with the client?

A website project, two kinds of work

Picture an active website build. The board has "design homepage," "implement checkout," "set up analytics," "test mobile." That's delivery.But around the same project you also need to send the Friday update, get the homepage approved, chase the missing product images, answer a budget question and set up a stakeholder review. That's relationship work.Put both on one board and the small relationship items end up competing with big production tasks. Guess which ones get pushed to tomorrow.

The CRM has the opposite problem

You drag the deal from "proposal sent" to "won." Nice. But for a service business, that's where the real relationship starts: promises, approvals, updates, requests, check-ins, and eventually a renewal. Most CRMs are at their best before the close, and a bit lost after it. Why that happens, and a 15-minute way to measure it: why client follow-ups get lost even when you have a CRM.

Why the third category falls through

Most agency stacks cover delivery well (Jira, Asana, ClickUp, Monday, Trello) and sales well (HubSpot, Pipedrive, Folk and others). Client next actions end up in email, calendar reminders, Slack, sticky notes and memory.That's how an agency with a great CRM and a great project tool still forgets to follow up. Nothing is misconfigured. There's just a workflow nobody set up.

Do you need another tool?

Not necessarily. If your current setup tells you, every morning:
  • who needs a reply,
  • what you're waiting for,
  • what you promised,
  • which follow-ups are late,
then you're covered. Keep going. But if you rebuild that list by hand each day from three apps, a lightweight layer might help.Be careful about adding tool overhead, though. Even in dedicated sales teams with full CRMs, admin eats most of the week: Salesforce's survey of over 7,700 sales professionals found reps spend only 28% of their time actually selling, with much of the rest going to deal management and data entry (Salesforce, State of Sales, 2022). A founder who also delivers the work can't afford that ratio. Lightweight is the key part. You don't need to copy your CRM somewhere else. You need just enough context to make the next step obvious. How to test whether a tool does that: client follow-up software that prevents silence.

Three signs you're missing that layer

  • Every morning you check the inbox, the CRM and the board just to decide who to contact.
  • Approvals and promises only come up in meetings, because nobody chased them in between.
  • A prospect becomes a client and everything from the sales conversation stays behind in the CRM.
If one or two of these sound familiar, it's worth trying. If none do, don't change a thing.

One record from lead to client

Related problem: the prospect lives in the sales tool, signs, and their information moves somewhere else. But the relationship didn't restart. What they said on the discovery call, what you promised, how they like to communicate, all of that still matters. Keeping it in one place makes the rest of the project noticeably smoother. The handoff checklist is in what happens after you win the deal.

Who owns the relationship layer?

In a two-person agency the founder owns everything, so ownership is obvious. From about four people up it gets blurry, and that's when follow-ups slip. The project manager assumes the account lead will send the update. The account lead assumes the PM did.A simple rule that works for most small agencies:
WorkOwner
Deal, pricing, renewalWhoever sold it (often the founder)
Delivery tasks and deadlinesProject lead
Client next action (updates, approvals, check-ins)One named account owner per client
Replies to client questionsWhoever was asked, but the account owner checks it happened
The important part is the third row: one name per client, not "the team." The account owner doesn't have to do every follow-up. They just make sure each client always has a next action and that it happens.

When follow-ups should live in the project tool

To be fair, there are setups where putting client follow-ups on the board is the right call:
  • The client works in your board. If they comment on cards and approve inside the tool, approvals naturally live there.
  • One client, one long project. A single retainer with weekly sprints may not need a separate layer.
  • Your whole team already reviews the board daily and the follow-ups are few.
It stops working when you have several clients at different stages, prospects without projects, or follow-ups that need context from sales conversations the board never saw.

Layers, not replacements

A practical setup for a small agency:
  • CRM: contacts, deals and pipeline
  • Project management: delivery
  • Email: conversations
  • Client next actions: the open loops between you and each client
The last layer sits next to the others. It doesn't replace them.

Common questions

Can I just use my project tool for follow-ups?

You can, and for a very small team it may be enough. It usually breaks down when follow-ups multiply and start burying delivery tasks, or when you need to follow up with a prospect who doesn't have a project yet.

Can a CRM handle follow-ups after the deal is won?

Many can, with tasks and reminders. The real question is whether you'll keep using them day to day once the sale is done, or whether they quietly stop at "won."

Isn't this just a task manager?

Partly. A next action is a task, but it belongs to a relationship and carries the reason and history with it. That context is what makes the follow-up quick to write.

The relationship layer in AwiFin

AwiFin deal panel with demo data: a $99,000 deal in negotiation with "No next action scheduled for this deal", exactly the gap between a pipeline and the relationship work
AwiFin deal panel with demo data: a $99,000 deal in negotiation with "No next action scheduled for this deal", exactly the gap between a pipeline and the relationship work
AwiFin is deliberately smaller than a full CRM. It holds leads and clients, but its main job is answering *what does this client need next, and when?* Keep Jira, ClickUp, Trello, Notion or your sales CRM. AwiFin sits next to them and keeps track of follow-ups, promises and waiting items.Your project tool tracks the work. AwiFin tracks the relationship.

Sources

Was this article helpful?One click, no sign-up needed.
Turn next actions into progressTrack every follow-up. Prepare your next message.
TagsAgency workflowClient communication
DM
Written by Dariusz M.AwiFin founder writing practical workflows for small agencies.
More articles →