How to Track Leads, Deals, and Projects in HubSpot

HubSpot works best when your team separates qualification, sales, and delivery. If every enquiry becomes a Deal, and every client project lives in a sales pipeline, the reports get noisy fast.

The clean model is simple: Contacts and Companies hold relationship data, Leads track qualification, Deals track revenue, and Projects track delivery after the sale. That keeps the CRM useful for both sales forecasting and client work.

For agencies, the choice is usually where delivery should live. HubSpot Projects can be enough for onboarding, fulfilment checklists, and account management, while ClickUp or Asana makes more sense if production has dependencies, templates, workload planning, and task-level operations.

The simple model: Lead → Deal → Project

A Lead is someone being qualified before there is a real opportunity. A Deal is a potential piece of revenue with value, ownership, a close date, and a sales stage. A Project is the delivery container after that Deal is won.

This separation protects reporting. Sales pipelines stay focused on money, while post-sale work moves into Projects instead of stretching the Closed Won stage into a delivery board.

The downside is that your team has to agree on handoff rules. If sales reps use Leads, Deals, and Projects inconsistently, HubSpot becomes a set of tidy-looking objects with messy data underneath.

Think of Contacts and Companies as the spine. Leads, Deals, Projects, tasks, tickets, notes, calls, and emails should point back to the right people and accounts, so the full client journey is visible from first touch to renewal.

How should you set up lead tracking in HubSpot?

Start with Contacts and Companies, even if you later use HubSpot’s dedicated Leads object. Contacts hold the person-level history, while Companies keep the account context in one place.

For a basic agency intake process, track lifecycle stage, lead source, owner, lead status, last contact, last engagement, and next activity. These fields are less glamorous than automations, but they decide whether follow-up happens.

If you have Sales Hub Professional or Enterprise, HubSpot lead records give prospecting and qualification their own workspace. Lead records show statuses, activities, associations, and engagement, but this object is not available to every HubSpot user.

HubSpot’s default lead stages are New, Attempting, Connected, Qualified, and Disqualified. They are a sensible starting point, but agencies should still define what each stage means in plain language.

For example, Qualified should mean more than “replied to an email”. It should usually mean there is a fit, a need, a decision path, and a reason to open a revenue opportunity.

Do not create a Deal for every raw enquiry, newsletter sign-up, or lead magnet download unless you want those records in revenue reporting. It may feel thorough at first, but it inflates pipeline and makes forecasting weaker.

When should a lead become a deal?

Create a Deal when there is a genuine revenue opportunity. That usually means the prospect has an identifiable need, a likely service fit, a rough value, and a next step with sales intent.

This rule keeps the Deal board useful. Your pipeline should show work that might close, rather than every person who has ever filled in a form.

The limitation is that early-stage sales teams sometimes want visibility before an opportunity is fully formed. In that case, use Leads, lifecycle stages, lists, and tasks for qualification rather than dragging weak prospects into the Deal pipeline.

A practical agency rule is to create a Deal after a discovery call is booked, a proposal is requested, or a scoped opportunity is confirmed. The exact trigger can vary, but it should be written down and used by everyone.

For inbound-heavy agencies, this stops content leads from polluting sales reports. For outbound teams, it stops call attempts and cold replies from being counted as pipeline before they deserve it.

How should agencies set up deal tracking?

Deals should track potential revenue through the sales process. HubSpot Deals can be associated with Contacts and Companies, which matters because agency sales often involve more than one stakeholder.

HubSpot’s default deal stages include Appointment scheduled, Qualified to buy, Presentation scheduled, Decision maker bought-in, Contract sent, Closed won, and Closed lost. Use these as a baseline, then adjust them to match how your agency actually sells.

For many agencies, the better stages are closer to Discovery booked, Discovery completed, Proposal in progress, Proposal sent, Negotiation, Contract sent, Closed won, and Closed lost. The upside is clearer forecasting; the downside is that changing stages later can make historical reports harder to compare.

Make key fields required before a Deal can move too far. At minimum, capture deal amount, close date, pipeline, deal owner, source, service or package, next step, and associated company or contact.

Board view is useful because sales teams can see the pipeline quickly. Weighted pipeline reporting is useful too, but default stage probabilities can mislead you if they do not match your real close rates.

HubSpot’s Sales Hub pricing page lists deal pipeline limits of 1 pipeline on Free, 2 on Starter, 15 on Professional, and 100 on Enterprise. One pipeline may be enough for a simple agency, but multiple service lines, regions, or sales motions can outgrow it.

How do HubSpot Projects fit after Closed Won?

HubSpot Projects are for post-sale work such as onboarding, implementation, fulfilment, retainers, and client-success handoffs. They help stop agencies using post-Closed Won deal stages for delivery, which keeps sales data cleaner.

Projects can be associated with CRM records including deals, contacts, companies, and tasks. Project data can also be used in reports or workflows, although some capabilities depend on paid seats or higher subscriptions.

A practical delivery pipeline might be Closed Won handoff, onboarding, strategy, production, review or QA, launch, reporting, and renewal or upsell. That gives leadership a client-work view without turning the sales pipeline into a task board.

HubSpot says the Projects object is available across products and plans. The catch is that project tags require Starter, Professional, or Enterprise, while project pipeline rules require Professional or Enterprise.

That matters for agencies trying to keep costs low. A simple HubSpot setup can track work, but more controlled delivery workflows may need a paid HubSpot tier or a dedicated project management tool.

Projects are strongest when the work must stay close to CRM data. They are weaker if your delivery team needs deep task dependencies, workload planning, production templates, time tracking, or client-facing operational boards.

How do you automate the Closed Won handoff?

The best handoff automation is triggered when a Deal moves to Closed Won. At that point, HubSpot should create a Project or delivery task and associate it with the Deal, Company, and main Contacts.

If you stay inside HubSpot, use Projects, tasks, workflows, and notifications to alert the delivery owner. This keeps the handoff close to the CRM, but it will only work if the sales record has the right fields completed.

Before automating anything, require clean ownership, amount, company or contact association, service or package, delivery start date, and next step. Messy sales data creates messy delivery tasks at scale.

If you use ClickUp, its HubSpot integration supports deal-based triggers that can create Spaces, Folders, Lists, tasks, and tasks from templates. It can also link ClickUp tasks to HubSpot objects and create or update HubSpot records from ClickUp automations.

That makes ClickUp a strong fit for agencies with repeatable fulfilment systems. The trade-off is another tool to maintain, and the integration design needs careful testing before the team relies on it.

If you use Asana, the HubSpot Marketplace lists the Asana app as a HubSpot Certified App. It can attach HubSpot deal or email campaign details to Asana tasks, create tasks when deals change, assign team members as a deal progresses, and start Asana workflows from HubSpot CRM objects.

The Asana route suits teams that want clean task handoffs and structured coordination. The catch is that the integration requires an Asana Starter or Advanced plan, and creating Asana tasks from HubSpot workflows requires Professional or Enterprise across eligible HubSpot hubs.

Do you need ClickUp or Asana as well?

Keep delivery in HubSpot if your work is lightweight, CRM-led, and easy to track with projects, tasks, notifications, and reports. This is often enough for simple onboarding, implementation checklists, customer-success handoffs, and account-management work.

The benefit is fewer tools and a clearer client record. The limitation is that HubSpot Projects are not automatically a full project management replacement for agencies with heavy production workflows.

Use ClickUp if your agency needs deeper operational project management. ClickUp is ranked fourth in our fixed index, starts Free then $7, and suits agencies that want project management, docs, and time tracking in one cheap tool.

ClickUp is a good fit for delivery systems with templates, dependencies, dashboards, workload views, time tracking, and task-level operations. The downside is that its flexibility can become fiddly if nobody owns the workspace structure.

Use Asana if your team values clean project tracking, timelines, portfolios, and cross-functional handoffs. Asana is ranked sixth in our fixed index, starts Free then $10.99, and suits agencies that want reliable project tracking without the clutter.

Asana is usually easier to adopt than a heavily customised ClickUp setup. The trade-off is that agencies wanting built-in time tracking and more operational depth may still favour ClickUp.

Even when delivery happens outside HubSpot, keep HubSpot as the source of truth for CRM, sales, and revenue. ClickUp or Asana should run the work; HubSpot should keep the client, pipeline, and revenue record clean.

How much does this HubSpot setup cost?

For buyer comparisons on this site, HubSpot is listed as Free, then $15. That makes it easy to test, but the plan you need depends on seats, hubs, objects, pipelines, and workflow requirements.

HubSpot Free includes $0/month, up to 2 users, 1,000 contacts, and no time limit. HubSpot also notes a 1 million records limit across other standard object types per account, but Free is still better treated as a test or small setup than a full agency operating system.

The first pricing catch is access to the Leads object. Lead records are tied to Sales Hub Professional and Enterprise, so teams on Free or Starter-style setups may need to use lifecycle stage, lead status, lists, and tasks instead.

The second catch is automation. Basic CRM work can be done cheaply, but advanced workflow automation often pushes agencies towards Professional or Enterprise, especially if HubSpot needs to create Asana tasks through workflows.

The third catch is seats. HubSpot introduced seat-based pricing changes for new accounts and subscriptions in 2024, with Core Seats and View-Only Seats. View-Only Seats are free and unlimited for Starter, Professional, and Enterprise, but those users cannot edit records, save reports, manage tools, or log and track emails.

If you take deposits, retainers, quotes, invoices, or subscriptions through HubSpot, check the payments setup before building a process around it. HubSpot payments is available only to businesses in the United States, United Kingdom, or Canada with a bank account in the same country, and using a paid version of HubSpot.

HubSpot says there is no monthly SaaS subscription fee for invoices, payment links, or subscriptions. Contracts and quotes require a Revenue Hub subscription, and payment availability or fees can vary by setup and country.

Recommended HubSpot tracking stacks by agency stage

For a solo consultant, a HubSpot Free or Starter-style setup can be enough if the process is simple. Use Contacts, Companies, lifecycle stages, tasks, Deals, and Projects for lightweight delivery, but do not expect it to behave like a mature agency operating system.

For a small agency sales team, HubSpot Sales Hub Professional makes sense if lead records, stronger sales process control, and workflow automation justify the cost. HubSpot ranks second overall in our fixed index and is our Best for Scaling pick, but GoHighLevel remains ranked first overall for agencies that want to run client marketing and resell software under their own brand.

For an agency with complex delivery, use HubSpot for CRM and sales, then connect ClickUp or Asana for fulfilment. This keeps pipeline reporting clean while giving the production team a tool built for daily delivery work.

For an agency taking retainers or deposits through HubSpot, evaluate Revenue Hub, payments availability, transaction fees, and whether existing Stripe processing is preferable. The best setup is the one that keeps sales, delivery, and finance clear without forcing the team into workarounds.

The main decision is where the handoff should live. If leadership needs client status inside the CRM and delivery is simple, HubSpot Projects are enough; if the delivery team runs complex production every day, connect a dedicated project tool and keep HubSpot clean.