CRM for project-based businesses: tracking the work, not just the sale
Project-based businesses (architects, agencies, consultancies, technical services) live with a CRM problem that most products don't solve well. The sale is just the beginning of months or years of work. Track only the sale and the CRM is empty for most of the client relationship. Track the work and most CRMs don't have the structure for it.
This piece is for the project-based businesses I work with. There's a pillar piece on CRMs with project management that covers this in depth, and a piece on how to use Capsule for client projects that covers the practical setup.
What "project-based" means in CRM terms
A project-based business has work that takes weeks, months, or years to deliver after a deal closes. Architectural projects. Agency engagements. Consulting assignments. Multi-phase implementations.
The defining characteristic, for CRM purposes, is that the relationship with the client during delivery is longer and more involved than the relationship during the sale. A CRM that goes quiet after the deal closes misses where most of the client interaction happens.
This is different from transactional businesses where the sale is the relationship (broker models, agency-style transactions, ecommerce). For those, a deal-centric CRM is fine. For project-based businesses, it isn't.
What the CRM needs to do
Five things.
Track the sale as it happens. Sales pipeline management. Standard CRM functionality.
Track the project as it happens. Templated workflows that fire when a deal closes, with the project's tasks, deliverables, and milestones visible on the client record.
Hold the relationship between sales and delivery. The CRM should know that the project running today connects to the deal that closed last month and the conversation that started six months before that.
Surface project status visibly. Anyone on the team should be able to look at the client record and see what's happening on the project right now.
Handle multi-project clients. The same client often has multiple projects over time. Each one needs its own tracking, attached to the same client record.
What works in practice
The setup I most often configure for project-based businesses.
A CRM with proper project workflow features. Capsule's Tracks are the obvious example. HubSpot Service Hub does similar things. Zoho's combination of CRM and Projects modules works if you configure it well. The full guide to Capsule covers the product I most often recommend.
Templates for the common project types. If you do three kinds of project (small, standard, complex), build a Track template for each. Apply the right template when a deal closes.
Pipeline that connects to project workflow. The "Won" stage of the sales pipeline triggers the project workflow. The two systems work together rather than being separate.
Custom fields for the data that matters across both sales and delivery. Client industry, project type, key contacts, contract value. Each piece of data captured once, visible in both views.
A weekly review habit that covers both pipeline and current projects. Twenty minutes, the team looks at deals in progress and projects in flight, identifies anything stalled, agrees next steps.
There's a piece on how to use Capsule for client projects with more detail on the project workflow side.
The pattern I see going wrong
The most common failure mode in project-based businesses: the sales side gets configured well, the project side never does.
The pipeline is set up. The stages match the sales process. Deals move through cleanly. Then a deal closes, and the CRM stops being useful for that client. The project team works in Asana or Notion or shared drives. The relationship between sales and delivery breaks. Six months later, when someone asks "what did we agree with that client?", the answer is in three different systems.
The fix is to configure the project workflow at the same time as the sales pipeline. Not as a phase-two addition. From day one.
Tools that work, and tools that don't
For project-based businesses specifically.
Capsule with Tracks: works well for small to mid-sized project businesses.
HubSpot with Service Hub: works if you're already in the HubSpot ecosystem.
Zoho CRM with Projects: works if you're committed to Zoho.
Monday.com: works the other way around (project tool with CRM features), particularly if delivery is more important than sales.
Pipedrive: I'd avoid for project-based businesses. The deal-centric model doesn't suit the work-continues-after-sale pattern.
Salesforce: works for large project-based businesses but overkill at small scale.
Specialist tools (agency management software, architectural practice management): worth considering for larger or specialist businesses. For smaller ones, a general CRM with project workflow is often simpler.
What to do next
If you're choosing a CRM for your project-based business, a CRM Audit is the structured way to think through what you need. An hour with me, a written summary, no obligation to engage further.
If you're earlier and you'd like a no-pressure first conversation, a discovery call is the place to start.
The pillar piece on CRMs with project management goes into the workflow side in more depth. The piece on best CRM for service businesses covers related sectors.
For project-based businesses, the CRM that tracks both the sale and the work is the one that earns its keep. The CRM that tracks only the sale becomes irrelevant within months of every deal closing. Worth getting this right at the start.