DH 409 Robert Patin
===
Introduction
---
Jonathan Stark: Hello and welcome to Ditching Hourly. I'm Jonathan Stark. Today I'm joined by guest Robert Patin. Robert, welcome to the show.
Robert Patin: Thank you so much for having me.
Jonathan Stark: Today we're going to talk about how your expertise is your advantage in the world of AI. But first, Robert, could you tell folks a little bit about who you are and what you do?
From Fine Art to Agency Consulting
---
Robert Patin: Sure. So, I mean, I suppose depending on how far back you want to go, but I, you know, in college went to school for fine art, had a wedding photography business for several years, realized I absolutely was not meant to do that, and shut that business down. Went on like a year walkabout and ended up at an agency when I got back to Los Angeles and found this kind of perfect mix between creative, which I absolutely love, but I'm absolutely a spreadsheet mind person, like I'm a total A-brained person. And so it was like this perfect kind of mixture between them, helped grow that agency substantially, went off, did it again, and then started, and I've been consulting with agencies now coming on two decades effectively.
Agencies and the AI Divide
---
Jonathan Stark: That's great. So I would imagine that that group, that audience, is scampering around trying to decide what to do about AI, and having talked to many myself, I know that's true in many cases. But I do see, maybe it's a vocal minority, but I do see people completely embracing it and kind of jumping in with both feet, and then other people kind of just like, I don't know what to do, and they're kind of hunkering down, maybe this will pass, or maybe something obvious will happen. So what's your, what's your high-level take?
Robert Patin: Well, I think that the reality of the world is if you're avoiding it, you're setting up yourself for a lot of pain in the future. I mean, I think that the reality is, is that those that are embracing it a bit more, and I think that there's an over-embracing it as well, where you end up in, you know, AI-oriented slop, and you're not spending the time slowing yourself down enough.
Jonathan Stark: Mm.
Robert Patin: But if you're avoiding it, you're actually creating a whole lot of risk for your business in the future. I mean, the reality is it isn't going away. It is absolutely here to stay, and it is going to transform most, if not all, industries entirely.
AI and Pricing Pressure
---
Jonathan Stark: Yeah. I do think it would have to be some kind of asteroid-level event for it to disappear, whether it gets regulated out of existence or it has a Chernobyl moment and people are just like, absolutely not, get this out of my Gmail, get this out of my Photoshop, but it's in everything. So, um, the main thing with, you know, this is mainly a pricing podcast, and one of the obvious things that people would be wrestling with, and, you know, they're saying they're wrestling with, is that clients are expecting their deliverables to have been cheaper to create now that people can use AI, whether or not they're using it, and that it's creating sort of downward pricing pressure for a lot of people. Is that true in your experience as well? And what is your advice for folks who are facing that kind of a...
Robert Patin: Yeah, it's true in my experience as well. I mean, I think generally there's two components that are happening at the moment. One is the impact of AI, the other piece is economic, but let's focus on the AI component. Any business that is very focused on deliverables is getting a lot of that pressure, and even more so now. The reality of the thing that clients have always cared about, and nothing is really augmented with AI, is they care about the outcome. So what is it going to take? How do I mitigate the risk? How is it that I'm able to achieve the outcome? The other piece that's been layered on with AI is the speed to outcome. So if you're able to encapsulate your expertise, you're able to encapsulate that outcome for the client and being able to reduce risk with AI, without AI, however you're able to go about doing it, but being able to reduce that risk changes the entire conversation. And that's ultimately what every client has always cared about, is how do I achieve the outcome I'm looking for and making sure that I'm not overspending, but I'm also not underspending in what I'm investing in as well.
Who Pockets the AI Savings?
---
Jonathan Stark: Mm, yeah, preaching to the choir here. So I'm always talking about, it's not the only way to price, but value-based pricing is a good way to price, and it forces you in the sales interview to find out what the client is hoping to achieve after you're done. Like, what do they think it's going to unlock? How's it going to make their business better? And I know from talking to thousands of especially developers, but others too, that they don't usually have that conversation. They just sort of have a sales meeting, and the client is like, oh, can you build this feature and that feature and this other thing? And you say, yeah, I can, and you estimate how much time you think it's going to take, and then you put together a proposal, and it's estimated amount of hours times your hourly rate, and then off to the races, and then you go over budget every single time because you underbid it accidentally. So I'm always talking about focusing on the results. How does the client want to be transformed? What do they think your contribution to their success metric might be? And then price based on that. So, even in that case, though, I want to argue against myself. Even in that case, I think there is a probability that clients will still have a little bit of pricing pressure on the seller in this case, if they do believe, rightly or wrongly, that the level of effort for the seller has dramatically decreased. Because there's a psychological truism, a sort of psychological phenomenon called inequity aversion, and if a buyer feels like they're getting the short end of the stick from the seller and the seller is capturing way too much profit, then they'll cut off their nose to spite their face, even though the value of the outcome is maybe 100,000 dollars. Getting charged 10,000 when it's only going to take 10 minutes for the seller doesn't feel, air quotes, fair. I think that this is just me thinking out loud to get your feedback. I think that AI can provide a lot of savings for the seller in terms of the level of effort, and that the real question is going to be, who pockets the difference, and where's the split? So if something that used to take me a month now takes me a day, and I'm still charging the same thing, especially for like a productized service, let's say, then it's like, well, listen, buddy, we could try and do this ourselves with AI if you're just doing it with AI. So first of all, what do you think about that? And then where does the expertise piece come in so that the seller, the person who is the creative, actually can do a better job with AI than the client could possibly have done?
Expertise as the Advantage
---
Robert Patin: So, couple things. One, I do want to push back for a second, and then I will answer your question from a feature set perspective, right? Like, if you're, the assumption is, hey, the features that the client is asking for, and you end up pricing that. I think it's important that you understand, is that even the right feature set? Like, you need to question that premise in the first place, because the base foundation of it is assuming that the client knows what they need in the first place. Like, they're not the expert in the room about this specific thing, and you need to make sure what is the outcome you're looking to achieve, and then work backwards from there. So I just wanted to say that, which I'm sure you've covered plenty of times in the podcast.
Jonathan Stark: Yes.
Robert Patin: But from an expertise perspective, I- I- you- you make an in- a truly valid point. The reality is, is that there's an IP-oriented component when it comes to AI as well. So how is it that you're actually going about the logic? So I- I put things in kind of two different camps. One, from a service-based business, you've got the administrative over- overhead, the operational component that is baked into every single project. The reality is I see a whole lot of opportunity for both the client and for any service-based business to reduce that administrative burden on every project. And there's an incredible amount of utility being able to get rid of that, and largely, I don't think anyone listening to this podcast is particularly enjoying after a meeting putting together the post-meeting notes, and like that's the part that they revel in, that's not the part that they enjoy of the work that they do. So like there's an opportunity to reduce costs there. But when you think about the actual deliverable, the reality of how you go about creating whatever interface, whatever workflow, how it is that you're going about doing something, the incredible power that now exists with AI is that data from for the last couple of decades has entirely been something that has been able to be used by enterprise, and now it's something that is made available to everyone. And there's an incredible amount of data that each one of us is sitting on. So if you've been in business for 5 or 10 years, 15, 20, you have an incredible data set that nobody else has. And so if you have a core level of expertise in a specific industry, in a specific product, in a specific service, there's so much information that you're sitting on from a treasure trove perspective. You need to catalog that, organize that, make it of a meaningful utility that actually reduces a significant amount of risk. And that has an in- an inherent value in and of itself. So you're able to reduce risk with clients if you're having conversations about how it is that you're able to do so, the information that you're relying upon, why it actually sets you apart from being able to work with any of the other service providers. And then from a workflow perspective, I mean, fair or unfair, I don't, I don't know that anything in the world is particularly fair in the first place, so I don't, I don't know that that's a conversation that really should be entering the room, but the reality is, is if someone is able to produce the same outcome for significantly less, then yes, the client should be questioning whether it's fair and whether they're overpaying for it. But if you're able to reduce the risk and able to produce the outcome faster, which is the thing that I meaningfully think is going to change the game even more so, is how quickly can I get to that outcome? And I mean, when conversations with powers that be in the industry that I serve, the, and even when you look at investments from PE firms, that sort of thing, the way that they're looking at valuation today is they're looking at speed to outcome. How quickly can this business, specifically one that is software enabled or AI enabled, how quickly can they achieve the outcome? Because if they're able to achieve it incredibly quickly, means one, they've actually leveraged AI in a meaningful way, but two, they are actually going to be able to outcompete the market. And it's incredibly important to understand the distinction between, hey, I've just made myself faster, or have I actually improved the speed to outcome, and also making sure that I'm able to articulate how I've been able to reduce the risk because of the data set that I'm relying on.
Jonathan Stark: Mm, okay. So two big themes that you've mentioned a couple of times each, both, uh, mitigating risk or reducing risk and speed to outcome. So, in- I think there's some overlap there, actually, because speed to the, like, really delay a project that takes 18 months, let's say, which is not unheard of and or wasn't unheard of in the software space. Uh, that's, that is very risky because there's so much opportunity cost. Like, you could be doing something, the client could be doing something else in that 18 months, but they're focusing on this big internal workflow automation or whatever it is. And if you could get that outcome in a month and know whether or not it's providing value, then, uh, in one sense, the client could experiment a lot more, more quickly, which, uh, if- if you can do it on a shorter time frame, then it re- reduces the risk, even if the price only decreased by half, let's say. Let's say for an 18- it's like, do you want it in 18 months? It'll be 100,000 dollars. Do you want it in 1 month? It'll be 50,000 dollars, so half the price, but way less work for the provider. So I feel like there is a sort of component to risk in just being
Robert Patin: I would have thought that I would have made 150,000 if it would have been in a month, but anyways.
Jonathan Stark: Yeah, I mean, yes, you could certainly argue that, and I do argue that, but normally, I feel like, I feel like that argument needs to be reexamined because of the perception of speed, perception of reduced cost for the seller. I think, I think we need to reexamine it. It's not like, you know, in 2 years, let's say, no one will even remember what it was like when people had to do code by hand. Like, that just won't even be a thing anymore. So everything, so like the, the, the expectations across the entire industry are going to change. So what we're in this phase right now where we sort of got one foot in both worlds, and normally I would say if the seller's cost, the developer's cost wasn't going to meaningfully change, then yes, I've exactly done what you just said, where someone was like, oh, we need this thing done, and I'd give a price, and they'd say, well, it needs to be by Monday, and I would double the price and price and say, well, if you want me to rearrange my plans for the weekend and totally focus on this thing, I'm happy to do it, but you're paying extra. So completely understand the psychology here, but this feels different. This feels, this feels like even if it's, even if it's not different, I think it's going to be a conversation. It's going to be an objection that needs to be dealt with in a sales context. Especially imagine you've been working with a client on and off for 5 years.
Robert Patin: Mhm.
Selling Access to Expertise
---
Jonathan Stark: And they know how long things from you take, and they know, they already know this, and then all of a sudden you get into this scenario where, as the seller, you're like, okay, I'm done with the thing they want, but should I wait 3 months to give it to them? So it seems like it took 3 months instead of 3 days.
Robert Patin: So, I mean, I'm gonna poke at the concept and the premise in the first place, because, like, if you were to talk about the current climate that we're currently sitting in, the SaaS model as an example, right? So, like, the reality of that is this is a product off the shelf that I'm already able to get. It actually doesn't cost the provider any additional money for me to just spin up an additional license, but then we pay incredible amounts of money for software today. I mean, I spend somewhere near 100,000 dollars a year in software because it's a meaningful utility, and that's perfectly fine, and I have no problem with it because it makes me faster, it makes me better, it makes my life less stressful, and it's perfectly fine, so it provides value. And so if you think about it in the same way, right, the reality of any service-based business that has created its own product, multiple products from a reality perspective in these workflows, it's essentially the same thing. The cost, effort, expertise that has gone into that R&D to develop that workflow is what they need to pay for, and it doesn't matter whether it existed already. It's something that has existed for 5 years. It's something that they don't otherwise have access to, the same way that I don't have access to software. But I also want to apply a practical example. Something happened with a client recently. So they actually, they do a lot of, they farm out a lot of research to external research firms. They're a brand and identity messaging agency. And so one of the things of a conversation that they had, right, is that they have an incredible amount of information in the industry that they serve. So they ended up creating synthetic research groups rather than actually needing to actually go and pay 25 dollars, 50 dollars for every single person to respond to this large amount of research, these questions that are being asked, and then fly people for a research group to a focus group for them to be able to ask and then go through this information. They were able to create loads of different synthetic research that allowed for them to do exactly the same thing. And the first set that they did, they did it simultaneously, one with the full research, and then another group of people in the agency spent the money to do them simultaneously, not charging the client for it. And so they did two separate groups doing the exact same thing, and ultimately the findings on the end output of that research was largely the same, then handed off to the brand team that was able to actually go through the branding exercises, right? And so the reality of how they're now pricing it in the future is like, hey, we can go and do traditional research, or we can do synthetic research. So in this example for the agency, they are no longer paying the research firm, you know, 700,000, a half a million, a million dollars for the research that they were formerly doing, but instead actually doing it with synthetic research, something that they've built themselves, that they're charging for access to, that no one else has access to that data set that allows for them to produce research that's largely almost similar, right? Like it's within a margin of error, similar to what the output would have been. And so they're making incredibly higher profit with these types of scopes of work because they're no longer paying a research firm to do so. So it's actually cheaper to the client, so they're actually getting it cheaper, but the agency is making more money. So there's ways for you to go about how is it that within your service model and on the way that you're going about execution, that you're able to reduce costs maybe to an external partner that allows for you to keep more of the money while also being able to produce the same output.
Jonathan Stark: Yeah, I mean, I don't want to give the impression that I disagree with any of that. It's like totally my normal way of, you know, your costs don't matter to the client one way or the other, generally speaking. So if you, like, you can't say to a client, like, oh yeah, I moved from Kentucky to New York City, and now I've got way more expenses, and I've got a big office, and so now you have to pay me way more. And the client's not going to say, oh great, yeah, sure, that's totally fine.
Robert Patin: I'll pay for your Madison Avenue office, why not?
Jonathan Stark: Right. So the client does not care about your costs. It's not persuasive. It's not a persuasive way to raise your prices, for example, and conversely, it's none of their business how much your costs really are. It's like, do you want this outcome? How fast do you want it? Do you believe that I can do it or at least contribute to it in some way? And you just set your prices. So I totally agree with all of that. And that said, I know these conversations are happening, but maybe when I'm hearing, you know, these objections from clients, it probably is more, I'm trying to think of specific examples, but it's, yeah, it's the ones that I've been privy to are really where the client is buying deliverables, and there's never been a conversation about, are these even the right deliverables? What are they for? You know, what are you hoping they're going to do to improve your business? Those conversations just haven't happened. So, okay, so pivoting a little bit, what you just described, the example with the people taking the research in-house using the synthetic research teams, is, just out of curiosity, are they selling that as, it sounded like they're selling it as access to a service, like an ongoing service, or is it project-based?
Escaping Deliverable-Based Work
---
Robert Patin: In that specific example, it's a project that they're selling, right, but they're utilizing, so that phase of the project that would have been the research phase is being done with synthetic research versus an external firm, in that example. I do want to hit on something that you're talking about from a deliverable perspective. One, I think for any business today that is focused on deliverables, you are in a very dangerous place.
Jonathan Stark: Yes, agreed.
Robert Patin: Um,
Jonathan Stark: Yeah.
Robert Patin: And that is true in every industry. You know, if you were to look at media buying agencies, SMMA, social media marketing agencies, those industries, those specific service sets are rife for disruption because so many people were like, I'm buying 5 social media posts.
Jonathan Stark: Yeah.
Robert Patin: Well, okay, those 5 social media posts take you 75% less time, so I expect to be able to pay 75% less money, or I'm just going to do it myself because someone else has created a tool to do so.
Jonathan Stark: Mhm.
Robert Patin: And those aspects of whatever industry of someone listening to this podcast, yeah, there's an aspect of disruption there.
Jonathan Stark: Yeah.
Moving Up the Value Chain
---
Robert Patin: The reality of it is that, and the concept behind the conversation you're having is that the reality of you being a social media marketing agency, as an example, the way that you're going about selection of the type of posts, the way that you're going about hook creation, the way that you're going about when you're posting, what you're posting about, how it is that you're targeting, how you're going about community management, those are really the valuable oriented components of what you do, and you have to move more towards the strategy angle, the expertise component of what it is that you do. If you're focusing on the deliverables, you are in a space that is going to be very painful in the coming years.
Jonathan Stark: Yeah, I agree. Yeah, so I sort of say, like, go up market. When people ask, what should I do, it's like, go up market, like, meaning, I don't mean up market like bigger clients, although that's not a bad idea. I mean going, increasing your altitude of engagement with the client, so, and all of the language that goes around it, so that they're more, the client is more focused on the outcomes and less focused on like what you're gonna do or, or what deliverables are gonna be there. It's like there's, it's like focus on this needle on your dashboard, you know, to the client. Hey client, you've got this dashboard of, of needles that you're looking at, you want to make sure none of them are in the red and all of them are in the green. Which ones do you want me to work on? And then I'll figure out how to do it. And like they need to believe that maybe a social media marketing person or agency can affect this particular needle they're looking at, but the- if the conversation is around 5 posts per month at this much spend, you're having the wrong conversation. The right conversation is, which needle do you want me to move and how much? And then you give me money to do it, I'll go do it, and then we can talk about, you know, whether- assuming it works and everybody's happy. If it doesn't work, then you do a whole different conversation. So what, so what about, oh, go ahead.
Robert Patin: I'm gonna push back for, for, for a piece that I just wanna, like, I think that there's a meaningful piece to just recognize for most people, because like, even the deliverable-based businesses, like, they're not charging for the thinking that they're applying. And one of the things that I can, I'll make this really personal, um, there's loads of different examples of me doing, you know, talks and speaking and even podcasts and content and, you know, consulting with people. Like, the reality is, is there are so many instances where I thought, no one's gonna pay me for that advice because, like, it seems so normal to me.
Jonathan Stark: So obvious, yeah.
Robert Patin: Yeah, because it's something that I talk about every single day. It's something that I, you know, look at the back of my hand, and it's just so incredibly obvious because I've gone through the logic of that hundreds of times, thousands of times before. So it seems innate, it seems obvious to me, but that's not true for someone that doesn't live that every single day, and there's an ownership that we each need to have that someone is in the room with you because they haven't lived the life that you've lived, the expertise that you ultimately have. And as every single one of us, and computers have largely been architected around our brain structure, right? Like if-then logic. So I want you to think about anything from an AI perspective, not anything, but a lot of the components of what you're building would be, well, I have this piece of information and these two pieces of information, right? So, like, I'm being asked a question, there's two potential directions to go, and within those two potential directions, there's multiple different, like, tree logic that might happen, right? So, like, you're going through if-then logic through your head, and the same thing is ultimately happening with what you'd want to be building when it comes to an AI-enabled future, and that thinking is what someone is paying for, and that has always been what they've been paying for. Like, you- you may have democratized yourself and commoditized yourself into a deliverable-based place because that's how- how maybe the market has been asking for it or even how you've just chosen to compete, but that's never what anybody actually wanted. No one specifically wanted- I wanted 5 posts a week because I cared about 5. Like, no, nobody cared.
Cataloging Your Expertise
---
Jonathan Stark: Yeah, yeah. If it worked with one. Yeah, so we're—no, we agree. We're in agreement. So let's drill into that a little bit more because I think this relates to when you mentioned IP earlier. What are you seeing from a tactical standpoint that firms who are doing a good job of this, kind of like embracing the future and focusing on cataloging their knowledge or their expertise, cataloging it internally and then using it to supercharge their delivery? What are some patterns that you're seeing? You know, like, for example, you said, oh, you're sitting on 10 or 20 years of data. It's like, well, is it really? Are they really sitting on that data? I have that much data, but I've been writing every day for 10 years. I don't think most people who have been executing have been cataloging it, right? Like, does it exist in digital format or is it just in their heads? I would bet it's mostly just in their heads. So, now maybe disagree if you want, but is that not the case, or?
Robert Patin: It's a bit of both, I would say, right? I'm gonna list off a litany of different components of data that are potentially incredibly useful. Your email, your project management tool, your Google Drive folder, your Zoom recordings. I mean, I have every single Zoom recording from every single conversation I've had with clients for years. Terabytes.
Jonathan Stark: That's great. Me too, but most people don't. Maybe I'm wrong, maybe I'm wrong. But okay, project management, yes, email, yes. So that's good, that's good.
Robert Patin: Every single, so you've got a load of information in email, you've got a load of information in your Drive folders, you have a load of information in the attachments that have been sent, you have a load of information in your SOWs, you have loads of information in your time tracking data, you have tons of information that's there, and it's how you go about organizing it, and then what are you going to use it for? So, like, how is it that you would use that information? So if you were to think about, I now have the capacity to be able to access, I mean, it's becoming more and more apparent to me in recent months and years that I'm aging and my memory isn't as good as it used to be.
Jonathan Stark: Yeah.
Robert Patin: And if you were to think about, all right, I now have my 20-year-old brain back that has all of the memory and capacity in the world, and I can remember all the things that ultimately were happening, and even that, multiply that by 100. I can access whatever information that I currently have within my computer, within my cloud space. What information would I want to access in order to answer the question that I have to get to the most precise answer that I possibly can? And that's the same thing that you want to be doing from a—now you're taking and putting it in a client's perspective, right? So the same kind of thing. The thing that was incredibly difficult for me going through exercises of how to put together workflows was to slow yourself down enough, and it is incredibly hard. The exercise that I ended up doing is I took several friends of mine and would start to talk to them, like, this is a process that would happen in agency world, and I want you just to ask me questions. So I laid out a scenario, here's the thing that needs to happen. And so a friend of mine, a dog groomer, I asked her to just interview me, like, why would I do this? And like, why this thing? And then why that thing? So I could start to write all the things down that seem so obvious to me now, but were not obvious to her because it's not something that she lives every day. And it helped me slow down enough, and it took a long time to figure that out, to be able to slow down of like, here's all the little pieces of information and questions that I'm asking in order to derive the result and the piece of advice that I would have provided. And that same thing needs to happen, and someone's going to do it, whether that's you, whether that's someone else. And largely, I think that the larger economic sphere of service-based businesses were in this kind of race of one of two things happening: a software company learning to do your service, or you learning to become a software-enabled service business. And that's the race that we're in. And you have an incredible advantage because you have the expertise right now that the software engineers do not have.
Keep the Tool Inside the Service
---
Jonathan Stark: Right. Yeah, I totally agree. And it raises a point that I was kind of glad you answered the question I asked earlier about whether or not the synthetic marketing research company tried to expose this expertise as a SaaS. You said no, they're doing it on a project basis, and that is what I would have recommended if they asked me one way or the other. They've got service business figured out; they know how to run a service business. They don't know how to run a SaaS. It's not the same thing; the numbers are different, everything's different.
Robert Patin: Mhm.
Jonathan Stark: Everything's different. It seems like, oh, we made this incredible internal tool, let's just sell access to the tool. But now you're in a completely different business that you're not familiar with. You're up against a bunch of SaaS companies that know everything. They understand churn and CAC and LTV, and they're thinking about that stuff. It's different.
Robert Patin: Yep.
Jonathan Stark: I would recommend, my default recommendation to someone, you could talk me out of it, or they could talk me out of it, would be to use the tools internally, do not sell access to them. Keep being a service business, and the fact that your clients have trusted you for 5 or 10 years to help them make their business better is still in play. It's still super important, and the kind of engagement that they have, the way that they're engaging with a person instead of a monthly SaaS subscription, you've got the advantage there, I think. You might as well keep it there and then just supercharge your delivery with these in-house tools. I know everyone has the idea like, oh, I'm going to start an AI company and get all this money, I'll go public and blah blah blah. The odds of that are just like, I mean, I've talked to a lot of software developers, and so they have built SaaSes for clients, but they don't have a SaaS model. They're not SaaS people. It's a dev shop or something like that. So anyway, I just wanted to say that out loud and get your take on it.
AI-Powered Agency Case Studies
---
Robert Patin: I mean, I agree, and I've advised clients to do the exact same thing several times. Another example, a web dev and design agency, predominantly on the design side. One of the things that I will not speak exactly what the feature set of the product is, but they have taken a component of the strategy side and information gathering and the direction of how you go about design from a user interface perspective to be guided with an AI tool that they've developed. And the output was for them, and the clients are aware that they're using the tool. They're aware of how they're going about it. It actually has become a, um, diamond in this agency of how it is that they're going about positioning themselves in front of clients, because now there's no longer questions of, like, opinion. It's no longer subjective of why you do something that you're doing, because now it's based in data. And they have almost nearly doubled on average their average SOW value. They have grown this past year, expected to be somewhere in the 28% year over year growth from 2025 into 2026, expectation the same into next year, and they're closing at a much higher rate than they've ever closed before because they're actually talking to clients about the fact that they've mitigated risk with this tool that they've developed. And the reality is, the design component and the amount of time that it takes, their margins are at like 63% gross margin. They're up 13% gross margin, so they're more profitable than they've been before. Clients are happy to pay, you know, higher dollar values because of the fact that they're utilizing this tool. I mean, there's more to it than that, but I fundamentally don't believe that any person, like the experience that I've had when it comes to making an investment in something, the only thing that I truly care about, and I'm an incredibly, I'm a finance person, right? So, like, risk aversion is, like, just built into me to the nth degree, right? Like, I'm also a person that wants to make sure that I'm making the most sound investment I possibly can be, and I'm not overpaying for it. So, like, I'm also looking at, I mean, as an example, the first car I ever purchased, I had, like, 15 different dealerships that were bidding against each other for me to buy my first car, for me to save a thousand dollars, right? Like, that's the kind of person I am.
Jonathan Stark: Okay.
Robert Patin: And, but if I'm buying a service and my objective is to be able to achieve an outcome, like, I do not care. What I want to know is how many times, how are you going about it? How many times have you done this before? What is the service profile, what it is that you're doing? What is the, how likely are you to achieve this outcome? What are the risk factors? What can I do that's going to blow it up and make it less likely? What are you doing to make it more reliable? How are you utilizing information? So, like, I was having a conversation with someone pitching me earlier today, and I had them walk me down all the numbers the entire way through their advice. And first time round, they didn't have it, and I'm like, here's some holes in what you're sharing with me. I need this information in order to make a buying choice. I'm an incredibly analytical buyer. Some people are more emotional. I'm incredibly analytical, and I could not care how much money they are making. Like, you could charge me three times the amount of money, but you've reduced the risk and the numbers still work out, and I feel comfortable in that you're going to achieve the outcome. Like, I could not care less. I could not care less. So the entire concept, like it, and I'll give one more example and my own learning lesson, which is just funny that I learned this in a sales context, is that there was, um, an agency out of New York years ago that I was pitching, and as a Californian, um, New Yorkers and East Coast folks are a little bit more, uh, like rough around the edges, but just like a lot more direct, right?
Jonathan Stark: Yeah, yeah.
Robert Patin: And, um, I was used to, you know, the Californian, like, smile, you know, ear to ear kind of personality, and I thought that they were going to be a pain in the ass. Like, that's just who I thought the client was going to be. So I more than doubled the fee that I was charging. And so I showed up to the meeting. I did not care about winning the business because I was raising the fee to the point that I wanted them to say no to me. I had already gone too far down the sales conversation to not have presented something, so I did, and did not blink an eye, said yes to the price point, and funny enough, they were absolutely lovely people. I really enjoyed working with them, and I learned an incredibly valuable lesson that I was the predominant reason why I was not charging what I felt, what I should have actually been charging, the value that I was ultimately delivering. And it was a massive shift for me understanding that I was the predominant limiting factor. Yeah, there's obviously market implications, like I cannot sell, you know, a 300,000 dollar website to a local barber, so they have to be able to afford it, but as long as I'm barking up the right economic tree, then nobody cares, like they do not care.
Jonathan Stark: Yeah, I mean, you are preaching to the choir. I, I do, I'll push back, some of them do care, but you can find plenty of ones who don't. Some people are just price buyers, and they're gonna, and they don't care about your expertise or your differentiation or your positioning, and you can lowball them, and they'll be the worst client you've had. And so, so yes, obviously we're, we're speaking in generalities.
Robert Patin: Yeah.
Jonathan Stark: But
Robert Patin: Well, those are not a client I wanted to win anyways, you know.
Price Buyers vs. Outcome Buyers
---
Jonathan Stark: That's right. So that's where I'm going next. If you're listening to this and you're like, Robert's full of it, this is not true, it's probably because you're talking to the wrong kinds of clients because they're out there. There are price buyers out there for sure. So, yes, I know a lot of people listening have never had the experience of another kind of buyer, and they're out there. So we're both here to tell you there's another kind of buyer out there who only cares about that list of things that Robert just listed off, like what are the odds of this happening, how sure am I that it's gonna... And then if you can do that, great. To help you believe that that's true, think about your own—I'm talking to the dear listener here—think about your own buying behavior. When you go to a Starbucks and buy a coffee, you're not calculating how much money they're making on the coffee. You just decided that you want...
Robert Patin: I might, but...
Jonathan Stark: ...a vanilla sweet cream cold brew and say, okay, that's what I want right now. It's worth 6 bucks or whatever it costs. And you don't know how much money they're making off of that versus some other thing that they might be selling as a loss leader. It doesn't matter. And that is the way that the listener, that's the way you buy everything, pretty much, you know? So, uh, you know, perhaps Robert is different, and it's worth a thousand bucks to put 15 car dealerships in conflict with each other.
Robert Patin: I was 18 years old, but a thousand bucks meant a lot to me back then.
Navigating the AI Apocalypse
---
Jonathan Stark: Yes, that definitely makes sense. Okay, so really what I'm hearing, and correct me if I'm wrong, but what I'm hearing is you are optimistic. You think that there's a way to navigate this sort of AI apocalypse for creative firms or agencies in a way that is great. And, you know, you've listed a couple of examples where people are doing way better this year, even though AI is a reality, and they're using it, and their clients are aware that they're using it. What would you say are the most important things? Is there something we didn't talk about here that's super important for people to be considering outside of, like, making it less risky, increasing the speed to outcome so they get things sooner? Is there something we haven't touched on, like productizing or projects versus projects, or, I don't know?
Where to Start with AI
---
Robert Patin: I mean, those components really depend on the client and what the service is. I would speak too far in generalities to answer the latter part of the question, but what I will say is the key thing when it comes to the current climate we're in is that if you are afraid of engaging with AI, you shouldn't be. I'm not an engineer; I'm a bit of a techie nerd, but I'm not a software engineer by any means. I now have developers and engineers working with me to create the things I'm working on, but the first versions of what I initially created, I built on my own. You can absolutely do it. It is not that far out of reach to do it yourself. You don't have to create a completely bespoke piece of software to do what you need within your business today. My recommendation is to take a couple of days off from your day-to-day work, figure out what you want to do with a key component of your thinking. There are two camps I would recommend you start with if you haven't done anything with AI and automation in your business today. The first thing I would look at is the basic economics of anything you're determining in business. What is the cost to build it? What is the frequency by which I am doing this, and how long will it take to have a return on investment for the time I'm going to take to build it? Once you have that kind of force ranked, go and build something and see how easy it is to do. It's really not that complicated. Creating skills in Claude of the simple things I'm able to do and just being able to speak into Whisperflow and tell it to do what I want, and it's able to work, is incredibly simple. Thirty minutes can remove hours every single month across my team's time. The other piece is on the expertise side, which is harder and takes more reflection to think through where your superpower is within the work you're doing. There's a component to what you do, right? If you're going to think through, apparently I'm just going to keep using the social media marketing agency example, within the workflow of that example, perhaps it's the ideation, the copy component, the community management, the strategy, or the way you're utilizing influencers to get greater viewership of the work being put out there. What component of the workflow and system you're selling are you incredibly great at? Focus your time and attention there on what meaningfully sets you apart. Is it the data? Is it the amount of information you're holding in your head because you're young and can still hold it all? Where within that workflow are you best in class? If you focus your time and attention there and slow yourself down enough to consider what information you're utilizing and what considerations you're making to give advice to a client, there's an incredible amount of value you can build within your business by focusing your time and attention there. It will meaningfully change things for you in a future market. If you're avoiding it, you shouldn't be. You need to lean in more, and if you've gone too far, like some people are going too far and are just utilizing AI everywhere within their business and having it do the thinking for them, you've gone too far and need to slow down a bit, take your foot off the gas. Like I mentioned earlier, me needing to be interviewed by a friend of mine to slow myself down enough to even think through the logic I would have been going through, I think it just shows and depicts the need of how far removed you have to get to even be able to look back at yourself in the mirror to see where it actually matters and how you're utilizing information to guide someone through the process they're following.
Jonathan Stark: Hmm, I love the interview idea. That's really good. Well, cool. That was super helpful. I think that's probably a great place to leave it. Where can folks go to find out more about what you're doing?
Robert Patin: You can go to creativeagencysuccess.com, or you can follow me on LinkedIn. It's just LinkedIn.com/creativeagencysuccess as well.
Jonathan Stark: Robert, thanks so much for joining me.
Robert Patin: Thanks for having me.
Jonathan Stark: All right, folks, that's it for this week. I'm Jonathan Stark, and I hope you join me again next time for Ditching Hourly. Bye.