If you're using Capsule for sales but not for project delivery, you're missing half the value of the product. Capsule's Tracks feature is genuinely good at handling project workflows for small service businesses, but it's also the feature most people skip during setup.
This piece is the practical walkthrough. What Tracks are, how to set them up properly, what templates I build for clients, and what going wrong looks like.
The broader context lives in the pillar piece on CRMs with project management. The full Capsule overview is in the main guide.
A Track is a Capsule feature that lets you build a template of tasks attached to a deal or contact, with each task assigned to someone and due relative to a trigger date.
The mechanics:
You build a Track template once. The template has a list of tasks, each with an assignee, a due date (relative to a trigger), and an optional description.
You apply the Track to a deal or contact when relevant (often automatically when a deal hits a certain stage). The tasks get created, assigned to people, and added to their task lists.
As the project progresses, tasks get completed. The Track shows progress against the template.
Tracks work for any process that follows a recognisable shape repeatedly. Client onboarding. Recruitment placement. Coaching programme delivery. Project phases. Annual contract renewals. If you do the same kind of work multiple times, a Track captures it.
Five principles.
Keep it tight. A good Track has eight to fifteen tasks. More and people stop engaging with it. Fewer and it's not adding structure.
Use relative dates. Tasks should be due relative to something (project start, deal won, contract signed), not absolute dates. The whole point of a template is that the dates flow from the trigger.
Assign every task to a specific person. Not "the team" or "whoever's free". A specific person. If you don't know who, the Track needs revising.
Name tasks as actions, not descriptions. "Send welcome email" not "Welcome email". "Confirm project scope with client" not "Scope confirmed".
Include the boring tasks. Send the invoice. Update the project file. Schedule the next review. The tasks that get forgotten are often the ones that aren't dramatic enough to remember.
A few examples from real client setups.
Client onboarding (8 tasks): Send welcome email. Schedule kickoff call. Send pre-call questionnaire. Set up client account. Hold kickoff call. Send call summary. Confirm project scope. Issue first invoice.
Recruitment placement (12 tasks): Qualify role with client. Brief candidates. Source shortlist. Send shortlist to client. Schedule first interviews. Hold interview debrief. Schedule second interviews. Negotiate offer. Confirm placement. Send placement invoice. Six-week check-in. Six-month repeat business call.
Coaching programme delivery (10 tasks): Intake session. Programme launch email. Session 1. Mid-programme review email. Session 5. Halfway check-in. Session 8. End-of-programme survey. Final session. Programme follow-up call.
Architectural project phase (15 tasks): Project setup. Initial brief confirmation. Concept design phase. Concept review meeting. Design development. Planning application submission. Planning decision tracking. Construction documents. Contractor selection. Construction phase kickoff. Site visits. Practical completion. Snagging. Final invoice. Project retrospective.
These are starting points. Each business adapts them to their reality.
The mechanics, briefly.
From within Capsule, navigate to Settings and find Tracks. Create a new Track template.
Add tasks to the template. For each task, set the name, the assignee (or assignee role), the due date relative to the trigger, and any description or instructions.
Save the template.
When you want to apply the Track, go to a deal or contact, click "Apply Track", and choose the template. The tasks get created on that record.
You can configure Tracks to apply automatically when deals hit certain stages, which removes the manual step.
The patterns I see in struggling Track setups.
Overbuilt templates. Twenty-five tasks for what's really a five-task workflow. The team stops using the Track because it's too heavy.
Tasks that don't match the work. The template was built around how someone thought the work should go, not how it does. People bypass the Track because following it is more work than just doing the job.
Unassigned tasks. Tasks marked as "the team" or with no owner. They sit untouched because nobody's responsible.
No Tracks at all. The Capsule setup runs the sales pipeline but doesn't use Tracks. The project delivery happens elsewhere. The CRM becomes a sales-only tool.
The piece on common Capsule mistakes covers more of these patterns.
If you'd like help setting up Tracks for your specific business, a discovery call is the no-pressure first conversation. For a more structured engagement, the piece on working with a CRM consultant covers what that looks like.
For the wider context, the pillar piece on CRMs with project management is the deeper read.
Tracks are the feature that turns Capsule from a sales tool into a sales-and-delivery tool. Setting them up properly is the single highest-leverage change you can make in a Capsule implementation. Worth the investment.