Service Objects

The Essence

The Project is where planned work gets organized and tracked. Unlike Tickets (which are reactive) or Services (which are ongoing), Projects are bounded initiatives with defined scope, participants, and objectives.

They answer "what are we working on, with whom, toward what outcome?" Projects can be customer-facing (implementation, transformation) or internal (process improvement, product development). They provide the container for coordinating work that spans time, involves multiple people, and produces specific outcomes.

HubSpot's Project Object (INBOUND 2025)

The Project object launched at INBOUND 2025 and is still early in its evolution.

What's Available Now:
  • โ€ข Project object with custom properties and pipelines
  • โ€ข Gantt chart view (public beta)
  • โ€ข Table and board views
  • โ€ข Tasks associated with Projects
  • โ€ข Workflow automation
  • โ€ข Associations to Contacts, Companies, Deals, Tickets
What's In Development:
  • โ€ข Project Subtasks
  • โ€ข Task Dependencies
  • โ€ข Project Templates
  • โ€ข Projects Task Card

Use Projects now for organizational and visibility benefits. Plan for advanced features to arrive.

"Projects are proactive. Tickets are reactive. If you're planning to do work โ†’ Project. If someone asked for help unexpectedly โ†’ Ticket. This distinction matters for accurate metrics, appropriate management, and clear accountability."


Unified View Contribution


Sarah's Story

When Sarah's CVP Implementation began, a Project was created:

Project: "Precision Components Manufacturing - CVP Implementation"

Type: Client Transformation
Status: Active
Phase: Foundation
Progress: 45% complete
Associated To:
โ€ข Company: Precision Components Manufacturing
โ€ข Contacts: Sarah (Sponsor), IT Director (Technical Lead), CFO (Stakeholder)
โ€ข Deal: VF-2024-0847
โ€ข Order: VF-2024-0847

This Project became the container for all implementation work:

Deliverables within the Project

  • Chicago Foundation Build (Complete)
  • Detroit Foundation Build (In Progress)
  • Atlanta Foundation Build (Scheduled)
  • ERP Integration Phase 1 (In Progress)
  • Team Training - Core Users (Complete)
  • Team Training - Advanced (Scheduled)

Associated Team

  • โ†’ Chris (Project Sponsor - Value-First)
  • โ†’ Ryan (Technical Lead - Value-First)
  • โ†’ Sarah (Customer Sponsor)
  • โ†’ Detroit Ops Manager (Site Lead)

Health Indicators

  • โœ“ On Track (no blockers, timeline holding)
  • โœ“ Budget: Within allocation
  • โœ“ Stakeholder engagement: Active

Sarah could see her Project in the portal:

My Projects (Portal View)

CVP Implementation In Progress โ€ข 45%
Current focus: Detroit Foundation Build
Next session: Wednesday implementation check-in

She wasn't guessing what was happening with her transformation. The Project gave her continuous visibility into planned work progress.


What It Holds

Project Identity

Name, type, description. What is this Project about? Customer transformation? Internal initiative? Process improvement?

Scope and Objectives

What are we trying to accomplish? Project scope defines boundaries; objectives define success criteria.

Timeline and Phases

When does this Project start and end? What phases does it move through? For trust-based milestones: Foundation โ†’ Capability โ†’ Multiplication.

Team and Roles

Who is involved? Project owner, contributors, stakeholders, customer participants. Clear roles enable accountability.

Status and Health

On Track, At Risk, Blocked. Project health indicates whether we're progressing as expected.

Progress Tracking

Percentage complete, milestones achieved, deliverables completed. Progress visibility enables management and customer communication.

Commercial Context

Which Deal/Order originated this Project? What budget governs it? Commercial association enables scope and resource management.

What It Connects To

Primary Associations

To Company

The organization this Project serves (for client Projects)

To Contacts

Team members, stakeholders, participants

To Deals

Commercial opportunity that originated the Project

To Orders

Transaction that funded the Project

To Services

Ongoing service relationships (Project may be part of Service delivery)

To Deliverables

Specific outputs the Project produces

To Appointments

Sessions within the Project (check-ins, workshops, reviews)

To Tickets

Support requests that arise during Project (reactive needs)

Project-to-Contact Labels

Sponsor
1

Customer decision-maker for the Project

Project Lead
1

Internal owner responsible for delivery

Technical Lead
1

Technical authority for Project decisions

Participant
โˆž

Active contributor to Project work

Stakeholder
โˆž

Visibility/input but not hands-on

Site Lead
โˆž

Responsible for specific site (multi-location)

Project-to-Object Labels

Primary Company
1

Organization the Project serves

Source Deal
1

Commercial opportunity that originated Project

Source Order
1

Transaction that funded Project

Project Deliverables
โˆž

Specific outputs produced

Project Appointments
โˆž

Sessions within Project

Related Tickets
โˆž

Support requests during Project


Common Patterns

The Order โ†’ Project Pattern

Commercial commitment triggers Project:
Order created (for project-type Product) โ†’ Project created โ†’ Associated to Order, Company, Contacts โ†’ Deliverables created within Project โ†’ Project kickoff scheduled โ†’ Work begins

The Deliverable Generation Pattern

Projects produce Deliverables:
Project scoped โ†’ Deliverables defined (each with own owner, pipeline, timeline) โ†’ Deliverables report progress to Project โ†’ Project completion = All Deliverables complete

The Phase Progression Pattern

Projects move through trust-based phases:
Discovery โ†’ Foundation โ†’ Capability โ†’ Optimization โ†’ Multiplication

Phase transitions may trigger: billing milestones, team adjustments, stakeholder communication, scope reviews.

The Multi-Location Pattern

For customers with multiple sites:
Option 1 (Same scope, different locations): Master Project with Deliverables per location
Option 2 (Different scope per location): Master Project with Child Projects

The Project โ†’ Service Handoff Pattern

Project work transitions to ongoing support:
Project complete โ†’ Service activated (ongoing support period) โ†’ Project status: Complete โ†’ Relationship continues via Service

Value-First vs. Industrial-Age

โœ— Traditional Thinking โœ“ Value-First Thinking
Projects driven by calendar deadlines Projects driven by trust-based milestones
Progress = Tasks completed Progress = Value delivered
Project success = On time, on budget Project success = Outcomes achieved
Project visibility internal only Project visibility includes customer
Projects end at delivery Projects end at capability transfer
Phase gates = Approvals Phase gates = Readiness indicators

Why This Shift Matters

When Projects are calendar-driven, arbitrary deadlines create artificial pressure. Work gets rushed to hit dates rather than achieve outcomes. Quality suffers. Trust erodes.

When Projects are milestone-driven, progress reflects reality. Foundation phase is complete when the foundation actually works โ€” not when the calendar says it should. Phases advance when readiness indicators show genuine progression. The Project serves the outcome, not the schedule.


In Practice

Implementation details and configuration

What You'll See in HubSpot

Projects appear under CRM โ†’ Projects (once activated). Each Project has:

  • Left sidebar: Project properties, status, dates, owner
  • Middle column: Activity timeline, associated Tasks
  • Right sidebar: Associations to Company, Contacts, Deals, Tickets

View Options

  • Table view: List of Projects with filterable columns
  • Board view: Kanban-style pipeline visualization
  • Gantt view (beta): Timeline visualization with Tasks

Activating Projects

  1. Navigate to Settings โ†’ Data Management โ†’ Objects โ†’ Object Library
  2. Toggle on Projects
  3. For Gantt view: Settings โ†’ Product Updates โ†’ Enable "Project Object with Gantt Chart View" beta

Key Properties

Key Properties

Native HubSpot Properties

Property Type Purpose
hs_project_name Native Text Project identifier
hs_project_status Native Enumeration Not Started, In Progress, Complete, On Hold
hs_pipeline Native Pipeline Project type
hs_pipeline_stage Native Stage Current phase
hs_start_date Native Date When Project begins
hs_target_due_date Native Date Target completion
hs_target_duration Native Number Expected duration
hubspot_owner_id Native User Project owner

Value-First Custom Properties

Property Type Purpose
vf_project_type Enumeration Client Transformation, Internal Initiative, Product Development
vf_trust_phase Enumeration Foundation, Capability, Multiplication
vf_health_status Enumeration On Track, At Risk, Blocked
vf_percent_complete Number Overall progress percentage
vf_budget_total Currency Allocated budget
vf_budget_consumed Currency Spent to date
vf_breakthrough_log Rich Text Key transformation moments captured
vf_blockers Text Current impediments
vf_next_milestone Text What comes next

Client Transformation Pipeline

1

Discovery

Research and scoping

Entry Criteria

Understanding current state and goals

Exit Criteria

Mutual understanding established

Portal Experience

In the My Value Path Portal, Sarah sees her Projects:

My Projects

  • Each active Project with phase, progress, health
  • Current milestone and next steps
  • Quick access to Project details

Project Detail

  • Full Deliverable list with status
  • Timeline and milestone history
  • Team members and roles
  • Recent activity and updates
  • Upcoming Appointments
  • Related Tickets

"The Transparency Principle: Sarah doesn't wonder 'what's happening with our implementation?' The Project gives her continuous visibility into planned work, progress, and what comes next."

Workflow Examples

Project Creation Workflow

WHEN Order created AND Order includes project-type Product
THEN:
โ€ข Create Project
โ€ข Set Project.type based on Product
โ€ข Associate to Order, Company, Contacts
โ€ข Create initial Deliverables based on scope
โ€ข Schedule kickoff Appointment

Phase Progression Workflow

WHEN all Deliverables in current phase = "Complete"
THEN:
โ€ข Prompt for phase advancement review
โ€ข If approved: Advance Project.phase
โ€ข Trigger billing milestone if applicable
โ€ข Notify stakeholders of phase transition

Health Monitoring Workflow

WHEN Project.deliverable has status = "Blocked" for > 5 days
OR Project.last_activity > 14 days ago
THEN:
โ€ข Update Project.health = "At Risk"
โ€ข Notify Project owner
โ€ข Create escalation task

See It In Action

Experience in the Value Path Simulator

โ†’ Project Dashboard: See Sarah's CVP Implementation with phase, progress, and health
โ†’ Deliverable Progress: Watch Deliverables complete and Project progress update
โ†’ Phase Transition: See Foundation complete and Capability phase begin
โ†’ Project vs. Ticket: Notice how Projects organize planned work while Tickets handle unexpected needs

Key Moment: Notice how Projects organize planned work with clear scope, while Tickets handle unexpected needs. The separation enables both proper project management and accurate support metrics.

Experience Project in the Value Path Simulator


Explore Further