CRM with project management: running client work and sales from one place
The shape of a service business is roughly this. You spend time winning work. You then spend time delivering it. Then you do more of both, often for the same clients, often at the same time. The selling and the doing run in parallel forever.
Most software pretends this isn't true. There are CRMs, which handle the selling, and there are project management tools, which handle the doing, and the two products live in separate worlds. Your team uses one for the front half of the client relationship and another for the back half, and the information between them either doesn't move or moves badly.
This is the central problem of CRM for service businesses. And the answer, for most small UK businesses I work with, is a CRM that does project management too.
This guide is the long view on why that matters, what to look for, and how it works in practice. There's a shorter piece on whether you need both tools or one, and a broader CRM guide for UK small businesses if you're earlier in the journey.
The split that doesn't have to exist
The reason CRMs and project management tools are separate categories isn't because they should be. It's a historical accident. CRMs grew out of sales departments. Project management tools grew out of operations departments. The two were owned by different teams, sold by different vendors, and budgeted from different lines.
For a large business, that split is sometimes useful. The sales team and the delivery team are genuinely separate, with different needs and different reporting lines. Two specialist tools serving two specialist teams can work.
For a small business, the split is almost always counterproductive. The same people are doing the selling and the delivering, often on the same client, often in the same conversation. The split means switching tools mid-conversation, copying information between systems, and remembering which tool holds which piece of the client's story.
What service businesses need is a single tool that follows the client from "we just heard about you" to "we've completed three projects together over four years and the next one starts in March". The relationship is continuous. The system tracking it should be too.
What a CRM with project management means
The phrase "CRM with project management" sounds like a checkbox feature. It isn't. The question is whether the project capability is properly integrated with the relationship capability, or whether it's a tab nobody uses.
Properly integrated, it works like this. Each client has a record. On that record sits everything you know about them: contact details, the history of conversations, the deals you've won and lost. Attached to the won deals are project workflows: templated sequences of tasks that describe how you deliver this kind of work, with each task assigned to someone, with dates, with status. As the project moves forward, the workflow updates. As the relationship continues, the record grows. Sales and delivery aren't separate dimensions; they're parts of one continuous client view.
In Capsule, this is the Tracks feature. In HubSpot Service Hub, it's tickets and pipelines combined. In Zoho, it's the Projects module connected to CRM contacts. In Monday, it's items linked to deals. Each works differently in detail. The principle is the same: the work that follows the sale lives on the same client record as the sale itself.
The opposite (a CRM where the project capability is a separate module that nobody connects, or a half-baked task system that goes unused) is what most businesses end up with by default. It looks like the same thing on paper. It works completely differently in practice.
The features that earn their place
If you're evaluating CRMs by their project capability, six features worth checking.
Templated workflows. Can you build a reusable template for the kind of work you do repeatedly? Onboarding a new client. Running a recruitment placement. Delivering a coaching programme. Architectural project phases. If the work follows a recognisable shape, the CRM should let you template it once and apply it many times. Without templates, you'll set up each project from scratch and the team will stop doing it.
Templates tied to deals or contacts. The template needs to attach to a specific client record so the work is visible alongside the relationship history. A project workflow that exists separately, somewhere else in the system, defeats the purpose.
Date-relative task scheduling. Tasks need to be due relative to something (project start, contract signed, last session). Not absolute dates that you have to set manually each time. The whole point of a template is that the dates flow from the trigger.
Task assignment to team members. Different people on the team handle different parts of the work. The CRM needs to assign tasks accordingly, and let people see what they personally need to do next.
Status visibility. You need to be able to see at a glance how each project is progressing. Which tasks are done, which are coming up, which are overdue. Without this, the templates become a hidden bureaucracy nobody opens.
Integration with calendar and email. Tasks should flow to the team's calendar so they're visible where work happens. Emails about the project should attach to the client record automatically.
If a CRM ticks all six, it can do real project management for service businesses. Most can tick three or four. The gap between four and six is where many implementations come unstuck.
How it works in practice
A concrete example, drawn from the kind of business I see often.
A small recruitment agency, four people, places candidates with mid-sized UK businesses. They win their work through a mix of inbound enquiry, networking, and referrals. Each placement involves: qualifying the role, sourcing candidates, screening, interviewing, offer management, and a post-placement check-in.
The naive setup: a CRM with a sales pipeline (Lead, Qualified, Proposal, Won, Lost). Deals move through it. Once they're Won, the CRM goes silent on that client until the next role.
The setup that works: the same CRM, the same pipeline, plus a Track template that fires when a deal is marked Won. The Track creates the placement workflow. Qualification interview scheduled. Candidate brief sent. Sourcing started. Shortlist due. Client interviews scheduled. Offer management. Placement confirmed. Check-in scheduled for six weeks post-placement. Repeat-business check-in scheduled for six months. Each task assigned, each due relative to the placement start. As the team works through the placement, the workflow updates. The client record holds everything: the original deal, the candidates considered, the placement, the post-placement follow-ups, the conversations about the next role.
The difference between those two setups is the difference between a CRM that earned its place and a CRM the team forgot about.
The shortlist for CRMs with project management
For UK small businesses, the realistic options.
Capsule with Tracks. Most of my clients end up here. Tracks are simple to build, the templates apply cleanly, the project view sits naturally alongside the relationship view. Light on the project-management bells and whistles (no Gantt charts, no resource scheduling), but for small service businesses that's an advantage rather than a limitation. The full guide to Capsule covers the wider product.
HubSpot with Service Hub. Works well if you're already in the HubSpot ecosystem and you'll use the marketing features too. Service Hub adds the project and ticket management. Expensive if you're only buying it for the project capability.
Zoho CRM with Projects. Works if you're committed to the Zoho ecosystem. The integration between CRM and Projects modules is real but takes setup work to feel natural.
Monday.com. Works the other way around: a project management tool that's grown CRM features. Good if your work is more project-heavy than sales-heavy.
Notable absence: Pipedrive. Pipedrive is a fine CRM but its project capability is shallow. If you need real project workflow management, Pipedrive isn't the answer.
The piece on best CRM for service businesses covers the industry-specific angles in more detail.
The mistakes I see
Three patterns that turn a CRM-with-project-management setup into a regret.
Setting up the sales side and forgetting the delivery side. The team uses the pipeline; the Tracks (or equivalent) never get configured. The CRM becomes a sales tool only, and the delivery work happens in spreadsheets and shared drives. Two months later the CRM is dusty.
Overbuilding the templates. The team tries to capture every possible step in every possible scenario, ending up with templates that take forty minutes to fill in for a simple project. Templates work when they're tight (eight to fifteen tasks for most workflows) and bend to handle variations. Overbuilt templates get bypassed.
Not training the team on the project side. People learn the contact list and the pipeline because they're the obvious parts. The project workflows are the part nobody learns until they need to, and by then the system has drifted. Train the project side at the start, not as an afterthought.
The piece on common Capsule mistakes goes into more of these in detail.
When to set this up
If you're earlier in your CRM journey and you don't yet have a CRM at all, set up the project capability from the start. It's much easier to design the system around both functions from day one than to bolt project management onto an existing CRM that's been running as sales-only for two years.
If you've got a CRM already and you've been using it as sales-only, the time to add the project capability is when you can articulate the work you do repeatedly. If you can describe your delivery process in a list of ten to fifteen steps that happen for most clients, you're ready. If you can't, it's worth spending a couple of hours documenting your delivery before you build it into the system.
There's a piece on working with a CRM consultant if you'd like to discuss the build with someone.
What to do next
If you'd like to talk through whether a CRM with project management fits your business, a discovery call is the no-pressure first step.
If you know roughly what you want and you'd like a structured second opinion, a CRM Audit is an hour with me plus a written summary of what I'd recommend.
The reason most service businesses end up dissatisfied with their CRMs isn't the products. It's that they bought a tool to track sales and never connected it to the work that follows. Closing that gap, in one well-configured system, is one of the single highest-leverage changes a small service business can make.