TRANSCRIPT 🔗
WEBVTT
00:00:06.799 --> 00:00:20.239
Welcome to the Stats Backwards Podcast, where we reverse engineer the success of fast-growing Stats firms and explore strategies CMOs and CEOs are using to drive their businesses forward.
00:00:24.239 --> 00:00:33.200
Welcome to StAS Backwards, a podcast that helps staff and AI CEOs and go-to-market leaders accelerate growth and enhance profitability.
00:00:33.439 --> 00:00:50.880
Our guest today is Cliff Simon, CEO and founder of Polaris Ops, a go-to-market advisory firm that helps SaaS companies and private equity operating partners evaluate AI readiness and deploy agentic AI capabilities across their revenue operations stack.
00:00:51.039 --> 00:00:52.799
Welcome to the podcast, Cliff.
00:00:53.119 --> 00:00:54.079
Thanks for having me, Dan.
00:00:54.240 --> 00:00:54.479
How are you?
00:00:54.719 --> 00:00:57.920
I'm great and excited to dig in with you.
00:00:58.079 --> 00:01:05.040
But before we jump into this episode, could you please tell us a little bit about yourself and your company, Polaris Ops?
00:01:05.359 --> 00:01:08.239
Yeah, I've been in GoToMarket for going on about two decades now.
00:01:08.480 --> 00:01:26.719
Enjoyed being on the bigger side of things at a Fortune 20 and then uh spent the majority of my career helping companies go from zero to 10, 0 to 15, but also on the consulting side, having helped companies anywhere from, I don't know, 10, 20 million all the way up to, you know, however many billion.
00:01:26.879 --> 00:01:29.040
So I've gotten to see a lot over the last few years.
00:01:29.200 --> 00:01:45.359
And then as far as what I and my team do, we focus mostly on helping companies understand where they are in their AI journey and help them deploy that within their systems and within their customer lifecycle, whether that is through a myriad of systems that they own today or helping them build custom AI solutions.
00:01:45.760 --> 00:01:55.200
Yeah, it's super important to be thoughtful and kind of detailed about how you're going to deploy AI and take advantage of those capabilities too, right?
00:01:55.280 --> 00:01:56.879
It's a lot of gains to be made.
00:01:57.200 --> 00:02:05.040
So when we did our prep, you mentioned that AI is really becoming a mandate from boards and private equity operating partners.
00:02:05.200 --> 00:02:10.719
But you also said that most go-to-market teams don't actually know how to operationalize AI.
00:02:10.960 --> 00:02:18.479
Where do you see the biggest gap in the pressure to quote unquote do AI and what companies can realistically execute today?
00:02:18.800 --> 00:02:22.719
There's a ton of pressure, not just from the board, from CEO down, right?
00:02:22.879 --> 00:02:24.879
We have to use it, we have to use it, we have to use it.
00:02:24.960 --> 00:02:27.840
But the problem is most companies aren't putting that into a programmatic fashion.
00:02:28.000 --> 00:02:33.520
There isn't a set way or motion or enablement around how we're going to be using AI.
00:02:33.759 --> 00:02:39.840
It's very much been go play with it, go figure it out, and sort of report back what you've been able to do.
00:02:40.159 --> 00:02:50.960
The places where there is the easiest level of entry and previous to the last couple of months was using ChatGPT, perplexity, the baseline stuff, right?
00:02:51.120 --> 00:02:55.520
Now with Cloud Cowork coming out, I'm seeing a ton of folks really drive into that.
00:02:55.680 --> 00:02:59.919
We're starting to see more and more platforms come in with an MCP capability.
00:03:00.159 --> 00:03:03.280
And that's driving a lot of the user adoption.
00:03:03.520 --> 00:03:19.919
But again, folks that are starting to jump over the chasm on these kinds of things are the people who are already putting in a significant amount of time off the clock to really do this because this is the next step in their career or the next step in how we operate as an industry.
00:03:20.159 --> 00:03:28.240
So yeah, we're seeing so many people that are really interested in this, putting in three, four, five, 10 hours a week outside of their nine to five, right?
00:03:28.400 --> 00:03:29.120
Yeah, it's amazing.
00:03:29.199 --> 00:03:37.360
We actually have a once and and probably future client, a guy named David Gabriel at a small software company called Rumbics.
00:03:37.520 --> 00:03:46.159
And he's built an entire agentic product marketing capability kind of as his own project, building it in the open.
00:03:46.240 --> 00:03:52.560
So I think you're exactly on where leaders and thoughtful people are going.
00:03:52.960 --> 00:04:04.479
And by the way, David's not even a programmer, has no technical talent, and is building a pretty robust go-to-market like enhancement on his own, basically.
00:04:04.719 --> 00:04:06.000
And those things are really cool.
00:04:06.159 --> 00:04:22.560
The challenge there becomes if you are not someone who's familiar with the different regulations, you're not familiar with best practices around security and those protocols, you might be very well building something that opens up a whole host of challenges, you know, Pandora's box, if you will.
00:04:22.800 --> 00:04:30.879
So you really want to make sure that you're testing one of the guys that works for us, built a pen testing tool for these vibe coded solutions.
00:04:31.199 --> 00:04:43.839
Tested it with a friend of his just looking at the URL, and just from that exposed URL, was able to go in and find private information, billing information, credit card numbers, things like that on the Stripe account.
00:04:43.920 --> 00:04:51.279
Like, so you have to be really careful with the things that you're actually making visible without recognizing it.
00:04:51.680 --> 00:04:58.079
Yeah, there's the exposure of the data, and there's also exposure to your internal systems, right?
00:04:58.160 --> 00:05:01.360
So building in isolation, probably a really good idea.
00:05:01.600 --> 00:05:06.720
Also,
Load full transcript
interestingly, just back to David, he implemented a way for people to engage with this system.
00:05:06.879 --> 00:05:15.519
They're using a Trello board to task the agents so that there's sort of an arm's length between the agent and the rest of the organization.
00:05:15.839 --> 00:05:21.759
So kind of a lot to think about in terms of the security and vulnerabilities that you might be creating.
00:05:22.000 --> 00:05:28.319
Are there ways that people are like reporting up and measuring this we're doing AI stuff?
00:05:28.399 --> 00:05:32.800
Like, what are the milestones that you see people committing to and achieving?
00:05:33.040 --> 00:05:47.360
So I think the most common ones are lines of code that are being written but with AI on the engineering side of the house within operating teams and within more specifically RevOps and VisOps teams, we're seeing hours saved.
00:05:47.600 --> 00:05:54.959
So if you would typically take a set of tasks, break them down into a level of effort of, you know, the way we would do it, a small, medium, large, right?
00:05:55.120 --> 00:06:04.959
Zero to five, five to 10, 10 to 15 hours for a task, and then break that specific task down into other tickets, more seeing people measure in time saved.
00:06:05.199 --> 00:06:13.199
So if a typical task used to take you 40 hours, but now because of AI, you're able to do it in five, you've gained 35 hours, right?
00:06:13.279 --> 00:06:16.800
And they're they're cataloging that across their team over the course of a month or a quarter.
00:06:17.040 --> 00:06:21.680
Oh, so that's real opportunities to demonstrate the return on investment.
00:06:21.920 --> 00:06:22.240
That's right.
00:06:22.399 --> 00:06:22.480
Yeah.
00:06:22.560 --> 00:06:27.600
And then if you want to, you multiply that against the average salary of that team member plus their fully burdened costs.
00:06:27.680 --> 00:06:32.240
And now you can roll that up and say, this is what we would have paid to do this thing, but now we can do it this much quicker.
00:06:32.560 --> 00:06:37.120
It's really interesting seeing the kind of metering the effort and go to market.
00:06:37.279 --> 00:06:40.399
That's something maybe that's coming more fully, right?
00:06:40.480 --> 00:06:45.439
That people are going to be much more able to measure what it takes to do things.
00:06:45.759 --> 00:06:52.959
I think the other way that we can measure is especially in a PLG motion, we're starting to see RevOps teams no longer be a cost center.
00:06:53.040 --> 00:06:58.800
We're seeing RevOps teams create automations and workflows and capabilities where they can start generating revenue.
00:06:58.959 --> 00:07:02.240
We don't need to have a salesperson in the loop on some of those areas.
00:07:02.399 --> 00:07:10.639
And if the RevOps team can architect the right customer journey, put the right systems in place to activate on that journey and bring that to a revenue perspective.
00:07:10.879 --> 00:07:12.639
Now they're covering their costs, right?
00:07:12.800 --> 00:07:16.079
It's a completely different paradigm than what we've thought about for the last 15 years.
00:07:16.319 --> 00:07:21.759
That is pretty amazing and would obviously spur more investment in those areas, right?
00:07:21.920 --> 00:07:22.959
So very positive.
00:07:23.199 --> 00:07:26.000
I want to start with where you begin an engagement with clients.
00:07:26.079 --> 00:07:32.560
And you said to me that you usually start with an AI readiness assessment before even touching the tech stack.
00:07:32.959 --> 00:07:35.680
Can you talk to us about what you're looking at there?
00:07:35.839 --> 00:07:42.319
What are the signals you look for that indicate a company might be ready to operational AI in go to market?
00:07:42.639 --> 00:07:45.839
And like if not, you know, what needs to be done usually.
00:07:46.560 --> 00:07:48.480
It's all the foundational components, right?
00:07:48.639 --> 00:08:10.639
We've spent so much time as an industry over the last 15 years growing as quickly as we wanted to, as quickly as we could, without ever really putting in the foundations, data hygiene, definitions within an organization, understanding how the customer journey actually moves from stage to stage to stage, both lead lifecycle, contact lifecycle, account lifecycle.
00:08:10.720 --> 00:08:13.680
We need to have all that metadata accurate.
00:08:13.920 --> 00:08:15.040
It has to be correct.
00:08:15.199 --> 00:08:23.439
Because if it's not, and we're not able to tell the AI what it's supposed to be doing, how could it ever get there?
00:08:23.680 --> 00:08:29.120
We need to have accuracy and we need to have clear direction and clear metrics of what success looks like.
00:08:29.199 --> 00:08:30.480
And we have to teach it that.
00:08:30.720 --> 00:08:32.159
Once you give it that, great.
00:08:32.240 --> 00:08:36.159
But if you don't have those pieces in place, it's never going to work the way you want it to.
00:08:36.480 --> 00:08:44.799
Can you maybe dig into recent engagements and talk about things you've discovered and remediations that were needed to be able to make next steps?
00:08:45.120 --> 00:08:48.000
Again, foundationally, things need to be entered into the CRM.
00:08:48.080 --> 00:08:51.200
They can't live in a hundred different Google Sheets, right?
00:08:51.519 --> 00:08:54.480
It's impossible to pull that all in into one place.
00:08:54.559 --> 00:08:55.519
It's very time consuming.
00:08:55.600 --> 00:08:58.879
It's very manual and gone through that process now with one of our customers.
00:08:59.200 --> 00:09:16.399
But in order to help them get to a place where they can actualize their dream of leveraging AI, which they're starting to do with Cloud directly inside of Salesforce now, there's so many other components that need to happen, business processes that needed to be documented, levels of maturity that needed to be created.
00:09:16.639 --> 00:09:19.679
So that is a very large-scale
effort.
00:09:19.840 --> 00:09:28.399
But once you get those pieces in place, you can start looking for the corollaries and the data patterns that will help you actually make decisions on where to drive the business forward.
00:09:28.799 --> 00:09:41.279
So if you're working within the CRM, right, the sort of system of the source of truth, we get everybody to a level of hygiene where we can actually put AI against it.
00:09:41.519 --> 00:09:45.279
Is the resulting workflow creating better data?
00:09:45.440 --> 00:09:51.600
Like our salespeople now, is it easier for them to be doing their part of getting the data in?
00:09:51.759 --> 00:09:52.639
And is that helping us?
00:09:52.960 --> 00:09:53.120
Yeah.
00:09:53.200 --> 00:10:01.679
So if you're using a good call recording technology, you make sure that you're driving enablement around that, that people are asking questions in the right way so that it's grabbing that information.
00:10:01.840 --> 00:10:04.320
And then the AI on the back end is filling in all that.
00:10:04.480 --> 00:10:07.039
This is the case of the pool was dirty.
00:10:07.120 --> 00:10:17.200
We cleaned all the crap out of the pool, you put it where it had to go, you clean it out, you put a new filter in, now it's working, but we still got to make sure people aren't just throwing random crap into the pool manually, right?
00:10:17.440 --> 00:10:25.759
I love the idea of farming the recordings to do the work that the salespeople just by nature don't want to do, right?
00:10:26.080 --> 00:10:27.519
It's not that they don't want to do it even.
00:10:27.679 --> 00:10:31.360
It's it's low quality work for them to be doing.
00:10:31.600 --> 00:10:40.240
If I'm paying an enterprise seller 303, 350 KOTE, I want that person talking to people.
00:10:40.399 --> 00:10:46.000
I don't want to be spending a quarter of their time paying them to type into a system.
00:10:46.159 --> 00:10:46.799
It's stupid.
00:10:46.879 --> 00:10:49.600
It's uh or a stewardship of capital.
00:10:49.840 --> 00:10:59.039
I could see a guy like Brian Burns saying those exact words like, why should you be forcing your people to do that when we can get the AI to do that work for you, right?
00:10:59.279 --> 00:11:05.679
Even if you only get 15% back from those high-performing salespeople, that's a lot.
00:11:06.240 --> 00:11:08.399
That's a lot of hundred percent.
00:11:08.639 --> 00:11:15.120
I want to dig a little deeper into kind of where AI agents do operational work.
00:11:15.440 --> 00:11:21.279
You know, can they effectively do, you know, total addressable market analysis?
00:11:21.519 --> 00:11:23.440
Can they do lead routing?
00:11:23.600 --> 00:11:27.360
And what are the signals they're able to create within the GTM world?
00:11:27.679 --> 00:11:39.600
Yes, you can have it look at all of your existing customer base, ideally, the customer base of the ones who are paying you the most, who are buying more of your services year over year, who are consistently renewing, right?
00:11:39.840 --> 00:11:47.360
We want to take that archetype and create that, and then have the AI go out and look into the open field for anything else that exists that looks like that.
00:11:49.840 --> 00:11:54.240
I think that's pretty straightforward and something that AI is very good at.
00:11:54.399 --> 00:12:02.720
But it's again, it needs a human in the loop to make sure that it's checking all those different parameters and that that's being refined over time.
00:12:02.960 --> 00:12:14.960
The other component there, and I this goes across all of AI, is we as executives need to understand that we are not buying an implementation the way that we've always thought of it.
00:12:15.120 --> 00:12:25.440
This is not me buying something off of the shelf that is going to be implemented within a two-week to two months to one quarter timeline and be set it and forget it and done.
00:12:25.600 --> 00:12:28.879
These AI solutions, especially when they're tied into multiple LLMs.
00:12:28.960 --> 00:12:36.960
You know, you've you're tied into anthropic, you're tied into open, you're tied into perplexity, you're tied into Garak, all of those have multiple models that are constantly being updated.
00:12:37.200 --> 00:12:45.440
The API maintenance here and the maintenance of how those LLMs are interacting with the components that you've built is a daily task.
00:12:45.679 --> 00:12:49.759
It is a very different level of intensity when it comes to managing it.
00:12:49.840 --> 00:12:53.600
And the cost of ownership is wildly different than traditional SaaS.
00:12:53.840 --> 00:12:54.960
So that's something to think about.
00:12:55.120 --> 00:12:56.720
And then also credit usage, et cetera.
00:12:56.879 --> 00:13:00.240
With that caveat said, yes, you can go out and build lead routing.
00:13:00.399 --> 00:13:01.600
HubSpot's a great example, right?
00:13:01.679 --> 00:13:04.000
We're partners with Line Data, with Chili Piper.
00:13:04.080 --> 00:13:07.200
Both those guys do a great job of doing lead routing into Salesforce.
00:13:07.279 --> 00:13:09.360
There's not really anything that does the lead routing into HubSpot.
00:13:09.519 --> 00:13:10.879
So we went out and built it.
00:13:11.120 --> 00:13:14.320
And HubSpot's great because they've got awesome documentation out there.
00:13:14.399 --> 00:13:18.480
They have a very robust and open API that we can access directly from an MCP server.
00:13:18.639 --> 00:13:21.120
Boom, boom, boom, send things back and forth.
00:13:21.279 --> 00:13:27.600
And you know, we can have very defined territories, very defined routing guidance based off of any of the firmographic information.
00:13:27.679 --> 00:13:29.440
So I think that's really straightforward.
00:13:29.600 --> 00:13:32.080
Salesforce is a little bit more touchy at the moment.
00:13:32.159 --> 00:13:34.559
And I think that's why there's still a bit of a moat there.
00:13:34.720 --> 00:13:38.639
But we'll see how that comes
around over the next six to 12 months.
00:13:38.799 --> 00:13:43.519
When it comes to the custom signal component, you can get really, really interesting.
00:13:44.000 --> 00:13:50.559
Anything that you want to get your hands on, you probably can, as long as you can find it publicly on the internet somewhere.
00:13:50.879 --> 00:14:00.320
The signal, signal identification and using those trigger events are a big part of what we see as helping sellers be more efficient, right?
00:14:00.559 --> 00:14:02.720
We're pointing them in pointing them in the direction.
00:14:02.799 --> 00:14:06.080
Let's say you've got 5,000 companies you might ever sell to.
00:14:06.399 --> 00:14:15.679
You have 10 sales executives, they really need to have some way to prioritize other than the obvious somebody comes to the website and asks for help.
00:14:15.919 --> 00:14:16.399
Yeah, yeah.
00:14:16.480 --> 00:14:19.919
So in that case, you're what you're doing is you're carving together all the right pieces.
00:14:20.080 --> 00:14:21.600
We have the right firmographic information.
00:14:21.759 --> 00:14:24.399
We know they're a company that's a potential client for us.
00:14:24.639 --> 00:14:25.600
We know they're big enough.
00:14:25.759 --> 00:14:31.200
We know they typically have the right employee count, whatever it might be, that they have the problem that our thing solves.
00:14:31.360 --> 00:14:32.480
What other things are we looking for?
00:14:32.559 --> 00:14:36.799
Yes, we're looking for new job postings in our typical personas.
00:14:37.279 --> 00:14:40.240
We're looking at new people in seat over the last 12 months.
00:14:40.399 --> 00:14:42.720
We're looking for a growing team.
00:14:42.960 --> 00:14:46.240
We're looking for changes in pricing on their website.
00:14:46.480 --> 00:14:49.679
We're looking for one of my customers is APAR software.
00:14:49.759 --> 00:14:54.399
We're looking to see if there's a payments link anywhere on their website, your typical fundraising information.
00:14:54.480 --> 00:14:56.720
But most of those are lagging indicators, right?
00:14:56.879 --> 00:15:08.559
We want to try to look for indicators that are going to be things that matter so we can find the people who are most likely going to be a customer of ours in the future, not necessarily just the three to five percent of people who are in a buying motion today.
00:15:08.799 --> 00:15:19.360
So one that a lot of our customers who happen to sell into legacy industry are finding very interesting is what we've called a succession planning capability or succession planning signal.
00:15:19.600 --> 00:15:31.840
We're finding companies where there is a boomer parent with a Gen X or a geriatric millennial child in the business in an operations or finance role.
00:15:32.000 --> 00:15:37.840
And we're pairing that together alongside all those other signals, and it's leading to some really great results.
00:15:38.080 --> 00:15:42.080
So interesting because you're trying to get ahead of them before they go through this process.
00:15:42.320 --> 00:15:43.759
They haven't digitized yet.
00:15:43.919 --> 00:15:53.360
And now you tie all that together, you've got a really good package of like, okay, a business where you know the business owner is going to be transacting out in the next few years just based off of demographic.
00:15:53.519 --> 00:15:54.960
Have you thought through this problem yet?
00:15:55.120 --> 00:16:00.159
And it leads to a very different type of conversation than if you're just trying to sell somebody something, you know?
00:16:00.559 --> 00:16:00.720
Yeah.
00:16:00.799 --> 00:16:07.679
So like figuring out what are the forward-looking insights here is a way to use these pretty commercially available tools now, right?
00:16:07.840 --> 00:16:08.000
Yeah.
00:16:08.240 --> 00:16:12.320
Now you guys also do some of your own research, right?
00:16:12.559 --> 00:16:22.000
I think you mentioned that many of the AI tools in our go-to-market stack depend on other platforms and data sources, something you alluded to earlier in the conversation.
00:16:22.320 --> 00:16:25.600
Can you highlight a couple of the risks that are created?
00:16:25.759 --> 00:16:33.759
Again, I think you sort of touched on it, but for these SaaS companies that are trying to adopt tools quickly, what are the top risks to be aware of?
00:16:34.080 --> 00:16:34.320
Yeah.
00:16:34.399 --> 00:16:42.960
So 80% of what we've seen to be the agentic go-to-market market is built on the other 80% of the market.
00:16:43.200 --> 00:17:01.360
So people who have really good contact level data are going and getting account level data from other sources, and vice versa, majority of the industry is still using either SmartLead or instantly as the sending capability to turn their system or their platform into a system of action so that it can actually go out and do those outbounds.
00:17:01.519 --> 00:17:10.640
The challenge with any of those is if a component fails or a company gets acquired or gets shut down, because most of these companies are fairly early, still sub$5 million in revenue.
00:17:10.799 --> 00:17:14.000
Now you've got a gaping hole that that company has to go fill.
00:17:14.079 --> 00:17:21.839
And for whatever period of time, you may not be able to use the software the way that you thought you were going to, which means your go-to-market motion is now at risk.
00:17:22.079 --> 00:17:28.960
Because if you're not generating the pipeline and doing the things today that you know you need to be doing, you're going to have a gap three, six months down the road.
00:17:29.279 --> 00:17:30.720
It's a significant risk.
00:17:30.960 --> 00:17:51.039
And the folks that came out on top from a technical perspective, within the research that we did, all scored as high as they did because they had proprietary technology that was built in that had redundancies that allowed them to continue to operate appropriately without having external risk pressures
from other vendors.
00:17:51.440 --> 00:17:53.440
I want to jump to your own research.
00:17:53.680 --> 00:17:57.039
You've been researching Agentic AI across GoToMarket.
00:17:57.279 --> 00:17:58.880
You've started to publish your findings.
00:17:59.039 --> 00:18:02.880
And for those, for those of your fans, this is a new firm, right?
00:18:02.960 --> 00:18:05.359
Polaris, a little less than a year old.
00:18:05.599 --> 00:18:07.440
You've been publishing your findings.
00:18:07.599 --> 00:18:17.200
And I'm wondering if there's a place that you publish or plan to publish the a full research report and if you want to share what's included and when that would be available.
00:18:17.440 --> 00:18:17.680
Yeah.
00:18:17.759 --> 00:18:21.599
So uh this year we did a 42 vendor diagnostic.
00:18:21.680 --> 00:18:27.039
We rank them as systems of action, systems of record, systems of information.
00:18:27.279 --> 00:18:32.240
And all of that's going to be available on our website, which is Polarisops.com.
00:18:32.319 --> 00:18:35.759
And we'll also put it out on our newsletter, put it out on LinkedIn.
00:18:35.920 --> 00:18:37.440
But yeah, we'll share that with everybody.
00:18:37.680 --> 00:18:53.119
Jumping back to one last topic, when you do complete a readiness assessment, a major decision that you told us about is whether to build AI capabilities internally or continue this process of stitching things together with the inherent opportunities and risks.
00:18:53.440 --> 00:18:55.039
This is like an age-old problem, right?
00:18:55.200 --> 00:19:02.400
Build versus buy, and especially at your larger customers or larger clients of your firm, they have the capability to build, right?
00:19:02.720 --> 00:19:04.880
So how are we making those decisions?
00:19:05.039 --> 00:19:08.400
Is it the same build versus buy decision we've always made?
00:19:08.640 --> 00:19:16.079
Core capability, core competitive set capability, or is it often better to buy, but buyer beware?
00:19:16.400 --> 00:19:34.400
I think that particular conversation has shifted dramatically because the old cost of building something meant that I was taking developers or engineers off of my product team and pushing them to something that was customer-facing right here or on the go-to-market side, right?
00:19:34.480 --> 00:19:38.960
Wasn't customer facing anymore, wasn't building something for the consumer, but I was building something for my internal team.
00:19:39.119 --> 00:19:41.119
And it used to take a really long time.
00:19:41.359 --> 00:19:44.079
Now you can build products in like a weekend.
00:19:44.240 --> 00:19:46.880
You know, something that gets the job done.
00:19:47.039 --> 00:19:48.319
I'm not saying it's a finalized thing.
00:19:48.400 --> 00:19:57.599
I'm not saying it's gotta pass all the security requirements, but the speed at which you can build and the cost at which you can build is incredible.
00:19:57.759 --> 00:20:03.440
Yes, I know there's an an ever increasing
cost when it comes to credit spend, et cetera, but it's it's so much faster.
00:20:03.519 --> 00:20:05.440
It's incredible how fast you can build.
00:20:05.680 --> 00:20:16.480
I'm really nervous for a majority of the tech companies that are like that 2013 to 2021 vintage.
00:20:16.799 --> 00:20:17.119
Right?
00:20:17.279 --> 00:20:29.039
That's there's a lot of tech today that can be rebuilt so much faster, so much cheaper as a lower back end cost by a single person that it used to take teams of 20 to 50 people to build.
00:20:29.359 --> 00:20:31.759
So that I think that's a very different thing.
00:20:32.000 --> 00:20:38.000
At those larger firms, it's not about do they have the capability, it's do they have the bandwidth.
00:20:38.400 --> 00:20:43.359
You've got smart folks, but they're probably already doing other things.
00:20:43.519 --> 00:20:47.279
How much time can you peel off and allow them to go out and experiment?
00:20:47.440 --> 00:20:52.160
I hear from people day in and day out that they feel like they can't keep up with the pace of change.
00:20:52.559 --> 00:21:00.240
I hear that from my team, and they're the ones that are doing the research and getting out there and like looking at all these tools and like they're constantly like, holy crap.
00:21:00.480 --> 00:21:04.960
So it it's very difficult, I think, for anyone in general to stay on top of it.
00:21:05.039 --> 00:21:08.559
You sort of have to pick a lane, see what you're interested in, and continue to build.
00:21:08.720 --> 00:21:22.799
If you if you're a company and you're thinking about build versus buy today, I'd really try to assess if you don't have a team internally that could go and tackle this for two weeks and see if you get to a product that's close enough.
00:21:23.200 --> 00:21:32.079
Because there are things that were not on the market three months ago that exist today that you could just buy, which is wild.
00:21:32.240 --> 00:21:34.400
But you can go out and build it probably just half the time.
00:21:34.480 --> 00:21:38.559
I just keep being asked to build things and then something else pops up, and something else pops up.
00:21:38.799 --> 00:21:41.519
It's it's very interesting to see both sides of the market.
00:21:41.839 --> 00:21:42.400
I agree with you.
00:21:42.480 --> 00:21:48.640
You know, early in my career I built stuff for IBM and Citibank, and they were person year projects, right?
00:21:48.720 --> 00:21:53.440
We would have eight people work for two years on one big push.
00:21:53.680 --> 00:21:57.039
And today, you know, you have eight people work for a week and you have a product.
00:21:57.119 --> 00:21:58.880
It's a it's a really different life.
00:21:59.200 --> 00:21:59.759
My buddy still.
00:22:00.079 --> 00:22:03.519
Phil, who was on on my podcast most recently was working with Verizon.
00:22:03.599 --> 00:22:20.160
He told me experimentation there was yeah, we take you know a PM, an engineer, a product manager, and maybe a fourth resource if necessary, and we just toss them at a problem and toss like, I don't know, seven or eight million dollars at it in in overall cost and spending.
00:22:20.319 --> 00:22:25.680
And that's an experiment in over a quarter, and they can generate tens, if not hundreds of millions of dollars.
00:22:25.759 --> 00:22:30.079
It's like that's crazy that things are driving to that point, you know.
00:22:30.319 --> 00:22:31.759
It's like a yin and yang, right?
00:22:31.839 --> 00:22:42.480
There's like immense positives possible out of all this technology and you know, some scary stuff either for existing software companies or people in career transition as a result of the tech.
00:22:42.799 --> 00:22:46.000
Lots of opportunity, lots of potential risk.
00:22:46.240 --> 00:22:53.279
And if people want to navigate that more effectively, Cliff, you probably could help them take a look at their plans.
00:22:53.519 --> 00:22:57.599
Please let listeners know how they might reach you and your new company, PolarisOps.
00:22:57.920 --> 00:23:01.839
Easiest way, you can go to PolarisOps.com or you can reach out to me directly on LinkedIn.
00:23:01.920 --> 00:23:04.240
I'm the Cliff Simon with the cloud in front of his name.
00:23:04.480 --> 00:23:07.359
My LinkedIn is LinkedIn slash in slash Ken Lempit.
00:23:07.599 --> 00:23:16.079
If you want to learn more about our advertising and go-to-market agency for SaaS and AI companies, we're at AustinLawrence.com.
00:23:16.480 --> 00:23:22.000
And if you haven't subscribed to the SAS Backwards Podcast yet, please do so wherever they're distributed.
00:23:22.160 --> 00:23:26.640
Cliff Simon, thanks so much for joining us again on the SAS Backwards Podcast.
00:23:27.119 --> 00:23:32.559
Thanks for listening to the SAS Backwards Podcast, brought to you by Austin Lawrence Group.
00:23:32.799 --> 00:23:40.319
We're a growth marketing agency that helps SaaS firms reduce churn, accelerate sales, and generate demand.
00:23:40.559 --> 00:23:44.799
Learn more about us at www.austinlawrence.com.
00:23:44.960 --> 00:23:52.799
You can email Ken Lempett at kl ataustinlawrence.com about any SaaS marketing or customer retention subject.
00:23:53.039 --> 00:23:56.799
We hope you'll subscribe and thanks again for listening.