ABOUT THIS EPISODE
Text us your thoughts on the episode or the show!
In this episode of OpsCast, hosted by Michael Hartmann and powered by MarketingOps.com, we are joined by Danielle Urban, Co-founder and CEO of Cartographer Consulting. Danielle brings a blend of demand generation, operations, and HubSpot expertise, helping early-stage startups and scaling teams build smarter, more sustainable marketing systems.
The conversation focuses on Martech maturity, how to know when you have outgrown your current setup, what signals indicate it is time to evolve, and how to align platforms and processes as your team grows. Danielle shares lessons from her experience guiding teams through HubSpot optimization, stack consolidation, and key maturity milestones to avoid growth slowdowns.
In this episode, you will learn:
- How to define Martech maturity and identify growth triggers
- Common pitfalls when teams outgrow their systems
- How to align HubSpot and processes with business evolution
- When to DIY and when to bring in outside expertise
- The growing role of AI in shaping marketing operations
This episode is perfect for marketing operations professionals, HubSpot users, and growth teams looking to scale efficiently without skipping important maturity steps.
Episode Brought to You By MO Pros
The #1 Community for Marketing Operations Professionals
IN THIS EPISODE
SHOW NOTES 🔗
TRANSCRIPT 🔗
00:00:25.130 --> 00:00:31.850
Hello everyone, welcome to another episode of OpsCast, brought to you by MarketingOps.com and powered by all the mud pros out there.
00:00:31.850 --> 00:00:37.850
Today, I'm excited to be joined by Danielle Urban, co-founder and CEO of Cartographer Consulting.
00:00:37.850 --> 00:00:43.850
Danielle brings a unique mix of demand gen, operations, and platform expertise, especially in the world of HubSpot.
00:00:43.850 --> 00:00:50.570
She's helped early stage startups and scaling companies figure out not just how to use HubSpot, but when and how to level up.
00:00:50.570 --> 00:00:59.370
We are going to be talking about RTech maturity, how to recognize when you're you've outgrown your setup and what signals to look for before your stack starts slowing you down.
00:00:59.370 --> 00:01:06.650
So whether you're a team of two or scaling fast, Daniel has been there and can help you avoid the pitfalls of skipping key maturity milestones.
00:01:06.650 --> 00:01:08.409
Danielle, welcome to the show.
00:01:08.810 --> 00:01:09.210
Thanks.
00:01:09.210 --> 00:01:10.730
Thank you so much for having me.
00:01:11.210 --> 00:01:24.090
You know, I thought I was going to trip over the name of Cartographer, but uh there's a nail that there's there's a one of the my favorite books that I ever read is it's called um, I think it's called The Map That Changed the World.
00:01:24.090 --> 00:01:28.329
So, you know, obviously cartography is a part of that somewhere.
00:01:28.329 --> 00:01:31.129
I I would like encourage you to go check it out.
00:01:31.129 --> 00:01:45.530
It's a pretty fascinating story about one of these people who did some work, wasn't appreciated at the time, died a pauper, you know, and in major debt, and then now is looked on as someone anyway, had to do with how we um the value.
00:01:45.530 --> 00:01:50.969
I forg I forget the person's name, but anyway, good good work.
00:01:50.969 --> 00:01:54.810
So, all right, well, um enough of that.
00:01:54.810 --> 00:02:08.250
So you um yeah, when we talked before, you you said you know you've worked with teams at different stages of growth, which is great because I think there's a lot of people who listen who maybe are probably gonna be going through transitions.
00:02:08.250 --> 00:02:12.969
When you think of maturity, especially around Martech, like how do you define that?
00:02:12.969 --> 00:02:15.129
Like, what's your approach to that?
00:02:15.610 --> 00:02:18.730
Yeah, I I've seen multiple inflection points.
00:02:18.730 --> 00:02:22.730
And it's funny because our sales conversations, we always try to say, like, what brings you here?
00:02:22.730 --> 00:02:24.329
Like, how can we help you today?
00:02:24.329 --> 00:02:26.969
Um, and you get a huge range of answers.
00:02:26.969 --> 00:02:38.250
But even when I was back in-house, I started my career in Demand Gen um million years ago at a very, it was like a medium-sized company that got acquired by a very, very large company.
00:02:38.250 --> 00:02:51.530
Um, and so it was really interesting to see the juxtaposition between like our small nimble team that was supporting a 200-person company inside of like a 300,000-person company and the differences in how we talk to our colleagues.
00:02:51.530 --> 00:02:55.689
And so very early in my career, I got exposed to like both extremes.
00:02:55.689 --> 00:03:03.210
Um, and then I went even further down the extreme on the smaller side where I worked in a handful of startups as their like first marketing hire.
00:03:03.210 --> 00:03:05.530
And so I was really setting up systems.
00:03:05.530 --> 00:03:14.810
And so, with that background knowledge, now coming into the consulting world over the past four or five years, um, I feel like we've seen, we've seen it all, truly.
00:03:14.810 --> 00:03:27.449
Um, and a lot of times there are these sort of trigger points where either they're expanding their team or they have some new initiative that they need to measure, that's sort of that inflection point of like, we actually can't measure any of this.
00:03:27.449 --> 00:03:28.409
We don't know how.
00:03:28.409 --> 00:03:38.810
Um, or it's a new leader that steps into play, or they they are putting a renewed or new focus on, say, customer success, and they need, you know, systems to support that function.
00:03:38.810 --> 00:03:43.530
So there are a lot of different things that will pull you in at different times.
00:03:43.530 --> 00:03:46.569
Um, and it can be as small as like, we made our first marketing hire.
00:03:46.569 --> 00:03:56.169
Now we need to give them tools to do their job, or it could be like we're building out an entirely new branch of our business, uh, or we're you know, beefing up our marketing team.
00:03:56.169 --> 00:04:03.530
So usually there's some indication of growth or major change that will start that conversation.
00:04:03.530 --> 00:04:08.330
Uh, but there sometimes it's just like we need to fix this, it's so bad.
00:04:08.650 --> 00:04:09.050
Yeah.
00:04:09.689 --> 00:04:09.930
Yeah.
00:04:10.009 --> 00:04:18.169
I mean, it seems like the the driver for the Martech maturity is really like almost like a business maturity is the leading indicator.
00:04:19.210 --> 00:04:20.810
Yeah, I'd say so, definitely.
00:04:20.810 --> 00:04:26.970
Because the the people who will see the need are the people who have a goal to accomplish.
00:04:26.970 --> 00:04:35.449
And so if you are adding new goals and new people are assigned to those goals, then you need systems to support that.
00:04:35.449 --> 00:04:38.569
And that system can be like a people-driven process.
00:04:38.569 --> 00:04:42.090
You know, when you hire a new salesperson, all of a sudden now you need to train them.
00:04:42.090 --> 00:04:43.850
Well, what are you even training them on?
00:04:43.850 --> 00:04:46.090
Uh, so there's that process piece of it.
00:04:46.090 --> 00:04:50.809
And then there's the system of like, okay, you're training them to follow the methodology.
00:04:50.809 --> 00:04:52.169
Well, where are you tracking that?
00:04:52.169 --> 00:04:54.649
Where are they understanding their success?
00:04:54.649 --> 00:04:56.169
How are you understanding their success?
00:04:56.169 --> 00:04:58.649
And that's where the Martech piece comes into it.
00:04:58.649 --> 00:05:05.289
And it's it's funny we're talking about sales and marketing technology, but in the HubSpot world, it's all one and the same these days.
00:05:05.289 --> 00:05:05.529
Right.
00:05:05.529 --> 00:05:11.129
So there are so many different functions that come into play when you can put it all under one roof in HubSpot.
00:05:11.370 --> 00:05:19.129
Yeah, I think I think it's interesting that you've had that exposure to like really, really large organizations down to early stage, startup, whatever, small organizations.
00:05:19.129 --> 00:05:22.889
And you talked about how like the lay the way that you talk to each other is different.
00:05:22.889 --> 00:05:26.250
And there's there's a difference in like there's a difference in language.
00:05:26.250 --> 00:05:33.129
There's also what I've seen is I think if there's an expectation, if you're growing, right, you add a person, right?
00:05:33.129 --> 00:05:37.850
There's um a straight line of increased output, right?
00:05:37.850 --> 00:05:55.529
But it's not that because there's I don't there's probably somebody studied this, but I suspect that like there's a there's a point at which like adding another person does you don't get another you know X one X of whatever uh uh the average is across the team, right?
00:05:55.529 --> 00:05:59.049
Right becomes lower because of a number of things.
00:05:59.049 --> 00:06:01.450
Part of it usually there's specialization, right?
00:06:01.450 --> 00:06:03.289
You've got enhanced you got it now.
00:06:03.289 --> 00:06:05.610
You put in more process, right?
00:06:05.610 --> 00:06:22.889
And I think there's there's a risk there too of um expecting more out of that one additional, you know, that marginal addition of the headcount to what you can produce to and then you add in the language differences, like it's just like that is a whole nother piece of it.
00:06:23.289 --> 00:06:23.610
Yeah.
00:06:23.610 --> 00:06:31.769
Well, if you think about it, there's sort of the small company that, you know, I like I said, I was a first marketing hire at a handful of startups.
00:06:31.769 --> 00:06:37.289
Usually they've got a salesperson, maybe a sales leader and one person under them in place.
00:06:37.289 --> 00:06:45.610
And so because I'm the first one in who cares about marketing, the sales team has probably just gotten by on spreadsheets.
00:06:45.610 --> 00:06:51.529
Maybe they've chosen their favorite cheap, free trial tool to keep track of everything.
00:06:51.529 --> 00:06:55.929
But then I'm like, well, now my job is to help you guys.
00:06:55.929 --> 00:07:00.490
I was usually in demand generals because that's what they hire marketing for at an early stage.
00:07:00.490 --> 00:07:11.529
So I'm like, if I have to do work to feed you leads and to create all of this buzz, how am I going to track what I'm doing and how it impacts what you're doing?
00:07:11.529 --> 00:07:18.409
And so I implemented HubSpot more than once when I was in-house because we just needed some level of tracking things.
00:07:18.409 --> 00:07:36.330
And I think if their sales team were to grow bigger before that point, they would have already been on a system to know that like if you've got more than two people, if you can sit down over coffee or talk to each other in the hallway to get your work done, when you add one more person, that's too much coordination.
00:07:36.330 --> 00:07:40.570
So if you reach more than two people on your team, you have to build processes.
00:07:40.570 --> 00:07:54.649
And so if I had stepped into a team where there's already more than three salespeople or three or more, then there probably would have been a completely different approach for me to take in trying to bolt on to what they're already using so that we can all work cohesively.
00:07:54.649 --> 00:07:56.250
And that's only at the small scale.
00:07:56.250 --> 00:08:10.250
When you talk about adding people at a larger scale, adding one more salesperson to a predefined role is not going to break anything because you've already gotten to that level of specialization and the sort of role function inside of the systems that you already have.
00:08:10.730 --> 00:08:11.210
Yeah.
00:08:11.210 --> 00:08:29.529
So, I mean, we're normally um sort of tool agnostic, but you basically you with your expertise with HubSpot, um, something that was interesting to me because I'm less familiar with HubSpot is that you said that the subscription tiers in HubSpot kind of loosely map to maturity levels that you think of.
00:08:29.529 --> 00:08:38.970
Walk us through what you mean by like what the tiers are, what those maturity levels are, and and maybe what is unlocked as you move forward in those maturity levels.
00:08:39.289 --> 00:08:41.929
Yeah, it's funny because since we last spoke, they've even changed it.
00:08:41.929 --> 00:08:49.850
They used to be pretty locked in, but at inbound, they announced their new smart CRM uh pricing model.
00:08:49.850 --> 00:08:54.970
Um, and so it I'm not gonna go too deep into what it used to be because there's a lot of what it used to be.
00:08:54.970 --> 00:08:59.129
But today you can buy a smart CRM seat.
00:08:59.129 --> 00:09:03.929
Seat-based pricing is still relatively new in the HubSpot world, but they announced seat-based pricing.
00:09:03.929 --> 00:09:11.929
And it used to be that you buy a core seat, which is like your super admin seat, and then you have specialized seats for sales, marketing, et cetera.
00:09:11.929 --> 00:09:15.049
We still have that, um, which is great.
00:09:15.049 --> 00:09:25.129
And then we've layered in this new smart CRM pricing model where you as one person can sort of push yourself through the subscription tiers.
00:09:25.129 --> 00:09:27.850
They have their starter level, which is pretty locked down.
00:09:27.850 --> 00:09:30.329
It's really just basic information keeping.
00:09:30.329 --> 00:09:36.169
It lets you into even on the free version, there's not much functionality you get over the free version and the starter version.
00:09:36.169 --> 00:09:39.610
Um, but free and starter, it's just like information keeping.
00:09:39.610 --> 00:09:45.049
You're tracking your emails, you see what happens where, you can keep track of people, you've got basic deal function.
00:09:45.209 --> 00:09:50.490
Um like a spreadsheet with connections and some app on top of it.
00:09:50.809 --> 00:09:51.449
Yeah, exactly.
00:09:51.449 --> 00:09:57.929
I think most people will move from a spreadsheet to HubSpot because it tracks your emails automatically to the contact record.
00:09:57.929 --> 00:10:04.409
So that is the thing that you want when you decide to go sign up for HubSpot on a random Tuesday.
00:10:04.409 --> 00:10:08.809
Um, but then you get into the pro level tiers, which unlocks some automation.
00:10:08.809 --> 00:10:15.769
So when you need more things to happen in a consistent way, then you feel yourself pushing into that pro level tier.
00:10:15.769 --> 00:10:33.529
Um, and the smart CRM seats let you, you as an admin or you as one person potentially who's building your one person company or a small company, can move yourself into that seat without having to get into the specialized functions of marketing sales, customer service, data, engineering, any of that.
00:10:33.529 --> 00:10:37.610
Um, whereas it used to be you had to choose one of those to sort of unlock that functionality.
00:10:37.610 --> 00:10:46.649
So I'm very excited about that because me, as one person, can do a lot if I'm able to push into some of those higher level features.
00:10:46.649 --> 00:10:58.089
But as soon as you move into one of those specialized tiers or specialized hubs, as HubSpot calls them, with marketing sales or customer success, then you're sort of locked into that.
00:10:58.089 --> 00:11:01.610
You follow that path now or follow multiple paths at once.
00:11:01.610 --> 00:11:08.730
Um, and so generally speaking, the HubSpot tiers are starter pro and enterprise with free as a kind of an option.
00:11:08.730 --> 00:11:13.929
Um, and pro is where you first unlock that uh automation piece of it.
00:11:13.929 --> 00:11:18.009
Um, you can customize some of your views, you get a little bit more flexibility in reporting.
00:11:18.009 --> 00:11:23.129
And then when you get into the enterprise level, you're able to capture data at such a granular level.
00:11:23.129 --> 00:11:28.169
Um, the big, big feature for me in that level is uh custom events tracking.
00:11:28.169 --> 00:11:32.649
So you can indicate if there's a change on a record, you're capturing that as its own thing.
00:11:32.649 --> 00:11:37.370
If somebody clicks a button on a certain page, you can capture that in its own record.
00:11:37.370 --> 00:11:42.889
And so you're able to track at a level of granularity that no one in a startup is really going to care about.
00:11:42.889 --> 00:11:48.569
And if they do, they probably have a specialized tool like their product team who's looking at product interactions.
00:11:48.569 --> 00:11:50.649
You're not building that into your marketing yet.
00:11:50.649 --> 00:11:52.970
And so, or definitely not your sales.
00:11:52.970 --> 00:12:01.689
So if you are reaching that level at a business, then generally your bigger business with more specialized people who want more specific information.
00:12:01.689 --> 00:12:04.649
And so that's roughly how it all sort of maps out.
00:12:04.889 --> 00:12:05.209
Yeah.
00:12:05.209 --> 00:12:26.009
It's interesting because I heard about that in my first reaction is if I was responsible for this, I would be really worried about people coming to me like, we want this random activity to be tracked without really thinking about like how would it, like, how would it actually inform what we do.
00:12:26.730 --> 00:12:26.970
Yeah.
00:12:27.289 --> 00:12:29.850
And in the reason, my pocket Mopsapalooza.
00:12:29.850 --> 00:12:30.889
Is that it?
00:12:30.889 --> 00:12:39.689
Talking about enterprise report or executive reporting and how you get to a report that's actually useful and not just because somebody asked you.
00:12:40.009 --> 00:12:47.129
Yeah, I just like my this is kind of goes back to my early years when I first moved into the kind of a marketing domain and I worked in database marketing.
00:12:47.129 --> 00:12:53.289
And you know, there's all these providers that could you could get, and they're still out there, probably more of them now where you could get additional data.
00:12:53.289 --> 00:12:55.929
In our case, it was consumer oriented, right?
00:12:55.929 --> 00:13:05.929
Like get at the zip code level, right, information about whatever income levels, you know, preferences that are typical, yada yada yada, right?
00:13:05.929 --> 00:13:08.089
You can imagine all those kinds of things.
00:13:08.089 --> 00:13:18.009
And if I ever put that in front of our marketers and said, here's you know, here's a basket of you know a hundred potential fields that we could get, right?
00:13:18.009 --> 00:13:18.809
What do you want?
00:13:18.809 --> 00:13:23.370
Invariably the answer would be like, well, we might use any of them, so let's get them all, right?
00:13:23.529 --> 00:13:23.689
Yeah.
00:13:24.009 --> 00:13:29.850
So and like, but the reality is there's probably 10 or fewer that are the realistic ones you would use.
00:13:29.850 --> 00:13:41.289
And I think like that's the like with what you just described, if like that's where my head went was like, how do we keep that from going out of control in terms of all the things we could track versus what we would actually use?
00:13:41.850 --> 00:13:42.809
Yeah, definitely.
00:13:42.809 --> 00:13:52.169
And I mean that you're at that point where if you have that functionality and you're willing to pay for that level of service from HubSpot, you're doing it for a reason.
00:13:52.169 --> 00:13:53.449
There's something you want to track.
00:13:53.449 --> 00:13:54.089
And it's okay.
00:13:54.089 --> 00:13:55.529
Yeah.
00:13:55.529 --> 00:13:58.490
It's okay if that evolves and changes over time.
00:13:58.490 --> 00:14:05.929
If you're measuring a single campaign and you want to know how many people click that red button during Black Friday, you don't care that much come January.
00:14:05.929 --> 00:14:11.769
You might want to compare year over year, but once you've captured that data, it's okay to just sort of move on and let it evolve.
00:14:11.769 --> 00:14:14.649
I think you have like 150 tracked events.
00:14:14.649 --> 00:14:16.970
So there's a lot of things to play with.
00:14:16.970 --> 00:14:20.250
And like at the end of the day, if you're capturing extra information, like fine.
00:14:20.250 --> 00:14:22.409
You're already paying for the feature, whatever.
00:14:22.730 --> 00:14:22.970
Yeah.
00:14:22.970 --> 00:14:28.329
I mean, my point is like have a plan for like actually using the stuff if you're gonna do it.
00:14:28.329 --> 00:14:32.730
And if in and it's okay if you think you will and you end up not, and then you can double it, right?
00:14:32.730 --> 00:14:37.850
But don't just keep it because you made that decision a year ago.
00:14:37.850 --> 00:14:52.490
So, okay, so let's know, like, this now to me gets into a little bit of like how how would I, maybe as a as a team of one or uh a leader, right?
00:14:52.490 --> 00:15:04.730
How would I know what are the signals that I should be looking for that we should be thinking about, you know, moving whether it's the next tier or someone based on what I if I understand right now with the new model, right?
00:15:04.730 --> 00:15:09.529
A particular user's tier to within HubSpot, right?
00:15:09.529 --> 00:15:10.490
How do you think about that?
00:15:10.490 --> 00:15:24.089
Like what what are the you've I think you've hit it at a couple of things, but what are some of the changes or signals that would indicate, hey, it's time to be thinking about us moving maturity, moving our users to different levels and so forth.
00:15:24.329 --> 00:15:24.649
Yeah.
00:15:24.649 --> 00:15:33.929
Well, why don't I outline what I've got for the sort of rough maturity model that's still a work in progress, but so far, I think it's tracking.
00:15:33.929 --> 00:15:37.769
Um, the first stage is really just like a speed to function.
00:15:37.769 --> 00:15:42.809
You're a small scrappy team, everybody is using tools that they need to get their job done that day.
00:15:42.809 --> 00:15:48.569
There's not a whole lot of thought about how it comes together as a functioning platform, a complete ecosystem.
00:15:48.569 --> 00:15:50.889
We're not really connecting things together that much.
00:15:50.889 --> 00:15:59.049
Maybe one or two things are sharing data, but it's really just like, how do I, as a marketer, as a salesperson, get through today?
00:15:59.049 --> 00:15:59.370
Yeah.
00:15:59.370 --> 00:16:00.889
And maybe next week.
00:16:00.889 --> 00:16:07.370
And maybe we get to some numbers for the board, but that's really not coming to mind on a day-to-day.
00:16:07.610 --> 00:16:12.569
And maybe this is something I want to be repeatable, but like that's not probably not thinking.
00:16:13.529 --> 00:16:15.370
Uh, would not from what I've seen.
00:16:15.370 --> 00:16:30.889
But in that case, there's so little focus on scalability, and you end up, it's very easy to change platforms, which is great to maintain flexibility, but that consistency and tracking and data capturing over time makes it very difficult for your team to share information.
00:16:30.889 --> 00:16:36.169
So if you're one salesperson working out of a spreadsheet, sure, you can share your Google Sheet and then it's up to date.
00:16:36.169 --> 00:16:44.409
But if it's not in a format that's accessible to other people, or if someone needs to transform that data to get a different kind of number, it kind of starts to fall apart really quickly.
00:16:44.569 --> 00:16:44.889
Yeah.
00:16:45.049 --> 00:16:51.610
Um, and so then you find that you need more specificity and you need a little bit more maturity.
00:16:51.769 --> 00:16:51.929
Yeah.
00:16:52.089 --> 00:16:54.809
Um, and you need to create those repeatable systems.
00:16:54.809 --> 00:16:56.569
And I think that usually comes.
00:16:56.569 --> 00:17:04.089
This is what I want to test a bit in more conversation is like, I think that comes when people want more analysis out of their data.
00:17:04.089 --> 00:17:09.210
So, like you're tracking it, you're reacting to it, you're doing things on the day-to-day.
00:17:09.210 --> 00:17:11.210
But when you're like, well, how did that work?
00:17:11.210 --> 00:17:12.890
Or how do I do more of that?
00:17:12.890 --> 00:17:14.730
What is the pattern here?
00:17:14.730 --> 00:17:18.569
That is, I think, when you hit step two in this maturity model.
00:17:18.569 --> 00:17:22.410
And that's where you start to need those repeatable systems.
00:17:22.410 --> 00:17:25.289
And maybe it's when your team grows past two.
00:17:25.289 --> 00:17:32.809
Um, and you just need to get that data model to be meaningful because your business needs to track deals consistently.
00:17:32.809 --> 00:17:39.210
They need to track, you know, lead um, lead creation consistently and those sources that they come in from.
00:17:39.210 --> 00:17:47.049
Uh, and you need to turn around and report that to a board and say, this is how we're growing our business because leads are coming in from these sources, we're following up in this way, and here you go.
00:17:47.369 --> 00:17:48.649
You want you to be able to translate.
00:17:48.649 --> 00:17:52.970
I mean, the word that comes to mind that I talk about when you get into that is discipline, right?
00:17:52.970 --> 00:17:56.009
You need to discipline the way that you're executing.
00:17:56.009 --> 00:18:07.289
And I I use that like specifically instead of process, because I think like it's really like we are gonna be because you like you said, you add this one other person.
00:18:07.289 --> 00:18:16.490
If you're doing this sort of free-for-all uh model, right, each if you now get two people doing things differently, they're calling things that are the same, different words, right?
00:18:16.490 --> 00:18:24.730
Yeah, very quickly reporting is gonna be a challenge, um, let alone like knowing like what's working across the two different people.
00:18:24.730 --> 00:18:25.529
Exactly.
00:18:25.529 --> 00:18:27.849
Like consistency and discipline is what you need there.
00:18:27.849 --> 00:18:28.329
Okay.
00:18:28.730 --> 00:18:29.450
Absolutely.
00:18:29.450 --> 00:18:36.009
And I think there's still at that stage, because it's still small, it's still pretty flexible, you're moving between systems.
00:18:36.009 --> 00:18:43.129
If you do a system migration three times in the space of a year, you get to that sort of tribal knowledge where it's like, we just use this one.
00:18:43.129 --> 00:18:47.609
Like, don't worry about those other confusing things that have created some debt for us.
00:18:47.609 --> 00:18:50.009
Like, just use that one and don't worry about the rest.
00:18:50.009 --> 00:18:57.289
And so there's still sort of that that people piece of it that hasn't been codified into the platforms that you're using.
00:18:57.289 --> 00:19:03.450
Um, but you're you're aiming at that consistency and you're aiming at that discipline because you recognize the need.
00:19:03.450 --> 00:19:14.410
So maybe you've got some tools, maybe you're starting to build that out and recognize the need, but you're still kind of sitting in this place where like everyone's just trying to get their job done and also get numbers to the board once a quarter.
00:19:14.410 --> 00:19:21.529
Um, and so then I think you can move into the next stage when you need to share that information more broadly.
00:19:21.529 --> 00:19:34.009
So maybe it's more teams, maybe it's that the board is putting more of a microscope on you because you're getting to a point where your revenue is high enough, the investment is high enough that that needs to be real.
00:19:34.009 --> 00:19:40.730
And they everyone needs the validity in the reporting that you're putting out to know that it's real.
00:19:40.730 --> 00:19:44.410
And so that's where you want to be able to look back over time.
00:19:44.410 --> 00:19:48.970
You want to do predictive uh modeling, you want to do forecasting.
00:19:48.970 --> 00:19:57.609
So all of that is the next stage three, maturity level, um, where you just need to get more granular, more specific, more disciplined.
00:19:57.609 --> 00:20:02.569
That data dictionary needs to be super duper clear and everyone needs to be bought in on it.
00:20:02.569 --> 00:20:09.930
And I think that is kind of the point where you need to put someone in the function of owning the platform and processes.
00:20:10.089 --> 00:20:10.410
Yeah.
00:20:10.410 --> 00:20:21.529
I mean, yeah, it sounds like it's almost like a switch, maybe not like a switch from we're just looking backwards in performance and now we're looking at that and trying to inform what we expect the future to look like.
00:20:21.930 --> 00:20:22.250
Right.
00:20:22.250 --> 00:20:22.889
Exactly.
00:20:22.889 --> 00:20:33.210
We want to be able to tell a complete story of a single person, but also find those patterns where, like, if this happened in the past, then it but it happened this way on the next few steps.
00:20:33.210 --> 00:20:40.089
So if we do the same thing or do something very similar to follow that path, we think this next thing is going to happen.
00:20:40.089 --> 00:20:45.369
But my notes here say the skill set is likely not on your team to be able to hit that.
00:20:45.369 --> 00:20:55.129
So you're still, even though you're getting to that point where you can capture the data and maybe you've got someone sort of owning the capture of that data, but do you get into like statistical modeling?
00:20:55.129 --> 00:20:56.970
You probably don't have a data engineering team.
00:20:56.970 --> 00:20:58.329
And how much money is that?
00:20:58.410 --> 00:21:00.809
What are the biggest gaps in skills across our team?
00:21:00.809 --> 00:21:01.769
Absolutely.
00:21:01.769 --> 00:21:02.809
Um definitely.
00:21:03.289 --> 00:21:29.529
And then I think the the stage four and final stage I have noted is like that deep analytical need where you do get that data engineer on board and you're finally big enough that you can justify having like an analytic center of excellence or a platform ownership that's more than one person, and really make sure that the data is flowing between your systems, that it's accurate, that it's measured, that there's you know, buy and an understanding on what what the numbers are telling you.
00:21:29.529 --> 00:21:35.690
Um and you're not sort of cobbling it together and saying, just use that one property that we made up three years ago.
00:21:36.250 --> 00:21:40.410
Well, yeah, this field is labeled this one thing in our CRM, we actually use it a different way.
00:21:40.410 --> 00:21:42.490
So do like this is what you yeah.
00:21:42.490 --> 00:21:44.730
Um that's interesting.
00:21:44.730 --> 00:21:56.730
Yeah, the thing about the one nuance I think I would add to that last stage, and I don't know if that was actually the last stage, but the last one we just talked about, yeah, is um when you get to that data engineering aid, right?
00:21:56.730 --> 00:22:10.809
What I've found is really difficult is finding someone who understands data statistical analysis in the general sense, but also in the domain of sales and marketing, because it's got its own set of uh like challenges, I think is the best way to put it, right?
00:22:10.809 --> 00:22:14.490
It's just it's messy data, it's not like finance data, right?
00:22:14.490 --> 00:22:15.609
All that kind of stuff.
00:22:15.609 --> 00:22:20.490
Um curious, so I mean, I I'm tracking all these different stages.
00:22:20.490 --> 00:22:21.769
I think there were four total.
00:22:21.769 --> 00:22:22.170
Yeah.
00:22:22.170 --> 00:22:35.129
Um the uh the thing I'm like it came to me in mind to me is like um is it ideal that like you would see organizations going kind of step by step through those?
00:22:35.129 --> 00:22:37.690
Or does it make sense to skip them?
00:22:37.690 --> 00:22:51.049
If so, when like what or like what are the it feels like it feels like it could be skipped in some cases, and maybe there's like a major capital infusion or merger, right, that would be a driver for that.
00:22:51.049 --> 00:22:56.410
But like outside of that, like it feels like there might be some risk in sort of jumping steps.
00:22:57.289 --> 00:23:03.289
Yeah, I I think you would find yourself like over-engineered if you skip some of these steps.
00:23:03.289 --> 00:23:04.649
And I've seen that be the case.
00:23:04.649 --> 00:23:15.849
You know, you outsource something and they you get sort of a a copy paste process into your systems, and then there's no adoption because it just wasn't built for a way that serves your business.
00:23:15.849 --> 00:23:18.730
And that's that's what we as consultants are always trying to do.
00:23:18.730 --> 00:23:23.210
We we want to talk about how do we build the best system for you right now.
00:23:23.210 --> 00:23:28.649
There's a lot of pattern matching that I can do, there's a lot of commonality between different types of clients.
00:23:28.649 --> 00:23:35.849
But at the end of the day, the way that your teams are structured, the way that your teams like to work, what else is in your tech stack is very custom.
00:23:35.849 --> 00:23:40.490
Um, and so I I've only seen one client really need to skip a stage.
00:23:40.490 --> 00:23:42.170
And it was exactly what you were talking about.
00:23:42.170 --> 00:23:46.089
Like they just they have the product market fit at exactly the right time.
00:23:46.089 --> 00:23:48.649
The industry was just absolutely blowing up.
00:23:48.649 --> 00:23:50.490
They couldn't even keep up with themselves.
00:23:50.490 --> 00:23:51.849
They couldn't hire fast enough.
00:23:51.849 --> 00:23:57.369
They had a massive capital infusion, and they went from like step one to step four.
00:23:57.369 --> 00:24:01.609
Like they really jumped the gun in a matter of a couple months.
00:24:01.609 --> 00:24:03.930
And but that is so, so unusual.
00:24:03.930 --> 00:24:06.490
I really think that it comes into play.
00:24:06.490 --> 00:24:10.250
And maybe you could break it out into the different teams that are doing that.
00:24:10.250 --> 00:24:13.849
But I think this this functions mostly at the business level.
00:24:13.849 --> 00:24:22.490
Um, because even if you had like the maturity of a customer success team, it's gonna sort of follow these same steps, but it's only gonna follow those steps because of the needs of the business.
00:24:22.490 --> 00:24:25.289
Um, so yeah, I think it's pretty rare that you would jump around.
00:24:25.450 --> 00:24:25.609
Yeah.
00:24:25.609 --> 00:24:28.809
I I love you use the term pattern matching, which I love.
00:24:28.809 --> 00:24:44.089
Like I feel like I see I it's I always sort of have this really like visceral reaction when people are like, I'm you know, there's this best practice, and it feels like that doesn't really like uh and I think what they be people mean is kind of what you're talking about, right?
00:24:44.089 --> 00:24:54.569
Pattern matching, like applying the lessons I've learned to your specific situation, environment, maturity, whatever, and trying to match that.
00:24:54.569 --> 00:25:01.529
And that's like that makes a way more sense to me than just throwing, hey, I've got a cookie cutter solution, I'm gonna drop it in, right?
00:25:01.529 --> 00:25:02.889
And I see Yeah.
00:25:03.210 --> 00:25:10.009
I I had to laugh once when I lost a deal because they wanted quick best practices, and I was like, Yeah, but for what?
00:25:10.009 --> 00:25:11.849
And they were like, we just want best practices.
00:25:11.849 --> 00:25:13.769
I was like, I'm not it then.
00:25:13.769 --> 00:25:14.089
Sorry.
00:25:14.410 --> 00:25:17.690
Yeah, that's probably probably good to avoid that client, right?
00:25:17.690 --> 00:25:18.569
Yeah, yeah.
00:25:18.569 --> 00:25:22.410
Because they think there's they think there's an easy button to to this stuff.
00:25:22.410 --> 00:25:24.649
And yeah, okay.
00:25:24.649 --> 00:25:27.529
I'm gonna I could go off on a tangent that I don't want to stack.
00:25:27.529 --> 00:25:35.049
So okay, so we've so we've I think we addressed maybe one common thing that could be a risk or a pitfall.
00:25:35.049 --> 00:25:48.809
Um are there other kinds of things that could be pitfalls as teams are going through this like maturation process, um, kind of trying to keep up with their growth or whatever that um we didn't already touch on?
00:25:49.609 --> 00:26:11.129
Um, I think maybe if the teams are, I just sort of said like if you hire customer success and they're sort of following their own path uh through those maturity stages, it really should be at a business level because if you have, say, sales and marketing, which is such a classic example, but if you have sales and marketing who are moving through this differently, then your whole business is going to fall apart.
00:26:11.129 --> 00:26:21.930
So I think the sort of platform considerations and how you bring people into processes and platforms needs to be done very carefully and sort of the assessment of platforms.
00:26:21.930 --> 00:26:45.049
Um, someone needs to own it, whether it's their full-time job because you're at you're at sort of a stage three or stage four where there's enough need, or it's someone who's recognizing the need enough to go looking for a solution, they need to sort of step back and move themselves from step one of very reactive day-to-day into step two, where it's like we are evaluating this for a long-term implementation.
00:26:45.049 --> 00:26:49.690
We don't want this for six months, we want this for three years, depending on how fast they're growing.
00:26:49.690 --> 00:26:57.529
But still, you don't, you don't want a sales leader going off and be like, well, I bought this CRM because I like how it works or it's my favorite.
00:26:57.529 --> 00:27:01.690
And marketing is like, but we already had a CRM that's hooked up to all of our marketing activities.
00:27:01.690 --> 00:27:04.250
Like, then you're just in different places.
00:27:04.250 --> 00:27:12.329
And so I think keeping that focus at sort of the top-level leadership executive level needs to be really important.
00:27:12.329 --> 00:27:13.930
You need to get everyone on board.
00:27:14.250 --> 00:27:14.809
Yeah.
00:27:14.809 --> 00:27:25.849
So have you, um, do you have any examples of where you've helped clients or where when you were on site or in embedded with teams, right?
00:27:25.849 --> 00:27:33.289
Where you had some, you know, did some changes, maybe because I think what you're alluding to is sometimes you need to make smaller changes, right?
00:27:33.289 --> 00:27:35.930
And they can have that size impact, which I'm a big fan of.
00:27:35.930 --> 00:27:38.329
It's like yes, looking share there.
00:27:38.889 --> 00:27:42.889
Yeah, I one of my favorite recent stories was uh a small company.
00:27:42.889 --> 00:27:44.250
They're a pretty small startup.
00:27:44.250 --> 00:27:50.250
Um, they've been around for a while, so they've they've sort of grown and shrunk and changed course a little bit.
00:27:50.250 --> 00:27:57.129
Uh, but they had been on HubSpot, not under my expertise, um, not under my guidance.
00:27:57.129 --> 00:28:11.129
And they they then sort of shifted focus, shifted their sales team a bit, ripped it out and went to Monday.com and then decided they hired like three new salespeople, came back to me and said, we think we want to be back on HubSpot because our salespeople are comfortable with HubSpot.
00:28:11.129 --> 00:28:14.009
And I was like, okay, here we go.
00:28:14.009 --> 00:28:15.930
So we got into it.
00:28:15.930 --> 00:28:23.049
And um the data model they had created for themselves in their Monday.com CRM was a train wreck.
00:28:23.049 --> 00:28:27.049
Like they didn't, there was no consistency to how data was captured.
00:28:27.049 --> 00:28:30.649
Like there was a company object and then there was company name typed in.
00:28:30.649 --> 00:28:36.009
And there was also like a notes field where sometimes company names were typed in and it just was all over the place.
00:28:36.009 --> 00:28:38.809
And so our team sort of take deep breaths right now.
00:28:38.809 --> 00:28:40.809
Like I exactly stressing me out.
00:28:40.809 --> 00:28:46.970
And you're like, but our team painstakingly pulled all of that apart.
00:28:46.970 --> 00:28:50.569
Thankfully, it wasn't a huge amount of data because they had they'd been through a lot of change.
00:28:50.569 --> 00:28:52.730
But they um we pulled that apart.
00:28:52.730 --> 00:28:54.410
We got it into HubSpot properly.
00:28:54.410 --> 00:29:01.289
One of my favorite things to do with HubSpot uh clients is to sit down and show them the view of the data model that you get inside of HubSpot.
00:29:01.289 --> 00:29:14.170
It's sort of this little thing that's tucked away, but it's really powerful for helping people understand what the different objects are and how they relate to each other because it lays them out in boxes, then you hover over a box and it draws lines to the other things that they're related to.
00:29:14.170 --> 00:29:18.730
It's a really great view for getting people to understand this is how it all connects together.
00:29:18.730 --> 00:29:20.089
Um, so I love that.
00:29:20.089 --> 00:29:20.649
We did that.
00:29:20.809 --> 00:29:27.529
We did not easier to consume than like if you're not familiar with looking at massive data models, right?
00:29:27.849 --> 00:29:28.089
Yeah.
00:29:28.089 --> 00:29:34.250
When you start talking about objects, uh the salesperson who's not familiar with administering a CRM is gonna be like, I don't care.
00:29:34.250 --> 00:29:36.569
Like they are so gone from that meeting.
00:29:36.569 --> 00:29:42.009
And so we went through and onboarded them very meticulously and set them up with a system.
00:29:42.009 --> 00:29:47.690
But the my favorite part of that project was that their CEO wanted visibility into leads in a very specific way.
00:29:47.690 --> 00:29:49.210
And he was like, I can't get that with HubSpot.
00:29:49.210 --> 00:29:50.490
That's why we got rid of it last time.
00:29:50.490 --> 00:29:52.170
I was like, that's such a lie.
00:29:52.170 --> 00:29:54.170
Like, we can always get you there.
00:29:54.170 --> 00:30:02.170
And so we sat down and had like a 45-minute working session and created CEO's homepage as a dashboard in HubSpot.
00:30:02.170 --> 00:30:06.089
I walked him through how to set that as his homepage and HubSpot.
00:30:06.089 --> 00:30:09.289
So when he logs into HubSpot, that is exactly what pops up in front of him.
00:30:09.289 --> 00:30:16.649
It's the fields he wants to see listed in the way he wants to see them, relevant to how the sales team is working that day.
00:30:16.649 --> 00:30:20.569
And they're thrilled and they're actually using the platform properly, finally.
00:30:21.129 --> 00:30:23.129
Yeah, it's so funny how these.
00:30:23.129 --> 00:30:29.769
Misperceptions or or not even misperceptions, but perceptions can taint someone's view.
00:30:29.769 --> 00:30:36.569
And sometimes it's like a little investment in like going, actually, no, this is like this is totally possible.
00:30:36.569 --> 00:30:37.930
Sometimes it's not, right?
00:30:37.930 --> 00:30:39.690
Sometimes what they want is that possible.
00:30:39.690 --> 00:30:43.609
But like at least you can show what is possible, and I think that's that's huge.
00:30:43.609 --> 00:30:47.369
So you see you you hinted at a couple of things.
00:30:47.369 --> 00:30:50.569
So I know like I like I said, I'm not familiar with HubSpot.
00:30:50.569 --> 00:30:58.730
What I do know is it's like as you already kind of hit it, like they're like, I feel like there's an announcement of some sort of change every week or two from them.
00:30:58.730 --> 00:30:58.970
Yeah.
00:30:58.970 --> 00:30:59.289
Right.
00:30:59.289 --> 00:31:00.649
So they're evolving a lot.
00:31:00.649 --> 00:31:08.649
What what are what are some of the what are some of the other underused features that you think more teams should be taking advantage of?
00:31:09.529 --> 00:31:11.690
Um there's so much.
00:31:11.690 --> 00:31:17.289
And it's the features that are getting released are getting more and more specific, I think.
00:31:17.289 --> 00:31:19.609
Uh, so it's a little bit harder to keep track of.
00:31:19.609 --> 00:31:27.609
But I think some of my favorite things to sort of really reduce complexity in accounts, um, people may not realize they're there, like calculated properties.
00:31:27.609 --> 00:31:36.970
Uh, you can write a calculation into a property so that you don't have to do that calculation in a report, in a workflow that adds it together and creates a new property.
00:31:36.970 --> 00:31:39.690
Like you can just do that and you can add days.
00:31:39.690 --> 00:31:41.369
There's some funkiness to it.
00:31:41.369 --> 00:31:45.289
Like you need to remember to change your time windows to epic time.
00:31:45.289 --> 00:31:50.170
But like once you figure out what that is, you can eliminate workflows.
00:31:50.170 --> 00:31:58.809
Like you can eliminate all of these processes that are happening and have built out, have been built out to automate things for you just because you rewrote it as an equation.
00:31:58.809 --> 00:32:06.089
Um, and in a similar vein, the sync properties that came out are very, very cool when you're stamping data between objects.
00:32:06.089 --> 00:32:07.609
Um, we try not to.
00:32:07.609 --> 00:32:16.009
In most cases, you don't need to because you can cross-reference objects in a lot of the different features in HubSpot, but there are cases where you can't or you need to be able to see it in a specific way.
00:32:16.009 --> 00:32:21.849
And so these sync properties are like a mirroring of data from the other object, which is super, super helpful.
00:32:21.849 --> 00:32:26.329
Again, can cut down on a lot of the workflows that people have to stamp numbers across.
00:32:26.329 --> 00:32:33.049
Um, and uh in the same vein, stamping data across the custom events are so desperately underused.
00:32:33.049 --> 00:32:35.690
There's been a huge amount of change in those.
00:32:35.690 --> 00:32:39.049
Shout out to uh Maggie Philbin over the last year.
00:32:39.049 --> 00:32:43.529
She's a product manager, she's wonderful, uh, very accessible, clearly.
00:32:43.529 --> 00:32:48.970
Uh, but there's been so much change just over the last year in what you can capture, how you can capture it.
00:32:48.970 --> 00:32:59.210
Um, and people just don't think about it for the use cases they're trying to solve because they don't know that it's matured to that point or that these new features are available, that you can track it in that way.
00:32:59.210 --> 00:33:03.930
Um, so I think there's a lot of opportunity in those that people just aren't aware of.
00:33:04.250 --> 00:33:06.089
Yeah, that sounds that sounds good.
00:33:06.089 --> 00:33:18.089
So another thing, like use what we talked before, you use a term that I hadn't heard before about doing reverse demos as a way of diagnosing things.
00:33:18.089 --> 00:33:23.849
So explain what that is and why you think it's so effective and helpful.
00:33:24.250 --> 00:33:28.809
Yeah, I think I co-opted the term from a sales method, but it's my own now.
00:33:28.809 --> 00:33:30.410
Go for it.
00:33:30.410 --> 00:33:34.009
Yeah, we we really like to do that as part of our discovery.
00:33:34.009 --> 00:33:40.889
So we'll schedule an hour-long call with the person who has to use the tools that we're developing for.
00:33:40.889 --> 00:33:52.809
So if it's a sales process that we're working on, then we want to talk to like the lowest level salesperson who is picking up those leads every day and logging in to make calls because I want to see how they work.
00:33:52.809 --> 00:33:59.450
I want to see what buttons they press, I want to see what they're looking at, I want to see what they're updating, what other platforms they're accessing.
00:33:59.450 --> 00:34:06.410
You might find out that somebody has their own spreadsheet that they're maintaining and copying data from HubSpot into that spreadsheet.
00:34:06.410 --> 00:34:13.530
You might realize that people are filling in data in three different places that they don't need to, but they think they do because no one told them otherwise.
00:34:13.530 --> 00:34:16.170
And it's so incredibly telling.
00:34:16.170 --> 00:34:17.450
It's mind-blowing.
00:34:17.769 --> 00:34:18.570
Yeah, hardest.
00:34:18.570 --> 00:34:20.410
So I've done that kind of thing before too.
00:34:20.410 --> 00:34:24.730
And I think the hardest part is not saying something while they're going through it.
00:34:24.730 --> 00:34:25.530
Oh my gosh.
00:34:25.530 --> 00:34:27.690
Not correct it, correct.
00:34:27.690 --> 00:34:29.690
Yeah, not yeah.
00:34:29.690 --> 00:34:33.530
Um, it's and it's funny that you talked about like the side spreadsheet.
00:34:33.530 --> 00:34:49.769
So I did a a project at a company years ago uh that was uh intended to try to enable the support team to scale without adding headcount, right, to match the growth of the company, which it typically had a parallel growth pattern.
00:34:49.769 --> 00:35:09.290
And so the like short short version is like we've we found a methodology and there was some pushback about it, but what we found in doing investigation is because it was kind of a knowledge-based solution um on steroids, but like we found out like pretty much all the all the sport teams had their own version of a knowledge base.
00:35:09.290 --> 00:35:13.530
It was usually like a Word document on their computer that nobody else could see, right?
00:35:13.530 --> 00:35:14.890
Control F.
00:35:14.890 --> 00:35:47.530
Right, yeah, and so they had already kind of made that solution themselves, but it's like that in like going and sitting with somebody and seeing how they actually do the work, yeah, is uh can be mind-blowing because if you're going like like I've I've I tell this to people all the time is like if you don't know what you're if you're asking as a marketing team, why can't those salespeople just update their CRM with opportunity status or convert a lead or whatever, right?
00:35:47.530 --> 00:35:49.370
Go watch what it takes to do it.
00:35:49.370 --> 00:35:50.250
Right.
00:35:50.250 --> 00:35:54.330
Because you might be shocked at what a pain in the ass it is to do it.
00:35:54.330 --> 00:35:55.130
Yeah.
00:35:55.130 --> 00:35:59.130
Um and then you can go, like I think it will give you a very different perspective about how to do it.
00:35:59.130 --> 00:36:04.170
Like, and it's not that you don't want that, and it's probably not that they don't want to do that for you.
00:36:04.170 --> 00:36:09.850
But their goals and objectives and what drives them is not that.
00:36:10.250 --> 00:36:10.810
Right.
00:36:10.810 --> 00:36:12.810
Well, and we'll have people come to us.
00:36:12.810 --> 00:36:14.410
I'm working on a project right now.
00:36:14.410 --> 00:36:20.090
They they signed on for a really small, like three-week project to just get some reports stood up, basically.
00:36:20.090 --> 00:36:22.810
They wanted a little bit of automation, a little bit of visibility.
00:36:22.810 --> 00:36:25.530
And I was like, all right, cool, we'll we'll start there.
00:36:25.530 --> 00:36:27.130
We will start there.
00:36:27.130 --> 00:36:32.730
And even in that conversation, I was like, put me on with one of your salespeople.
00:36:32.730 --> 00:36:36.410
And I we've gone back and forth a bit because they were like, well, you can talk to the sales manager.
00:36:36.410 --> 00:36:39.050
I'm like, I don't really care what the sales manager has to say.
00:36:39.050 --> 00:36:48.490
I want to see who's clicking the buttons and how, because I need to build what the sales manager wants them to do into what they're already comfortable with.
00:36:48.490 --> 00:37:05.210
Like, we all benefit if I can build a system that gets done what the sales manager wants done, but it is in such a way that it's so accessible and straightforward to the low-level brand new salesperson that just came in because they are being basically guided through that process.
00:37:05.210 --> 00:37:08.330
Like, yeah, sales manager, you need to tell me what the process should be.
00:37:08.330 --> 00:37:09.130
We'll get there.
00:37:09.130 --> 00:37:16.650
But I want to see what the person is actually doing every single day because I'm setting up these automations to say, hey, there's a new lead assigned to you.
00:37:16.650 --> 00:37:18.170
Are they checking their emails?
00:37:18.170 --> 00:37:20.250
Are they seeing it in HubSpot?
00:37:20.250 --> 00:37:21.450
How do they get into that?
00:37:21.450 --> 00:37:23.210
What are the views that they're accessing?
00:37:23.210 --> 00:37:26.810
How do I make sure that they know it's there and they should follow up?
00:37:26.810 --> 00:37:29.530
Um, and this your sales manager can't tell me that.
00:37:29.769 --> 00:37:30.250
Yeah.
00:37:30.250 --> 00:37:34.090
Well, we set up notifications for when a new lead goes and they should be checking their email.
00:37:34.090 --> 00:37:37.530
And they go, like, I get so many email notifications, I ignore it, right?
00:37:37.769 --> 00:37:38.010
Yeah.
00:37:38.010 --> 00:37:41.130
Your inbox starts filtering them out because you never open them.
00:37:41.130 --> 00:37:41.530
Right.
00:37:41.530 --> 00:37:42.970
Like, you just don't know.
00:37:43.210 --> 00:37:55.530
That is like that by itself, that tip of getting that insight into like the boots on the ground and what they go through on a day-to-day basis, is such a great piece of advice.
00:37:55.530 --> 00:38:03.290
Like that, like I tell people regularly, like, go hang out with these people, these other organizations, it will benefit you.
00:38:03.290 --> 00:38:05.130
And they'd loved for you to know.
00:38:05.130 --> 00:38:08.810
It like this is exactly why, right?
00:38:09.050 --> 00:38:09.690
Yes.
00:38:09.690 --> 00:38:16.810
I had a client where we had one representative of their team do the screen share, but they brought the whole team with them.
00:38:16.810 --> 00:38:23.930
That was really interesting too, because it's one person saying, This is how me, as a representative of our team, is doing this process.
00:38:23.930 --> 00:38:25.610
Some people were like, Oh, I didn't know you did that.
00:38:25.610 --> 00:38:27.450
Or like, yeah, I didn't know we were supposed to do that.
00:38:27.450 --> 00:38:29.370
I didn't even know that I could do that, right?
00:38:29.370 --> 00:38:29.850
Yep.
00:38:29.850 --> 00:38:31.850
Or like, oh, I didn't know you could filter it like that.
00:38:31.850 --> 00:38:34.090
I didn't know that button was there that made my life easier.
00:38:34.090 --> 00:38:39.370
And so you get that information sharing, even just among your team, to look at the same screen.
00:38:39.370 --> 00:38:43.290
And it's so, as a consultant, I'm like, great, there's project number three, four, five.
00:38:43.290 --> 00:38:48.970
Like, I'm seeing so much that can be impacted, you know, depending on the scope of what we're working on to begin with.
00:38:48.970 --> 00:38:58.010
But it could be as simple as like creating a new card view in their center column so that they can just click and start typing into the things that they're supposed to be filling in.
00:38:58.010 --> 00:39:07.769
That takes me five minutes, but I wouldn't know that that's helpful without seeing the exact buttons and things you're hunting for in other platforms that you're accessing directly on your screen every day.
00:39:08.090 --> 00:39:08.410
Yeah.
00:39:08.410 --> 00:39:09.530
Yeah, I love that.
00:39:09.530 --> 00:39:11.769
Yeah, like we could almost like this.
00:39:11.769 --> 00:39:15.850
Maybe we need to like cut out just this part and just share that to the world.
00:39:17.130 --> 00:39:19.290
Consulting advice piece of this podcast.
00:39:19.290 --> 00:39:19.930
Yeah.
00:39:20.410 --> 00:39:36.810
Well, I mean, but it's like it's if people aren't thinking about that, which I suspect a lot of people aren't, um especially when they are looking across at other teams and um like it's like putting yourself in those other people's shoes, right?
00:39:36.810 --> 00:39:42.570
Call it whatever you want to call it, is is a valuable exercise to go through, right?
00:39:42.570 --> 00:39:50.250
And it feels like it's maybe a waste of time, maybe you feel like you know already, yeah, but you don't.
00:39:50.890 --> 00:39:52.890
It's that like go slow to go fast.
00:39:53.210 --> 00:39:53.370
Yeah.
00:39:53.850 --> 00:39:54.330
Thinking.
00:39:54.330 --> 00:40:02.330
Like if you slow down and understand how people work, you make their work more efficient, you make everybody's data better because the data capture is easier.
00:40:02.330 --> 00:40:04.330
Like it just pays off tenfold.
00:40:04.570 --> 00:40:04.730
Yeah.
00:40:04.730 --> 00:40:05.210
What is it?
00:40:05.210 --> 00:40:07.450
Like slow is smooth, smooth is fast.
00:40:07.450 --> 00:40:10.410
Is that the I don't know if I've heard that one.
00:40:10.410 --> 00:40:14.090
I think they're anyway, it was some variation of one of those, right?
00:40:14.090 --> 00:40:22.650
Okay, so so we talked a lot about like different things like stages and when to recognize it, some like great tips like we talked about.
00:40:22.650 --> 00:40:31.210
Yeah, but let's say that someone in our audience is listening, they're a team of one, maybe a team of two, um, and they're buried.
00:40:31.210 --> 00:40:43.850
How how would you advise them to think about like when do you need to like look at hiring somebody versus bringing in maybe outside help like your team?
00:40:43.850 --> 00:40:47.530
Um and and going through that thought process.
00:40:48.490 --> 00:40:52.570
Yeah, I think it it differs for a lot of different use cases.
00:40:52.570 --> 00:41:00.730
I think in the the smaller teams, I've had a lot of conversations with freelancers consultants who are like, hey, I just got onto HubSpot, I'm paying for the basic version.
00:41:00.730 --> 00:41:02.170
What should I be doing?
00:41:02.170 --> 00:41:05.530
And I the first thing I do, I'm always open to like a one-hour call.
00:41:05.530 --> 00:41:06.890
Like, yeah, let's get you set up.
00:41:06.890 --> 00:41:08.250
Let's be friends, let's hang out.
00:41:08.250 --> 00:41:09.530
Well, you're never generous enough.
00:41:09.530 --> 00:41:13.530
Yeah, it's more of a networking call, but like, how do I help you?
00:41:13.530 --> 00:41:19.290
Um, and so in that conversation, I had one last week, uh, I was like, share your screen and tell me what you're working on.
00:41:19.290 --> 00:41:22.170
And the very first thing I did was show them the data model and HubSpot.
00:41:22.170 --> 00:41:25.210
I'm like, you have all of these different things that connect to each other.
00:41:25.210 --> 00:41:27.210
She was like, I didn't know I had companies.
00:41:27.210 --> 00:41:28.330
I saw that they were there.
00:41:28.330 --> 00:41:29.290
I didn't know what they were.
00:41:29.290 --> 00:41:31.290
I didn't know how they connect to anything else.
00:41:31.290 --> 00:41:37.610
And so once we got that baseline, she understood all of the things that she could do, even at the starter level.
00:41:37.610 --> 00:41:39.610
And so we walked through some of her views.
00:41:39.610 --> 00:41:41.050
I introduced her to some new features.
00:41:41.050 --> 00:41:48.730
We sort of got some things dialed in, made sure that she had all of her um like inbox tracking set up properly, her calendar and got that connected.
00:41:48.730 --> 00:41:53.930
So there was a lot that we could do in that hour just to be like, all right, you are set up as much as you can.
00:41:53.930 --> 00:41:57.850
Because on the starter version, there's not a whole lot of things you can customize.
00:41:57.850 --> 00:42:00.730
You're just sort of getting into it to use the core features.
00:42:00.730 --> 00:42:16.970
Um, but I think when you get to that maturity level where you're working across teams, that's where you might want to talk to a consultant or a platform expert, even if it's just like an advisory call one time, like talking to someone to figure out how these teams need to work together.
00:42:16.970 --> 00:42:24.410
They each have their own goals and focuses that they need to like dive into and own and the outcomes they need to own.
00:42:24.410 --> 00:42:27.050
But someone needs to tie it together.
00:42:27.050 --> 00:42:31.050
And hopefully you have leaders that can do that and are talking to each other and working very closely.
00:42:31.050 --> 00:42:36.490
But when you get multiple teams, uh, those leaders are focused on guiding their team.
00:42:36.490 --> 00:42:43.450
And then there's no one to really own that in between and own the process of how data flows through the rest of the company.
00:42:43.450 --> 00:42:53.769
So you might have someone like me come in and say, like, all right, let's figure out what sales needs, let's figure out what marketing needs, let's figure out how we need to track the data through for the executive team, for the product team.
00:42:53.769 --> 00:42:58.570
How can we bring product activity into HubSpot to better inform your sales and marketing teams?
00:42:58.570 --> 00:43:03.210
Like, that's where we can start to pull all these pieces across the organization.
00:43:03.210 --> 00:43:15.210
Um, and so I think you kind of have to get to that point where you've got one or two levels of management, maybe even three levels, if you've got sort of the executive team, a VP level, and then you know, a marketing manager type person.
00:43:15.210 --> 00:43:22.090
Um, that's when you need someone to step in and own the processes and the platforms that connect it all together.
00:43:22.410 --> 00:43:22.730
Okay.
00:43:22.730 --> 00:43:23.690
Yeah.
00:43:23.690 --> 00:43:25.370
I mean, I know how I've thought about it.
00:43:25.370 --> 00:43:28.890
Like usually for me, I like use a spreadsheet.
00:43:28.890 --> 00:43:34.490
Like, here's all the things that our team or I mean or my team needs to accomplish.
00:43:34.490 --> 00:43:43.690
And then who's got the responsibility of it um sort of a matrix of the people quickly identifies where the gaps are or where there's points of failure, right?
00:43:43.690 --> 00:43:44.090
Right.
00:43:44.090 --> 00:43:45.769
Right, there's no redundancy.
00:43:45.769 --> 00:43:49.210
Um, and then I can sort of prioritize.
00:43:49.210 --> 00:43:56.010
I I hadn't thought of tying in the connection with like I guess because it's sort of implied in my own brain, right?
00:43:56.010 --> 00:43:59.290
There's just connection to other teams, and how do you build those relationships?
00:43:59.290 --> 00:44:00.730
Um, so that's good.
00:44:00.730 --> 00:44:02.490
Um why don't we do this?
00:44:02.490 --> 00:44:06.490
Like I we're uh we could go on for a while here, I think, but we need to probably wrap up.
00:44:06.970 --> 00:44:08.010
Seven minutes left.
00:44:08.250 --> 00:44:08.730
Yes.
00:44:08.730 --> 00:44:16.330
Um okay, so like it like it feels like this is an obligatory question these days.
00:44:16.330 --> 00:44:24.570
Like, like what's what do you see as the impact of AI um in kind of marketing teams, marketing ops teams, RevOps teams?
00:44:24.570 --> 00:44:29.050
Um and I know there's a lot of stuff going on within the Hubsbot ecosystem around it too.
00:44:29.450 --> 00:44:31.130
Yeah, such a token question.
00:44:31.130 --> 00:44:45.930
There's there's so many different ways that you can apply it though, because me as an admin and the things that I'm doing to assess sort of as an outside perspective, I'm using AI in a bunch of different ways every day.
00:44:45.930 --> 00:44:49.610
I one of my favorite tools these days is Fathom Note Taker.
00:44:49.610 --> 00:44:57.930
Um, and the reason I love it is because you can add your recordings to folders and then have a chat conversation with the entire folder.
00:44:57.930 --> 00:45:08.170
So if you're trying to do these reverse demos that you're recording and you're putting them all in the same folder, then you can go back and say, like, okay, the sales team, it's so good.
00:45:08.170 --> 00:45:12.650
The sales team said they're filling out this property because they think marketing needs it.
00:45:12.650 --> 00:45:14.410
Well, did marketing say they needed it?
00:45:14.410 --> 00:45:18.890
Where when the video was sales talking about that, and then did marketing talk about this?
00:45:18.890 --> 00:45:22.730
And then you just like three seconds later have an answer.
00:45:22.730 --> 00:45:26.730
Like, it's so powerful because I don't have to sit there and take notes and go back through.
00:45:26.730 --> 00:45:30.010
And that's driven by AI on top of the transcripts.
00:45:30.010 --> 00:45:39.450
One of my friends yesterday introduced me to a new concept that I feel like is a complete unlock for me, where I have very, very basic coding knowledge.
00:45:39.450 --> 00:45:43.210
Like I can do some JavaScript magic inside of AppScript, but I'm not a coder.
00:45:43.210 --> 00:45:44.810
I went to business school, I studied marketing.
00:45:44.810 --> 00:45:46.730
Like, don't trust me with apps.
00:45:46.730 --> 00:45:54.730
Um, but I know how powerful it is, and I have built out solutions on uh JavaScript that can accomplish things I can't do inside of HubSpot.
00:45:54.730 --> 00:46:01.610
Um, or if I need reporting in a specific format, we can build JavaScript that like pulls it every week and sticks it into a spreadsheet.
00:46:01.610 --> 00:46:15.850
Um, but one of my friends showed me a trick where he pulled the JSON for I was trying to audit a whole bunch of workflows and figure out which ones were relevant to the project I was working on and might impact the work that I'm doing.
00:46:15.850 --> 00:46:27.610
And so he pulled out the JSON of all of those workflows, fed it into an AI project, and then just asked, like, is how does this work?
00:46:27.610 --> 00:46:29.370
Which ones are the ones that matter?
00:46:29.370 --> 00:46:32.250
And I was like, I never thought to do that.
00:46:32.250 --> 00:46:36.250
I was trying to use like the Chat GPT connector or the cloud connector into HubSpot.
00:46:36.250 --> 00:46:38.090
It didn't have visibility into that object.
00:46:38.090 --> 00:46:42.730
I was trying to use HubSpot Breeze, which I have a lot of not very positive feelings about.
00:46:42.730 --> 00:46:50.810
Um, and so I was like, that like pull data out and put it here and then ask questions, like broke my brain.
00:46:50.810 --> 00:46:54.410
I'm so excited for the things that I can do with that.
00:46:54.410 --> 00:47:11.050
Um, and I just using my very basic JavaScripting knowledge that is very much supported by AI these days, to get the data that I want to ask questions of and then put it into an AI project where I'm just accessing it in that chat.
00:47:11.050 --> 00:47:12.330
Like that's huge.
00:47:12.330 --> 00:47:23.050
There's so much that I can do to shortcut my day in getting the answers I need and like taking inventory, like my efficiency is off the charts now, if I can do that.
00:47:23.050 --> 00:47:26.730
So I think that's my favorite use case that came up yesterday.
00:47:27.050 --> 00:47:31.210
Well, the so the the one I'll just add, somebody I saw somebody posting about notebook LM.
00:47:31.210 --> 00:47:32.090
Have you used that?
00:47:32.410 --> 00:47:35.850
I haven't yet, but we've talked about using that as a handoff for our clients.
00:47:36.090 --> 00:47:42.250
So I am I'm playing around with it now where I've been very like feeding in transcripts from from conversations.
00:47:42.250 --> 00:47:50.010
And I I have I'm in the car regularly listening to podcasts anyway, and it generates this audio sort of summary that's like feels like a podcast.
00:47:50.010 --> 00:47:55.370
And I'm I did one, I'm like, ooh, this is kind of interesting to see that perspective.
00:47:55.370 --> 00:48:00.970
Um, so I'm kind of curious to see if that will work, especially for like the kinds of things you're talking about with those reverse demos.
00:48:00.970 --> 00:48:01.690
Yeah.
00:48:01.690 --> 00:48:07.769
Anyway, um, I love hearing these new stories about how to use these tools because it's really, really fun.
00:48:07.769 --> 00:48:09.530
Danielle, so much fun.
00:48:09.530 --> 00:48:10.570
Enjoyed it.
00:48:10.570 --> 00:48:14.090
Um, if if I'm sure we could go on for hours, actually.
00:48:14.090 --> 00:48:22.650
But uh, if folks want to continue this process or want to connect with you or understand what you're doing or what's going on with cartographer, what's the best way for them to do that?
00:48:22.890 --> 00:48:24.330
Yeah, you can find me on LinkedIn.
00:48:24.330 --> 00:48:25.370
I'm pretty active there.
00:48:25.370 --> 00:48:29.130
Um, you can reach us at cartographerconsulting.com.
00:48:29.130 --> 00:48:32.810
Um, I'm Danielle at cartographerconsulting.com if you want to email me.
00:48:32.810 --> 00:48:36.890
Um and then I'm in like a million Slack groups, obviously, including the marketing ops one.
00:48:37.050 --> 00:48:37.450
There you go.
00:48:37.450 --> 00:48:40.650
And you say you're speaking at Massapalooza 25?
00:48:40.970 --> 00:48:41.290
I am.
00:48:41.290 --> 00:48:47.610
I'm speaking with a good friend of mine, Brian D'Andrea, on executive reporting and how to do that in HubSpot.
00:48:47.610 --> 00:48:49.690
It's called peeling the HubSpot Reporting Onion.
00:48:49.930 --> 00:48:50.410
Nice.
00:48:50.410 --> 00:48:50.890
All right.
00:48:50.890 --> 00:48:55.210
Well, hopefully I don't I'm not sure if this will get out before then, but I think it will be close.
00:48:55.210 --> 00:48:56.490
It'll be very close.
00:48:56.490 --> 00:49:00.250
So anyway, well, hopefully that'll drive will traffic to yours.
00:49:00.250 --> 00:49:01.850
So thank you again, Danielle.
00:49:01.850 --> 00:49:04.890
Thanks to our our our audience for continuing to support us.
00:49:04.890 --> 00:49:10.330
If you have ideas for topics or guests or want to be a guest, you can always reach out to Naomi, Mike, or me.
00:49:10.330 --> 00:49:11.210
Till next time.
00:49:11.210 --> 00:49:12.410
Bye everyone.
00:49:12.730 --> 00:49:13.370
Bye.