Small agencies should stop separating their CRM from their projects
The standard advice for a growing agency is to buy a CRM for sales and a project tool for delivery. HubSpot or Pipedrive on one side, Asana or ClickUp on the other, a Zapier connection in between.
For a 50-person agency with a sales team and a delivery team, that is correct. For an agency under 20 people, it creates a problem that looks small and isn't: the handoff between "won" and "kickoff" belongs to nobody.
In a small agency, sales and delivery are the same people
At five people, the founder sells the deal and then runs the project. The promises made on the sales call are the brief. The objections the client raised are the risks. The person who signed is the person who approves deliverables.
Split that across two tools and all of it has to be retyped, or it gets lost. The CRM knows what was promised. The project tool knows what is being done. Nothing knows both.
What goes wrong when an agency separates CRM and project management?
Separating CRM and project management creates promise drift, duplicate data entry and blind spots in client relationships.
1. Promise drift. The delivery team, or the assistant drafting the kickoff plan, never sees the call notes where the founder said "we'll include two rounds of revisions."
2. Re-entry. Every won deal means recreating the client, contacts and agreed work in the project tool. Integrations help, but someone maintains them, and they usually sync fields, not context.
3. Blind spots. When a client is at risk, the signal is in the project tool (late approvals, extra requests). When a renewal is coming, the signal is in the CRM. Nobody sees both until it is late.
Why do ChatGPT and Claude need sales and project context together?
ChatGPT and Claude need the agreed sales context to plan client work without losing what was promised.
If you run your agency with ChatGPT or Claude doing much of the drafting, the split gets worse. Your assistant can only use the context it can reach. If sales context lives in one system and delivery in another, it will plan the project without knowing what was sold.
One record fixes that. The assistant reads the deal, the agreed work and the client history before it plans the work, then keeps the same record current as delivery moves.
When should an agency keep CRM and project management separate?
Agencies should keep dedicated tools when sales requires forecasting, sequences or high lead volume, or delivery requires hourly invoicing.
Be honest about where this breaks:
- You have a dedicated sales team with forecasting, sequences and quotas. Use a real CRM.
- You bill hourly and need invoicing. Agency suites like Productive.io or Teamwork.com combine pipeline with time and billing; on Teamwork that pipeline feature sits on the Optimize plan (contact sales).
- Your pipeline is hundreds of leads a month. You need a sales tool built for volume.
For most agencies under 20 people, none of those apply yet.
What one record looks like in practice
- Deals, clients and the projects they turn into sit in one workspace.
- The project brief starts with what was sold.
- Your assistants read the brief before they plan, reserve tasks as they work, and submit results for review.
- From one home view you see what needs you today.
That is how Flori is set up: pipeline, clients and projects in one workspace, worked on by the assistants you already use, with no AI credits.
Start your workspace