0:14 Welcome to another event of the HubSpot
0:17 Admins Hug. Um, we're here every Tuesday
0:18 at this time. Uh, great to have you
0:22 here. Uh, this is our homepage. This is
0:24 your source of truth for all of our
0:26 weekly events. Uh, be sure to bookmark
0:27 this, keep an eye on it, especially as
0:29 we're heading into the new year. um make
0:31 sure this is this is a part of your plan
0:34 for 2026. You are here. We've got Mark
0:35 with us. He's going to talk about the
0:37 new projects object inside of HubSpot.
0:39 Very excited for that. Uh next week will
0:42 be our last uh session for the year. Uh
0:43 we're going to do a little bit of admin
0:45 networking. And before that, uh Diana
0:47 and I will give some awards to various
0:49 people and do a readout of some of the
0:51 stats, just interesting fun facts about
0:53 what the uh what the admin hug has been
0:55 like in 2025. So encourage you all to
0:58 come uh see if your name gets read on on
1:00 a slide of fame or something. We have a
1:01 couple weeks we're taking off for the
1:03 end of the year. Uh and then January
1:05 we've got booked already. We're going to
1:08 talk about uh HubSpot AI connectors.
1:10 Going to dive deep in help desk. Talk
1:12 about the new flexible CRM views. Very
1:14 exciting. And then this goodbye data
1:15 gaps. The team that works on HubSpot's
1:17 data model tools. So the data model
1:19 overview, data model builder, um
1:21 properties, all that stuff is going to
1:22 talk about how they're they're closing
1:24 the gaps of how different objects have
1:25 had different functionalities and
1:26 they're we're getting to parody. It's
1:28 very exciting. Uh so keep an eye on this
1:30 page to know what's coming. Uh this is
1:32 our YouTube channel where you can find
1:34 recordings of our previous sessions.
1:36 We've this one I guess will make 180.
1:39 Very exciting milestone. Um so if you
1:41 ever want to rewatch or if you miss a
1:42 session or if you want to share it with
1:43 someone, uh this is your best place to
1:47 do that. Um, we have showand tells
1:48 occasionally. We are going to schedule
1:50 one probably for February. We'll let you
1:52 know when that date is fixed. Uh, we
1:54 still have room in that one and we are
1:55 going to do these regularly throughout
1:57 2026. So, if you ever build anything
2:00 you're proud of, if you ever uh crack a
2:03 puzzle inside of HubSpot, puzzles aren't
2:05 cracked. Solve a puzzle. Uh, let us
2:08 know. Fill out this uh this form and uh
2:10 we would love to have you share that
2:11 with with everyone else here so we can
2:12 all learn from each other. These are
2:14 some of the best events we run in my
2:16 opinion and we really want to have them
2:18 happen quarterly in 2026. So that's the
2:20 goal. Um we have a space on HubSpot
2:22 community if you want a forum experience
2:24 you can do that. Uh we also have a group
2:27 on uh LinkedIn and a a company page
2:29 also. So you follow that uh connect with
2:32 with people here. Um and then if you
2:35 ever have suggestions for uh an upcoming
2:37 hug we are here every week. We love your
2:38 suggestions. We want to make sure the
2:40 content we're providing is as valuable
2:42 and relevant as possible. You can fill
2:43 out this form or you can always just
2:45 reach out to me or Diana directly. We're
2:47 very active on LinkedIn and we'd love to
2:48 hear from you. Um and then if you want
2:51 to see any of these links I just shared
2:53 and and several others, uh Diana's put
2:54 together this little resource page where
2:56 you can see everything uh on a single
3:00 spot. So that's all from me. Uh two
3:01 minutes of housekeeping, not bad. Mark
3:10 >> Oh wait, hold on. You got to unmute yourself.
3:10 yourself.
3:12 >> There we go. unmuted. There we go.
3:13 Everyone can see this? >> Yep.
3:15 >> Yep.
3:17 >> Perfect. Hey everyone, my name is Mark.
3:18 I work on the product management team at
3:20 HubSpot. I'm excited to talk to you more
3:23 about the project object today. So, just
3:25 to get started, I can start by I'll
3:27 introduce myself a little bit. I've been
3:29 at HubSpot for a little over two years.
3:31 I've worked on two other teams before
3:33 projects. So, I started out working on
3:35 permissions. Then I was working on uh
3:37 multi-count management and brands. And
3:39 for those that aren't aware, multi-count
3:41 management is a set of features that
3:42 help some of our our larger customers
3:44 with complex organizations to use
3:47 separate HubSpot accounts. And now I'm
3:48 working on projects. So, it's actually
3:50 only been a few months, probably about
3:51 three or four months since I started
3:53 working on projects. And actually,
3:54 HubSpot itself hasn't really been
3:55 thinking about projects for for too
3:58 long, uh, too much longer than that.
4:01 Some fun facts about me. I have a
4:03 one-year-old daughter. I live in San
4:05 Diego. And some of my favorite things
4:07 when I have any free time outside of
4:09 parenting, working, I like to do yoga
4:12 and I I love to cook. All right, so
4:15 let's uh get moving. For some context,
4:17 for those that aren't aware, HubSpot
4:20 launched the project object at Inbound
4:23 of 2025. Inbound was in September of
4:25 this past year and is HubSpot's large
4:27 one of our our large events where uh
4:29 this is the Inerson conference where we
4:31 announced some of our our major project
4:33 uh announcements. So when we launched
4:35 the project object that was paired with
4:38 a new Gant view type uh as well and just
4:40 to define some things for people that
4:41 aren't as familiar with everything with
4:44 HubSpot we say project object because
4:46 basically HubSpot has these different
4:48 data objects that you store data uh
4:50 within the platform. So for example
4:52 contacts, companies, deals, those are
4:54 some of the classic objects that HubSpot
4:57 has that refers to them being on what we
4:59 call the HubSpot framework. And what we
5:00 try to do is then have a consistent
5:02 experience with a lot of outof-the-box
5:03 capabilities which I'll show some of
5:05 them for projects that come with being
5:08 an object within HubSpot. And when I
5:10 talk about the Gant view type, what I'm
5:12 referring to on the screen here next to
5:14 this search bar, there's this dropdown
5:16 where you can view the data that you're
5:18 seeing in different ways. So for a
5:21 while, HubSpot's main view type was a
5:23 table. And as part of the recent launch,
5:25 we've incorporated a Gant view, which is
5:27 obviously an important capability when
5:30 it comes to project management.
5:33 So before I go too much into demoing the
5:35 feature or talk about the road map, I
5:36 wanted to just talk a little bit more
5:38 around what are the use cases that we've
5:39 been seeing from customers as they start
5:41 to do project management within HubSpot
5:43 and then why have we been seeing that
5:44 customers want to do project management
5:47 within HubSpot. So we've seen three main
5:50 use cases for project management. The
5:52 first is service delivery. The second is
5:53 marketing campaign project management.
5:55 And the third is around sales and
5:57 account management. And the theme that
5:59 you'll see that carries through all of
6:02 these is that it relates to project
6:04 management for gotomarket teams, which
6:06 isn't too surprising because HubSpot's
6:08 main users are go to market users across
6:11 sales, service, and marketing. And they
6:12 have project management needs that it
6:14 makes sense that they would want to do
6:16 within HubSpot. So let me just go
6:18 through these each one by one. Service
6:20 delivery has been the most common use
6:21 case that we've been seeing from
6:23 customers for project management. And I
6:25 break this down into three
6:27 subcategories. So the first is software
6:29 onboarding. The second is professional
6:32 services. So shout out to all the I saw
6:33 some solution partners on the call uh
6:35 who have been really great at giving us
6:37 feedback on projects. And the third is
6:39 around physical good and production and
6:43 delivery. And I put a fun fact here. So
6:45 we look at who what seats seat types
6:47 that that customers have who are using
6:50 projects and about 50% of the active
6:52 users of HubSpot have a service seat. So
6:53 this has been the most common use case
6:54 that we've been seeing and I'll talk a
6:56 little bit more around why that's so
6:59 common. The second is around marketing
7:01 campaign project management. So
7:03 campaigns and the new marketing studio
7:05 today offer tasks but they fall short in
7:07 true project management. And what we've
7:08 been hearing is that customers want to
7:10 have a more complete campaign project
7:13 management software within HubSpot.
7:16 The third category is sales and account
7:17 management. And this has been a couple
7:19 of different types of sub use cases. So
7:20 when it comes to sales, we've been
7:22 seeing some businesses that want to have
7:24 a more structured container for tasks
7:26 for their sales process. So for example,
7:28 like an enterprise sales motion where
7:29 you have a group of people who are
7:31 involved. You might have a task for
7:33 getting an executive involved, a task
7:35 for creating a PowerPoint, etc. And the
7:37 second is around account plans. So say
7:39 you're an account manager in thinking
7:41 about an account and you're coming up
7:43 with what's the goal for this account
7:45 for next year and one of those goals
7:46 might be let's up we want to try to
7:49 upsell this customer to a new tier or we
7:51 want to cross-ell them to a separate
7:53 product. Those have a collection of
7:54 tasks that you want to track progress on
7:56 and we've seen some customers want to
7:58 use those projects. A lot of this
8:00 relates to how can a project be
8:01 associated to some of the other objects
8:05 that exist within HubSpot for context.
8:07 So now let's go why use projects. Now it
8:10 varies a little bit by the use case but
8:11 there have been three main themes that
8:13 we're hearing around what are the
8:14 benefits of bringing these types of use
8:16 cases into HubSpot for project
8:20 management. The first is customer data
8:22 and that is that HubSpot has the context
8:25 on your customer inside of the platform.
8:26 This is really relevant particularly for
8:28 a service delivery, a sales, account
8:30 management use case where you're
8:32 creating projects that relate to the
8:34 associated CRM data. So for example, if
8:36 we think about service delivery, when
8:38 you're creating a project for onboarding
8:40 a customer or delivering a service,
8:42 there's some really useful context that
8:44 exists on the deal that can help figure
8:46 out what are the right tasks for that project.
8:47 project.
8:49 The second is having the complete lead
8:52 to revenue journey within HubSpot from a
8:55 both a ease of collaboration and use
8:56 ability and the other is from a
8:58 reporting perspective. We've
8:59 consistently heard from customers that
9:01 they're doing their marketing in
9:02 HubSpot, they're doing their sales
9:04 process in HubSpot and that they're
9:06 frustrated that once the deal closes,
9:08 they have to move away into another
9:09 software to manage that onboarding
9:11 process. Now you can do that endto-end
9:13 process in one place. And now you can do
9:15 reporting that thinks about what's the
9:16 complete revenue reporting of this
9:18 entire journey.
9:20 And the final one is around planning and
9:22 executing in one place. This is
9:24 particularly relevant on the marketing
9:25 campaign side. So we've heard from
9:28 customers is that they come to HubSpot's
9:30 marketing hub. They're planning, they're
9:32 creating their assets, they're running
9:33 their campaigns, they're doing their
9:35 reporting, but a lot of the times when
9:37 it comes to creating the assets for a
9:38 campaign, there's different people
9:41 involved. It takes time. There's these
9:42 planning process to doing that and
9:44 there's a planning process to running a
9:45 campaign. You have to go speak to
9:46 finance and figure out the budget for
9:48 your campaign, etc. And what's happening
9:50 is that none of that could be really
9:51 tracked effectively within HubSpot. And
9:53 so we were hearing from customers that
9:55 they have to log into HubSpot to do that
9:57 to do some of their campaign work. Then
9:58 they log into another software to do
10:00 some of their planning process. And they
10:02 really just want to do it all within one place.
10:03 place.
10:05 So those are the top three reasons that
10:07 we're seeing from customers for why they
10:09 want to use projects inside of HubSpot.
10:11 I think one thing that I would call out
10:13 that you would explicitly see that we're
10:16 not focused on. So we're focused on how
10:18 can we help these existing go-to market
10:21 teams do their job processes better
10:24 within HubSpot. What we are not really
10:26 focused on is for example take myself.
10:29 I'm a product manager. I do project
10:30 management for my roadmap for the
10:32 features that we build. And we're not
10:34 really saying that I'm a target persona
10:37 to come into HubSpot. That may change in
10:38 the future, but for the time being,
10:40 we're really focused on how can we take
10:42 the existing types of users for HubSpot
10:45 and provide them more value.
10:48 So now let's do a demo of how projects
10:50 works within HubSpot.
10:53 So to start out what I'll just share
10:56 with you all to start is that when you
10:58 first want to use projects you have to
11:00 come to the data model
11:02 which is a feature that allows you to
11:05 turn on and off objects within HubSpot.
11:08 So we'll go to edit the data model and
11:10 within it you can see that I have here
11:12 that projects is already activated but
11:13 if you hadn't yet turned on projects you
11:16 would see a little box a card here where
11:18 you have to click activate the object.
11:20 This is and and just for context,
11:22 projects is available to all customers
11:24 on all plans. So, everyone is able to do
11:27 this. Now, once you activate the object,
11:29 projects will appear in the CRM section
11:32 of the navigation. This is what we call
11:34 a project index page. And this is where
11:36 you'll see the projects that you create.
11:38 It follows similar patterns to contacts,
11:40 companies, deals, etc. So, hopefully
11:41 people are familiar with it. You can see
11:43 the different view types here. So a
11:45 table view is a pretty classic
11:47 experience that customers have for
11:50 managing objects within HubSpot. But now
11:52 new with the uh release of projects is
11:55 the Gant view. Uh for context, the Gant
11:58 view requires you to have a starter plan
12:00 at least. So once you actually create a
12:02 project, we'll click into these are all
12:04 just fake projects that I have. You'll
12:06 be taken into the project record.
12:08 Something that we recently released
12:10 about a month ago as a follow-up is this
12:12 task card. We felt that viewing tasks
12:14 within the activity section, which is
12:16 another way that you can view act tasks
12:18 within a project, wasn't quite as
12:20 effective or front and center. So, we
12:22 created this task card that shows the
12:24 task really right in front of you. You
12:26 can expand here to manage some of the
12:28 associations between the project and
12:31 other CRM data. Just to show some of the
12:33 other platform concepts that come with
12:36 having a new CRM object, there is now a
12:38 settings page. So to access that you
12:41 come to settings you scroll down to
12:44 objects you click on projects and what
12:46 you'll see here is here you can get
12:48 access to then go manage the project
12:49 properties. So projects have both
12:51 default properties as well as custom
12:54 properties. So you are now in the pro
12:55 properties page where you can click
12:56 create property and that's a standard
12:59 custom property. We also have the
13:01 ability to have pipelines here for
13:04 context. So what with pipelines what the
13:05 idea here is is that if you have
13:08 different types of use cases for
13:10 projects. So for example say you have a
13:12 project for service delivery another set
13:14 of use cases of projects for marketing
13:17 campaigns. You might want to adjust what
13:19 the processes for that project which you
13:23 can do with different pipelines.
13:25 Next moving along projects now also
13:28 exists within workflows. So if you come
13:30 to create a workflow to give two
13:32 different types of examples, one of them
13:34 that you can do is to have a workflow
13:37 that triggers off of a project. So when
13:39 a project is created, you could then do
13:41 things on top of that. So right now we
13:43 don't yet have project templates, which
13:44 is something that we're investing in
13:45 where you would have the ability to
13:47 automatically create a set of tasks when
13:49 a project's created. But in the short
13:51 term, you could use workflows to be able
13:54 to, for example, create a set of tasks
13:56 every time a workflow a project is
13:59 created. Another good use case for using
14:02 workflows is from a service delivery
14:05 perspective. Every time a deal is closed one,
14:07 one,
14:09 let's just
14:12 try to do this. If I could do this
14:15 quickly. So we want to do deal deal properties
14:18 properties
14:21 is closed one is equal to true. So now
14:23 what this is going to do is have a
14:26 workflow where every time a deal
14:28 is closed one we then want to create a
14:30 new corresponding project. So you can
14:33 see that we have actions like create
14:35 record. We also have another one for
14:38 that is around editing a record but in
14:41 this case we would be creating a record
14:44 for creating a project.
14:46 Now right now it's just creating a
14:47 project. It's not then creating the
14:49 associate tasks. You could do subsequent
14:52 actions to create tasks over time, which
14:53 I'll speak about a little bit more
14:54 later. We're going to have the ability
14:55 to have project templates where this can
14:57 be a simpler process to create the right
14:59 set of tasks when you create a project.
15:01 So this is how workflows works with
15:03 projects. And finally, we'll pop over to
15:06 reports. So projects is now an object
15:08 that's available in both single object
15:10 reports and custom reports that follow a
15:12 similar patterns to every other object
15:14 in HubSpot. So if you come to create a
15:23 projects are available here. So a lot of
15:24 customers what they'll do is they'll
15:27 take projects they'll join it with tasks
15:30 and then create reports on top of that.
15:31 I won't go through the process of
15:33 showing you all the reports but you you
15:36 can get the idea.
15:38 All right. So this is how projects is
15:40 currently existing within HubSpot.
15:42 Everyone is welcome to use it. It
15:43 functions really similar to other other
15:45 objects like contacts, companies and
15:47 deals. Hopefully it's not intimidating
15:48 for people and you all I would encourage
15:50 you all to get started and to just try
15:53 it out. Now let's go in and talk a
15:56 little bit more about the roadmap.
15:59 So where we're heading is that we are
16:01 really focused on the top two use cases
16:04 that we've heard from customers. The
16:06 first is service delivery and the second
16:08 is marketing campaign project
16:10 management. And in order for us to
16:12 effectively solve for those two use
16:14 cases, we're investing in two categories
16:17 of improvements. And you'll have to
16:19 excuse me. I'm going to walk upstairs. I
16:21 was trying to uh be quiet while my
16:23 daughter was asleep upstairs. So, give
16:25 me a second while I move up to my my
16:28 desk upstairs. Some live parenting and
16:31 remote work environment.
16:33 Cool. So, just to keep talking. So the
16:34 two categories of improvements that
16:37 we're investing in are core capabilities
16:40 and core experiences. So to speak to
16:41 core capabilities, that's really the
16:43 biggest area that we have to do better
16:45 in. So for those of you who have tried
16:47 out projects since it was launched at
16:49 inbound, I think what your experience
16:50 will be, which is what we've
16:52 consistently heard, is that customers
16:53 are excited to bring projects into
16:56 HubSpot, but that we're missing a lot of
16:57 core project management capabilities
16:59 that are required for them to be willing
17:02 to do so. So, I'm going to go through
17:04 some of these we have designs for. So,
17:05 I'm going to show you what some of those
17:07 designs look like. Others we won't. I'm
17:09 happy in the Q&A to speak to any
17:11 timelines, any ideas that we have of the
17:13 requirements, etc. for these features.
17:15 So, for core capabilities, the first is subtasks.
17:17 subtasks.
17:20 The second are task dependencies.
17:22 The third are project templates so that
17:23 when you create a project, it
17:24 automatically creates an associated set
17:28 of tasks. The fourth is status updates.
17:30 So you can post a an update for what's
17:32 going on with your project. You could
17:35 notify your other HubSpot users. You
17:37 could send an email to c to customers if
17:38 you're doing a service delivery use
17:41 case. The next is custom properties for
17:43 tasks. So just to make sure that that's
17:45 clear. Right now projects have default
17:48 and custom properties, but tasks only
17:50 have default properties. There's no
17:52 ability to have a custom property for a
17:55 task. So just to give my own use case, I
17:57 use hub projects for my own product
17:59 planning just to use the product myself.
18:02 I can't put a custom property on a task
18:04 like which engineer is responsible for
18:07 that task in addition to saying like I'm
18:08 running a project but I want to say who
18:10 is the designer for this who is the
18:12 engineer and and we can't define those
18:15 things. Well today the next is projects
18:17 in the customer portal. So this is
18:19 really relevant for a service delivery
18:21 use case. So right now when how how
18:23 projects works is it's really just
18:25 inside of your HubSpot account. So you
18:27 create a project, you have tasks that
18:29 you can only assign to HubSpot users.
18:32 And this isn't really good enough for a
18:33 service delivery use case. When it comes
18:35 to service delivery, you need to be able
18:38 to share a project externally with the
18:40 customer that you're working with and be
18:42 able to assign certain tasks to be
18:44 completed by those customers or clients.
18:46 So, what we're doing is we're
18:47 collaborating with HubSpot's customer
18:49 portal concept so that for every
18:51 customer, you can have a unique URL
18:53 where they will be able to log into that
18:56 URL and see a project and certain tasks
18:57 that are assigned to them, complete
18:59 those tasks that doesn't require them to
19:03 be invited to your own HubSpot account.
19:05 Next, we have time tracking, which is
19:06 which will allow you to track the
19:09 estimated and actual time for tasks and
19:11 have that roll up to the project level.
19:13 And then finally for core capabilities
19:15 is a workload view so that you'll be
19:17 able to visualize across your users
19:20 within HubSpot what is the work that's
19:21 assigned to them relative to their
19:23 capacity and are they at their
19:24 allocation or not. So these are all the
19:26 core capabilities and when it comes to
19:28 the core experiences what we're saying
19:30 is what I demoed for you was that
19:32 projects exists within the project
19:34 navigation section.
19:36 What we want to do for the two use cases
19:38 is also bring projects into the
19:40 contextual experiences that these users
19:42 have when they use marketing hub and
19:45 service hub. So for projects being in
19:46 the CS workspace, this was actually
19:48 something that I could I didn't demo but
19:50 I can jump in and just show you quickly
19:51 actually that would be good to call out.
19:53 This is actually already live in our
19:55 production environments right now. So if
19:58 you come over to the CS workspace, you
20:01 can now see that projects,
20:02 let's hide this. Projects is now
20:04 actually a tab within the customer
20:06 success workspace and is the default
20:09 recommended object for customer success
20:11 uh when it comes to onboarding. So we're
20:13 expecting that for many customer success
20:15 and onboarding professionals, they will
20:16 live out of this customer success
20:18 workspace and it's important that
20:19 projects integrates into here effectively.
20:21 effectively.
20:23 The other one that is listed here is
20:25 marketing studio. So, for those that
20:27 aren't familiar, Marketing Studio is a
20:30 redesigned new version of campaigns
20:32 within HubSpot. And we are working to
20:34 bring projects into that experience for
20:36 customers that wanted to take their
20:38 project management to the next level
20:40 within marketing within marketing studio.
20:41 studio.
20:43 Okay, only five minutes or so more. I
20:44 just want to show you some screenshots
20:46 and some details of things that I do
20:48 have available. So, what you're seeing
20:50 here is Subtask, which we're building
20:52 right now. Subtask will be entering into
20:54 a beta in January. What you're seeing
20:57 here is in our Gant view, you'll have
20:59 the ability to create subtasks. And you
21:01 can see how there's this third level of
21:03 subtasks that are it goes projects,
21:06 tasks, and subtasks. You'll also be able
21:08 to create and edit subtasks within the
21:10 task creation in other places as well
21:12 over time.
21:14 Next, we have status updates. This is
21:16 also going to have a beta in January.
21:18 And you can see here we're creating a
21:19 new CRM card. This is what you're seeing
21:22 here is a project preview. They will the
21:23 project status card would also be
21:25 available within a project record and
21:27 you can see how a user has posted a
21:29 status update here. What I I'm not
21:30 showing the whole process. We are going
21:32 to allow you to manually enter a project
21:34 status update as well as have AI help
21:36 you generate it and have you review it.
21:38 You'll then also be able to share this
21:40 with external users such as uh your
21:43 customers as well as notify other people
21:44 within your company that are working on
21:47 this project.
21:49 Here you're seeing dependencies. We're
21:51 aiming for a beta for this in about
21:53 April of next year. What you're seeing
21:55 is that you can see these lines between
21:56 the different tasks, which is a pretty
21:59 standard way to visualize a dependency
22:00 between tasks as a drag and drop
22:02 environment. What this is saying is that
22:05 task A is blocking the work of task C.
22:08 You can see how this task is currently
22:09 blocked. This subtask is blocked. This
22:10 task is blocked. So these are some of
22:12 the ways that we're going to visualize
22:16 dependencies for our customers.
22:18 Next, we have templates. So, what you're
22:20 seeing here is within the settings page
22:21 of projects, we're going to have a new
22:23 tab for project templates where users
22:25 can create templates. And within that,
22:28 you'll be able to predefine tasks for a
22:30 given project template. So that when
22:31 that template is then used, either
22:33 manually or in a workflow, we will
22:36 autogenerate the set of tasks that you
22:38 would expect. These tasks will also have
22:40 a concept of a relative due date based
22:42 off of things like the project start
22:44 date. So with instead of having to enter
22:46 50 task due dates, you can just say,
22:49 "Oh, this task will will start about a
22:50 week after the project's created and
22:52 will finish two weeks after the project
22:53 created," which can automate some of
22:55 that uh work that you might have to do
22:58 to set up a new project.
23:00 This I just demoed uh so I won't go too
23:02 much more detail. Projects is now the
23:04 default object within the customer
23:06 success workspace instead of the service
23:08 object uh for customers to handle their
23:12 service delivery and onboarding process.
23:14 All right, that was everything that I
23:16 have to go through. I'm happy to go
23:19 through a Q&A process now with everyone
23:21 uh and answer any questions that I might
23:22 be able to.
23:25 >> Love it. Amazing. I imagine you were not
23:27 able to see the chat during that just
23:29 given the nature of a web- based
23:31 webinar, but mostly lots of love. People
23:34 are so excited about projects being here
23:36 and uh everything everything they want
23:40 is on your list for next year. So, uh
23:44 you you are all all all all your your
23:46 plans are validated by this particular
23:48 group. Um so, we're going to do Q&A now.
23:50 Uh hop over into that panel. Drop your
23:52 questions in. Look through the questions
23:54 quickly. Upvote the ones you most want
23:56 to hear about. We will go most upvoted
23:59 to least upvoted and uh get through as
24:01 many as we possibly can. Um I'll give
24:04 you like 10 seconds here, then I'll sort
24:07 it. Uh, I used to I used to promise a
24:10 minute and that I could never ever
24:12 [laughter] wait that long. Are you
24:14 telling me I can't even wait 10 seconds?
24:17 Oh, it's killing me. [laughter]
24:19 All right, most voted question with 13
24:21 up votes from Dale. We really need
24:23 subtasks and custom properties in both
24:25 tasks and subtasks to make it a viable
24:27 solution for us. Is there a timeline on
24:28 these pieces making it to the beta
24:32 environment? Well, Dale, yes. [laughter]
24:34 This question came in right at the
24:37 beginning 11:05. So I you just just
24:38 answered that. I don't know if there's
24:39 more color you want to add. We can move
24:40 on to the next one. [snorts]
24:43 >> Subtasks we are closer as I mentioned is
24:44 going to be ready in January. It's what
24:46 our team's working on right now. Custom
24:48 properties is something that we're still
24:50 figuring out a timeline. Uh and we're
24:52 hoping that custom properties we'd be at
24:53 some point in the first half of next
24:54 year, but we don't have a precise
24:56 timeline. When we have custom
24:58 properties, they would work on both
25:00 tasks and subtasks though.
25:03 >> Awesome. So will subtask like from like
25:05 a creation view and and and like with
25:06 task cues and that sort of thing will
25:08 they behave just like a normal task but
25:11 in the hierarchy of a project?
25:13 >> Yeah. So subtasks are a task. So for
25:14 people that are familiar with like our
25:16 object concepts as we were talking about
25:19 subtasks are a task object. So they will
25:21 be manifested in the product in a way
25:23 that's cohesive with how tasks work. And
25:25 I can actually just for the sake of a
25:27 live experience just show you something
25:30 that we're working on right now which is
25:32 uh just like help you understand that
25:35 concept a little better. Uh we right now
25:36 are currently building subtask and
25:38 you're seeing this within our test
25:40 environment. So what I just to help make
25:43 that clear when I edit this I'll add a
25:45 subtask here. So you can just see like I
25:47 didn't show this in this in the in the
25:49 PowerPoint, but you can see right here
25:50 there's now this subtask component
25:54 within editing a task
25:57 and we're going to save that. And what's
25:59 going to happen here is you can start to
26:01 see how there's this what we're doing is
26:03 we're starting to flatten the subtasks
26:04 into the task. So like when you see
26:06 tasks represented elsewhere in the
26:08 product with a list of tasks over time
26:10 you'll start to see this experience of
26:13 where they're sort of con consolidated
26:15 into the parent task that you're seeing
26:17 and we will be figuring out how these
26:18 elegantly get handled through things
26:21 like task cues as well over time.
26:24 >> Amazing. That's awesome. Um thanks for
26:27 showing that. Uh love to see something
26:30 in in in the building development
26:32 stages. Michelle asks, "Do you plan to
26:35 incorporate incorporate time tracking
26:36 into projects? We track projects by
26:38 hourly billing retainers, which also
26:40 function based on hours, either native
26:42 time tracking built in or integrations
26:44 with existing time tracking apps. We'd
26:46 of course want to take it a step further
26:48 and manage invoicing as well.
26:52 >> Got it. So, yes, we are. That is one of
26:54 the top projects that we're going to be
26:56 working on. And actually, uh, our
26:57 designer is currently working on how
26:59 time tracking will function within
27:01 HubSpot right now.
27:02 The general way that we're thinking
27:04 about this is that on the tasks there
27:07 will be an estimated time and an actual
27:10 time spent property. Those properties
27:12 can allow multiple time entries either
27:14 in the form of hours or minutes. And
27:16 then the idea is that that time would
27:19 then be rolled up at the project level.
27:20 And then what we're planning to do is to
27:22 pair that as I mentioned with a workload
27:24 view where you'll be able to say for a
27:28 given user what's the both count of
27:31 tasks the time that's being assigned to
27:33 that user over time. You can enter in
27:34 their capacity and then we'll be telling
27:37 you are they at capacity or not. In
27:39 general we agree with all of you that
27:41 this category of resource management is
27:44 equally critical to the core project
27:46 management use cases a as far as how it
27:48 connects into invoicing. So we actually
27:51 just built uh the enabled an association
27:54 between projects and line items. We are
27:56 very interested in figuring out how to
27:58 further the connection between projects
28:00 and billing. Like as we mentioned the
28:02 number one use case that we're solving
28:04 for is service delivery. So time tracking,
28:06 tracking,
28:09 resource allocation, the billing process
28:11 of those tasks, we understand how
28:12 important those are and are are looking
28:14 forward to to making them work really
28:18 well over the next year. That's amazing.
28:19 Um, and it makes a lot of sense because
28:21 HubSpot has that stuff in there already.
28:24 So, uh, Sarah also asked about time
28:26 tracking. Uh, you answered that. Lindsay
28:29 wants time tracking, so answered that.
28:31 Ally says, "Would like to be able to set
28:33 up recurring tasks. Is that something
28:35 you're thinking about?"
28:37 >> So, recurring tasks are a concept that
28:40 already exists within HubSpot. Um, so
28:42 today on a task, there's a button that
28:44 you can click that makes it a recurring
28:46 task. that concept still exists within
28:48 projects uh for when you're creating a
28:50 test. So I think that I would just say
28:52 like that feature already exists. I'd be
28:53 happy if you want to like email me and
28:54 share where it's working or not working
28:57 for you to hear more from you.
29:00 >> Great. Um Charlene says, "Can you
29:02 trigger transactional emails from
29:04 projects similar to tickets i.e. thank
29:08 you onboarding email to the client?" I
29:10 I
29:12 I think that's a one that I would say I
29:14 don't have the an exact off the top of
29:16 my head knowledge of exactly how
29:18 transition transactional emails work in
29:20 HubSpot. Conceptually, the use case that
29:21 you want to do is something that we want
29:24 to enable. So if it's not enabled
29:25 effectively, you should follow up with
29:26 me. Like I certainly know that you can
29:28 have a workflow triggered off of a
29:30 project that then has an action of a
29:33 marketing email, but I will admit I have
29:34 not studied transactional emails
29:36 specifically enough to say if there's
29:37 something else that's missing. Like you
29:39 can just to continue forward like you
29:42 could create contact lists of contacts
29:43 based off of the associated project
29:45 data. So I think the answer to this
29:47 should be yes, but if you run into any
29:49 challenges you can let me know.
29:53 >> Great. Uh Charlene asks, "Is the plan
29:55 with projects to compete with other PM
29:57 softwares like teamwork with the ability
29:59 to see team members capacity on
30:00 projects?" You mentioned capacity a
30:03 little bit in passing, I think.
30:06 >> Yes, we will provide capacity planning
30:08 capabilities. In terms of how we think
30:11 about our our competition with other
30:14 project management softwares, the way I
30:16 would personally think about it is that
30:18 there are benefits to doing certain use
30:20 cases within HubSpot without leaving
30:22 HubSpot. And there will be some
30:27 businesses that only need a certain
30:29 standard set of capabilities for project
30:32 management and they will find the value
30:34 in using HubSpot's projects for that
30:36 purpose and not having to use another
30:37 software. There will be other businesses
30:39 that have more advanced project
30:41 management capability needs that we are
30:43 not going to deliver upon. And the idea
30:45 is that we want to have both a native
30:48 solution and a birectional integration
30:50 with ma major project management
30:51 software. So there there's flexibility
30:53 for you to choose what the right option
30:55 is for you. So just to play that example
30:58 out, the marketing studio team is both
31:00 planning to offer native project
31:02 management through HubSpot as well as
31:03 having integrations with softwares like
31:06 Asauna, Monday, etc. So if you prefer to
31:07 do your project management outside of
31:09 HubSpot, you'll be able to do so as
31:11 well. I love that. And that that to me
31:13 just feels like classic HubSpot
31:15 technique, right? Like we have a meeting
31:17 scheduling tool. We also have an
31:19 integration with Calendarly, right? And
31:21 like uh if if our native solution gets
31:22 you where you need to go, great, use
31:23 that. There's a lot of advantages to
31:26 that. But if you uh need a point
31:28 solution that outfeatures us, we're not
31:29 offended and we want your data to to
31:33 flow through. So that's that's great. Um
31:36 Valerie says, "Additional template use
31:37 case developing a project template for
31:39 the business development and scoping
31:41 process, i.e. connect to task,
31:44 playbooks, etc. Template is helpful from
31:47 a repeatability standpoint."
31:49 That's not a question, but
31:50 >> more of a feedback. Yeah. >> Yeah.
31:51 >> Yeah.
31:53 >> Yeah. Well, I would just say templates
31:54 has been one of the top three or four
31:56 features that customers have been asking
31:58 us for. It's very understandable that
31:59 people have repeatable business
32:02 processes that they want to ensure are
32:04 both repeated by their users. Like a a
32:06 CSM director wants to ensure that their
32:08 CSMs follow a standard process for
32:11 onboarding a customer and it's just a
32:12 huge efficiency thing of needing to have
32:14 to recreate tasks every time you create
32:16 a project. So we very much understand
32:19 the importance of project templates. The
32:20 playbooks piece is not something that is
32:22 connected into it right now. It's more
32:23 so creating a project with the
32:25 associated tasks but uh we're it's
32:27 something we're working on actively and
32:29 really care about as well.
32:32 >> Yeah, that's really interesting. Um
32:34 because I know playbooks I'm trying to
32:37 do this quickly on the fly. Uh can
32:39 trigger certain you can insert assets uh
32:41 or actions. >> Um
32:48 yeah, there's a create a record action.
32:50 Looks like projects isn't currently in
32:51 the list. I wonder what it would take to
32:54 unlock that. That's really interesting.
32:54 >> All right. >> Yeah.
32:56 >> Yeah.
32:58 >> Um if I create a project, this is from
33:01 Janette. If I create a project and I
33:04 clone it as an almost template, can I
33:05 clone it as an almost template before
33:07 templates are released? >> Does
33:08 >> Does
33:10 >> that is a that is a good question. I
33:12 would need to test the cloning
33:13 functionality because what I'm not sure
33:15 about is when you clone a project, will
33:17 it also clone the associated tasks that
33:19 are part of the project or does it just
33:21 clone the property data of the project?
33:24 So, I'd say that's what I would go test.
33:25 With that said, I could see it being
33:28 frustrating to clone if you want to use
33:30 the templates of the task, but you don't
33:32 necessarily want all of the things that
33:33 are within the task from the previous
33:36 project to be cloned over. So, if it's
33:38 possible, it might not be a very great
33:40 experience to do it. What we've been
33:41 seeing more commonly as a workaround is
33:44 the use of workflows as the workaround
33:46 where basically when a new project is
33:48 created, you then have a process that
33:50 creates all the associated tasks that
33:52 you want. That is what I've been seeing
33:54 more commonly as the the workaround as
33:57 opposed to manual cloning.
34:00 >> Makes sense. Michael says, I think I saw
34:02 recently that the services object might
34:04 be going away in favor of project
34:06 object. Is that correct?
34:09 We are evaluating the overlap between
34:10 the project object and the service
34:13 object with the intent of trying to
34:17 reduce customer confusion over there are
34:19 different options that seem similar and
34:20 so how does a customer know which is the
34:23 right object for them to choose. We
34:26 believe that the project object is the more
34:28 more
34:30 extensible future direction for managing
34:33 work within HubSpot. So we are leaning
34:36 towards either renaming the service
34:38 object or deprecating the service object
34:41 we to be something that reduces customer
34:42 confusion. The renaming would be to make
34:45 it something more generic that's not
34:48 clearly project management oriented uh
34:51 or to deprecate and basically those are
34:52 the two options that we're evaluating.
34:54 We haven't really figured out exactly
34:56 which path we're going to go. What I
34:58 would share is that we are already
35:00 building features for the project object
35:03 that are not available on the service
35:06 object. So for example, if you I showed
35:08 you that task card that uh exists now
35:10 within the project object. It doesn't
35:11 exist within the service object. Some of
35:13 the features that we've been talking
35:15 about uh like subtask dependencies will
35:17 only initially be available for tasks
35:18 within the project object, although that
35:20 can change over time. And then things
35:22 like project templates are a templating
35:24 feature for projects, not for the
35:26 service object. Like in general, we are
35:27 not taking all the features we're
35:29 building and building them on both
35:30 objects with the intent of knowing that
35:33 we're trying to move away from the
35:35 service object being the object that's
35:36 used for service delivery in favor of
35:39 the project object. So my feedback to
35:42 you would be if you're currently using
35:44 the service object, you can think about
35:46 what is the path to switch over to the
35:49 project object over time without saying
35:51 like there's no immediate urgency that
35:53 says you're that there's like a specific
35:55 date where they won't be supported by
35:56 any means. It's more so if you want to
35:58 take advantage of what we're doing with
36:00 the project object, then you should
36:01 start to figure out how that fits into
36:03 your your administration plan of HubSpot.
36:04 HubSpot.
36:07 >> Yeah. And I'll add to that for a while
36:11 the the default in the CS workspace was
36:13 the services object and that tab was
36:14 called services. Now the default is
36:16 projects and it's called projects. But
36:20 if you have the CS workspace set up and
36:22 a services object connected there that
36:23 will not automatically change and you
36:25 can still select services as an option
36:28 for that page. Uh we are not at a phase
36:30 right now where any changes are being
36:32 forced upon you.
36:34 >> That's correct.
36:36 So, uh, it's important thing to keep in
36:38 mind. Anna says, "Can we start
36:40 associating marketing items such as
36:42 blogs and emails and sequences to a project?"
36:44 project?"
36:46 >> Today, you cannot, but what we are
36:49 currently evaluating right now is the
36:51 assoc is the ability to associate a
36:54 project to a campaign. As part of that,
36:55 we are going to figure we will have to
36:57 figure out do we want to be able to also
36:59 associate the project to individual
37:01 marketing assets. Uh, is something that
37:03 will be evaluated over time. But our
37:04 first step that we're going towards is
37:06 figuring out how to connect to campaigns.
37:08 campaigns.
37:09 >> Got it.
37:12 >> Uh Shell asks, "What does permissioning
37:14 look like? Our end users would be
37:15 expected to have more flexibility with
37:17 what project properties or project
37:19 related forms they can edit and create.
37:21 They cannot grant the same access to
37:23 other objects and tools inside of HubSpot.
37:25 HubSpot.
37:27 Today, the permissions for projects
37:30 functions the same as other CRM objects.
37:33 And just for people who I could just
37:35 quickly show it so everyone's aware of
37:37 how these things work.
37:39 >> So when you come into settings, if you
37:43 come to users and teams,
37:47 if I edit a user's permissions,
37:50 let's start from scratch.
37:58 you can see we have view, edit, and
38:01 delete permissions. These follow what's
38:03 called an ownershipbased permissions
38:05 model where for each action you can
38:07 either have that set to just their own
38:09 projects which is based off of the
38:11 project owner property as well as other
38:13 custom owner properties their team's
38:16 projects or all projects. So these are
38:18 how you determine access to projects.
38:21 It's worth noting that we also have a
38:23 separate set of permissions for tasks
38:24 that are worth calling out that have
38:27 already always existed for the past year
38:29 or so. So for tasks you can set
38:32 permissions to view and edit which are
38:33 similarly an ownerbased permissions
38:35 model. And then the last thing I just
38:37 want to mention is that we also support
38:39 what's called property level permissions
38:41 or controlling property access for
38:44 projects. So if you come to properties,
38:47 if we come to projects
38:49 for every property, you can determine
38:51 who are the users that can view or edit
38:58 >> Yep. So, um, Shell, I feel like implying
39:01 your question is, uh, you there may be
39:04 specific, uh, CRM objects you don't want
39:05 some of these users to have access to,
39:07 maybe deals or or something like that,
39:08 and those are those are managed
39:10 separately, and that is fine. Um, and
39:11 then one other thing I think we should
39:14 call out, the field level permissions,
39:15 is that enterprise feature?
39:17 >> Yeah, that that requires enterprise,
39:18 whereas the view, edit, and delete
39:20 permissions for projects is available
39:22 across all all plans. >> Great.
39:24 >> Great.
39:28 Uh Valerie asks, "I'm sure this question
39:30 is coming. Is a feature similar to the
39:33 legacy project template functionality
39:35 coming, i.e. customize a template to
39:37 your partner portal and deploy into
39:39 customer portals?" I am curious in
39:42 general the status of this legacy
39:44 projects tool, what its future is. Uh
39:46 and there are I think a lot of like
39:48 preconfigured templates in there just
39:51 like from HubSpot. Um,
39:53 >> yeah, maybe I'll share my screen because
39:55 this is kind of a a niche question that
39:57 a lot of people will not know what we're
39:58 talking about. [laughter]
40:02 >> That is true. Maybe not in this room.
40:04 >> Yeah, you all might be the expert users,
40:06 so you'll know everything. So, within
40:09 this dropdown, there's a feature called projects.
40:10 projects.
40:12 And when you come here, this looks
40:15 suspiciously a lot like the feature that
40:18 we are building. So this is what the
40:19 feature that we're talking about. There
40:21 are two use cases that we've heard for
40:24 what this old we'll call this the legacy
40:26 project feature. We've heard two use
40:28 cases. One is customers are using it for
40:29 actual project management which is like
40:31 heavily overlapping with the feature
40:33 that we just built. The other is that
40:36 they're using it to onboard we we are
40:39 using it ourselves to onboard projects
40:42 onboard customers into HubSpot.
40:44 And what we're planning to do here is
40:46 first it's confusing that there are two
40:48 features that have the same name. So we
40:50 are first planning to rename this
40:53 feature to not be called projects to be
40:54 something that makes a little bit of a
40:57 differentiated use case. We want to
41:00 encourage customers that are onboarding
41:02 their customers to use the projects
41:05 feature for project management.
41:07 for our own internal teams that are
41:10 using projects to onboard our customers
41:12 to HubSpot. We're going to migrate them
41:14 more towards what our internal teams
41:16 have built, which is something called
41:18 growth plans.
41:19 We are going to figure out there's a
41:21 different team that owns this feature
41:23 and we will figure out what to do more
41:30 >> Great. Fun fact, when I moved to the
41:32 HubSpot Academy team almost 10 years
41:35 ago, one of my first jobs was populating
41:37 the templates in that that that feature
41:39 had just released, uh, we had a whole
41:42 bunch of checklist things just like on
41:44 CMS pages and we were so excited to pull
41:46 them into this internal tool and we were
41:47 going to change the world and then
41:48 nobody ever discovered that tool
41:51 existed. So, [laughter] uh,
41:53 uh,
41:55 uh, when is projects and customer portal
41:58 coming? Jonathan would like to know
42:00 >> that is something that's an early idea
42:01 that we don't have a specific timeline
42:03 on. I would say the hope is that in the
42:06 second half of next year.
42:10 >> Great. Um we have another question about
42:12 capacity planning. Just letting you know
42:14 we've already addressed that. We have
42:16 another question about uh the difference
42:18 between the service object and project.
42:19 So these are questions that are going to
42:22 keep coming up.
42:24 And then we have another question.
42:25 Debbie is also asking about those
42:29 onboarding projects. Uh
42:32 so let's see uh
42:34 uh
42:36 Paul asked about permissions and and
42:39 limit views to projects based on owner.
42:40 So yes, that's definitely a thing you
42:44 showed that. Uh
42:46 will view only seats be able to see projects?
42:48 projects?
42:52 >> Yes. So how things work are that you
42:55 require a core seat to be able to create
42:58 or edit projects but you can with a view
43:00 only seat you can view projects and we
43:02 also tested this recently you can also
43:04 comment on tasks. So one use case we
43:06 heard was that you might be
43:07 collaborating with somebody in your
43:10 business on a project who's responsible
43:12 for a task but you might not want to pay
43:14 for them to have a core seat. So they
43:16 can comment on the task. They wouldn't
43:17 be able to mark a task complete. that
43:20 would require a core seat. But there are
43:22 some ways that you can think about when
43:23 you're collaborating on a project, who
43:25 needs a view only seat versus a core seat.
43:26 seat.
43:28 And just to know, just to like make sure
43:30 it's clear, the customer success
43:33 workspace requires a service seat. So
43:35 you can use projects in without a
43:37 service seat for a service delivery use
43:39 case, but if you want to take advantage
43:40 of the customer success workspace and
43:41 the corresponding features that are
43:43 available through service hub, that
43:45 would require a service seat. >> Great.
43:47 >> Great.
43:50 Um, thanks for clarifying that. Hamza
43:53 asks, "What type of work should be
43:55 tracked in a project versus a ticket
43:57 versus a task?"
43:59 Well, that's an interesting one. So, the
44:02 way I think about this is that I think a
44:05 ticket is meant to be a support type of issue.
44:06 issue.
44:10 I think that a project is meant to be a
44:13 set of work that is collab that has
44:15 multiple steps that's collaborated
44:18 across different individuals and has a
44:20 due date.
44:22 I think a task is a unit of work where
44:25 like the project is a container and a
44:28 task is a unit of work. Now, there is a
44:30 use case for just like a one-off task.
44:32 Like, for example, you might have a task
44:35 when you're working with a c with a
44:36 company that just says like send a
44:39 follow-up or like uh I don't know like
44:40 send an email, reach out to the
44:41 customer, see how they're doing or
44:43 something like that. That doesn't need
44:46 to be contained within a project. So, I
44:47 think it just depends on what is the
44:49 work that you're trying to manage to
44:51 figure out what is the right object for
44:54 you to use. We see you value in like a
44:56 defined onboarding process where
44:58 somebody purchases something. You're
45:00 trying to complete that work by a
45:02 certain date. It has steps like that's
45:03 something that belongs in a project with
45:05 associated tasks. You might just in your
45:07 regular course of work have a task where
45:09 you want to check in with a customer
45:10 that's unrelated to an onboarding
45:12 process. Maybe it's after onboarding is
45:13 complete. It's just the day-to-day work
45:16 of a CSM. That doesn't need to be a
45:18 project. It can just be a task that's
45:20 associated to say the company object.
45:22 And now a customer might write into you
45:24 saying we have an issue and that makes
45:26 sense to be represented as a ticket.
45:28 That's my personal opinion.
45:32 >> Makes sense to me. Uh
45:34 Corey says, "I think projects right now
45:36 is okay for small projects, but my
45:38 company does OKRs for team work plans
45:40 and individual work plans, which
45:42 requires specific task types,
45:44 milestones, projects, etc., and multiple
45:47 subtasks, sometimes up to 10, or we use
45:50 check sheets. Do you think projects will
45:51 ever get to that point? Also, instead of
45:54 pipelines having spaces or folders or
45:56 lists, again, multiple teams would want
45:58 to keep projects separate, but may have
46:00 different needs that wouldn't fit into
46:03 one project pipeline.
46:05 >> I would say yes, our intent is to mature
46:08 into that direction. As you saw from the
46:10 presentation earlier, a lot of the
46:12 capabilities that you're referencing
46:13 like subtasks are things that we're
46:15 working on. One of the ones that wasn't
46:16 included in the presentation that you
46:19 mentioned is milestones. Milestones is
46:20 is a capability that we view as
46:22 important. It's not in our next like
46:24 nine-month plan, but I would say it's on
46:26 like the 18month plan. So, we will get
46:28 to the point of also having milestones
46:31 over time. In G, we already have support
46:33 for different pipelines that you can
46:35 address those types of use cases. So, I
46:36 would say yes, in general, we're
46:38 building out the capabilities that you
46:40 would need to do these more complicated
46:42 projects. I think what we have to figure
46:44 out as a business of HubSpot is where we
46:46 draw the line of like what is the level
46:49 of complexity of a project that we will
46:51 accept to be managed in HubSpot versus
46:52 ones where we say like oh no you
46:54 probably should be using something like
46:56 a sauna. Uh like just to give it to like
46:58 talk that example through like we are
47:01 building subtasks with currently a
47:03 single level. So you can have tasks that
47:05 have subtasks. We also right now have a
47:09 limit of 30 subtasks for a parent task.
47:11 If you go to a software like uh ASA for
47:13 example like that you can have like five
47:16 levels of subtasks nested within them
47:18 and you could have hundreds or thousands
47:21 of subtasks. We are clearly not there
47:23 and the question is where how far we
47:24 will go is something that we're going to
47:26 have to evaluate over time. So certainly
47:28 like what you described should be a
47:30 standard sophistication of project
47:32 management that we want to get to but
47:34 there will be a certain point where we
47:36 won't be as sophisticated as other
47:38 softwares that exist.
47:40 Yeah, that makes sense. And as far as
47:42 having spaces or folders, Corey, uh,
47:44 some of the permissioning stuff I think
47:46 might get you there with, you know,
47:48 saved views and things and certainly the
47:51 CS workspace is even a a level
47:54 >> or a small step above that. Um,
47:56 >> we also have lists. You can also create
47:58 lists of projects if you want to.
47:59 >> That's great. [snorts]
48:00 >> Yeah, I was going to ask that because
48:03 she mentioned folders or lists. So, >> yeah,
48:04 >> yeah,
48:06 >> there you go. Uh, another
48:07 >> I agree. Through through permissions and
48:08 views, you should be able to achieve
48:10 that type of separation. >> Yeah,
48:12 >> Yeah,
48:18 Michelle again, is it possible to factor
48:20 working hours into reporting similar to
48:22 ticket SLAs's? How about adding working
48:25 hours to time between calculated properties?
48:27 properties?
48:29 >> I don't know about the last one, but
48:33 working hours. So I think the
48:36 how I have thought about it a little. So
48:38 okay so working hours like you're gonna
48:40 have a task that's assigned to a user
48:42 and I think the the question of working
48:44 hours comes into how we are assigning
48:47 work to individuals. So what we are
48:50 going to evaluate when we start to build
48:52 some of our resource management
48:54 capabilities, we are over time going to
48:57 figure out how do we ensure that users
48:59 who are assigned work have the time and
49:01 capacity to be able to achieve to
49:03 accomplish that work. So I think we
49:05 haven't totally figured out how that
49:06 will mature over time, but that yes,
49:09 things like out of office working hours,
49:12 your out your capacity for a given day,
49:13 and the amount of work you can do, all
49:15 that will will factor into us
49:17 determining whether you're actually able
49:18 to accomplish the work that's been
49:20 assigned to you.
49:23 >> Great. Jennifer asks, "Will we be able
49:25 to track budgets through projects in the future?"
49:27 future?"
49:29 >> That's a good question. We are like as
49:30 we've thought about some of the things
49:33 like time tracking uh we're trying to
49:35 figure out what default properties we
49:37 want to support
49:39 for now like this the earliest ones
49:40 we're thinking about you know like
49:42 estimated time actual time spent. We've
49:44 been debating whether we should have a
49:46 property on a project like allocated or
49:49 budgeted time for example. Uh that would
49:50 then bring up questions of like should
49:52 we start to have properties that relate
49:55 to costs and billing like should we have
49:57 like your hourly rate for example?
49:59 should we say whether the task is
50:01 billable or not. I think we're figuring
50:03 that out over time and it will continue
50:07 to evolve. Projects have the ability to
50:09 have custom properties. I think like the
50:10 general HubSpot philosophy would be like
50:12 we have default properties but you
50:14 should be able to customize the objects
50:16 with custom properties however you'd
50:18 like. In the short term that exists for
50:20 projects there are already custom
50:22 properties which I demoed. Tasks don't
50:23 yet have custom properties but it's
50:26 something we want to work on. So maybe
50:28 we will have default properties for
50:29 budget and things like that. We're still
50:31 figuring that out, but if we don't, we
50:33 should be supporting the ability to set
50:35 custom properties.
50:39 >> Great. Uh Melissa says, "How do we turn
50:40 on projects? I miss the steps in
50:42 HubSpot." Um I will share my screen real
50:44 quick just because I have a portal that
50:45 they're not turned on in, which I think
50:47 is valuable. So if you come to data
50:49 management, go to your data model. Um
50:51 this is you can see your data model
50:53 here. Uh there's this edit. Well, I'm
50:55 getting on boarded. Um, you can edit
50:57 your do data model. Projects will be
50:59 listed here in CRM objects and it'll
51:01 probably look like this for you and you
51:02 just click that activate object button
51:04 and confirm that you want to activate it
51:11 So,
51:13 uh, oh, it looks like Diana answered
51:18 that written also. Great. Uh,
51:20 will subtasks have custom properties as well?
51:21 well?
51:24 subtasks will have the same custom the
51:25 the custom properties will only be
51:28 configured at the task level uh like at
51:30 the task object level and they will just
51:32 carry forward into the subtask because
51:34 subtask and task parent tasks are the
51:37 same object. They're still task objects.
51:39 So basically once we enable you to
51:41 create a custom property for the for
51:44 tasks it will just be the same custom
51:45 property for both parent tasks and
51:49 subtasks. We decided to not have
51:51 separate custom prop basically we chose
51:54 not to have separate property schemas
51:56 between parent tasks and subtasks.
51:58 But I think what you're asking for is
51:59 like will we have custom properties for
52:01 subtasks? Yes, we will once they're made
52:03 available for parent tasks.
52:04 >> Yeah, that makes sense to me. So similar
52:06 to like parent and child companies, a
52:08 child company isn't a different kind of
52:10 object with different properties. It's
52:12 it's a relationship between two objects
52:13 of the same type.
52:15 >> Exactly. That was the the major
52:17 architecture decision that we thought
52:18 through when we were introducing
52:20 subtasks is whether we want them to be a
52:23 separate object or not from parent tasks
52:25 and we chose no. So instead the way we
52:28 would articulate that is that subtasks
52:30 are a same object association between
52:33 tasks meaning a subtask can only be
52:35 associated to its parent tasks and the
52:37 rest of the associations of how a task
52:39 relates to contacts etc is managed
52:42 through a parent task.
52:45 >> Great. Um, we are running short on time
52:46 here. We're going to fit in a couple
52:48 more. Uh,
52:50 >> oh, this is a feature request, not a
52:52 question. Uh, overall percentage
52:54 complete in the Gant bar as tasks are
52:56 being completed or at least an option to
52:58 customize between days or percent
53:00 complete or both.
53:02 >> Nice. That that makes sense.
53:05 >> Um, and then
53:08 will you be able to do subtask? How many
53:09 layers of subtasks? You mentioned this
53:11 for now. Just one, right? There there
53:14 can only be one level of subtask beneath
53:17 the tasks and our initial limit is 30
53:20 subtasks for a single parent task. We
53:22 are open to feedback as the features get
53:24 into beta of where that works or doesn't
53:27 work for customers and I would always
53:30 hub product team means that friends. So
53:32 um as these betas come available opt
53:34 into them there will be an option to
53:36 give feedback and that is that is so
53:38 helpful. It's you can you can opt in and
53:40 you can test it out and you can let them
53:42 know and that'll all be for for Mark and
53:44 his team just put in one repository.
53:46 They can see all the feedback aggregated
53:48 and pick up on the patterns of what
53:50 people are saying
53:51 >> and that's the best way to actually then
53:53 get a conversation too because we we get
53:55 we have a a Slack channel that whenever
53:57 you post those survey responses we
54:00 automatically see the survey and I
54:01 actively review that look at the
54:03 feedback and reach out to people to
54:05 schedule conversations to learn more.
54:06 So, if you have feedback on any of the
54:10 betas or projects, I'd love to hear it.
54:13 Great. Um, there is a long tale of
54:18 questions with one or zero up votes. Um,
54:21 and I'm just kind of glancing through a
54:23 lot of these we've already touched on. Um,
54:26 Um,
54:28 oh, any news about projects API? Do you
54:30 guys have any API?
54:32 >> Yeah, the project. So for for context
54:34 for the group when we launched at
54:36 inbound we did not yet have an API for
54:38 projects that has since been built is
54:41 available in uh our public API
54:45 documentation and so it's available now
54:47 [snorts] uh
54:51 great I think that is probably
54:53 sufficient I will export out the whole
54:55 Q&A and share it with Mark and his team
54:58 the chat also so you guys can dig into
55:00 this. Uh there's a lot of questions
55:04 here. We're just uh out of time. Uh so
55:06 thanks so much Mark for coming. If if
55:07 people want to follow up with you, your
55:09 team, what's what's the best way for
55:11 them to Diana has dropped your LinkedIn
55:14 into the chat. Is that is there anything
55:14 more than that?
55:16 >> I'll just also put my email address.
55:18 You're welcome to share any feedback
55:20 with me, questions you might have, and I
55:22 can try to help you out.
55:25 >> Amazing. Um well, thank you so much for
55:27 being here. Thanks everyone for coming.
55:28 Uh really excited about the projects
55:30 tools. So glad we were able to share it
55:33 with all of you. Um we will see you all
55:35 back next week for our last session of
55:36 the year. Please come. We'll have some
55:39 fun facts and stats to share. Then we'll
55:41 do some networking. And Mark, thanks so
55:42 much for being here.
55:43 >> Thanks Mark.
55:44 >> Thanks for having me.
55:46 >> Bye friends. See you next week. [music]
55:52 to the admin. No flash of facts and a
55:56 whole lot of love. We get it done
55:59 or all in choice. [music]
56:04 Add spies and lift their voice.
56:08 Fixing fields [music] and hacking time.
56:11 Making magic with no headline. [music]
56:13 [music]
56:15 Tiana brings fire in a crew that's here
56:17 to lift you higher. We swap the winds
56:19 and share the pain. No one [music] solo
56:23 in this game. It's the admin hug where
56:28 legends walk in from chaos to clarity.
56:30 That's how we win.
56:33 Dirty got a challenge accepted. Portal
56:42 Quick fix queen kings [music] custom
56:45 coded everything. Tabs open. Coffee
56:48 strong. You've been solving all along.
56:50 We've got the knowhow. We've got the
56:52 map. Leaving hub product [music] to
56:54 chat. You're not just heard. You help
56:56 shape the tools. Admit rewriting all the
57:00 rules. Thanks for building with the hug.
57:02 Thanks for powering [music] the hug
57:05 behind every campaign. Push nudge.
57:07 There's a whole crew holding [music]
