Debug Information

Processing Details

• VTT File: 12079990-338-how-tech-debt-hurts-your-small-business-with-corey-winter.vtt
• Model Used: models/gemini-2.5-flash-lite
• Processing Time: September 12, 2025 at 10:01 AM
• Total Chunks: 2
• Transcript Length: 80,697 characters
• Caption Count: 770 captions
• Temperature: 0.1
• Max Tokens: 1024
• Top-K: Not used
• Top-P: 0.95
• Candidate Count: 1
• Affiliate Tag: spokengoods-20

Prompts Used

Prompt 1: Context Setup

You are an expert data extractor tasked with analyzing a podcast transcript. 
I will provide you with part 1 of 2 from a podcast transcript. 
I will then ask you to extract different types of information from this content in subsequent messages. Please confirm you have received and understood the transcript content.

Transcript section:
[00:00:00.480 --> 00:00:07.360] Look, payday is awesome, but running payroll, calculating taxes and deductions, staying compliant, that's not easy.
[00:00:07.360 --> 00:00:09.360] Unless, of course, you have Gusto.
[00:00:09.360 --> 00:00:14.400] Gusto is a simple online payroll and benefits tool built for small businesses like yours.
[00:00:14.400 --> 00:00:18.400] Gusto gets your team paid while automatically filing your payroll taxes.
[00:00:18.400 --> 00:00:25.600] Plus, you can offer benefits like 401k, health insurance, and workers' comp, and it makes onboarding new employees a breeze.
[00:00:25.600 --> 00:00:28.320] We love it so much, we really do use it ourselves.
[00:00:28.320 --> 00:00:34.800] And we have four years, and I personally recommend you give it a try, no matter how small your business is.
[00:00:34.800 --> 00:00:38.880] And to sweeten the deal, just for listening today, you also get three months free.
[00:00:38.880 --> 00:00:41.360] Go to gusto.com slash beingboss.
[00:00:41.360 --> 00:00:45.120] That's gusto.com/slash beingboss.
[00:00:46.400 --> 00:00:53.840] Welcome to Being Boss, a podcast for creatives, business owners, and entrepreneurs who want to take control of their work and live life on their own terms.
[00:00:53.840 --> 00:01:05.520] I'm your host, Emily Thompson, and in this episode, I'm not only joined by my podcast companion, Corey Winter, but I'm interviewing him on building a good online presence for your business from the start.
[00:01:05.520 --> 00:01:10.560] Or in other words, not accumulating a little something called tech debt.
[00:01:10.560 --> 00:01:16.000] You can find all the tools, books, and links we reference on the show notes at www.beingboss.club.
[00:01:16.000 --> 00:01:21.120] And if you like this episode, be sure to subscribe to the show and share us with a friend.
[00:01:23.040 --> 00:01:28.240] Having a fulfilling career and succeeding in business are what we're all here to accomplish, right?
[00:01:28.240 --> 00:01:36.240] Well, if it resonates, then I've got a new show for you to check out that's all about educating you on how to best market yourself in the new digital age.
[00:01:36.240 --> 00:01:44.720] It's called Big Brand Energy, hosted by Sophie Wilson, brought to you by the HubSpot Podcast Network, the audio destination for business professionals.
[00:01:44.720 --> 00:01:53.920] With episodes on building an authentic brand and how business and online dating are the same, you'll get a fresh take on online marketing in the new year.
[00:01:53.920 --> 00:01:58.360] Listen to Big Brand Energy wherever you get your podcasts.
[00:01:57.840 --> 00:02:02.680] So, I'm a companion again.
[00:02:03.000 --> 00:02:15.720] Well, I figured if you were going to make such a fuss about being a pal bro, a bro pal, then I would lateral move you back to companion.
[00:02:16.920 --> 00:02:17.720] Okay, yes.
[00:02:17.720 --> 00:02:20.920] In my mind, it was lateral previously.
[00:02:21.400 --> 00:02:28.040] Um, so you are back to companion, but you're also interviewee today.
[00:02:28.040 --> 00:02:29.400] How does that feel?
[00:02:29.400 --> 00:02:33.640] A little stressful, not sure I can actually put out words.
[00:02:33.640 --> 00:02:35.400] We'll see how this goes.
[00:02:35.400 --> 00:02:36.920] Good thing you edited.
[00:02:36.920 --> 00:02:38.680] Yep.
[00:02:38.840 --> 00:02:40.920] Then I'm very excited about this one.
[00:02:40.920 --> 00:02:47.400] A couple of weeks ago, or every couple of weeks, the Being Boss team gets together and we're like, okay, what is Emily talking about?
[00:02:47.400 --> 00:02:50.920] Basically, over the next couple of episodes.
[00:02:50.920 --> 00:02:53.080] And everyone always throws out some really good ideas.
[00:02:53.080 --> 00:02:57.560] You should all know that all of these episodes that you are delivered, it ain't just me.
[00:02:57.560 --> 00:03:06.280] There is a content team that is helping me come up with ideas and help create agendas and ask questions and those sorts of things.
[00:03:06.280 --> 00:03:08.520] And a lot of it comes from the Being Boss community.
[00:03:08.520 --> 00:03:12.680] If you are not a member of the Being Boss community, I highly recommend you go check that place out.
[00:03:12.680 --> 00:03:17.960] There's all kinds of conversations that are being had on, obviously, creative entrepreneurship.
[00:03:17.960 --> 00:03:26.360] And a lot of those conversations do make or do inspire the conversations that we are having here on this show.
[00:03:26.680 --> 00:03:32.600] So we were recently in one of those meetings with the team, and Corey yells out tech debt.
[00:03:32.920 --> 00:03:33.560] Yes.
[00:03:33.560 --> 00:03:35.480] And I was like, I don't even know what that is.
[00:03:35.480 --> 00:03:36.600] What are you saying to me?
[00:03:36.600 --> 00:03:37.880] Are those words?
[00:03:38.200 --> 00:03:38.760] Those are words.
[00:03:38.920 --> 00:03:39.720] And he went on to explain.
[00:03:40.040 --> 00:03:41.160] Those are words.
[00:03:41.160 --> 00:03:48.240] So I have a bone to pick with the internet as a whole.
[00:03:48.880 --> 00:03:50.080] I got a couple of those two.
[00:03:50.320 --> 00:03:51.520] Continue.
[00:03:51.840 --> 00:03:57.840] And specifically with people that build things on the internet.
[00:03:57.840 --> 00:03:59.440] Because there's this little phrase.
[00:03:59.440 --> 00:04:03.920] It's a little buzzword, buzz phrase called tech debt.
[00:04:04.240 --> 00:04:08.160] It was a term coined by Ward.
[00:04:08.160 --> 00:04:08.640] Ward?
[00:04:08.800 --> 00:04:09.360] Ward?
[00:04:09.360 --> 00:04:10.640] Ward Cunningham.
[00:04:11.040 --> 00:04:11.680] Ward.
[00:04:11.920 --> 00:04:12.960] Ward Cunningham.
[00:04:12.960 --> 00:04:14.160] He is a computer programmer.
[00:04:14.320 --> 00:04:16.880] He has been in the game for decades.
[00:04:16.880 --> 00:04:19.600] He's actually the original inventor of the wiki.
[00:04:19.600 --> 00:04:21.920] Not Wikipedia, but like the thing wiki.
[00:04:21.920 --> 00:04:23.680] He invented the wiki.
[00:04:23.680 --> 00:04:26.320] And he coined the term tech debt.
[00:04:26.320 --> 00:04:34.400] It's a term specifically used for coding and programming, but it can be used in a broader sense, just technology in general.
[00:04:34.400 --> 00:04:47.680] And the idea is that it's the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.
[00:04:48.880 --> 00:04:53.040] And so this is all going to tie into working smarter, not harder.
[00:04:53.040 --> 00:04:59.120] Really, actually, maybe even the opposite, working harder in the beginning so you can work smarter later.
[00:04:59.760 --> 00:05:20.400] And this has come up a lot in the client work that I do, so much so that I think it's kind of accidentally become what I specialize in because I've had a lot of clients come to me that previously maybe worked with another developer or did everything themselves and they did things in a way that is not sustainable.
[00:05:20.400 --> 00:05:31.240] And so, trying to change anything in the future or trying to do things, just changing things up in general, is even harder than it should have been if they had just done things in a different way to begin with.
[00:05:31.560 --> 00:05:38.840] So, that's my bone to pick with the internet: a lot of things that just have not been done well because they weren't thought all the way through.
[00:05:39.960 --> 00:05:40.440] Right.
[00:05:40.440 --> 00:05:42.440] Okay, that is a nice little bone to pick.
[00:05:42.440 --> 00:05:45.240] Love that for you and the internet.
[00:05:45.560 --> 00:05:50.680] Whenever you started explaining this to me a little bit, it all made sense.
[00:05:51.000 --> 00:06:04.200] And for me, I recalled years at Indie Shopography where there wasn't a phrase for this, but I was literally trying to sell people on not having tech debt.
[00:06:04.200 --> 00:06:09.160] And what this looks like and why this matters, just sort of bring it into some context.
[00:06:09.160 --> 00:06:12.120] I know it's not just websites, it's so many things.
[00:06:12.120 --> 00:06:13.800] Back in all of the things, right?
[00:06:13.800 --> 00:06:14.680] It's all of the things.
[00:06:14.680 --> 00:06:20.440] Back in the day, whenever I was working in websites, it was around building e-commerce sites.
[00:06:20.440 --> 00:06:23.480] And people would come to me going, Well, what's the difference?
[00:06:23.480 --> 00:06:37.800] And, you know, going with you and this like big e-commerce platform as I'm just getting started in business and just going and starting at that point, it was like a very small and not very highly functional Squarespace site or whatever it may be.
[00:06:38.040 --> 00:06:41.560] I mean, this is 10 years ago, y'all, plus years ago.
[00:06:42.280 --> 00:06:46.280] Squarespace was a baby with no functionality back then.
[00:06:46.280 --> 00:06:50.920] And so it was like a fully functioning website or just like a landing page.
[00:06:50.920 --> 00:06:55.320] And I was explaining to them, you're going to pay one way or the other.
[00:06:55.320 --> 00:06:57.480] The question is, do you want to pay again in a year?
[00:06:57.480 --> 00:06:57.880] Yeah.
[00:06:58.200 --> 00:07:09.880] Or do you want to do the thing that you are trying to build with the things that you need to build the thing that you want to build and not having to do another rebuild super soon?
[00:07:09.880 --> 00:07:13.880] Because the goal is that you outgrow the basic thing really quickly.
[00:07:13.880 --> 00:07:14.680] That's why you're here.
[00:07:14.680 --> 00:07:15.120] Yes.
[00:07:14.760 --> 00:07:16.880] To start the business and do the thing.
[00:07:17.520 --> 00:07:27.760] So it often looks like I think probably the context for everyone listening to this is websites, you can also think like some payment processor aspects of this as well.
[00:07:27.760 --> 00:07:35.280] Also, I think email marketing platforms is a really great thing to look at whenever we're having this conversation.
[00:07:35.280 --> 00:07:36.160] What am I missing?
[00:07:36.160 --> 00:07:39.280] So those were actually the big ones that I was going to really pull examples from.
[00:07:39.280 --> 00:07:53.280] So yes, definitely build on your website, email marketing platforms/slash customer relationship platforms, but also just team management things like project management software and team communication software.
[00:07:53.280 --> 00:07:56.720] But also, this could apply to in-person hardware as well.
[00:07:56.720 --> 00:08:00.560] If you run a retail shop, so like your POS system and things like that.
[00:08:00.560 --> 00:08:07.200] So just computers, anything, any tech in your business could apply to this.
[00:08:07.680 --> 00:08:08.000] Right.
[00:08:08.000 --> 00:08:19.920] It's opting for the cheap and fast now as opposed to investing in the good now so that you don't experience growing pains quite so quickly.
[00:08:19.920 --> 00:08:25.840] And yes, and this is all essentially one big metaphor for monetary debt.
[00:08:25.840 --> 00:08:27.440] So it also has interest.
[00:08:27.440 --> 00:08:35.360] So if technical debt is not repaid, it can accumulate interest, making it harder to implement changes in the future.
[00:08:35.360 --> 00:08:37.040] Absolutely.
[00:08:37.040 --> 00:08:41.600] This is what I was always selling people on when it came to e-commerce back in the day, right?
[00:08:41.920 --> 00:08:44.400] Where this is going to be a big project.
[00:08:44.400 --> 00:08:49.760] And I would always get questions of like, well, can't we just like migrate things over like in a year whenever I'm done?
[00:08:49.760 --> 00:09:05.480] Yes, if you want to basically pay just as much as you would pay for me to do it right right now, because those migrations I think are usually more difficult than just setting it up well the first time.
[00:09:05.720 --> 00:09:09.720] I also think of literally all the times that we have moved email marketing platforms.
[00:09:09.720 --> 00:09:10.760] Oh my God.
[00:09:10.760 --> 00:09:11.240] Yeah.
[00:09:11.240 --> 00:09:15.240] Like that is literally Corey's job.
[00:09:16.200 --> 00:09:19.320] So like I'm like the least fun thing ever, but I haven't done that in a long time.
[00:09:19.320 --> 00:09:20.120] Thank you, Corey.
[00:09:20.440 --> 00:09:35.640] And I was actually going to say, I'm going to save the bigger examples for later in the episode, but actually now that you mentioned that, moving e-commerce or email marketing systems, one big example comes to mind that's actually something we're currently dealing with at BiddyTarot.
[00:09:35.720 --> 00:09:42.280] And for the most part, I'm not going to mention client names or anything during this episode because most of these issues are painting a customer in a bad light.
[00:09:42.280 --> 00:09:50.520] So I'm not going to mention customer names or anything during this episode, but I will mention BiddyTarot right now specifically because we have been using Entreport.
[00:09:50.600 --> 00:09:52.680] They have been using Entreport for 10 years.
[00:09:52.680 --> 00:09:55.480] Like they're one of the oldest Entreport clients.
[00:09:55.480 --> 00:10:05.560] And Entreport is not really meant to be used for companies of a large scale, like a company that has, you know, seven-figure, eight-figure businesses.
[00:10:05.560 --> 00:10:08.600] They're really meant for like mid-sized businesses.
[00:10:08.600 --> 00:10:13.080] But back when BiddyTarot started using Entreport, it was a mid-sized business.
[00:10:13.080 --> 00:10:27.000] But now we have ingrained Entreport so heavily into the business, like with all the APIs that tie into delivering content and empowering our e-commerce systems, all of our products, everything goes through Entreport.
[00:10:27.320 --> 00:10:36.600] We have hundreds of thousands of contacts in Entreport, thousands of emails, who knows how many transactions and things.
[00:10:36.600 --> 00:10:42.040] We are so integrated into the Entreport ecosystem that it's impossible to get out of it.
[00:10:42.040 --> 00:10:57.280] Like, we want to move to a better platform for the size of business that we are, but we, it's almost impossible at this point because we did not, where I say we, I was not here during this time, but the team as a whole did not anticipate the growth.
[00:10:57.280 --> 00:11:01.680] And so they kind of locked themselves in, and now it's almost impossible to get out of it.
[00:11:01.680 --> 00:11:04.880] Yeah, that's a really interesting scenario.
[00:11:04.880 --> 00:11:10.320] It gives me anxiety just hearing you say those things because I see how that can happen.
[00:11:10.320 --> 00:11:17.520] I also do want to say that time is a big element of this conversation as well.
[00:11:17.520 --> 00:11:17.920] Yes.
[00:11:17.920 --> 00:11:24.080] Whereas I imagine in that scenario, and I can think of a couple of like personal scenarios as well.
[00:11:24.080 --> 00:11:33.280] You know, back in those like baby days of the internet, love that, or baby days of like regular people doing e-commerce on the internet, right?
[00:11:33.280 --> 00:11:34.800] There weren't very many options.
[00:11:34.800 --> 00:11:36.880] And so you just went with what was there.
[00:11:37.600 --> 00:11:39.520] And then things grew and changed.
[00:11:39.520 --> 00:11:48.560] And then other options became available that were better options for what you do, but you were already in this thing and you didn't migrate then because things were going to, or like new features were coming or whatever it may be.
[00:11:48.560 --> 00:12:10.160] And so it's easy to just find yourself with debt, with tech debt as a product of operating on the internet, which really even makes it more important than to really sit down and have the kinds of conversations very early on around what your goals are, what sort of business you want to grow.
[00:12:10.560 --> 00:12:22.640] And really, this is a reason to think about business plans in a way that, you know, we don't really talk about a ton here, but is really important for building this infrastructure for your business.
[00:12:22.640 --> 00:12:25.680] So, anyway, that's just like a nutshell what we're talking about today.
[00:12:25.680 --> 00:12:33.480] I hope everyone can understand why this is so important and how it really does affect each and every one of us in some aspect or another.
[00:12:33.720 --> 00:12:42.120] I have some really great examples of how this has affected my work over the years and multiple different kinds of businesses, and I'm excited to dive in.
[00:12:42.120 --> 00:12:44.520] So, Corey, first question for you, sir.
[00:12:44.520 --> 00:12:51.400] Actually, really quick, if you wouldn't mind giving me like a 30-second why you can talk about this.
[00:12:51.400 --> 00:12:54.840] Oh, ooh, put this is gonna stroke my ego.
[00:12:54.840 --> 00:13:01.320] So, I know I have a huge tech background in my career.
[00:13:01.320 --> 00:13:09.160] I have been building websites for 20-ish years now, but then my technical expertise has grown.
[00:13:09.160 --> 00:13:14.680] So, obviously, we worked full-time on website development at IndieShopography for several years.
[00:13:14.840 --> 00:13:19.480] My expertise grew into podcast editing about eight, nine years ago.
[00:13:19.720 --> 00:13:34.200] And then at Biddy Tarot and other clients, I have grown my expertise into email marketing systems and funnel building and a whole wide range of people have worked with huge clients to clean up their tech systems.
[00:13:34.200 --> 00:13:46.040] So, it's really my specialty nowadays is focusing on the tech debt that clients and companies have and helping them address those issues and figuring out a path forward.
[00:13:46.040 --> 00:13:52.520] So, this really is my specialty nowadays for being boss, but also for Bitty Tarot and all the clients I still have.
[00:13:52.520 --> 00:13:52.920] Yeah.
[00:13:52.920 --> 00:13:57.000] Oh, I love that because you have done this for us for years.
[00:13:57.640 --> 00:14:00.200] I love that it has like such a nerdy little name.
[00:14:00.200 --> 00:14:00.920] All right, perfect.
[00:14:00.920 --> 00:14:02.840] So, let's like really dive into this.
[00:14:02.840 --> 00:14:09.640] And a couple of key little aspects to this really big conversation.
[00:14:09.640 --> 00:14:11.800] First, why does it matter?
[00:14:11.800 --> 00:14:17.520] And really, what does it hurt to accumulate tech debt?
[00:14:14.040 --> 00:14:28.240] Why should people listening to this think ahead and plan for bigger, better solutions as opposed to going with the fast, cheap, and easy of right now?
[00:14:28.240 --> 00:14:28.480] Yes.
[00:14:28.480 --> 00:14:33.520] And I do want to preface this by saying tech debt does not have to be a bad thing.
[00:14:33.520 --> 00:14:40.560] Just like financial debt does not have to be a bad thing, as long as you are aware of the debt.
[00:14:40.560 --> 00:14:42.240] But we'll talk about that in a second.
[00:14:42.240 --> 00:14:46.320] So, as far as what tech debt hurts, there's four big things.
[00:14:46.320 --> 00:14:51.920] The first big thing is dissatisfied users or customers.
[00:14:51.920 --> 00:15:21.280] So if you're putting out some kind of customer-facing thing, maybe something like a new website or e-course platform or anything like that, if you're building it or maybe going to a pre-built platform that maybe does not have all the functionality you need, it results in a bad user experience, which turns into possibly refunds and poor reviews and poor recommendations and just a bad customer experience.
[00:15:21.280 --> 00:15:25.600] Yeah, or like I imagine part of this is also lost sales.
[00:15:25.600 --> 00:15:26.000] Yes.
[00:15:26.000 --> 00:15:39.600] I was having a conversation with someone recently who, and now that I think about this, it is a tech debt issue of using an old platform or using the platform she'd been using for years.
[00:15:39.600 --> 00:15:47.360] But because she'd had it for so long, it did not have functionality that allowed her team to easily build sales pages.
[00:15:47.360 --> 00:15:50.240] So it was like a little more intense for them to do it.
[00:15:50.240 --> 00:15:51.040] They thought they could do it.
[00:15:51.040 --> 00:15:51.520] They went in.
[00:15:51.520 --> 00:15:52.640] They thought they did it.
[00:15:52.640 --> 00:15:55.200] Launched the thing, didn't test.
[00:15:55.200 --> 00:15:56.800] The button didn't work.
[00:15:56.800 --> 00:15:57.280] Yeah.
[00:15:57.520 --> 00:16:01.240] So she launched the thing and had people going to it.
[00:16:01.240 --> 00:16:07.080] And it took a couple of hours for someone to finally email and be like, I tried to buy this thing and I could not.
[00:16:07.080 --> 00:16:19.800] An issue, like a dissatisfied user literally lost sales because using an old platform that was not as easy for her team to utilize to create the things she needed to launch what she was launching.
[00:16:19.800 --> 00:16:20.280] Yes.
[00:16:20.280 --> 00:16:22.920] And that actually ties into another one of these.
[00:16:22.920 --> 00:16:26.520] So the next thing is limited innovation.
[00:16:26.760 --> 00:16:39.560] So when tech debt is severe, developers or if it's, you know, maybe your team or something needs to continue servicing the issues instead of devoting time to building new innovative features.
[00:16:39.560 --> 00:16:45.400] So if your team is spending all their time fixing things instead of building new things, that's tech debt.
[00:16:45.400 --> 00:16:45.800] Yeah.
[00:16:45.800 --> 00:16:49.080] Oh, that's literally interest that you're paying.
[00:16:49.080 --> 00:16:49.560] Yes.
[00:16:49.560 --> 00:16:52.840] Oh, and labor hours.
[00:16:52.840 --> 00:16:53.720] Snap.
[00:16:53.720 --> 00:16:54.360] I love that.
[00:16:54.360 --> 00:16:56.920] I mean, I don't, but like, yes, that's real.
[00:16:56.920 --> 00:16:57.960] That's real, real.
[00:16:57.960 --> 00:17:04.200] Okay, I want to share another aspect of this too, or maybe a way you can see red flags.
[00:17:04.200 --> 00:17:15.720] Or whenever I'm searching for a new platform for anything, like, you know, social media manager, email marketing platform, whatever, whatever, I always go look at their change logs.
[00:17:15.720 --> 00:17:16.120] Yes.
[00:17:16.120 --> 00:17:19.320] Or like their announcements for new features.
[00:17:19.320 --> 00:17:23.000] Are they managing their own platform?
[00:17:23.000 --> 00:17:26.200] Are they creating their own new features?
[00:17:26.200 --> 00:17:31.160] Are they like listening to the customers and creating little buttons and widgets and all the things that they need?
[00:17:31.160 --> 00:17:35.080] Or have they not updated their own software in three months?
[00:17:35.080 --> 00:17:39.000] Because sometimes the tech debt isn't just your fault.
[00:17:39.000 --> 00:17:41.400] It's also the fault of the platform.
[00:17:41.400 --> 00:17:54.640] And so, that's a way that I, um, it's a way, or one of the things I do when I'm searching for new platforms for things is I'm checking their updates to see how active their team is.
[00:17:54.640 --> 00:18:00.640] Yeah, because if their team is not active, this limited innovation is going to happen even faster.
[00:18:00.640 --> 00:18:02.880] Yeah, so actually, I'm glad you said that.
[00:18:02.880 --> 00:18:09.520] So, over at Biddy Tarot, we're all up in our metrics reporting project right now.
[00:18:09.520 --> 00:18:21.280] We're trying to reinvent how we're doing metrics reporting and data calculations and everything just to kind of centralize it and make sure we're getting a clearer picture on all of our conversion points and stuff like that.
[00:18:21.440 --> 00:18:31.360] So, we're trying to find a new dashboard platform that actually integrates with Entreport and everything that can build like pretty graphs and stuff like that.
[00:18:31.360 --> 00:18:39.920] And we came across one service that does have an Entreport integration, which is relatively rare, and it looked great.
[00:18:39.920 --> 00:18:43.680] But I dove a little bit deeper into this platform.
[00:18:43.680 --> 00:18:48.160] Their website, the copyright date, was like four years old.
[00:18:48.640 --> 00:18:53.200] Their Facebook group had their Facebook page had not been updated in a couple of years.
[00:18:53.200 --> 00:19:00.240] And so it was just not painting a pretty picture that this was actually a platform that was constantly being kept up to date.
[00:19:00.240 --> 00:19:01.600] And so that was kind of like a red flag.
[00:19:01.600 --> 00:19:05.040] Like, yeah, maybe it works right now, but will it work a year from now?
[00:19:05.040 --> 00:19:05.680] Yeah.
[00:19:05.680 --> 00:19:12.400] So I would not recommend signing up for that because you might have to start all over again if the software ever actually stops working.
[00:19:12.400 --> 00:19:12.960] Yep.
[00:19:12.960 --> 00:19:14.480] Oh, that's, yeah.
[00:19:14.480 --> 00:19:15.600] Check those things.
[00:19:15.920 --> 00:19:17.360] You also mentioned integrations.
[00:19:17.360 --> 00:19:23.280] I also like to look at what things integrate with because if there's just a couple, they're not doing much.
[00:19:23.280 --> 00:19:27.600] If they have like a really great integration list, then they're doing their job.
[00:19:27.600 --> 00:19:33.240] If they have too many integrations, I'm like, something's a little odd here.
[00:19:33.480 --> 00:19:34.440] Are these all real?
[00:19:29.840 --> 00:19:37.400] Yeah, so we're getting into kind of the prevention things.
[00:19:37.400 --> 00:19:38.600] So what to look out for?
[00:19:39.160 --> 00:19:40.040] Oh, am I getting ahead of us?
[00:19:40.120 --> 00:19:40.520] No, you're fine.
[00:19:40.520 --> 00:19:41.080] You're fine at all.
[00:19:44.360 --> 00:19:45.560] Then what's next?
[00:19:45.560 --> 00:19:47.160] What is another one of these four?
[00:19:47.160 --> 00:19:47.400] Yes.
[00:19:47.400 --> 00:19:50.760] So number three is longer development cycles.
[00:19:51.320 --> 00:19:57.480] So yet again, this is all coming from a tech perspective, so like coding and stuff, but it could be applied in a broader sense.
[00:19:57.640 --> 00:20:11.240] So as tech tech debt worsens, it becomes harder for developers to work within the existing code base, splitting time between developing new features and correcting old ones, which slows the build process and delays time to market.
[00:20:11.240 --> 00:20:18.120] So this could apply for obviously website development, but also maybe email marketing funnels and stuff like that.
[00:20:18.440 --> 00:20:21.720] I mean, I think about this with our old website projects.
[00:20:22.280 --> 00:20:31.800] I never loved it when someone came to me with an old, clunky website and wanted to update that thing.
[00:20:31.800 --> 00:20:32.280] Yeah.
[00:20:32.280 --> 00:20:33.000] Right?
[00:20:33.000 --> 00:20:34.120] Absolutely not.
[00:20:34.120 --> 00:20:45.880] I will create for you a whole new website and I will do that painful migration process and I will do the thing, but going in and one, figuring out someone else's code or figuring actually the same thing for email flows.
[00:20:45.880 --> 00:20:49.640] For like people build email flows differently.
[00:20:49.640 --> 00:20:52.600] I can't look at your email flows and make any sense of it.
[00:20:52.600 --> 00:20:54.920] And I know that you can't look at mine and make any sense of it.
[00:20:54.920 --> 00:20:57.080] Like we build them completely differently.
[00:20:57.080 --> 00:21:13.880] And so it's going to take twice as long for me to just get in there and figure something out, like what I'm looking at before I go and start tweaking and building, as opposed to just doing something fresh over here, completely separate from that thing that I don't understand.
[00:21:13.880 --> 00:21:18.400] Yeah, this is kind of where the Bandaid solution comes into play.
[00:21:18.400 --> 00:21:28.560] If you identify a problem and you implement a simple fix with the idea that, oh, we'll come back and fix it later, but then you never come back and fix it later.
[00:21:28.560 --> 00:21:41.760] Then when you actually come in to do something new, it's a whole bigger issue because you're not only having to try to build something new, you're also having to deal with this age-old issue that it's going to take hours and hours and hours to fix.
[00:21:41.760 --> 00:21:42.080] Yeah.
[00:21:42.080 --> 00:21:48.480] So the idea is that instead, you should keep things more maintained, more up to date on a consistent basis.
[00:21:48.480 --> 00:21:52.720] So when it does come time to do something new, it's a lot easier and simpler.
[00:21:52.720 --> 00:21:53.920] Amen to that.
[00:21:53.920 --> 00:21:55.280] What's the fourth one?
[00:21:55.280 --> 00:21:57.200] The fourth one that's a scary one.
[00:21:57.200 --> 00:21:59.840] It's security problems.
[00:22:00.160 --> 00:22:00.800] Yeah.
[00:22:01.120 --> 00:22:02.160] Real, real.
[00:22:02.160 --> 00:22:14.080] So this one, yet again, tying more heavily into the code side of things, but nowadays it could factor into two-factor authentication or making sure your passwords are regularly changed out and stuff like that.
[00:22:14.080 --> 00:22:21.040] So poorly written code is often poorly secured, which can introduce unexpected vulnerabilities to enterprise software systems.
[00:22:21.040 --> 00:22:29.680] So applying this in a broader sense, if you go make your password password, that's first of all, just lazy.
[00:22:29.680 --> 00:22:30.560] So come on.
[00:22:30.560 --> 00:22:36.560] But also, that's pretty poorly secured and it's going to open you up to vulnerabilities.
[00:22:36.560 --> 00:22:47.440] So taking the time at the beginning of the project or beginning of creating your account to set a more secure password or what have you, it's going to save you issues in the long run.
[00:22:47.440 --> 00:22:47.920] Yeah.
[00:22:47.920 --> 00:22:58.560] I will just say, even looking at the platform thing again, a platform that will allow you to create a password that is just password is also a red flag.
[00:22:58.880 --> 00:23:00.680] They should be more secure.
[00:23:00.680 --> 00:23:02.760] And security is a real one.
[00:23:02.760 --> 00:23:06.120] And it's become more important.
[00:22:59.840 --> 00:23:06.760] It's always been important.
[00:23:07.000 --> 00:23:07.480] It's always been important.
[00:23:07.560 --> 00:23:14.520] It's become more at the forefront of conversations, especially since GDPR happened a couple of years ago.
[00:23:14.520 --> 00:23:25.000] If you look, Google it, where in the EU, they did some legislation around keeping people's personal information safe on the internet.
[00:23:25.240 --> 00:23:28.040] That affected all of us in one way or another.
[00:23:28.040 --> 00:23:29.400] So I have two thoughts.
[00:23:29.400 --> 00:23:44.040] So that sucked because that was kind of forced upon us tech debt because everybody on the internet had to scramble to implement these changes to keep customers' data private and give them options to opt out of things.
[00:23:44.040 --> 00:23:46.440] So that was things we were not prepared for.
[00:23:46.520 --> 00:23:48.040] Like no one was prepared for.
[00:23:48.040 --> 00:23:54.840] And so when that was put into effect, everyone had to scramble to address that debt immediately, which kind of sucked.
[00:23:54.840 --> 00:24:02.280] But this also ties into our examples section of this podcast, which is where I get to kind of tell some Corey stories.
[00:24:02.280 --> 00:24:06.200] So this is going to be a four-parter now, everybody.
[00:24:06.840 --> 00:24:21.240] So the big scary one, kind of tying into the security we were just talking about, I had a client whose website was infected by malware and it created a whole snowball of big issues.
[00:24:21.560 --> 00:24:27.480] And so going back, I guess, three years ago, they paid no attention to securing their website.
[00:24:27.480 --> 00:24:30.360] So they didn't have any kind of firewalls in place.
[00:24:30.360 --> 00:24:35.080] They didn't have any kind of like CAPTCHAs or anything on their admin interface.
[00:24:35.080 --> 00:24:41.480] So if some kind of robot or bad actor wanted to get low-hanging fruit.
[00:24:41.560 --> 00:24:45.040] Yeah, low-hanging fruit, unsecured server, everything.
[00:24:44.600 --> 00:24:47.840] So their site got infected by malware.
[00:24:48.480 --> 00:24:52.880] You know, it was all kinds of pop-ups and things.
[00:24:52.880 --> 00:24:54.480] I'll just put it at that.
[00:24:56.240 --> 00:24:58.480] So that created issue number one.
[00:24:58.480 --> 00:25:06.960] Just their site was taken over by unseemly things, which had to be addressed because they were actually, this was a law firm.
[00:25:06.960 --> 00:25:15.600] And so they were having like clients that were coming to them for legal things and their website was showing them porn.
[00:25:15.600 --> 00:25:17.200] So big issue, right?
[00:25:17.200 --> 00:25:17.840] Yeah, yeah.
[00:25:18.080 --> 00:25:25.520] So first of all, that just that malware was a headache to clean up because it was infecting all parts of the website.
[00:25:25.520 --> 00:25:27.200] It was on the back end of the website.
[00:25:27.200 --> 00:25:28.960] It was on the server.
[00:25:28.960 --> 00:25:30.160] It was in the database.
[00:25:30.160 --> 00:25:31.040] It was all over.
[00:25:31.040 --> 00:25:32.800] It was a nightmare to clean up.
[00:25:32.800 --> 00:25:49.680] Two years later, the website is still showing up on malware blacklists because robots of the security providers that scanned the website back when it was still infected, they have not updated their listings for this website.
[00:25:49.680 --> 00:25:57.280] So a lot of security providers still think the website is infected, even though it's confirmed clean by multiple providers.
[00:25:57.280 --> 00:26:02.320] So this is causing the website to be blocked by different internet providers.
[00:26:02.320 --> 00:26:11.360] So ATT, actually, one of the bigger providers in the country, is actually still blocking this website for a lot of people, even though the website is clean.
[00:26:11.360 --> 00:26:12.800] It's been verified clean.
[00:26:12.800 --> 00:26:15.200] But ATT still thinks it's infected.
[00:26:15.200 --> 00:26:18.720] That was an awful story before it turned into an awful story.
[00:26:18.720 --> 00:26:22.640] And actually, it snowballs because of malware infections.
[00:26:22.640 --> 00:26:25.120] It's actually a domain reputation thing.
[00:26:25.120 --> 00:26:29.040] So it's infecting, or it's affecting their email delivery ability as well.
[00:26:29.040 --> 00:26:35.080] So they're having an issue emailing clients because their domain name is also being flagged as malware.
[00:26:35.720 --> 00:26:38.200] So it's affecting their entire business.
[00:26:38.200 --> 00:26:38.920] Ew.
[00:26:38.920 --> 00:26:39.480] Yeah.
[00:26:39.480 --> 00:26:39.960] Okay.
[00:26:39.960 --> 00:26:41.880] You started, I think, with, was that the best one?
[00:26:41.880 --> 00:26:44.680] That was the scariest one.
[00:26:44.680 --> 00:26:46.280] Okay, that is scary.
[00:26:47.000 --> 00:26:48.680] That is scary.
[00:26:49.960 --> 00:26:53.960] Growing your business can get complicated, but the tech you use shouldn't.
[00:26:53.960 --> 00:26:58.280] That's why HubSpot's CRM platform is easy to learn, use, and love.
[00:26:58.280 --> 00:27:11.080] Hear it from a real boss using HubSpot to grow their business better in 2023 and get a special offer of 20% off on eligible plans at hubspot.com/slash being boss.
[00:27:11.400 --> 00:27:12.840] My name is Kelly Kimple.
[00:27:12.840 --> 00:27:15.480] I'm the CEO of Adventures and Good Company.
[00:27:15.480 --> 00:27:19.960] As you know, growing a business is hard, and the tools you use should help make things easier.
[00:27:19.960 --> 00:27:23.240] It's important to us to have tools that work the way we do.
[00:27:23.240 --> 00:27:26.760] HubSpot CRM platform has seamlessly scaled with our needs.
[00:27:26.760 --> 00:27:34.760] We were seeking a more efficient way to extend the longevity of communicating with our current customers while still nurturing the relationships and new and potential customers.
[00:27:34.760 --> 00:27:42.200] With HubSpot, our team is able to work all in one place to create a customized experience for every encounter at every stage of the customer's journey.
[00:27:42.200 --> 00:27:47.000] The HubSpot CRM platform makes daily tasks easier for all of our departments to use.
[00:27:47.000 --> 00:27:58.040] From the marketing team to customer service to operations, our busy work gets automated, and we can spend time doing what we do best, creating experiences of a lifetime for women seeking new adventures.
[00:27:58.040 --> 00:28:03.400] We're able to grow our database with free forms and landing pages that convert visitors into qualified leads.
[00:28:03.400 --> 00:28:09.160] HubSpot CRM automatically organizes, enriches, and tracks each content into a tidy timeline.
[00:28:09.160 --> 00:28:16.000] From there, we're able to nurture our leads with bulk emails that are easy to create and automatically optimize for a different devices.
[00:28:14.920 --> 00:28:22.160] With the built-in analytics, we can easily learn which emails, pages, and traffic sources are driving the most conversions.
[00:28:22.480 --> 00:28:27.040] Learn how HubSpot can help your business grow better at hubspot.com.
[00:28:28.960 --> 00:28:33.920] So, number two, my second example is a coding thing.
[00:28:33.920 --> 00:28:37.680] So, more like just development, poor development practices.
[00:28:37.680 --> 00:28:40.240] This is why you hire a good website versus everybody.
[00:28:40.480 --> 00:28:50.400] This is why you should do your due diligence when you're hiring someone to build something new for you, whether it's a website or your email marketing, what have you.
[00:28:50.400 --> 00:29:00.560] Just when you're hiring an outside somebody to come build something for you, make sure you're hiring someone that comes with glowing recommendations and can show their work.
[00:29:00.560 --> 00:29:21.280] Because I have an example of a client who was launching a brand new community platform, community website where people could pay to have a membership to access things like e-courses and a community forum and free webinars and all this stuff.
[00:29:21.280 --> 00:29:31.360] A big paid platform with a bunch of content because their previous version of the community was running on a platform that was six, seven years old.
[00:29:31.360 --> 00:29:35.920] And if you have been on the internet, that's ancient years.
[00:29:36.240 --> 00:29:45.760] So, with all of the innovation that social networks and things like that have had the past few years, a six, seven-year-old platform for a community, super old.
[00:29:45.760 --> 00:29:47.440] It's not what people are expecting anymore.
[00:29:47.440 --> 00:29:54.480] So, they finally put in all of the money, all the time to hire an agency to relaunch their community offering.
[00:29:54.480 --> 00:30:04.040] And the team for this company, before it launched, flagged that the way it was being built was not ideal, at least as far as the code went.
[00:30:04.040 --> 00:30:11.880] It was not being built in a very database-friendly way because this was a pretty high-trafficked community, so thousands of members.
[00:30:11.880 --> 00:30:17.480] If thousands of members are accessing this, there's going to be a lot of data on the back end, so it's going to be a huge database.
[00:30:17.480 --> 00:30:21.320] And if the server's not up to the task, it's going to load slow and stuff like that.
[00:30:21.560 --> 00:30:39.720] So, it was flagged that the code and everything on the back end was not being done in a very sustainable way, and it was kind of ignored because it was a very important project to get launched on time because the date had already been announced for when this project or when this new community website was going to be launched.
[00:30:39.720 --> 00:30:44.520] And so, it launched, and the problems that were flagged ended up being a problem.
[00:30:44.520 --> 00:30:53.160] It was so slow, customers were flagging that they were being timed out, they couldn't access anything, so it was just a huge bad launch.
[00:30:53.160 --> 00:30:59.160] And so, it actually ties into dissatisfied customers, but also a longer development cycle.
[00:30:59.160 --> 00:31:07.240] Because now that the website is launched, another person has been hired to actually go in and fix all those issues that should not have been issues to begin with.
[00:31:07.240 --> 00:31:10.360] Yeah, scope creep out-the-wall zoo.
[00:31:10.360 --> 00:31:23.400] It is triple what it should have been, what it should have cost because not only did they have all of the original payment for the original team that built it, now they had to have someone else to come in and fix all the issues that should have been not an issue to begin with.
[00:31:23.400 --> 00:31:32.360] If this had been done perfectly, at what point in this journey should something have happened differently?
[00:31:32.360 --> 00:31:41.320] As soon as that issue was flagged, it should have been okay to extend the development cycle and not launch a broken product.
[00:31:41.640 --> 00:31:48.400] So, even if it takes longer to build something, it's okay as long as you eventually put out a working product.
[00:31:48.560 --> 00:31:53.040] This actually ties into a video game issue because I love video games.
[00:31:53.040 --> 00:32:01.440] A couple of years ago, a video game, Cyberpunk 2077, launched and it was a broken game, but like it was supposed to be like the next big thing in video games.
[00:32:01.440 --> 00:32:03.280] It was completely broken.
[00:32:03.280 --> 00:32:07.360] PlayStation and Xbox ended up issuing refunds, which they never do.
[00:32:07.680 --> 00:32:16.160] And it was all because in the quality control phase of that video game development, they completely ignored the fact that it was a broken game.
[00:32:16.160 --> 00:32:24.080] They just, from what they were seeing, it was fine, but no one actually bothered to raise the flag that, oh, this is going to cause a lot of problems when it launches.
[00:32:24.080 --> 00:32:26.960] Maybe we should wait until it's actually fixed before we launch it.
[00:32:26.960 --> 00:32:28.160] And so it's a whole thing.
[00:32:28.160 --> 00:32:39.040] So anyway, it's just once you flag that there are issues, slow down, take more time, get it right, wait till it's ready, and then launch it.
[00:32:39.360 --> 00:32:39.920] Yeah.
[00:32:40.400 --> 00:32:48.240] I want to look at, I want to talk a little bit about what this looks like from doing things as best you can from the beginning.
[00:32:48.240 --> 00:32:53.280] I'm going to use myself as an example.
[00:32:53.280 --> 00:32:59.040] Because coming from websites, I understand the importance of this.
[00:32:59.040 --> 00:33:30.840] And so whenever I launched Almanac, you know, launch really small 2018 handful of products, whole shebang, it would have been very easy for me to go back to any of the platforms that I had developed websites on before and build something that I was used to building, that had the ability or had the functionality that I needed for right now, but was not going to help me get to my goals because my goal was absolutely in-person retail.
[00:33:29.920 --> 00:33:37.320] Yeah, so instead of doing what was fast, cheap, and easy for right now, I could have done it myself.
[00:33:37.960 --> 00:33:42.520] I could have done it super quickly in a platform that I was familiar with.
[00:33:42.520 --> 00:34:02.600] I instead looked at my growth goals and made the decision to go with a platform that I don't know I had built on it like twice before, like two times, not 50, like some of the other platforms, two times, two times before.
[00:34:02.600 --> 00:34:10.680] I ended up going to Shopify because it had functionality that I knew I wasn't going to use for like two years at least.
[00:34:10.680 --> 00:34:15.560] And to this day, six years later, I'm is it been six years?
[00:34:15.560 --> 00:34:17.240] Holy cow, it has been six years.
[00:34:17.240 --> 00:34:20.280] That came out of my nope, it's been four.
[00:34:20.600 --> 00:34:21.320] What is time?
[00:34:21.400 --> 00:34:22.840] Timey, whimy, right?
[00:34:23.160 --> 00:34:35.000] So, four years later, still on the exact same website, exact same platform, inventory is in there, team is using it, training is happening, functionality is growing, right?
[00:34:35.000 --> 00:34:42.920] As we are in there going, I made a decision four years ago for something that I wanted in four years, basically.
[00:34:43.240 --> 00:34:49.240] And I invested in doing the big thing then that has me fully functional now.
[00:34:49.240 --> 00:34:57.320] And I have not had to do any major rework to that piece of my technological existence in all of that time.
[00:34:57.320 --> 00:35:02.600] And I probably won't have to for the foreseeable future, knock on wood.
[00:35:02.600 --> 00:35:03.880] Yeah, you had forethought.
[00:35:03.880 --> 00:35:05.160] Good job.
[00:35:05.160 --> 00:35:06.360] Indeed, indeed.
[00:35:06.360 --> 00:35:07.400] And that's what I want.
[00:35:07.400 --> 00:35:08.520] That's what I want for everyone.
[00:35:08.520 --> 00:35:11.240] I want everyone to sort of see the difference in that as well.
[00:35:11.240 --> 00:35:26.240] I think this client you were just talking about, with, you know, having had this community built that came to a point where things were not good, needed to move forward, made maybe not the best decision to move forward despite the problems.
[00:35:26.560 --> 00:35:33.360] I want to make this point that like that first iteration, even though it ended up being the problem, it wasn't the problem.
[00:35:33.680 --> 00:35:39.760] Like you do the best you can with what you can, knowing what you know when you know it.
[00:35:40.080 --> 00:35:46.560] But the moment the flag came up is when the problem existed and then you move forward from that.
[00:35:46.560 --> 00:35:59.520] So not everyone is able to make the decision that I made in terms of our like, and whenever I say like website platform at Almanac, Shopify is the system that runs our business.
[00:35:59.520 --> 00:36:00.640] It's our POS.
[00:36:00.640 --> 00:36:02.240] It's tracking our inventory.
[00:36:02.240 --> 00:36:06.160] We do have a separate inventory tracking system that is a whole other conversation.
[00:36:07.120 --> 00:36:12.080] But that was a decision that we made then for now.
[00:36:12.080 --> 00:36:14.160] And I love that for us.
[00:36:14.480 --> 00:36:18.720] And it's something that I want everyone to think about when they are investing in something.
[00:36:18.720 --> 00:36:36.000] Because I don't think I'm going to find myself in a situation like this client did, because I was at a point in the life of the internet when I could make the investment and where I wanted to be in four, six, ten years.
[00:36:36.000 --> 00:36:36.400] Yeah.
[00:36:37.040 --> 00:36:44.640] So I have one more example I want to mention because it kind of slightly outside of the tech thing.
[00:36:44.640 --> 00:36:48.640] So it's not going to be about coding and stuff, but it is tech related.
[00:36:48.640 --> 00:36:51.840] So, a little bit more people can relate to this one.
[00:36:52.480 --> 00:36:54.560] So, it's another horror story.
[00:36:54.880 --> 00:36:58.480] It's about being delisted from Google.
[00:36:58.480 --> 00:37:01.000] God, that's like internet suicide.
[00:36:59.920 --> 00:37:02.520] Yes, especially for this company.
[00:37:02.760 --> 00:37:08.680] So, this is another client, and their entire business ran on their blog.
[00:37:08.680 --> 00:37:17.320] It was a seven-figure business, and vast majority of their traffic, 90-95% of the traffic, came from Google search.
[00:37:17.320 --> 00:37:25.800] And their blog functioned by running ads as well as sponsored blog posts.
[00:37:25.800 --> 00:37:33.240] And so, occasionally, maybe every couple of weeks, they would publish a blog post that was paid for by some third party.
[00:37:33.240 --> 00:37:52.440] Now, with Google, they require you to flag in some way in that post that it is sponsored content, such as if they click on a link and it's a link that could generate money for that business, you have to label it as an affiliate link.
[00:37:52.760 --> 00:37:56.040] They had not been doing this for years.
[00:37:56.680 --> 00:37:58.040] Oh, God.
[00:37:58.040 --> 00:37:59.800] And so, when I felt that in my gut.
[00:37:59.800 --> 00:38:12.280] Yeah, so when Google finally realized that all of these sponsored posts and affiliate links were not being labeled, they delisted the website entirely from Google.
[00:38:12.280 --> 00:38:32.680] Years and years of Google search results had been wiped overnight, and it obviously tanked their business because all of their traffic ceased to come in, and that dried up their revenue almost overnight because they relied so heavily on traffic from Google.
[00:38:32.680 --> 00:38:38.200] And when you get delisted from Google, for they were flagged for being spam, essentially.
[00:38:38.200 --> 00:38:46.720] When Google flags your site as spam, it is a task to get relisted because you have to go through a verification process.
[00:38:47.040 --> 00:38:52.880] And unless you do every single thing exactly how they want it, you're gonna have to re-go through the verification process.
[00:38:52.880 --> 00:38:56.400] And the verification process takes weeks sometimes.
[00:38:56.400 --> 00:39:04.880] And so they had to go post by post to address every single link that they had not flagged or labeled as an affiliate link.
[00:39:04.880 --> 00:39:09.680] It took them, I think, three months to finally get relisted in Google.
[00:39:09.680 --> 00:39:20.400] And you have to think when 95% of your traffic is coming from Google and that's what's generating your seven-figure income, and you're delisted for three months, their revenue tanked.
[00:39:20.400 --> 00:39:22.480] It destroyed their business.
[00:39:22.480 --> 00:39:24.160] Oh, I want to barf.
[00:39:24.160 --> 00:39:24.640] Yeah.
[00:39:24.640 --> 00:39:26.480] I want to barf over that one.
[00:39:26.480 --> 00:39:35.120] You know, what's coming up for me with this one, and it's something that I've experienced a couple of times before, and I think we're probably going to talk around this in a minute.
[00:39:35.120 --> 00:39:45.200] Is this why internet business needs to be taken as seriously as non-internet business?
[00:39:45.200 --> 00:39:45.600] Yes.
[00:39:45.600 --> 00:39:51.120] I feel like there is this idea that getting, and it used to be, used to, you could get away with all kinds of shit.
[00:39:51.120 --> 00:39:54.560] Kathleen and I used to call it the wild, wild west of the internet, right?
[00:39:54.560 --> 00:40:00.880] Where you could just like show up and put links and sell things, and it didn't, you didn't need terms and conditions, like whatever.
[00:40:00.880 --> 00:40:02.000] You could do anything.
[00:40:02.000 --> 00:40:05.440] Now they care, and they is everybody.
[00:40:05.440 --> 00:40:05.840] Yeah.
[00:40:05.840 --> 00:40:11.040] Google, the government, what's the difference between the two, right?
[00:40:11.040 --> 00:40:17.600] And so you have to know, you have to stay up to date on all of these things.
[00:40:17.840 --> 00:40:25.120] If you have not subscribed to our lawyer Autumn Whitboyd's email, list, go sign up.
[00:40:25.120 --> 00:40:29.440] She's always doing nice little updates of some things that are happening in the world that are incredibly important.
[00:40:29.440 --> 00:40:35.000] But I feel like so much of this stuff also just comes from not knowing.
[00:40:35.320 --> 00:40:38.520] You don't even know that you need to do these things.
[00:40:38.520 --> 00:40:40.840] I think sometimes you do know and you don't do it.
[00:40:40.840 --> 00:40:42.440] And that's obviously a problem.
[00:40:42.440 --> 00:40:53.480] But I think a lot of these things can also come from not knowing, which is why it's important to like have your good resources, awbfirm.com, right?
[00:40:53.800 --> 00:41:04.680] And also have a tech guy, not tech guy, a tech person, not in your pocket, but on speed dial/slash fast email.
[00:41:04.680 --> 00:41:05.000] Yeah.
[00:41:05.000 --> 00:41:06.200] Slack on Slack.
[00:41:06.200 --> 00:41:06.920] How about that?
[00:41:08.440 --> 00:41:11.800] Because these things are incredibly important.
[00:41:11.800 --> 00:41:15.080] Someone needs to be looking out for you if this is not your forte.
[00:41:15.080 --> 00:41:20.920] And when all shit hits the fan and no one saw the thing coming, you need someone to fix it for you.
[00:41:20.920 --> 00:41:21.560] Yeah.
[00:41:22.280 --> 00:41:25.800] You want to talk about the causes of tech debt?
[00:41:25.800 --> 00:41:26.120] Absolutely.
[00:41:26.280 --> 00:41:27.560] And what to look out for?
[00:41:27.560 --> 00:41:28.200] Yeah.
[00:41:28.200 --> 00:41:28.520] Yeah.
[00:41:28.520 --> 00:41:34.360] I feel like everyone probably currently is thinking of their horror story one way or the other, right?
[00:41:34.360 --> 00:41:35.240] Everyone has them.
[00:41:35.240 --> 00:41:38.280] And I, what is what is one of ours?
[00:41:38.280 --> 00:41:39.160] Can we share?
[00:41:39.160 --> 00:41:42.120] Is there a Bing boss or an almanac one?
[00:41:42.360 --> 00:41:44.200] I mean, I don't let you have these issues.
[00:41:44.200 --> 00:41:44.600] So no.
[00:41:44.840 --> 00:41:45.160] I know.
[00:41:45.160 --> 00:41:45.800] I was.
[00:41:45.800 --> 00:41:46.360] I love that.
[00:41:46.360 --> 00:41:47.800] None of these were about us.
[00:41:47.800 --> 00:41:51.240] Just so you know, we are GDPR was one for everyone.
[00:41:51.240 --> 00:41:52.280] You mentioned that one.
[00:41:52.600 --> 00:41:56.680] Actually, I have a little almanac one, and it's because I didn't get you to do it.
[00:41:57.000 --> 00:41:58.360] I think I know what you're going to say.
[00:41:58.360 --> 00:41:59.080] So, yes.
[00:41:59.640 --> 00:42:00.760] You probably don't.
[00:42:01.240 --> 00:42:12.120] So, whenever we moved our email marketing platform from ConvertKit, which is not for e-commerce, we just put it there because that was something I was familiar with.
[00:42:12.120 --> 00:42:14.680] Okay, so you're here in that, something I was familiar with.
[00:42:14.680 --> 00:42:20.400] Went with something that a platform that wasn't really for the kind of business we did, but like just needed fast, cheap, and easy.
[00:42:14.840 --> 00:42:20.960] Let's make it do.
[00:42:21.360 --> 00:42:24.000] Went with ConvertKit, worked okay for a couple of years.
[00:42:24.000 --> 00:42:29.520] Time to move to Clavio, which I do highly recommend for users of Shopify in particular.
[00:42:29.520 --> 00:42:32.400] I think the functionality is really great.
[00:42:32.400 --> 00:42:35.920] Do recommend not an affiliate.
[00:42:35.920 --> 00:42:39.120] So, moved over, which was a whole scenario in itself.
[00:42:39.120 --> 00:42:42.640] Moved over our funnels, moved over our contacts, like did all the things.
[00:42:42.640 --> 00:42:46.160] And I had hired someone to help me do some marketing things.
[00:42:46.160 --> 00:42:48.160] And I was like, Can you set up our Clavio for us?
[00:42:48.160 --> 00:42:50.080] And she was like, Sure, I'll make it do.
[00:42:50.560 --> 00:43:02.080] One of the things that did not get moved over correctly that I then had to fix about a year later when I realized that it had been done incorrectly was moving over birthday tags.
[00:43:02.080 --> 00:43:12.640] So, we had been working for years to have our contacts tag themselves with their birthday month so that we could send them a coupon code during the month of their birthday.
[00:43:12.640 --> 00:43:20.960] It was one of our regular marketing things, had done it for years, loved it, had people waiting on their birthday coupon, whole amazing thing.
[00:43:21.280 --> 00:43:34.160] She'd created the tags, but because she was not a Clavio expert, she didn't know that she didn't do it right until it came time for me to create a whole new year of emails and tag everybody with this tag.
[00:43:34.160 --> 00:43:41.440] ConvertKit has been deleted, so I can't go like double-check and like re-import people with the right tags.
[00:43:41.440 --> 00:43:43.280] Nothing I could do about it.
[00:43:43.280 --> 00:43:46.480] All of that data was lost, every single bit of it.
[00:43:46.480 --> 00:43:56.800] So, I had to come up with another solution, which was actually implementing a reward system that I had been meaning to implement anyway as an alternative to birthday rewards.
[00:43:56.800 --> 00:44:03.880] Um, but that one for me was that's a very minor little nightmare, but hurt my feelings.
[00:43:59.840 --> 00:44:05.000] Didn't hurt my feelings.
[00:44:05.240 --> 00:44:12.040] Like it made me sad to have lost that data and that ability to nurture my customers in that way.
[00:44:12.040 --> 00:44:12.760] Yeah.
[00:44:13.080 --> 00:44:15.240] If I'd gotten you to do it, it probably wouldn't have happened.
[00:44:15.240 --> 00:44:16.120] I'm sorry.
[00:44:16.120 --> 00:44:17.320] It's okay.
[00:44:17.640 --> 00:44:18.280] Now you know.
[00:44:18.280 --> 00:44:19.000] Now you know.
[00:44:19.000 --> 00:44:19.800] You learned.
[00:44:19.800 --> 00:44:20.120] Right.
[00:44:20.440 --> 00:44:21.320] So there's mine.
[00:44:21.320 --> 00:44:24.600] So I'll have to say we all have, we all have them for sure.
[00:44:24.600 --> 00:44:25.400] It's fine.
[00:44:25.400 --> 00:44:27.560] But what causes them, Corey?
[00:44:27.880 --> 00:44:33.400] So there are the four quadrants of technical debt.
[00:44:33.400 --> 00:44:35.880] So for literally a graph in our agendas.
[00:44:35.880 --> 00:44:38.440] This has never happened, literally ever.
[00:44:38.440 --> 00:44:45.400] In like almost 400 episodes, there has never been a graph present in an agenda.
[00:44:45.400 --> 00:44:46.760] And I'm looking at one right now.
[00:44:46.760 --> 00:44:48.520] Corey, you have outbossed me.
[00:44:48.520 --> 00:44:49.320] I know, right?
[00:44:49.480 --> 00:45:00.840] Corinne, when you're making the show notes, we can include this Asana link in the show notes because Asana put together a great article that kind of summarizes all the aspects of technical debt with graphs.
[00:45:00.840 --> 00:45:06.200] So I stole one of their graphs and they break it down into four quadrants of technical debt.
[00:45:06.520 --> 00:45:10.200] So the first one is prudent and deliberate.
[00:45:10.520 --> 00:45:15.560] This is the decision to ship quickly and deal with the consequences later.
[00:45:15.560 --> 00:45:23.960] So this type of debt is most commonly used when the stakes of the product are relatively low and the benefits of a quick delivery outweigh the risk.
[00:45:26.040 --> 00:45:27.480] Speedy much.
[00:45:27.480 --> 00:45:28.120] Yeah.
[00:45:28.120 --> 00:45:28.520] Right?
[00:45:28.520 --> 00:45:30.440] Just get it out there even if it's broken.
[00:45:30.440 --> 00:45:32.120] That's never cute, y'all.
[00:45:32.120 --> 00:45:33.960] You're going to pay for that later.
[00:45:33.960 --> 00:45:37.240] So, that is prudent and deliberate tech debt.
[00:45:37.240 --> 00:45:37.800] What's next?
[00:45:37.800 --> 00:45:40.200] Number two, reckless and deliberate.
[00:45:40.200 --> 00:45:46.160] So, knowing how to produce the best product, but by prioritizing speedy delivery over it.
[00:45:46.160 --> 00:45:47.920] Oh, so that's just like screw it.
[00:45:47.920 --> 00:45:48.560] Yeah.
[00:45:44.760 --> 00:45:48.800] Yeah.
[00:45:49.760 --> 00:45:53.200] Like, the flag has been raised, but you're just like, ah, whatever.
[00:45:53.440 --> 00:45:57.840] So, number three is prudent and inadvertent.
[00:45:57.840 --> 00:46:05.280] So, this is when there's a desire to produce the best product, but you find a better solution after implementation.
[00:46:05.600 --> 00:46:07.280] Oh, like my birthday tags.
[00:46:07.280 --> 00:46:08.000] Yeah.
[00:46:08.640 --> 00:46:09.040] Right.
[00:46:09.280 --> 00:46:12.960] So, this is accidental, but you realized it after the fact.
[00:46:12.960 --> 00:46:13.360] Yes, yes.
[00:46:13.680 --> 00:46:18.080] And then, the worst of all, the reckless and inadvertent.
[00:46:18.080 --> 00:46:23.760] So, this occurs when a team tries to produce the best product without the necessary knowledge to do so.
[00:46:23.760 --> 00:46:27.280] The team is often unaware of the mistakes they're making.
[00:46:27.280 --> 00:46:32.080] So, this is just you're not knowledgeable that you're not having the best practices.
[00:46:32.080 --> 00:46:34.880] And maybe you should have done more research before doing it.
[00:46:34.960 --> 00:46:36.080] This is everybody.
[00:46:36.080 --> 00:46:36.480] Yeah.
[00:46:36.480 --> 00:46:37.040] Yeah.
[00:46:37.040 --> 00:46:45.120] We are all reckless and inadvertent in some aspect of our business in terms of like everything, but really tech debt.
[00:46:45.120 --> 00:46:53.440] And this is like, this is you, you know, using email marketing and not realizing that you don't have your double opt-in opted in.
[00:46:53.440 --> 00:46:53.920] Yeah.
[00:46:53.920 --> 00:46:54.560] Right?
[00:46:54.560 --> 00:47:02.000] Or you are using a website hosting platform that's not as secure as it should be.
[00:47:02.000 --> 00:47:02.880] And you don't know it.
[00:47:02.880 --> 00:47:04.320] You don't realize it.
[00:47:04.320 --> 00:47:06.960] Or, I don't know, a million other.
[00:47:06.960 --> 00:47:12.400] Or you're not tagging all of your links with affiliate and you get blacklisted by Google.
[00:47:12.400 --> 00:47:12.800] Yeah.
[00:47:12.800 --> 00:47:12.960] Right?
[00:47:13.200 --> 00:47:16.480] Just completely unaware and it bait you in the butt.
[00:47:16.720 --> 00:47:17.040] Yes.
[00:47:17.200 --> 00:47:18.800] Let's talk about some actual causes.
[00:47:18.800 --> 00:47:22.480] So the first one is insufficient upfront definitions.
[00:47:22.480 --> 00:47:28.480] So this is also just scope creep, essentially, or not defining the project with definition.
[00:47:28.800 --> 00:47:30.920] Define the project definition, details.
[00:47:32.600 --> 00:47:37.640] So the solution to that is like at Almanac, where I was like, okay, I know where I want to be in a couple of years.
[00:47:37.640 --> 00:47:42.600] Let's make decisions based on my growth goals, not just where I am right now.
[00:47:42.600 --> 00:47:43.400] Yep.
[00:47:43.400 --> 00:47:45.880] And another one is business pressures.
[00:47:45.880 --> 00:47:51.880] So where the business considers getting something released sooner before the necessary changes are complete.
[00:47:51.880 --> 00:47:58.120] So this is kind of tying back into that community thing where flags were raised, but they released the product.
[00:47:58.360 --> 00:47:58.760] Deadlines.
[00:47:58.920 --> 00:47:59.320] Yep.
[00:47:59.320 --> 00:47:59.960] Yeah.
[00:47:59.960 --> 00:48:00.920] Deadlines.
[00:48:00.920 --> 00:48:03.080] And which are usually made up.
[00:48:03.080 --> 00:48:08.760] I just want to remind everyone: a lot of times you just make them up and you can remake them up and change them as needed.
[00:48:08.760 --> 00:48:10.200] They are not end-all-be-all.
[00:48:10.200 --> 00:48:15.960] You will not die in 99.9% of the scenarios.
[00:48:16.600 --> 00:48:20.600] There's like, there's a weird James Bond scenario out there somewhere.
[00:48:20.920 --> 00:48:21.480] Probs.
[00:48:21.480 --> 00:48:22.040] Okay.
[00:48:22.280 --> 00:48:35.160] And then the big one, the big, big one is just a lack of process or understanding where businesses are blind to the concept of technical debt and make decisions without considering the implications.
[00:48:36.440 --> 00:48:37.080] Yeah.
[00:48:37.080 --> 00:48:43.480] And I think this is also the big one, too, because you don't even realize that these decisions are going to have an impact until later.
[00:48:43.480 --> 00:48:45.160] I have a really great example of this one.
[00:48:45.160 --> 00:48:46.040] Can I share?
[00:48:46.040 --> 00:48:46.600] Yes.
[00:48:46.600 --> 00:48:47.880] I have an e-commerce friend.
[00:48:48.120 --> 00:48:55.400] No, a retail friend who a couple of years ago decided to put some CBD products in her store.
[00:48:56.040 --> 00:49:05.320] And so she put them on her POS system, which I believe was Shopify, if I'm not mistaken, just to come in the next morning.
[00:49:05.320 --> 00:49:16.800] And she had been kicked out of Shopify because Shopify and their terms and conditions did not allow the sell of CBD.
[00:49:14.840 --> 00:49:20.080] And so they just have bots that are, you know, crawling everything.
[00:49:20.240 --> 00:49:25.600] And if they see keywords like CBD, they're not going to ask questions.
[00:49:25.600 --> 00:49:26.640] They're going to kick you out.
[00:49:27.280 --> 00:49:30.160] And so her team goes to open the store the next day.
[00:49:30.160 --> 00:49:31.600] There is no point of sale system.
[00:49:31.600 --> 00:49:34.000] There's literally no way for them to sell anything.
[00:49:34.000 --> 00:49:37.120] They have, and Shopify is not taking phone calls.
[00:49:37.120 --> 00:49:37.840] Yikes.
[00:49:38.160 --> 00:49:50.080] So they have to close down the store for the next couple of days and implement an entire new inventory and POS and website system because it was tied to their website.
[00:49:50.080 --> 00:49:56.160] Because they made the decision to list a product that at that point, I don't know what the rules are now.
[00:49:56.160 --> 00:49:58.720] I won't touch the stuff because that is a horror story.
[00:50:00.000 --> 00:50:02.880] But because they had put a like, what's it called?
[00:50:02.880 --> 00:50:09.920] Like a not a regulated product on like it was like CBD bath bombs or something.
[00:50:09.920 --> 00:50:11.040] It wasn't anything crazy.
[00:50:11.200 --> 00:50:13.440] They just put some bath bombs in her store.
[00:50:13.440 --> 00:50:22.480] I've also heard this around putting some scientific names to like smudge sticks.
[00:50:22.480 --> 00:50:22.960] Okay.
[00:50:23.280 --> 00:50:34.000] So like you really have to watch some words for some of those things, but also read the terms and conditions for the things you sign up for so that you don't have a lack of understanding.
[00:50:34.000 --> 00:50:36.480] You fully understand as much as possible.
[00:50:36.480 --> 00:50:40.320] And also have friends that tell you stories because that can keep you from lots of trouble.
[00:50:40.320 --> 00:50:40.720] Yeah.
[00:50:41.040 --> 00:50:42.240] We have a few other things here.
[00:50:42.240 --> 00:50:43.200] And I know we're running out of time.
[00:50:43.200 --> 00:50:45.920] So I'm going to try and just touch on all of these.
[00:50:46.320 --> 00:50:51.680] So the next one is, or the next cause for tech debt is tightly coupled components.
[00:50:51.680 --> 00:50:57.520] And so that sounds very, very cody, but it's really just where things are not modular.
[00:50:57.520 --> 00:51:02.280] So when you need to replace one thing, you instead have to replace the entire thing.
[00:50:59.440 --> 00:51:06.840] So what comes to mind is funnels, email funnels.
[00:51:07.400 --> 00:51:12.920] And I will call out Biddy Tarot specifically this time because I've been all up in their email funnels.
[00:51:13.080 --> 00:51:22.200] So Biddy Tarot, they have had multiple funnels in their email system for years, for years and years and years.
[00:51:22.200 --> 00:51:23.560] Really four main ones.
[00:51:23.560 --> 00:51:25.720] So they're all based around webinars.
[00:51:25.720 --> 00:51:30.600] So they have a webinar funnel for one product, a webinar funnel for another product.
[00:51:30.920 --> 00:51:42.200] And the way they were built is that there was no easy way to change out one sequence of emails without breaking the entire thing.
[00:51:42.200 --> 00:51:43.720] And I say sequence of emails.
[00:51:43.720 --> 00:51:46.120] It's like it was phased funnels.
[00:51:46.120 --> 00:51:51.080] So like there was the first email sequence, which is like it was complex.
[00:51:51.080 --> 00:51:51.320] Yeah.
[00:51:51.320 --> 00:52:00.120] So like there were webinar invites, and then once you register for the webinar, you get the post-webinar emails and you get like the down sell emails and all that.
[00:52:00.120 --> 00:52:06.680] But because of how it was all wibbly wobbly inside of these automations, you couldn't take just one little itty-bitty piece out of it.
[00:52:06.680 --> 00:52:16.040] Like if you had to replace one email because the messaging in that email was out of date or something, to replace that one email would just crash and burn the entire funnel.
[00:52:16.040 --> 00:52:18.360] It didn't have to be that way.
[00:52:18.360 --> 00:52:33.000] If more thorough planning had been put in place to make that more modular, so you could take things out and replace them as things need to be up to date, it would have created a more simple, easy to maintain system.
[00:52:33.320 --> 00:52:39.880] So, yes, just making sure things are modular and easy to plug and play with.
[00:52:39.880 --> 00:52:40.840] So, that's another big one.
[00:52:41.160 --> 00:52:42.040] More flexible.
[00:52:42.040 --> 00:52:42.680] Yeah.
[00:52:42.680 --> 00:52:43.320] It's funny.
[00:52:43.320 --> 00:52:48.560] I love that you say that because it's something with my website background, I think about whenever I'm building things.
[00:52:48.800 --> 00:52:53.680] I want to be able to move things, change things, take things away, put them back together.
[00:52:53.680 --> 00:53:00.400] I even think about this at Almanac and how, you know, Shopify has like an inventory system, but I have like another inventory system.
[00:53:00.400 --> 00:53:04.480] So, if something ever happens to one, I have another, I can change one and keep things.
[00:53:04.480 --> 00:53:12.480] And like, once you think about this, y'all, you start thinking about this as to how it is that you're building what you're building.
[00:53:12.480 --> 00:53:13.040] Continue.
[00:53:13.040 --> 00:53:16.080] And I'm just going to list these off, and you can pull from it what you will.
[00:53:16.400 --> 00:53:21.920] So, the rest of the list, and this is not an all-exhaustive list, like this is just the highlights that I pulled from my research.
[00:53:22.240 --> 00:53:40.080] So, other causes of tech debt are lack of documentation or systems and processes, lack of collaboration, lack of ownership, lack of knowledge, last-minute changes, and lack of standards.
[00:53:43.920 --> 00:53:45.440] Yes, absolutely.
[00:53:46.080 --> 00:53:47.440] Absolutely.
[00:53:47.680 --> 00:53:52.160] You also, you missed one: lack of testing, which is incredibly important too.
[00:53:52.160 --> 00:53:52.640] Yeah.
[00:53:52.640 --> 00:53:53.520] For sure.
[00:53:53.520 --> 00:53:54.240] Love it.
[00:53:54.240 --> 00:53:54.880] Okay.
[00:53:54.880 --> 00:53:56.400] Ben, quick.
[00:53:56.400 --> 00:53:57.280] How can you fix it?
[00:53:57.280 --> 00:54:03.040] What does it look like to be better and/or do it better if you've already started?
[00:54:03.360 --> 00:54:07.840] I think just the big one that comes to mind is doing your research.
[00:54:07.840 --> 00:54:08.400] Yep.
[00:54:08.400 --> 00:54:13.200] Like, don't just go all into building something new if you don't really know what you're doing.
[00:54:13.200 --> 00:54:13.440] Yeah.
[00:54:13.440 --> 00:54:18.560] Like, it's okay to go read some articles, watch some YouTube videos, take some courses.
[00:54:18.560 --> 00:54:21.680] Just take a little time to do some prep work.
[00:54:21.680 --> 00:54:23.840] I think it's just the really big thing.
[00:54:24.160 --> 00:54:31.880] And then, other things, make sure you're addressing debt as just a regular part of your to-dos.
[00:54:32.440 --> 00:54:48.040] So, if you have a team or if you're just working alone, if you know that there is debt that needs to be addressed, like you know, you put a Bandaid fix in place because it needed to launch tomorrow, but you know you have time next week to go fix it, make sure you are keeping track of that debt.
[00:54:48.040 --> 00:54:53.480] So, monitor that debt, keep a list in your task management system.
[00:54:53.480 --> 00:55:01.160] If you have a team, if you're meeting regularly, make sure there's always time in that meeting, whether it's at the beginning or the end, to address the debt.
[00:55:01.160 --> 00:55:09.240] So, there's visibility on the issues so it never loses sight and so it doesn't fall off of your to-do list.
[00:55:09.240 --> 00:55:09.640] Right.
[00:55:09.640 --> 00:55:11.800] And then, also, just regular maintaining.
[00:55:11.800 --> 00:55:26.360] I cannot recommend enough that every single person that has a website that they are currently using to run their business have a web person on retainer.
[00:55:26.360 --> 00:55:31.320] And not just on retainer for security purposes, but on retainer for maintenance.
[00:55:31.320 --> 00:55:35.960] If you are not doing this yourself, having them go in and check your stuff, make sure things are still working.
[00:55:35.960 --> 00:55:50.040] Like, even if they're just testing it, incredibly important because platforms change, new features become available, things get tweaked and broken, especially if you have, you know, a VA who's like, you know, nosing around in your email software.
[00:55:50.040 --> 00:55:57.160] Like, make sure someone is there who knows what it's supposed to look like to fix things when buttons accidentally get pushed, whatever it may be.
[00:55:57.160 --> 00:56:10.680] I do, I think it could be a potential first-ish hire, contract or employee, but definitely contract, I think, for 90% of the people listening.
[00:56:11.000 --> 00:56:21.280] Having someone on retainer to do these things for you, whose job is to know what your tech debt is to, but also to be constantly maintaining it is incredibly important.
[00:56:21.600 --> 00:56:33.280] I've had someone on staff or contract before that from about like my first six-ish figure year.
[00:56:33.280 --> 00:56:33.760] Yeah.
[00:56:34.080 --> 00:56:34.720] Right?
[00:56:34.720 --> 00:56:52.320] So, like, really early on, because when you're building websites, when you're building email marketing stuff, when you are building integrations, when you are moving from maybe not for the purpose of this, but like even someone who's going to move you from Trello to Asana or whatever it may be.
[00:56:52.320 --> 00:56:55.920] That's not a web guy or girl or web person.
[00:56:55.920 --> 00:56:56.240] Could be.
[00:56:56.480 --> 00:56:57.040] Could be.
[00:56:57.520 --> 00:57:04.880] But like having someone, having someone on retainer so that you can at least call them when something happens is incredibly important.
[00:57:04.880 --> 00:57:05.520] Yeah.
[00:57:05.840 --> 00:57:06.960] Amen.
[00:57:08.480 --> 00:57:20.480] So I think the last big one, the last preventative thing you can do is really just a mindset shift into how you approach creating new things and managing your to-do list.
[00:57:20.480 --> 00:57:27.040] And it's the agile approach, the agile project management or agile development of creating new things.
[00:57:27.040 --> 00:57:36.240] And this is the idea that you do more iterative development rather than trying to do one big thing all at once and just put it out there.
[00:57:36.240 --> 00:57:42.000] So the idea is that you get it to a good place, you release it, and then you plan.
[00:57:42.000 --> 00:57:47.280] You actually create a plan to do consistent smaller updates.
[00:57:47.600 --> 00:57:50.080] So you're constantly addressing issues.
[00:57:50.080 --> 00:58:00.000] You're constantly growing whatever it is that you built, but you planned for that to be a consistent, iterative approach to consistently maintaining it and growing it.
[00:58:00.360 --> 00:58:00.760] Yeah.
[00:58:01.080 --> 00:58:01.560] I love it.
[00:58:01.560 --> 00:58:02.440] Corey, this is great.
[00:58:02.440 --> 00:58:09.560] I also just had thought about all the tech debt I have both in my Dropbox and in Notion.
[00:58:09.880 --> 00:58:18.280] Just so much stuff hanging around that needs to be like maybe even if you're aware of it, it's kind of daunting the longer you put it off.
[00:58:18.280 --> 00:58:18.600] Yeah.
[00:58:18.600 --> 00:58:19.800] And it just kind of snowballs.
[00:58:20.920 --> 00:58:21.640] The debt gets bigger.
[00:58:21.640 --> 00:58:23.080] It snowballs into all kinds of things.
[00:58:23.320 --> 00:58:26.200] And finding things gets harder, not just for me, but for everyone.
[00:58:26.200 --> 00:58:30.040] I literally am paying interest on my tech debt, everybody.
[00:58:30.040 --> 00:58:30.360] Literally.
[00:58:30.600 --> 00:58:33.800] You're not paying your monthly down, your monthly minimum payment.
[00:58:33.800 --> 00:58:35.480] You're just accumulating that interest.
[00:58:35.480 --> 00:58:36.920] Yeah, I'm accumulating.
[00:58:37.240 --> 00:58:37.800] You're right.
[00:58:37.800 --> 00:58:38.360] You're right.
[00:58:38.360 --> 00:58:38.920] Okay, perfect.
[00:58:38.920 --> 00:58:40.200] Corey, this has been great.
[00:58:40.200 --> 00:58:53.560] I hope everyone listening to this has gotten a little bit of a push to deal with something in your technical existence that you have maybe been putting off because you're paying interest whether you like it or not.
[00:58:53.560 --> 00:58:57.240] And again, this does not have to be technical specifically.
[00:58:57.240 --> 00:59:02.520] Like this, apply these thoughts to just the way you run your business as a whole.
[00:59:02.520 --> 00:59:06.600] Just apply these things everywhere in your personal life, too.
[00:59:07.000 --> 00:59:11.320] If you're putting off doing those dishes in your sink, come on, that's taking up time from later.
[00:59:11.320 --> 00:59:13.560] Like, go, go, go, clean your dishes.
[00:59:13.560 --> 00:59:14.200] Go do your lunch.
[00:59:14.280 --> 00:59:14.920] Go do your lunch.
[00:59:14.920 --> 00:59:16.360] You're going to do a little lesson for today.
[00:59:16.360 --> 00:59:18.520] Go do your dishes, everybody.
[00:59:18.520 --> 00:59:22.120] All right, Corey, because this is a legit interview of you.
[00:59:22.440 --> 00:59:24.120] What makes you feel most boss?
[00:59:24.120 --> 00:59:27.000] Doing this episode where I actually know what I'm talking about.
[00:59:27.000 --> 00:59:28.440] Oh, I do love that for you.
[00:59:28.440 --> 00:59:29.560] This has been a good one.
[00:59:29.560 --> 00:59:30.520] A very good one.
[00:59:30.520 --> 00:59:34.280] Literally, the nicest agenda anyone has ever made for this show ever.
[00:59:34.280 --> 00:59:35.320] Nice job.
[00:59:35.320 --> 00:59:36.040] Yep.
[00:59:36.680 --> 00:59:37.240] All right.
[00:59:37.240 --> 00:59:38.520] Thanks.
[00:59:39.800 --> 00:59:46.240] All right, boss, because you're here, I know you want to be a better creative business owner, which means I've got something for you.
[00:59:46.560 --> 01:00:03.120] Each week, the team at Bean Boss is scouring the news, the best entrepreneurial publications, and updates and r

Prompt 2: Key Takeaways

Now please extract the key takeaways from the transcript content I provided.

Extract the most important key takeaways from this part of the conversation. Use a single sentence statement (the key takeaway) rather than milquetoast descriptions like "the hosts discuss...". 

Limit the key takeaways to a maximum of 3. The key takeaways should be insightful and knowledge-additive. 

IMPORTANT: Return ONLY valid JSON, no explanations or markdown. Ensure:
- All strings are properly quoted and escaped
- No trailing commas
- All braces and brackets are balanced
Format: {"key_takeaways": ["takeaway 1", "takeaway 2"]}

Prompt 3: Segments

Now identify 2-4 distinct topical segments from this part of the conversation.

For each segment, identify:
- Descriptive title (3-6 words)  
- START timestamp when this topic begins (HH:MM:SS format)
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Most important Key takeaway from that segment. Key takeaway must be specific and knowledge-additive.
- Brief summary of the discussion

IMPORTANT: The timestamp should mark when the topic/segment STARTS, not a range. Look for topic transitions and conversation shifts.

Return ONLY valid JSON. Ensure all strings are properly quoted, no trailing commas:
{
  "segments": [
    {
      "segment_title": "Topic Discussion", 
      "timestamp": "01:15:30",
      "key_takeaway": "main point from this segment",
      "segment_summary": "brief description of what was discussed"
    }
  ]
}

Timestamp format: HH:MM:SS (e.g., 00:05:30, 01:22:45) marking the START of each segment.

Prompt 4: Media Mentions

Now scan the transcript content I provided for ACTUAL mentions of specific media titles:

Find explicit mentions of:
- Books (with specific titles)
- Movies (with specific titles)  
- TV Shows (with specific titles)
- Music/Songs (with specific titles)

DO NOT include:
- Websites, URLs, or web services
- Other podcasts or podcast names

IMPORTANT: 
- Only include items explicitly mentioned by name. Do not invent titles.
- Valid categories are: "Book", "Movie", "TV Show", "Music"
- Include the exact phrase where each item was mentioned
- Find the nearest proximate timestamp where it appears in the conversation
- THE TIMESTAMP OF THE MEDIA MENTION IS IMPORTANT - DO NOT INVENT TIMESTAMPS AND DO NOT MISATTRIBUTE TIMESTAMPS
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Timestamps are given as ranges, e.g. 01:13:42.520 --> 01:13:46.720. Use the EARLIER of the 2 timestamps in the range.

Return ONLY valid JSON. Ensure all strings are properly quoted and escaped, no trailing commas:
{
  "media_mentions": [
    {
      "title": "Exact Title as Mentioned",
      "category": "Book",
      "author_artist": "N/A",
      "context": "Brief context of why it was mentioned",
      "context_phrase": "The exact sentence or phrase where it was mentioned",
      "timestamp": "estimated time like 01:15:30"
    }
  ]
}

If no media is mentioned, return: {"media_mentions": []}

Prompt 5: Context Setup

You are an expert data extractor tasked with analyzing a podcast transcript. 
I will provide you with part 2 of 2 from a podcast transcript. 
I will then ask you to extract different types of information from this content in subsequent messages. Please confirm you have received and understood the transcript content.

Transcript section:
this has been great.
[00:58:40.200 --> 00:58:53.560] I hope everyone listening to this has gotten a little bit of a push to deal with something in your technical existence that you have maybe been putting off because you're paying interest whether you like it or not.
[00:58:53.560 --> 00:58:57.240] And again, this does not have to be technical specifically.
[00:58:57.240 --> 00:59:02.520] Like this, apply these thoughts to just the way you run your business as a whole.
[00:59:02.520 --> 00:59:06.600] Just apply these things everywhere in your personal life, too.
[00:59:07.000 --> 00:59:11.320] If you're putting off doing those dishes in your sink, come on, that's taking up time from later.
[00:59:11.320 --> 00:59:13.560] Like, go, go, go, clean your dishes.
[00:59:13.560 --> 00:59:14.200] Go do your lunch.
[00:59:14.280 --> 00:59:14.920] Go do your lunch.
[00:59:14.920 --> 00:59:16.360] You're going to do a little lesson for today.
[00:59:16.360 --> 00:59:18.520] Go do your dishes, everybody.
[00:59:18.520 --> 00:59:22.120] All right, Corey, because this is a legit interview of you.
[00:59:22.440 --> 00:59:24.120] What makes you feel most boss?
[00:59:24.120 --> 00:59:27.000] Doing this episode where I actually know what I'm talking about.
[00:59:27.000 --> 00:59:28.440] Oh, I do love that for you.
[00:59:28.440 --> 00:59:29.560] This has been a good one.
[00:59:29.560 --> 00:59:30.520] A very good one.
[00:59:30.520 --> 00:59:34.280] Literally, the nicest agenda anyone has ever made for this show ever.
[00:59:34.280 --> 00:59:35.320] Nice job.
[00:59:35.320 --> 00:59:36.040] Yep.
[00:59:36.680 --> 00:59:37.240] All right.
[00:59:37.240 --> 00:59:38.520] Thanks.
[00:59:39.800 --> 00:59:46.240] All right, boss, because you're here, I know you want to be a better creative business owner, which means I've got something for you.
[00:59:46.560 --> 01:00:03.120] Each week, the team at Bean Boss is scouring the news, the best entrepreneurial publications, and updates and releases of the apps and tools that run our businesses and is curating it all into a weekly email that delivers the must-know tips and tactics in the realms of mindset, money, and productivity.
[01:00:03.120 --> 01:00:05.040] This email is called Brood.
[01:00:05.040 --> 01:00:11.120] We brew it up for you each week to give you the insight you need to make decisions and move forward in your creative business.
[01:00:11.120 --> 01:00:15.600] Check it out now and sign up for yourself at beingboss.club/slash brood.
[01:00:15.600 --> 01:00:20.320] That's beingboss.club/slash B-R-E-W-E-D.
[01:00:20.640 --> 01:00:23.280] Now, until next time, do the work.
[01:00:23.280 --> 01:00:24.560] Be boss.

Prompt 6: Key Takeaways

Now please extract the key takeaways from the transcript content I provided.

Extract the most important key takeaways from this part of the conversation. Use a single sentence statement (the key takeaway) rather than milquetoast descriptions like "the hosts discuss...". 

Limit the key takeaways to a maximum of 3. The key takeaways should be insightful and knowledge-additive. 

IMPORTANT: Return ONLY valid JSON, no explanations or markdown. Ensure:
- All strings are properly quoted and escaped
- No trailing commas
- All braces and brackets are balanced
Format: {"key_takeaways": ["takeaway 1", "takeaway 2"]}

Prompt 7: Segments

Now identify 2-4 distinct topical segments from this part of the conversation.

For each segment, identify:
- Descriptive title (3-6 words)  
- START timestamp when this topic begins (HH:MM:SS format)
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Most important Key takeaway from that segment. Key takeaway must be specific and knowledge-additive.
- Brief summary of the discussion

IMPORTANT: The timestamp should mark when the topic/segment STARTS, not a range. Look for topic transitions and conversation shifts.

Return ONLY valid JSON. Ensure all strings are properly quoted, no trailing commas:
{
  "segments": [
    {
      "segment_title": "Topic Discussion", 
      "timestamp": "01:15:30",
      "key_takeaway": "main point from this segment",
      "segment_summary": "brief description of what was discussed"
    }
  ]
}

Timestamp format: HH:MM:SS (e.g., 00:05:30, 01:22:45) marking the START of each segment.

Prompt 8: Media Mentions

Now scan the transcript content I provided for ACTUAL mentions of specific media titles:

Find explicit mentions of:
- Books (with specific titles)
- Movies (with specific titles)  
- TV Shows (with specific titles)
- Music/Songs (with specific titles)

DO NOT include:
- Websites, URLs, or web services
- Other podcasts or podcast names

IMPORTANT: 
- Only include items explicitly mentioned by name. Do not invent titles.
- Valid categories are: "Book", "Movie", "TV Show", "Music"
- Include the exact phrase where each item was mentioned
- Find the nearest proximate timestamp where it appears in the conversation
- THE TIMESTAMP OF THE MEDIA MENTION IS IMPORTANT - DO NOT INVENT TIMESTAMPS AND DO NOT MISATTRIBUTE TIMESTAMPS
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Timestamps are given as ranges, e.g. 01:13:42.520 --> 01:13:46.720. Use the EARLIER of the 2 timestamps in the range.

Return ONLY valid JSON. Ensure all strings are properly quoted and escaped, no trailing commas:
{
  "media_mentions": [
    {
      "title": "Exact Title as Mentioned",
      "category": "Book",
      "author_artist": "N/A",
      "context": "Brief context of why it was mentioned",
      "context_phrase": "The exact sentence or phrase where it was mentioned",
      "timestamp": "estimated time like 01:15:30"
    }
  ]
}

If no media is mentioned, return: {"media_mentions": []}

Full Transcript

[00:00:00.480 --> 00:00:07.360] Look, payday is awesome, but running payroll, calculating taxes and deductions, staying compliant, that's not easy.
[00:00:07.360 --> 00:00:09.360] Unless, of course, you have Gusto.
[00:00:09.360 --> 00:00:14.400] Gusto is a simple online payroll and benefits tool built for small businesses like yours.
[00:00:14.400 --> 00:00:18.400] Gusto gets your team paid while automatically filing your payroll taxes.
[00:00:18.400 --> 00:00:25.600] Plus, you can offer benefits like 401k, health insurance, and workers' comp, and it makes onboarding new employees a breeze.
[00:00:25.600 --> 00:00:28.320] We love it so much, we really do use it ourselves.
[00:00:28.320 --> 00:00:34.800] And we have four years, and I personally recommend you give it a try, no matter how small your business is.
[00:00:34.800 --> 00:00:38.880] And to sweeten the deal, just for listening today, you also get three months free.
[00:00:38.880 --> 00:00:41.360] Go to gusto.com slash beingboss.
[00:00:41.360 --> 00:00:45.120] That's gusto.com/slash beingboss.
[00:00:46.400 --> 00:00:53.840] Welcome to Being Boss, a podcast for creatives, business owners, and entrepreneurs who want to take control of their work and live life on their own terms.
[00:00:53.840 --> 00:01:05.520] I'm your host, Emily Thompson, and in this episode, I'm not only joined by my podcast companion, Corey Winter, but I'm interviewing him on building a good online presence for your business from the start.
[00:01:05.520 --> 00:01:10.560] Or in other words, not accumulating a little something called tech debt.
[00:01:10.560 --> 00:01:16.000] You can find all the tools, books, and links we reference on the show notes at www.beingboss.club.
[00:01:16.000 --> 00:01:21.120] And if you like this episode, be sure to subscribe to the show and share us with a friend.
[00:01:23.040 --> 00:01:28.240] Having a fulfilling career and succeeding in business are what we're all here to accomplish, right?
[00:01:28.240 --> 00:01:36.240] Well, if it resonates, then I've got a new show for you to check out that's all about educating you on how to best market yourself in the new digital age.
[00:01:36.240 --> 00:01:44.720] It's called Big Brand Energy, hosted by Sophie Wilson, brought to you by the HubSpot Podcast Network, the audio destination for business professionals.
[00:01:44.720 --> 00:01:53.920] With episodes on building an authentic brand and how business and online dating are the same, you'll get a fresh take on online marketing in the new year.
[00:01:53.920 --> 00:01:58.360] Listen to Big Brand Energy wherever you get your podcasts.
[00:01:57.840 --> 00:02:02.680] So, I'm a companion again.
[00:02:03.000 --> 00:02:15.720] Well, I figured if you were going to make such a fuss about being a pal bro, a bro pal, then I would lateral move you back to companion.
[00:02:16.920 --> 00:02:17.720] Okay, yes.
[00:02:17.720 --> 00:02:20.920] In my mind, it was lateral previously.
[00:02:21.400 --> 00:02:28.040] Um, so you are back to companion, but you're also interviewee today.
[00:02:28.040 --> 00:02:29.400] How does that feel?
[00:02:29.400 --> 00:02:33.640] A little stressful, not sure I can actually put out words.
[00:02:33.640 --> 00:02:35.400] We'll see how this goes.
[00:02:35.400 --> 00:02:36.920] Good thing you edited.
[00:02:36.920 --> 00:02:38.680] Yep.
[00:02:38.840 --> 00:02:40.920] Then I'm very excited about this one.
[00:02:40.920 --> 00:02:47.400] A couple of weeks ago, or every couple of weeks, the Being Boss team gets together and we're like, okay, what is Emily talking about?
[00:02:47.400 --> 00:02:50.920] Basically, over the next couple of episodes.
[00:02:50.920 --> 00:02:53.080] And everyone always throws out some really good ideas.
[00:02:53.080 --> 00:02:57.560] You should all know that all of these episodes that you are delivered, it ain't just me.
[00:02:57.560 --> 00:03:06.280] There is a content team that is helping me come up with ideas and help create agendas and ask questions and those sorts of things.
[00:03:06.280 --> 00:03:08.520] And a lot of it comes from the Being Boss community.
[00:03:08.520 --> 00:03:12.680] If you are not a member of the Being Boss community, I highly recommend you go check that place out.
[00:03:12.680 --> 00:03:17.960] There's all kinds of conversations that are being had on, obviously, creative entrepreneurship.
[00:03:17.960 --> 00:03:26.360] And a lot of those conversations do make or do inspire the conversations that we are having here on this show.
[00:03:26.680 --> 00:03:32.600] So we were recently in one of those meetings with the team, and Corey yells out tech debt.
[00:03:32.920 --> 00:03:33.560] Yes.
[00:03:33.560 --> 00:03:35.480] And I was like, I don't even know what that is.
[00:03:35.480 --> 00:03:36.600] What are you saying to me?
[00:03:36.600 --> 00:03:37.880] Are those words?
[00:03:38.200 --> 00:03:38.760] Those are words.
[00:03:38.920 --> 00:03:39.720] And he went on to explain.
[00:03:40.040 --> 00:03:41.160] Those are words.
[00:03:41.160 --> 00:03:48.240] So I have a bone to pick with the internet as a whole.
[00:03:48.880 --> 00:03:50.080] I got a couple of those two.
[00:03:50.320 --> 00:03:51.520] Continue.
[00:03:51.840 --> 00:03:57.840] And specifically with people that build things on the internet.
[00:03:57.840 --> 00:03:59.440] Because there's this little phrase.
[00:03:59.440 --> 00:04:03.920] It's a little buzzword, buzz phrase called tech debt.
[00:04:04.240 --> 00:04:08.160] It was a term coined by Ward.
[00:04:08.160 --> 00:04:08.640] Ward?
[00:04:08.800 --> 00:04:09.360] Ward?
[00:04:09.360 --> 00:04:10.640] Ward Cunningham.
[00:04:11.040 --> 00:04:11.680] Ward.
[00:04:11.920 --> 00:04:12.960] Ward Cunningham.
[00:04:12.960 --> 00:04:14.160] He is a computer programmer.
[00:04:14.320 --> 00:04:16.880] He has been in the game for decades.
[00:04:16.880 --> 00:04:19.600] He's actually the original inventor of the wiki.
[00:04:19.600 --> 00:04:21.920] Not Wikipedia, but like the thing wiki.
[00:04:21.920 --> 00:04:23.680] He invented the wiki.
[00:04:23.680 --> 00:04:26.320] And he coined the term tech debt.
[00:04:26.320 --> 00:04:34.400] It's a term specifically used for coding and programming, but it can be used in a broader sense, just technology in general.
[00:04:34.400 --> 00:04:47.680] And the idea is that it's the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.
[00:04:48.880 --> 00:04:53.040] And so this is all going to tie into working smarter, not harder.
[00:04:53.040 --> 00:04:59.120] Really, actually, maybe even the opposite, working harder in the beginning so you can work smarter later.
[00:04:59.760 --> 00:05:20.400] And this has come up a lot in the client work that I do, so much so that I think it's kind of accidentally become what I specialize in because I've had a lot of clients come to me that previously maybe worked with another developer or did everything themselves and they did things in a way that is not sustainable.
[00:05:20.400 --> 00:05:31.240] And so, trying to change anything in the future or trying to do things, just changing things up in general, is even harder than it should have been if they had just done things in a different way to begin with.
[00:05:31.560 --> 00:05:38.840] So, that's my bone to pick with the internet: a lot of things that just have not been done well because they weren't thought all the way through.
[00:05:39.960 --> 00:05:40.440] Right.
[00:05:40.440 --> 00:05:42.440] Okay, that is a nice little bone to pick.
[00:05:42.440 --> 00:05:45.240] Love that for you and the internet.
[00:05:45.560 --> 00:05:50.680] Whenever you started explaining this to me a little bit, it all made sense.
[00:05:51.000 --> 00:06:04.200] And for me, I recalled years at Indie Shopography where there wasn't a phrase for this, but I was literally trying to sell people on not having tech debt.
[00:06:04.200 --> 00:06:09.160] And what this looks like and why this matters, just sort of bring it into some context.
[00:06:09.160 --> 00:06:12.120] I know it's not just websites, it's so many things.
[00:06:12.120 --> 00:06:13.800] Back in all of the things, right?
[00:06:13.800 --> 00:06:14.680] It's all of the things.
[00:06:14.680 --> 00:06:20.440] Back in the day, whenever I was working in websites, it was around building e-commerce sites.
[00:06:20.440 --> 00:06:23.480] And people would come to me going, Well, what's the difference?
[00:06:23.480 --> 00:06:37.800] And, you know, going with you and this like big e-commerce platform as I'm just getting started in business and just going and starting at that point, it was like a very small and not very highly functional Squarespace site or whatever it may be.
[00:06:38.040 --> 00:06:41.560] I mean, this is 10 years ago, y'all, plus years ago.
[00:06:42.280 --> 00:06:46.280] Squarespace was a baby with no functionality back then.
[00:06:46.280 --> 00:06:50.920] And so it was like a fully functioning website or just like a landing page.
[00:06:50.920 --> 00:06:55.320] And I was explaining to them, you're going to pay one way or the other.
[00:06:55.320 --> 00:06:57.480] The question is, do you want to pay again in a year?
[00:06:57.480 --> 00:06:57.880] Yeah.
[00:06:58.200 --> 00:07:09.880] Or do you want to do the thing that you are trying to build with the things that you need to build the thing that you want to build and not having to do another rebuild super soon?
[00:07:09.880 --> 00:07:13.880] Because the goal is that you outgrow the basic thing really quickly.
[00:07:13.880 --> 00:07:14.680] That's why you're here.
[00:07:14.680 --> 00:07:15.120] Yes.
[00:07:14.760 --> 00:07:16.880] To start the business and do the thing.
[00:07:17.520 --> 00:07:27.760] So it often looks like I think probably the context for everyone listening to this is websites, you can also think like some payment processor aspects of this as well.
[00:07:27.760 --> 00:07:35.280] Also, I think email marketing platforms is a really great thing to look at whenever we're having this conversation.
[00:07:35.280 --> 00:07:36.160] What am I missing?
[00:07:36.160 --> 00:07:39.280] So those were actually the big ones that I was going to really pull examples from.
[00:07:39.280 --> 00:07:53.280] So yes, definitely build on your website, email marketing platforms/slash customer relationship platforms, but also just team management things like project management software and team communication software.
[00:07:53.280 --> 00:07:56.720] But also, this could apply to in-person hardware as well.
[00:07:56.720 --> 00:08:00.560] If you run a retail shop, so like your POS system and things like that.
[00:08:00.560 --> 00:08:07.200] So just computers, anything, any tech in your business could apply to this.
[00:08:07.680 --> 00:08:08.000] Right.
[00:08:08.000 --> 00:08:19.920] It's opting for the cheap and fast now as opposed to investing in the good now so that you don't experience growing pains quite so quickly.
[00:08:19.920 --> 00:08:25.840] And yes, and this is all essentially one big metaphor for monetary debt.
[00:08:25.840 --> 00:08:27.440] So it also has interest.
[00:08:27.440 --> 00:08:35.360] So if technical debt is not repaid, it can accumulate interest, making it harder to implement changes in the future.
[00:08:35.360 --> 00:08:37.040] Absolutely.
[00:08:37.040 --> 00:08:41.600] This is what I was always selling people on when it came to e-commerce back in the day, right?
[00:08:41.920 --> 00:08:44.400] Where this is going to be a big project.
[00:08:44.400 --> 00:08:49.760] And I would always get questions of like, well, can't we just like migrate things over like in a year whenever I'm done?
[00:08:49.760 --> 00:09:05.480] Yes, if you want to basically pay just as much as you would pay for me to do it right right now, because those migrations I think are usually more difficult than just setting it up well the first time.
[00:09:05.720 --> 00:09:09.720] I also think of literally all the times that we have moved email marketing platforms.
[00:09:09.720 --> 00:09:10.760] Oh my God.
[00:09:10.760 --> 00:09:11.240] Yeah.
[00:09:11.240 --> 00:09:15.240] Like that is literally Corey's job.
[00:09:16.200 --> 00:09:19.320] So like I'm like the least fun thing ever, but I haven't done that in a long time.
[00:09:19.320 --> 00:09:20.120] Thank you, Corey.
[00:09:20.440 --> 00:09:35.640] And I was actually going to say, I'm going to save the bigger examples for later in the episode, but actually now that you mentioned that, moving e-commerce or email marketing systems, one big example comes to mind that's actually something we're currently dealing with at BiddyTarot.
[00:09:35.720 --> 00:09:42.280] And for the most part, I'm not going to mention client names or anything during this episode because most of these issues are painting a customer in a bad light.
[00:09:42.280 --> 00:09:50.520] So I'm not going to mention customer names or anything during this episode, but I will mention BiddyTarot right now specifically because we have been using Entreport.
[00:09:50.600 --> 00:09:52.680] They have been using Entreport for 10 years.
[00:09:52.680 --> 00:09:55.480] Like they're one of the oldest Entreport clients.
[00:09:55.480 --> 00:10:05.560] And Entreport is not really meant to be used for companies of a large scale, like a company that has, you know, seven-figure, eight-figure businesses.
[00:10:05.560 --> 00:10:08.600] They're really meant for like mid-sized businesses.
[00:10:08.600 --> 00:10:13.080] But back when BiddyTarot started using Entreport, it was a mid-sized business.
[00:10:13.080 --> 00:10:27.000] But now we have ingrained Entreport so heavily into the business, like with all the APIs that tie into delivering content and empowering our e-commerce systems, all of our products, everything goes through Entreport.
[00:10:27.320 --> 00:10:36.600] We have hundreds of thousands of contacts in Entreport, thousands of emails, who knows how many transactions and things.
[00:10:36.600 --> 00:10:42.040] We are so integrated into the Entreport ecosystem that it's impossible to get out of it.
[00:10:42.040 --> 00:10:57.280] Like, we want to move to a better platform for the size of business that we are, but we, it's almost impossible at this point because we did not, where I say we, I was not here during this time, but the team as a whole did not anticipate the growth.
[00:10:57.280 --> 00:11:01.680] And so they kind of locked themselves in, and now it's almost impossible to get out of it.
[00:11:01.680 --> 00:11:04.880] Yeah, that's a really interesting scenario.
[00:11:04.880 --> 00:11:10.320] It gives me anxiety just hearing you say those things because I see how that can happen.
[00:11:10.320 --> 00:11:17.520] I also do want to say that time is a big element of this conversation as well.
[00:11:17.520 --> 00:11:17.920] Yes.
[00:11:17.920 --> 00:11:24.080] Whereas I imagine in that scenario, and I can think of a couple of like personal scenarios as well.
[00:11:24.080 --> 00:11:33.280] You know, back in those like baby days of the internet, love that, or baby days of like regular people doing e-commerce on the internet, right?
[00:11:33.280 --> 00:11:34.800] There weren't very many options.
[00:11:34.800 --> 00:11:36.880] And so you just went with what was there.
[00:11:37.600 --> 00:11:39.520] And then things grew and changed.
[00:11:39.520 --> 00:11:48.560] And then other options became available that were better options for what you do, but you were already in this thing and you didn't migrate then because things were going to, or like new features were coming or whatever it may be.
[00:11:48.560 --> 00:12:10.160] And so it's easy to just find yourself with debt, with tech debt as a product of operating on the internet, which really even makes it more important than to really sit down and have the kinds of conversations very early on around what your goals are, what sort of business you want to grow.
[00:12:10.560 --> 00:12:22.640] And really, this is a reason to think about business plans in a way that, you know, we don't really talk about a ton here, but is really important for building this infrastructure for your business.
[00:12:22.640 --> 00:12:25.680] So, anyway, that's just like a nutshell what we're talking about today.
[00:12:25.680 --> 00:12:33.480] I hope everyone can understand why this is so important and how it really does affect each and every one of us in some aspect or another.
[00:12:33.720 --> 00:12:42.120] I have some really great examples of how this has affected my work over the years and multiple different kinds of businesses, and I'm excited to dive in.
[00:12:42.120 --> 00:12:44.520] So, Corey, first question for you, sir.
[00:12:44.520 --> 00:12:51.400] Actually, really quick, if you wouldn't mind giving me like a 30-second why you can talk about this.
[00:12:51.400 --> 00:12:54.840] Oh, ooh, put this is gonna stroke my ego.
[00:12:54.840 --> 00:13:01.320] So, I know I have a huge tech background in my career.
[00:13:01.320 --> 00:13:09.160] I have been building websites for 20-ish years now, but then my technical expertise has grown.
[00:13:09.160 --> 00:13:14.680] So, obviously, we worked full-time on website development at IndieShopography for several years.
[00:13:14.840 --> 00:13:19.480] My expertise grew into podcast editing about eight, nine years ago.
[00:13:19.720 --> 00:13:34.200] And then at Biddy Tarot and other clients, I have grown my expertise into email marketing systems and funnel building and a whole wide range of people have worked with huge clients to clean up their tech systems.
[00:13:34.200 --> 00:13:46.040] So, it's really my specialty nowadays is focusing on the tech debt that clients and companies have and helping them address those issues and figuring out a path forward.
[00:13:46.040 --> 00:13:52.520] So, this really is my specialty nowadays for being boss, but also for Bitty Tarot and all the clients I still have.
[00:13:52.520 --> 00:13:52.920] Yeah.
[00:13:52.920 --> 00:13:57.000] Oh, I love that because you have done this for us for years.
[00:13:57.640 --> 00:14:00.200] I love that it has like such a nerdy little name.
[00:14:00.200 --> 00:14:00.920] All right, perfect.
[00:14:00.920 --> 00:14:02.840] So, let's like really dive into this.
[00:14:02.840 --> 00:14:09.640] And a couple of key little aspects to this really big conversation.
[00:14:09.640 --> 00:14:11.800] First, why does it matter?
[00:14:11.800 --> 00:14:17.520] And really, what does it hurt to accumulate tech debt?
[00:14:14.040 --> 00:14:28.240] Why should people listening to this think ahead and plan for bigger, better solutions as opposed to going with the fast, cheap, and easy of right now?
[00:14:28.240 --> 00:14:28.480] Yes.
[00:14:28.480 --> 00:14:33.520] And I do want to preface this by saying tech debt does not have to be a bad thing.
[00:14:33.520 --> 00:14:40.560] Just like financial debt does not have to be a bad thing, as long as you are aware of the debt.
[00:14:40.560 --> 00:14:42.240] But we'll talk about that in a second.
[00:14:42.240 --> 00:14:46.320] So, as far as what tech debt hurts, there's four big things.
[00:14:46.320 --> 00:14:51.920] The first big thing is dissatisfied users or customers.
[00:14:51.920 --> 00:15:21.280] So if you're putting out some kind of customer-facing thing, maybe something like a new website or e-course platform or anything like that, if you're building it or maybe going to a pre-built platform that maybe does not have all the functionality you need, it results in a bad user experience, which turns into possibly refunds and poor reviews and poor recommendations and just a bad customer experience.
[00:15:21.280 --> 00:15:25.600] Yeah, or like I imagine part of this is also lost sales.
[00:15:25.600 --> 00:15:26.000] Yes.
[00:15:26.000 --> 00:15:39.600] I was having a conversation with someone recently who, and now that I think about this, it is a tech debt issue of using an old platform or using the platform she'd been using for years.
[00:15:39.600 --> 00:15:47.360] But because she'd had it for so long, it did not have functionality that allowed her team to easily build sales pages.
[00:15:47.360 --> 00:15:50.240] So it was like a little more intense for them to do it.
[00:15:50.240 --> 00:15:51.040] They thought they could do it.
[00:15:51.040 --> 00:15:51.520] They went in.
[00:15:51.520 --> 00:15:52.640] They thought they did it.
[00:15:52.640 --> 00:15:55.200] Launched the thing, didn't test.
[00:15:55.200 --> 00:15:56.800] The button didn't work.
[00:15:56.800 --> 00:15:57.280] Yeah.
[00:15:57.520 --> 00:16:01.240] So she launched the thing and had people going to it.
[00:16:01.240 --> 00:16:07.080] And it took a couple of hours for someone to finally email and be like, I tried to buy this thing and I could not.
[00:16:07.080 --> 00:16:19.800] An issue, like a dissatisfied user literally lost sales because using an old platform that was not as easy for her team to utilize to create the things she needed to launch what she was launching.
[00:16:19.800 --> 00:16:20.280] Yes.
[00:16:20.280 --> 00:16:22.920] And that actually ties into another one of these.
[00:16:22.920 --> 00:16:26.520] So the next thing is limited innovation.
[00:16:26.760 --> 00:16:39.560] So when tech debt is severe, developers or if it's, you know, maybe your team or something needs to continue servicing the issues instead of devoting time to building new innovative features.
[00:16:39.560 --> 00:16:45.400] So if your team is spending all their time fixing things instead of building new things, that's tech debt.
[00:16:45.400 --> 00:16:45.800] Yeah.
[00:16:45.800 --> 00:16:49.080] Oh, that's literally interest that you're paying.
[00:16:49.080 --> 00:16:49.560] Yes.
[00:16:49.560 --> 00:16:52.840] Oh, and labor hours.
[00:16:52.840 --> 00:16:53.720] Snap.
[00:16:53.720 --> 00:16:54.360] I love that.
[00:16:54.360 --> 00:16:56.920] I mean, I don't, but like, yes, that's real.
[00:16:56.920 --> 00:16:57.960] That's real, real.
[00:16:57.960 --> 00:17:04.200] Okay, I want to share another aspect of this too, or maybe a way you can see red flags.
[00:17:04.200 --> 00:17:15.720] Or whenever I'm searching for a new platform for anything, like, you know, social media manager, email marketing platform, whatever, whatever, I always go look at their change logs.
[00:17:15.720 --> 00:17:16.120] Yes.
[00:17:16.120 --> 00:17:19.320] Or like their announcements for new features.
[00:17:19.320 --> 00:17:23.000] Are they managing their own platform?
[00:17:23.000 --> 00:17:26.200] Are they creating their own new features?
[00:17:26.200 --> 00:17:31.160] Are they like listening to the customers and creating little buttons and widgets and all the things that they need?
[00:17:31.160 --> 00:17:35.080] Or have they not updated their own software in three months?
[00:17:35.080 --> 00:17:39.000] Because sometimes the tech debt isn't just your fault.
[00:17:39.000 --> 00:17:41.400] It's also the fault of the platform.
[00:17:41.400 --> 00:17:54.640] And so, that's a way that I, um, it's a way, or one of the things I do when I'm searching for new platforms for things is I'm checking their updates to see how active their team is.
[00:17:54.640 --> 00:18:00.640] Yeah, because if their team is not active, this limited innovation is going to happen even faster.
[00:18:00.640 --> 00:18:02.880] Yeah, so actually, I'm glad you said that.
[00:18:02.880 --> 00:18:09.520] So, over at Biddy Tarot, we're all up in our metrics reporting project right now.
[00:18:09.520 --> 00:18:21.280] We're trying to reinvent how we're doing metrics reporting and data calculations and everything just to kind of centralize it and make sure we're getting a clearer picture on all of our conversion points and stuff like that.
[00:18:21.440 --> 00:18:31.360] So, we're trying to find a new dashboard platform that actually integrates with Entreport and everything that can build like pretty graphs and stuff like that.
[00:18:31.360 --> 00:18:39.920] And we came across one service that does have an Entreport integration, which is relatively rare, and it looked great.
[00:18:39.920 --> 00:18:43.680] But I dove a little bit deeper into this platform.
[00:18:43.680 --> 00:18:48.160] Their website, the copyright date, was like four years old.
[00:18:48.640 --> 00:18:53.200] Their Facebook group had their Facebook page had not been updated in a couple of years.
[00:18:53.200 --> 00:19:00.240] And so it was just not painting a pretty picture that this was actually a platform that was constantly being kept up to date.
[00:19:00.240 --> 00:19:01.600] And so that was kind of like a red flag.
[00:19:01.600 --> 00:19:05.040] Like, yeah, maybe it works right now, but will it work a year from now?
[00:19:05.040 --> 00:19:05.680] Yeah.
[00:19:05.680 --> 00:19:12.400] So I would not recommend signing up for that because you might have to start all over again if the software ever actually stops working.
[00:19:12.400 --> 00:19:12.960] Yep.
[00:19:12.960 --> 00:19:14.480] Oh, that's, yeah.
[00:19:14.480 --> 00:19:15.600] Check those things.
[00:19:15.920 --> 00:19:17.360] You also mentioned integrations.
[00:19:17.360 --> 00:19:23.280] I also like to look at what things integrate with because if there's just a couple, they're not doing much.
[00:19:23.280 --> 00:19:27.600] If they have like a really great integration list, then they're doing their job.
[00:19:27.600 --> 00:19:33.240] If they have too many integrations, I'm like, something's a little odd here.
[00:19:33.480 --> 00:19:34.440] Are these all real?
[00:19:29.840 --> 00:19:37.400] Yeah, so we're getting into kind of the prevention things.
[00:19:37.400 --> 00:19:38.600] So what to look out for?
[00:19:39.160 --> 00:19:40.040] Oh, am I getting ahead of us?
[00:19:40.120 --> 00:19:40.520] No, you're fine.
[00:19:40.520 --> 00:19:41.080] You're fine at all.
[00:19:44.360 --> 00:19:45.560] Then what's next?
[00:19:45.560 --> 00:19:47.160] What is another one of these four?
[00:19:47.160 --> 00:19:47.400] Yes.
[00:19:47.400 --> 00:19:50.760] So number three is longer development cycles.
[00:19:51.320 --> 00:19:57.480] So yet again, this is all coming from a tech perspective, so like coding and stuff, but it could be applied in a broader sense.
[00:19:57.640 --> 00:20:11.240] So as tech tech debt worsens, it becomes harder for developers to work within the existing code base, splitting time between developing new features and correcting old ones, which slows the build process and delays time to market.
[00:20:11.240 --> 00:20:18.120] So this could apply for obviously website development, but also maybe email marketing funnels and stuff like that.
[00:20:18.440 --> 00:20:21.720] I mean, I think about this with our old website projects.
[00:20:22.280 --> 00:20:31.800] I never loved it when someone came to me with an old, clunky website and wanted to update that thing.
[00:20:31.800 --> 00:20:32.280] Yeah.
[00:20:32.280 --> 00:20:33.000] Right?
[00:20:33.000 --> 00:20:34.120] Absolutely not.
[00:20:34.120 --> 00:20:45.880] I will create for you a whole new website and I will do that painful migration process and I will do the thing, but going in and one, figuring out someone else's code or figuring actually the same thing for email flows.
[00:20:45.880 --> 00:20:49.640] For like people build email flows differently.
[00:20:49.640 --> 00:20:52.600] I can't look at your email flows and make any sense of it.
[00:20:52.600 --> 00:20:54.920] And I know that you can't look at mine and make any sense of it.
[00:20:54.920 --> 00:20:57.080] Like we build them completely differently.
[00:20:57.080 --> 00:21:13.880] And so it's going to take twice as long for me to just get in there and figure something out, like what I'm looking at before I go and start tweaking and building, as opposed to just doing something fresh over here, completely separate from that thing that I don't understand.
[00:21:13.880 --> 00:21:18.400] Yeah, this is kind of where the Bandaid solution comes into play.
[00:21:18.400 --> 00:21:28.560] If you identify a problem and you implement a simple fix with the idea that, oh, we'll come back and fix it later, but then you never come back and fix it later.
[00:21:28.560 --> 00:21:41.760] Then when you actually come in to do something new, it's a whole bigger issue because you're not only having to try to build something new, you're also having to deal with this age-old issue that it's going to take hours and hours and hours to fix.
[00:21:41.760 --> 00:21:42.080] Yeah.
[00:21:42.080 --> 00:21:48.480] So the idea is that instead, you should keep things more maintained, more up to date on a consistent basis.
[00:21:48.480 --> 00:21:52.720] So when it does come time to do something new, it's a lot easier and simpler.
[00:21:52.720 --> 00:21:53.920] Amen to that.
[00:21:53.920 --> 00:21:55.280] What's the fourth one?
[00:21:55.280 --> 00:21:57.200] The fourth one that's a scary one.
[00:21:57.200 --> 00:21:59.840] It's security problems.
[00:22:00.160 --> 00:22:00.800] Yeah.
[00:22:01.120 --> 00:22:02.160] Real, real.
[00:22:02.160 --> 00:22:14.080] So this one, yet again, tying more heavily into the code side of things, but nowadays it could factor into two-factor authentication or making sure your passwords are regularly changed out and stuff like that.
[00:22:14.080 --> 00:22:21.040] So poorly written code is often poorly secured, which can introduce unexpected vulnerabilities to enterprise software systems.
[00:22:21.040 --> 00:22:29.680] So applying this in a broader sense, if you go make your password password, that's first of all, just lazy.
[00:22:29.680 --> 00:22:30.560] So come on.
[00:22:30.560 --> 00:22:36.560] But also, that's pretty poorly secured and it's going to open you up to vulnerabilities.
[00:22:36.560 --> 00:22:47.440] So taking the time at the beginning of the project or beginning of creating your account to set a more secure password or what have you, it's going to save you issues in the long run.
[00:22:47.440 --> 00:22:47.920] Yeah.
[00:22:47.920 --> 00:22:58.560] I will just say, even looking at the platform thing again, a platform that will allow you to create a password that is just password is also a red flag.
[00:22:58.880 --> 00:23:00.680] They should be more secure.
[00:23:00.680 --> 00:23:02.760] And security is a real one.
[00:23:02.760 --> 00:23:06.120] And it's become more important.
[00:22:59.840 --> 00:23:06.760] It's always been important.
[00:23:07.000 --> 00:23:07.480] It's always been important.
[00:23:07.560 --> 00:23:14.520] It's become more at the forefront of conversations, especially since GDPR happened a couple of years ago.
[00:23:14.520 --> 00:23:25.000] If you look, Google it, where in the EU, they did some legislation around keeping people's personal information safe on the internet.
[00:23:25.240 --> 00:23:28.040] That affected all of us in one way or another.
[00:23:28.040 --> 00:23:29.400] So I have two thoughts.
[00:23:29.400 --> 00:23:44.040] So that sucked because that was kind of forced upon us tech debt because everybody on the internet had to scramble to implement these changes to keep customers' data private and give them options to opt out of things.
[00:23:44.040 --> 00:23:46.440] So that was things we were not prepared for.
[00:23:46.520 --> 00:23:48.040] Like no one was prepared for.
[00:23:48.040 --> 00:23:54.840] And so when that was put into effect, everyone had to scramble to address that debt immediately, which kind of sucked.
[00:23:54.840 --> 00:24:02.280] But this also ties into our examples section of this podcast, which is where I get to kind of tell some Corey stories.
[00:24:02.280 --> 00:24:06.200] So this is going to be a four-parter now, everybody.
[00:24:06.840 --> 00:24:21.240] So the big scary one, kind of tying into the security we were just talking about, I had a client whose website was infected by malware and it created a whole snowball of big issues.
[00:24:21.560 --> 00:24:27.480] And so going back, I guess, three years ago, they paid no attention to securing their website.
[00:24:27.480 --> 00:24:30.360] So they didn't have any kind of firewalls in place.
[00:24:30.360 --> 00:24:35.080] They didn't have any kind of like CAPTCHAs or anything on their admin interface.
[00:24:35.080 --> 00:24:41.480] So if some kind of robot or bad actor wanted to get low-hanging fruit.
[00:24:41.560 --> 00:24:45.040] Yeah, low-hanging fruit, unsecured server, everything.
[00:24:44.600 --> 00:24:47.840] So their site got infected by malware.
[00:24:48.480 --> 00:24:52.880] You know, it was all kinds of pop-ups and things.
[00:24:52.880 --> 00:24:54.480] I'll just put it at that.
[00:24:56.240 --> 00:24:58.480] So that created issue number one.
[00:24:58.480 --> 00:25:06.960] Just their site was taken over by unseemly things, which had to be addressed because they were actually, this was a law firm.
[00:25:06.960 --> 00:25:15.600] And so they were having like clients that were coming to them for legal things and their website was showing them porn.
[00:25:15.600 --> 00:25:17.200] So big issue, right?
[00:25:17.200 --> 00:25:17.840] Yeah, yeah.
[00:25:18.080 --> 00:25:25.520] So first of all, that just that malware was a headache to clean up because it was infecting all parts of the website.
[00:25:25.520 --> 00:25:27.200] It was on the back end of the website.
[00:25:27.200 --> 00:25:28.960] It was on the server.
[00:25:28.960 --> 00:25:30.160] It was in the database.
[00:25:30.160 --> 00:25:31.040] It was all over.
[00:25:31.040 --> 00:25:32.800] It was a nightmare to clean up.
[00:25:32.800 --> 00:25:49.680] Two years later, the website is still showing up on malware blacklists because robots of the security providers that scanned the website back when it was still infected, they have not updated their listings for this website.
[00:25:49.680 --> 00:25:57.280] So a lot of security providers still think the website is infected, even though it's confirmed clean by multiple providers.
[00:25:57.280 --> 00:26:02.320] So this is causing the website to be blocked by different internet providers.
[00:26:02.320 --> 00:26:11.360] So ATT, actually, one of the bigger providers in the country, is actually still blocking this website for a lot of people, even though the website is clean.
[00:26:11.360 --> 00:26:12.800] It's been verified clean.
[00:26:12.800 --> 00:26:15.200] But ATT still thinks it's infected.
[00:26:15.200 --> 00:26:18.720] That was an awful story before it turned into an awful story.
[00:26:18.720 --> 00:26:22.640] And actually, it snowballs because of malware infections.
[00:26:22.640 --> 00:26:25.120] It's actually a domain reputation thing.
[00:26:25.120 --> 00:26:29.040] So it's infecting, or it's affecting their email delivery ability as well.
[00:26:29.040 --> 00:26:35.080] So they're having an issue emailing clients because their domain name is also being flagged as malware.
[00:26:35.720 --> 00:26:38.200] So it's affecting their entire business.
[00:26:38.200 --> 00:26:38.920] Ew.
[00:26:38.920 --> 00:26:39.480] Yeah.
[00:26:39.480 --> 00:26:39.960] Okay.
[00:26:39.960 --> 00:26:41.880] You started, I think, with, was that the best one?
[00:26:41.880 --> 00:26:44.680] That was the scariest one.
[00:26:44.680 --> 00:26:46.280] Okay, that is scary.
[00:26:47.000 --> 00:26:48.680] That is scary.
[00:26:49.960 --> 00:26:53.960] Growing your business can get complicated, but the tech you use shouldn't.
[00:26:53.960 --> 00:26:58.280] That's why HubSpot's CRM platform is easy to learn, use, and love.
[00:26:58.280 --> 00:27:11.080] Hear it from a real boss using HubSpot to grow their business better in 2023 and get a special offer of 20% off on eligible plans at hubspot.com/slash being boss.
[00:27:11.400 --> 00:27:12.840] My name is Kelly Kimple.
[00:27:12.840 --> 00:27:15.480] I'm the CEO of Adventures and Good Company.
[00:27:15.480 --> 00:27:19.960] As you know, growing a business is hard, and the tools you use should help make things easier.
[00:27:19.960 --> 00:27:23.240] It's important to us to have tools that work the way we do.
[00:27:23.240 --> 00:27:26.760] HubSpot CRM platform has seamlessly scaled with our needs.
[00:27:26.760 --> 00:27:34.760] We were seeking a more efficient way to extend the longevity of communicating with our current customers while still nurturing the relationships and new and potential customers.
[00:27:34.760 --> 00:27:42.200] With HubSpot, our team is able to work all in one place to create a customized experience for every encounter at every stage of the customer's journey.
[00:27:42.200 --> 00:27:47.000] The HubSpot CRM platform makes daily tasks easier for all of our departments to use.
[00:27:47.000 --> 00:27:58.040] From the marketing team to customer service to operations, our busy work gets automated, and we can spend time doing what we do best, creating experiences of a lifetime for women seeking new adventures.
[00:27:58.040 --> 00:28:03.400] We're able to grow our database with free forms and landing pages that convert visitors into qualified leads.
[00:28:03.400 --> 00:28:09.160] HubSpot CRM automatically organizes, enriches, and tracks each content into a tidy timeline.
[00:28:09.160 --> 00:28:16.000] From there, we're able to nurture our leads with bulk emails that are easy to create and automatically optimize for a different devices.
[00:28:14.920 --> 00:28:22.160] With the built-in analytics, we can easily learn which emails, pages, and traffic sources are driving the most conversions.
[00:28:22.480 --> 00:28:27.040] Learn how HubSpot can help your business grow better at hubspot.com.
[00:28:28.960 --> 00:28:33.920] So, number two, my second example is a coding thing.
[00:28:33.920 --> 00:28:37.680] So, more like just development, poor development practices.
[00:28:37.680 --> 00:28:40.240] This is why you hire a good website versus everybody.
[00:28:40.480 --> 00:28:50.400] This is why you should do your due diligence when you're hiring someone to build something new for you, whether it's a website or your email marketing, what have you.
[00:28:50.400 --> 00:29:00.560] Just when you're hiring an outside somebody to come build something for you, make sure you're hiring someone that comes with glowing recommendations and can show their work.
[00:29:00.560 --> 00:29:21.280] Because I have an example of a client who was launching a brand new community platform, community website where people could pay to have a membership to access things like e-courses and a community forum and free webinars and all this stuff.
[00:29:21.280 --> 00:29:31.360] A big paid platform with a bunch of content because their previous version of the community was running on a platform that was six, seven years old.
[00:29:31.360 --> 00:29:35.920] And if you have been on the internet, that's ancient years.
[00:29:36.240 --> 00:29:45.760] So, with all of the innovation that social networks and things like that have had the past few years, a six, seven-year-old platform for a community, super old.
[00:29:45.760 --> 00:29:47.440] It's not what people are expecting anymore.
[00:29:47.440 --> 00:29:54.480] So, they finally put in all of the money, all the time to hire an agency to relaunch their community offering.
[00:29:54.480 --> 00:30:04.040] And the team for this company, before it launched, flagged that the way it was being built was not ideal, at least as far as the code went.
[00:30:04.040 --> 00:30:11.880] It was not being built in a very database-friendly way because this was a pretty high-trafficked community, so thousands of members.
[00:30:11.880 --> 00:30:17.480] If thousands of members are accessing this, there's going to be a lot of data on the back end, so it's going to be a huge database.
[00:30:17.480 --> 00:30:21.320] And if the server's not up to the task, it's going to load slow and stuff like that.
[00:30:21.560 --> 00:30:39.720] So, it was flagged that the code and everything on the back end was not being done in a very sustainable way, and it was kind of ignored because it was a very important project to get launched on time because the date had already been announced for when this project or when this new community website was going to be launched.
[00:30:39.720 --> 00:30:44.520] And so, it launched, and the problems that were flagged ended up being a problem.
[00:30:44.520 --> 00:30:53.160] It was so slow, customers were flagging that they were being timed out, they couldn't access anything, so it was just a huge bad launch.
[00:30:53.160 --> 00:30:59.160] And so, it actually ties into dissatisfied customers, but also a longer development cycle.
[00:30:59.160 --> 00:31:07.240] Because now that the website is launched, another person has been hired to actually go in and fix all those issues that should not have been issues to begin with.
[00:31:07.240 --> 00:31:10.360] Yeah, scope creep out-the-wall zoo.
[00:31:10.360 --> 00:31:23.400] It is triple what it should have been, what it should have cost because not only did they have all of the original payment for the original team that built it, now they had to have someone else to come in and fix all the issues that should have been not an issue to begin with.
[00:31:23.400 --> 00:31:32.360] If this had been done perfectly, at what point in this journey should something have happened differently?
[00:31:32.360 --> 00:31:41.320] As soon as that issue was flagged, it should have been okay to extend the development cycle and not launch a broken product.
[00:31:41.640 --> 00:31:48.400] So, even if it takes longer to build something, it's okay as long as you eventually put out a working product.
[00:31:48.560 --> 00:31:53.040] This actually ties into a video game issue because I love video games.
[00:31:53.040 --> 00:32:01.440] A couple of years ago, a video game, Cyberpunk 2077, launched and it was a broken game, but like it was supposed to be like the next big thing in video games.
[00:32:01.440 --> 00:32:03.280] It was completely broken.
[00:32:03.280 --> 00:32:07.360] PlayStation and Xbox ended up issuing refunds, which they never do.
[00:32:07.680 --> 00:32:16.160] And it was all because in the quality control phase of that video game development, they completely ignored the fact that it was a broken game.
[00:32:16.160 --> 00:32:24.080] They just, from what they were seeing, it was fine, but no one actually bothered to raise the flag that, oh, this is going to cause a lot of problems when it launches.
[00:32:24.080 --> 00:32:26.960] Maybe we should wait until it's actually fixed before we launch it.
[00:32:26.960 --> 00:32:28.160] And so it's a whole thing.
[00:32:28.160 --> 00:32:39.040] So anyway, it's just once you flag that there are issues, slow down, take more time, get it right, wait till it's ready, and then launch it.
[00:32:39.360 --> 00:32:39.920] Yeah.
[00:32:40.400 --> 00:32:48.240] I want to look at, I want to talk a little bit about what this looks like from doing things as best you can from the beginning.
[00:32:48.240 --> 00:32:53.280] I'm going to use myself as an example.
[00:32:53.280 --> 00:32:59.040] Because coming from websites, I understand the importance of this.
[00:32:59.040 --> 00:33:30.840] And so whenever I launched Almanac, you know, launch really small 2018 handful of products, whole shebang, it would have been very easy for me to go back to any of the platforms that I had developed websites on before and build something that I was used to building, that had the ability or had the functionality that I needed for right now, but was not going to help me get to my goals because my goal was absolutely in-person retail.
[00:33:29.920 --> 00:33:37.320] Yeah, so instead of doing what was fast, cheap, and easy for right now, I could have done it myself.
[00:33:37.960 --> 00:33:42.520] I could have done it super quickly in a platform that I was familiar with.
[00:33:42.520 --> 00:34:02.600] I instead looked at my growth goals and made the decision to go with a platform that I don't know I had built on it like twice before, like two times, not 50, like some of the other platforms, two times, two times before.
[00:34:02.600 --> 00:34:10.680] I ended up going to Shopify because it had functionality that I knew I wasn't going to use for like two years at least.
[00:34:10.680 --> 00:34:15.560] And to this day, six years later, I'm is it been six years?
[00:34:15.560 --> 00:34:17.240] Holy cow, it has been six years.
[00:34:17.240 --> 00:34:20.280] That came out of my nope, it's been four.
[00:34:20.600 --> 00:34:21.320] What is time?
[00:34:21.400 --> 00:34:22.840] Timey, whimy, right?
[00:34:23.160 --> 00:34:35.000] So, four years later, still on the exact same website, exact same platform, inventory is in there, team is using it, training is happening, functionality is growing, right?
[00:34:35.000 --> 00:34:42.920] As we are in there going, I made a decision four years ago for something that I wanted in four years, basically.
[00:34:43.240 --> 00:34:49.240] And I invested in doing the big thing then that has me fully functional now.
[00:34:49.240 --> 00:34:57.320] And I have not had to do any major rework to that piece of my technological existence in all of that time.
[00:34:57.320 --> 00:35:02.600] And I probably won't have to for the foreseeable future, knock on wood.
[00:35:02.600 --> 00:35:03.880] Yeah, you had forethought.
[00:35:03.880 --> 00:35:05.160] Good job.
[00:35:05.160 --> 00:35:06.360] Indeed, indeed.
[00:35:06.360 --> 00:35:07.400] And that's what I want.
[00:35:07.400 --> 00:35:08.520] That's what I want for everyone.
[00:35:08.520 --> 00:35:11.240] I want everyone to sort of see the difference in that as well.
[00:35:11.240 --> 00:35:26.240] I think this client you were just talking about, with, you know, having had this community built that came to a point where things were not good, needed to move forward, made maybe not the best decision to move forward despite the problems.
[00:35:26.560 --> 00:35:33.360] I want to make this point that like that first iteration, even though it ended up being the problem, it wasn't the problem.
[00:35:33.680 --> 00:35:39.760] Like you do the best you can with what you can, knowing what you know when you know it.
[00:35:40.080 --> 00:35:46.560] But the moment the flag came up is when the problem existed and then you move forward from that.
[00:35:46.560 --> 00:35:59.520] So not everyone is able to make the decision that I made in terms of our like, and whenever I say like website platform at Almanac, Shopify is the system that runs our business.
[00:35:59.520 --> 00:36:00.640] It's our POS.
[00:36:00.640 --> 00:36:02.240] It's tracking our inventory.
[00:36:02.240 --> 00:36:06.160] We do have a separate inventory tracking system that is a whole other conversation.
[00:36:07.120 --> 00:36:12.080] But that was a decision that we made then for now.
[00:36:12.080 --> 00:36:14.160] And I love that for us.
[00:36:14.480 --> 00:36:18.720] And it's something that I want everyone to think about when they are investing in something.
[00:36:18.720 --> 00:36:36.000] Because I don't think I'm going to find myself in a situation like this client did, because I was at a point in the life of the internet when I could make the investment and where I wanted to be in four, six, ten years.
[00:36:36.000 --> 00:36:36.400] Yeah.
[00:36:37.040 --> 00:36:44.640] So I have one more example I want to mention because it kind of slightly outside of the tech thing.
[00:36:44.640 --> 00:36:48.640] So it's not going to be about coding and stuff, but it is tech related.
[00:36:48.640 --> 00:36:51.840] So, a little bit more people can relate to this one.
[00:36:52.480 --> 00:36:54.560] So, it's another horror story.
[00:36:54.880 --> 00:36:58.480] It's about being delisted from Google.
[00:36:58.480 --> 00:37:01.000] God, that's like internet suicide.
[00:36:59.920 --> 00:37:02.520] Yes, especially for this company.
[00:37:02.760 --> 00:37:08.680] So, this is another client, and their entire business ran on their blog.
[00:37:08.680 --> 00:37:17.320] It was a seven-figure business, and vast majority of their traffic, 90-95% of the traffic, came from Google search.
[00:37:17.320 --> 00:37:25.800] And their blog functioned by running ads as well as sponsored blog posts.
[00:37:25.800 --> 00:37:33.240] And so, occasionally, maybe every couple of weeks, they would publish a blog post that was paid for by some third party.
[00:37:33.240 --> 00:37:52.440] Now, with Google, they require you to flag in some way in that post that it is sponsored content, such as if they click on a link and it's a link that could generate money for that business, you have to label it as an affiliate link.
[00:37:52.760 --> 00:37:56.040] They had not been doing this for years.
[00:37:56.680 --> 00:37:58.040] Oh, God.
[00:37:58.040 --> 00:37:59.800] And so, when I felt that in my gut.
[00:37:59.800 --> 00:38:12.280] Yeah, so when Google finally realized that all of these sponsored posts and affiliate links were not being labeled, they delisted the website entirely from Google.
[00:38:12.280 --> 00:38:32.680] Years and years of Google search results had been wiped overnight, and it obviously tanked their business because all of their traffic ceased to come in, and that dried up their revenue almost overnight because they relied so heavily on traffic from Google.
[00:38:32.680 --> 00:38:38.200] And when you get delisted from Google, for they were flagged for being spam, essentially.
[00:38:38.200 --> 00:38:46.720] When Google flags your site as spam, it is a task to get relisted because you have to go through a verification process.
[00:38:47.040 --> 00:38:52.880] And unless you do every single thing exactly how they want it, you're gonna have to re-go through the verification process.
[00:38:52.880 --> 00:38:56.400] And the verification process takes weeks sometimes.
[00:38:56.400 --> 00:39:04.880] And so they had to go post by post to address every single link that they had not flagged or labeled as an affiliate link.
[00:39:04.880 --> 00:39:09.680] It took them, I think, three months to finally get relisted in Google.
[00:39:09.680 --> 00:39:20.400] And you have to think when 95% of your traffic is coming from Google and that's what's generating your seven-figure income, and you're delisted for three months, their revenue tanked.
[00:39:20.400 --> 00:39:22.480] It destroyed their business.
[00:39:22.480 --> 00:39:24.160] Oh, I want to barf.
[00:39:24.160 --> 00:39:24.640] Yeah.
[00:39:24.640 --> 00:39:26.480] I want to barf over that one.
[00:39:26.480 --> 00:39:35.120] You know, what's coming up for me with this one, and it's something that I've experienced a couple of times before, and I think we're probably going to talk around this in a minute.
[00:39:35.120 --> 00:39:45.200] Is this why internet business needs to be taken as seriously as non-internet business?
[00:39:45.200 --> 00:39:45.600] Yes.
[00:39:45.600 --> 00:39:51.120] I feel like there is this idea that getting, and it used to be, used to, you could get away with all kinds of shit.
[00:39:51.120 --> 00:39:54.560] Kathleen and I used to call it the wild, wild west of the internet, right?
[00:39:54.560 --> 00:40:00.880] Where you could just like show up and put links and sell things, and it didn't, you didn't need terms and conditions, like whatever.
[00:40:00.880 --> 00:40:02.000] You could do anything.
[00:40:02.000 --> 00:40:05.440] Now they care, and they is everybody.
[00:40:05.440 --> 00:40:05.840] Yeah.
[00:40:05.840 --> 00:40:11.040] Google, the government, what's the difference between the two, right?
[00:40:11.040 --> 00:40:17.600] And so you have to know, you have to stay up to date on all of these things.
[00:40:17.840 --> 00:40:25.120] If you have not subscribed to our lawyer Autumn Whitboyd's email, list, go sign up.
[00:40:25.120 --> 00:40:29.440] She's always doing nice little updates of some things that are happening in the world that are incredibly important.
[00:40:29.440 --> 00:40:35.000] But I feel like so much of this stuff also just comes from not knowing.
[00:40:35.320 --> 00:40:38.520] You don't even know that you need to do these things.
[00:40:38.520 --> 00:40:40.840] I think sometimes you do know and you don't do it.
[00:40:40.840 --> 00:40:42.440] And that's obviously a problem.
[00:40:42.440 --> 00:40:53.480] But I think a lot of these things can also come from not knowing, which is why it's important to like have your good resources, awbfirm.com, right?
[00:40:53.800 --> 00:41:04.680] And also have a tech guy, not tech guy, a tech person, not in your pocket, but on speed dial/slash fast email.
[00:41:04.680 --> 00:41:05.000] Yeah.
[00:41:05.000 --> 00:41:06.200] Slack on Slack.
[00:41:06.200 --> 00:41:06.920] How about that?
[00:41:08.440 --> 00:41:11.800] Because these things are incredibly important.
[00:41:11.800 --> 00:41:15.080] Someone needs to be looking out for you if this is not your forte.
[00:41:15.080 --> 00:41:20.920] And when all shit hits the fan and no one saw the thing coming, you need someone to fix it for you.
[00:41:20.920 --> 00:41:21.560] Yeah.
[00:41:22.280 --> 00:41:25.800] You want to talk about the causes of tech debt?
[00:41:25.800 --> 00:41:26.120] Absolutely.
[00:41:26.280 --> 00:41:27.560] And what to look out for?
[00:41:27.560 --> 00:41:28.200] Yeah.
[00:41:28.200 --> 00:41:28.520] Yeah.
[00:41:28.520 --> 00:41:34.360] I feel like everyone probably currently is thinking of their horror story one way or the other, right?
[00:41:34.360 --> 00:41:35.240] Everyone has them.
[00:41:35.240 --> 00:41:38.280] And I, what is what is one of ours?
[00:41:38.280 --> 00:41:39.160] Can we share?
[00:41:39.160 --> 00:41:42.120] Is there a Bing boss or an almanac one?
[00:41:42.360 --> 00:41:44.200] I mean, I don't let you have these issues.
[00:41:44.200 --> 00:41:44.600] So no.
[00:41:44.840 --> 00:41:45.160] I know.
[00:41:45.160 --> 00:41:45.800] I was.
[00:41:45.800 --> 00:41:46.360] I love that.
[00:41:46.360 --> 00:41:47.800] None of these were about us.
[00:41:47.800 --> 00:41:51.240] Just so you know, we are GDPR was one for everyone.
[00:41:51.240 --> 00:41:52.280] You mentioned that one.
[00:41:52.600 --> 00:41:56.680] Actually, I have a little almanac one, and it's because I didn't get you to do it.
[00:41:57.000 --> 00:41:58.360] I think I know what you're going to say.
[00:41:58.360 --> 00:41:59.080] So, yes.
[00:41:59.640 --> 00:42:00.760] You probably don't.
[00:42:01.240 --> 00:42:12.120] So, whenever we moved our email marketing platform from ConvertKit, which is not for e-commerce, we just put it there because that was something I was familiar with.
[00:42:12.120 --> 00:42:14.680] Okay, so you're here in that, something I was familiar with.
[00:42:14.680 --> 00:42:20.400] Went with something that a platform that wasn't really for the kind of business we did, but like just needed fast, cheap, and easy.
[00:42:14.840 --> 00:42:20.960] Let's make it do.
[00:42:21.360 --> 00:42:24.000] Went with ConvertKit, worked okay for a couple of years.
[00:42:24.000 --> 00:42:29.520] Time to move to Clavio, which I do highly recommend for users of Shopify in particular.
[00:42:29.520 --> 00:42:32.400] I think the functionality is really great.
[00:42:32.400 --> 00:42:35.920] Do recommend not an affiliate.
[00:42:35.920 --> 00:42:39.120] So, moved over, which was a whole scenario in itself.
[00:42:39.120 --> 00:42:42.640] Moved over our funnels, moved over our contacts, like did all the things.
[00:42:42.640 --> 00:42:46.160] And I had hired someone to help me do some marketing things.
[00:42:46.160 --> 00:42:48.160] And I was like, Can you set up our Clavio for us?
[00:42:48.160 --> 00:42:50.080] And she was like, Sure, I'll make it do.
[00:42:50.560 --> 00:43:02.080] One of the things that did not get moved over correctly that I then had to fix about a year later when I realized that it had been done incorrectly was moving over birthday tags.
[00:43:02.080 --> 00:43:12.640] So, we had been working for years to have our contacts tag themselves with their birthday month so that we could send them a coupon code during the month of their birthday.
[00:43:12.640 --> 00:43:20.960] It was one of our regular marketing things, had done it for years, loved it, had people waiting on their birthday coupon, whole amazing thing.
[00:43:21.280 --> 00:43:34.160] She'd created the tags, but because she was not a Clavio expert, she didn't know that she didn't do it right until it came time for me to create a whole new year of emails and tag everybody with this tag.
[00:43:34.160 --> 00:43:41.440] ConvertKit has been deleted, so I can't go like double-check and like re-import people with the right tags.
[00:43:41.440 --> 00:43:43.280] Nothing I could do about it.
[00:43:43.280 --> 00:43:46.480] All of that data was lost, every single bit of it.
[00:43:46.480 --> 00:43:56.800] So, I had to come up with another solution, which was actually implementing a reward system that I had been meaning to implement anyway as an alternative to birthday rewards.
[00:43:56.800 --> 00:44:03.880] Um, but that one for me was that's a very minor little nightmare, but hurt my feelings.
[00:43:59.840 --> 00:44:05.000] Didn't hurt my feelings.
[00:44:05.240 --> 00:44:12.040] Like it made me sad to have lost that data and that ability to nurture my customers in that way.
[00:44:12.040 --> 00:44:12.760] Yeah.
[00:44:13.080 --> 00:44:15.240] If I'd gotten you to do it, it probably wouldn't have happened.
[00:44:15.240 --> 00:44:16.120] I'm sorry.
[00:44:16.120 --> 00:44:17.320] It's okay.
[00:44:17.640 --> 00:44:18.280] Now you know.
[00:44:18.280 --> 00:44:19.000] Now you know.
[00:44:19.000 --> 00:44:19.800] You learned.
[00:44:19.800 --> 00:44:20.120] Right.
[00:44:20.440 --> 00:44:21.320] So there's mine.
[00:44:21.320 --> 00:44:24.600] So I'll have to say we all have, we all have them for sure.
[00:44:24.600 --> 00:44:25.400] It's fine.
[00:44:25.400 --> 00:44:27.560] But what causes them, Corey?
[00:44:27.880 --> 00:44:33.400] So there are the four quadrants of technical debt.
[00:44:33.400 --> 00:44:35.880] So for literally a graph in our agendas.
[00:44:35.880 --> 00:44:38.440] This has never happened, literally ever.
[00:44:38.440 --> 00:44:45.400] In like almost 400 episodes, there has never been a graph present in an agenda.
[00:44:45.400 --> 00:44:46.760] And I'm looking at one right now.
[00:44:46.760 --> 00:44:48.520] Corey, you have outbossed me.
[00:44:48.520 --> 00:44:49.320] I know, right?
[00:44:49.480 --> 00:45:00.840] Corinne, when you're making the show notes, we can include this Asana link in the show notes because Asana put together a great article that kind of summarizes all the aspects of technical debt with graphs.
[00:45:00.840 --> 00:45:06.200] So I stole one of their graphs and they break it down into four quadrants of technical debt.
[00:45:06.520 --> 00:45:10.200] So the first one is prudent and deliberate.
[00:45:10.520 --> 00:45:15.560] This is the decision to ship quickly and deal with the consequences later.
[00:45:15.560 --> 00:45:23.960] So this type of debt is most commonly used when the stakes of the product are relatively low and the benefits of a quick delivery outweigh the risk.
[00:45:26.040 --> 00:45:27.480] Speedy much.
[00:45:27.480 --> 00:45:28.120] Yeah.
[00:45:28.120 --> 00:45:28.520] Right?
[00:45:28.520 --> 00:45:30.440] Just get it out there even if it's broken.
[00:45:30.440 --> 00:45:32.120] That's never cute, y'all.
[00:45:32.120 --> 00:45:33.960] You're going to pay for that later.
[00:45:33.960 --> 00:45:37.240] So, that is prudent and deliberate tech debt.
[00:45:37.240 --> 00:45:37.800] What's next?
[00:45:37.800 --> 00:45:40.200] Number two, reckless and deliberate.
[00:45:40.200 --> 00:45:46.160] So, knowing how to produce the best product, but by prioritizing speedy delivery over it.
[00:45:46.160 --> 00:45:47.920] Oh, so that's just like screw it.
[00:45:47.920 --> 00:45:48.560] Yeah.
[00:45:44.760 --> 00:45:48.800] Yeah.
[00:45:49.760 --> 00:45:53.200] Like, the flag has been raised, but you're just like, ah, whatever.
[00:45:53.440 --> 00:45:57.840] So, number three is prudent and inadvertent.
[00:45:57.840 --> 00:46:05.280] So, this is when there's a desire to produce the best product, but you find a better solution after implementation.
[00:46:05.600 --> 00:46:07.280] Oh, like my birthday tags.
[00:46:07.280 --> 00:46:08.000] Yeah.
[00:46:08.640 --> 00:46:09.040] Right.
[00:46:09.280 --> 00:46:12.960] So, this is accidental, but you realized it after the fact.
[00:46:12.960 --> 00:46:13.360] Yes, yes.
[00:46:13.680 --> 00:46:18.080] And then, the worst of all, the reckless and inadvertent.
[00:46:18.080 --> 00:46:23.760] So, this occurs when a team tries to produce the best product without the necessary knowledge to do so.
[00:46:23.760 --> 00:46:27.280] The team is often unaware of the mistakes they're making.
[00:46:27.280 --> 00:46:32.080] So, this is just you're not knowledgeable that you're not having the best practices.
[00:46:32.080 --> 00:46:34.880] And maybe you should have done more research before doing it.
[00:46:34.960 --> 00:46:36.080] This is everybody.
[00:46:36.080 --> 00:46:36.480] Yeah.
[00:46:36.480 --> 00:46:37.040] Yeah.
[00:46:37.040 --> 00:46:45.120] We are all reckless and inadvertent in some aspect of our business in terms of like everything, but really tech debt.
[00:46:45.120 --> 00:46:53.440] And this is like, this is you, you know, using email marketing and not realizing that you don't have your double opt-in opted in.
[00:46:53.440 --> 00:46:53.920] Yeah.
[00:46:53.920 --> 00:46:54.560] Right?
[00:46:54.560 --> 00:47:02.000] Or you are using a website hosting platform that's not as secure as it should be.
[00:47:02.000 --> 00:47:02.880] And you don't know it.
[00:47:02.880 --> 00:47:04.320] You don't realize it.
[00:47:04.320 --> 00:47:06.960] Or, I don't know, a million other.
[00:47:06.960 --> 00:47:12.400] Or you're not tagging all of your links with affiliate and you get blacklisted by Google.
[00:47:12.400 --> 00:47:12.800] Yeah.
[00:47:12.800 --> 00:47:12.960] Right?
[00:47:13.200 --> 00:47:16.480] Just completely unaware and it bait you in the butt.
[00:47:16.720 --> 00:47:17.040] Yes.
[00:47:17.200 --> 00:47:18.800] Let's talk about some actual causes.
[00:47:18.800 --> 00:47:22.480] So the first one is insufficient upfront definitions.
[00:47:22.480 --> 00:47:28.480] So this is also just scope creep, essentially, or not defining the project with definition.
[00:47:28.800 --> 00:47:30.920] Define the project definition, details.
[00:47:32.600 --> 00:47:37.640] So the solution to that is like at Almanac, where I was like, okay, I know where I want to be in a couple of years.
[00:47:37.640 --> 00:47:42.600] Let's make decisions based on my growth goals, not just where I am right now.
[00:47:42.600 --> 00:47:43.400] Yep.
[00:47:43.400 --> 00:47:45.880] And another one is business pressures.
[00:47:45.880 --> 00:47:51.880] So where the business considers getting something released sooner before the necessary changes are complete.
[00:47:51.880 --> 00:47:58.120] So this is kind of tying back into that community thing where flags were raised, but they released the product.
[00:47:58.360 --> 00:47:58.760] Deadlines.
[00:47:58.920 --> 00:47:59.320] Yep.
[00:47:59.320 --> 00:47:59.960] Yeah.
[00:47:59.960 --> 00:48:00.920] Deadlines.
[00:48:00.920 --> 00:48:03.080] And which are usually made up.
[00:48:03.080 --> 00:48:08.760] I just want to remind everyone: a lot of times you just make them up and you can remake them up and change them as needed.
[00:48:08.760 --> 00:48:10.200] They are not end-all-be-all.
[00:48:10.200 --> 00:48:15.960] You will not die in 99.9% of the scenarios.
[00:48:16.600 --> 00:48:20.600] There's like, there's a weird James Bond scenario out there somewhere.
[00:48:20.920 --> 00:48:21.480] Probs.
[00:48:21.480 --> 00:48:22.040] Okay.
[00:48:22.280 --> 00:48:35.160] And then the big one, the big, big one is just a lack of process or understanding where businesses are blind to the concept of technical debt and make decisions without considering the implications.
[00:48:36.440 --> 00:48:37.080] Yeah.
[00:48:37.080 --> 00:48:43.480] And I think this is also the big one, too, because you don't even realize that these decisions are going to have an impact until later.
[00:48:43.480 --> 00:48:45.160] I have a really great example of this one.
[00:48:45.160 --> 00:48:46.040] Can I share?
[00:48:46.040 --> 00:48:46.600] Yes.
[00:48:46.600 --> 00:48:47.880] I have an e-commerce friend.
[00:48:48.120 --> 00:48:55.400] No, a retail friend who a couple of years ago decided to put some CBD products in her store.
[00:48:56.040 --> 00:49:05.320] And so she put them on her POS system, which I believe was Shopify, if I'm not mistaken, just to come in the next morning.
[00:49:05.320 --> 00:49:16.800] And she had been kicked out of Shopify because Shopify and their terms and conditions did not allow the sell of CBD.
[00:49:14.840 --> 00:49:20.080] And so they just have bots that are, you know, crawling everything.
[00:49:20.240 --> 00:49:25.600] And if they see keywords like CBD, they're not going to ask questions.
[00:49:25.600 --> 00:49:26.640] They're going to kick you out.
[00:49:27.280 --> 00:49:30.160] And so her team goes to open the store the next day.
[00:49:30.160 --> 00:49:31.600] There is no point of sale system.
[00:49:31.600 --> 00:49:34.000] There's literally no way for them to sell anything.
[00:49:34.000 --> 00:49:37.120] They have, and Shopify is not taking phone calls.
[00:49:37.120 --> 00:49:37.840] Yikes.
[00:49:38.160 --> 00:49:50.080] So they have to close down the store for the next couple of days and implement an entire new inventory and POS and website system because it was tied to their website.
[00:49:50.080 --> 00:49:56.160] Because they made the decision to list a product that at that point, I don't know what the rules are now.
[00:49:56.160 --> 00:49:58.720] I won't touch the stuff because that is a horror story.
[00:50:00.000 --> 00:50:02.880] But because they had put a like, what's it called?
[00:50:02.880 --> 00:50:09.920] Like a not a regulated product on like it was like CBD bath bombs or something.
[00:50:09.920 --> 00:50:11.040] It wasn't anything crazy.
[00:50:11.200 --> 00:50:13.440] They just put some bath bombs in her store.
[00:50:13.440 --> 00:50:22.480] I've also heard this around putting some scientific names to like smudge sticks.
[00:50:22.480 --> 00:50:22.960] Okay.
[00:50:23.280 --> 00:50:34.000] So like you really have to watch some words for some of those things, but also read the terms and conditions for the things you sign up for so that you don't have a lack of understanding.
[00:50:34.000 --> 00:50:36.480] You fully understand as much as possible.
[00:50:36.480 --> 00:50:40.320] And also have friends that tell you stories because that can keep you from lots of trouble.
[00:50:40.320 --> 00:50:40.720] Yeah.
[00:50:41.040 --> 00:50:42.240] We have a few other things here.
[00:50:42.240 --> 00:50:43.200] And I know we're running out of time.
[00:50:43.200 --> 00:50:45.920] So I'm going to try and just touch on all of these.
[00:50:46.320 --> 00:50:51.680] So the next one is, or the next cause for tech debt is tightly coupled components.
[00:50:51.680 --> 00:50:57.520] And so that sounds very, very cody, but it's really just where things are not modular.
[00:50:57.520 --> 00:51:02.280] So when you need to replace one thing, you instead have to replace the entire thing.
[00:50:59.440 --> 00:51:06.840] So what comes to mind is funnels, email funnels.
[00:51:07.400 --> 00:51:12.920] And I will call out Biddy Tarot specifically this time because I've been all up in their email funnels.
[00:51:13.080 --> 00:51:22.200] So Biddy Tarot, they have had multiple funnels in their email system for years, for years and years and years.
[00:51:22.200 --> 00:51:23.560] Really four main ones.
[00:51:23.560 --> 00:51:25.720] So they're all based around webinars.
[00:51:25.720 --> 00:51:30.600] So they have a webinar funnel for one product, a webinar funnel for another product.
[00:51:30.920 --> 00:51:42.200] And the way they were built is that there was no easy way to change out one sequence of emails without breaking the entire thing.
[00:51:42.200 --> 00:51:43.720] And I say sequence of emails.
[00:51:43.720 --> 00:51:46.120] It's like it was phased funnels.
[00:51:46.120 --> 00:51:51.080] So like there was the first email sequence, which is like it was complex.
[00:51:51.080 --> 00:51:51.320] Yeah.
[00:51:51.320 --> 00:52:00.120] So like there were webinar invites, and then once you register for the webinar, you get the post-webinar emails and you get like the down sell emails and all that.
[00:52:00.120 --> 00:52:06.680] But because of how it was all wibbly wobbly inside of these automations, you couldn't take just one little itty-bitty piece out of it.
[00:52:06.680 --> 00:52:16.040] Like if you had to replace one email because the messaging in that email was out of date or something, to replace that one email would just crash and burn the entire funnel.
[00:52:16.040 --> 00:52:18.360] It didn't have to be that way.
[00:52:18.360 --> 00:52:33.000] If more thorough planning had been put in place to make that more modular, so you could take things out and replace them as things need to be up to date, it would have created a more simple, easy to maintain system.
[00:52:33.320 --> 00:52:39.880] So, yes, just making sure things are modular and easy to plug and play with.
[00:52:39.880 --> 00:52:40.840] So, that's another big one.
[00:52:41.160 --> 00:52:42.040] More flexible.
[00:52:42.040 --> 00:52:42.680] Yeah.
[00:52:42.680 --> 00:52:43.320] It's funny.
[00:52:43.320 --> 00:52:48.560] I love that you say that because it's something with my website background, I think about whenever I'm building things.
[00:52:48.800 --> 00:52:53.680] I want to be able to move things, change things, take things away, put them back together.
[00:52:53.680 --> 00:53:00.400] I even think about this at Almanac and how, you know, Shopify has like an inventory system, but I have like another inventory system.
[00:53:00.400 --> 00:53:04.480] So, if something ever happens to one, I have another, I can change one and keep things.
[00:53:04.480 --> 00:53:12.480] And like, once you think about this, y'all, you start thinking about this as to how it is that you're building what you're building.
[00:53:12.480 --> 00:53:13.040] Continue.
[00:53:13.040 --> 00:53:16.080] And I'm just going to list these off, and you can pull from it what you will.
[00:53:16.400 --> 00:53:21.920] So, the rest of the list, and this is not an all-exhaustive list, like this is just the highlights that I pulled from my research.
[00:53:22.240 --> 00:53:40.080] So, other causes of tech debt are lack of documentation or systems and processes, lack of collaboration, lack of ownership, lack of knowledge, last-minute changes, and lack of standards.
[00:53:43.920 --> 00:53:45.440] Yes, absolutely.
[00:53:46.080 --> 00:53:47.440] Absolutely.
[00:53:47.680 --> 00:53:52.160] You also, you missed one: lack of testing, which is incredibly important too.
[00:53:52.160 --> 00:53:52.640] Yeah.
[00:53:52.640 --> 00:53:53.520] For sure.
[00:53:53.520 --> 00:53:54.240] Love it.
[00:53:54.240 --> 00:53:54.880] Okay.
[00:53:54.880 --> 00:53:56.400] Ben, quick.
[00:53:56.400 --> 00:53:57.280] How can you fix it?
[00:53:57.280 --> 00:54:03.040] What does it look like to be better and/or do it better if you've already started?
[00:54:03.360 --> 00:54:07.840] I think just the big one that comes to mind is doing your research.
[00:54:07.840 --> 00:54:08.400] Yep.
[00:54:08.400 --> 00:54:13.200] Like, don't just go all into building something new if you don't really know what you're doing.
[00:54:13.200 --> 00:54:13.440] Yeah.
[00:54:13.440 --> 00:54:18.560] Like, it's okay to go read some articles, watch some YouTube videos, take some courses.
[00:54:18.560 --> 00:54:21.680] Just take a little time to do some prep work.
[00:54:21.680 --> 00:54:23.840] I think it's just the really big thing.
[00:54:24.160 --> 00:54:31.880] And then, other things, make sure you're addressing debt as just a regular part of your to-dos.
[00:54:32.440 --> 00:54:48.040] So, if you have a team or if you're just working alone, if you know that there is debt that needs to be addressed, like you know, you put a Bandaid fix in place because it needed to launch tomorrow, but you know you have time next week to go fix it, make sure you are keeping track of that debt.
[00:54:48.040 --> 00:54:53.480] So, monitor that debt, keep a list in your task management system.
[00:54:53.480 --> 00:55:01.160] If you have a team, if you're meeting regularly, make sure there's always time in that meeting, whether it's at the beginning or the end, to address the debt.
[00:55:01.160 --> 00:55:09.240] So, there's visibility on the issues so it never loses sight and so it doesn't fall off of your to-do list.
[00:55:09.240 --> 00:55:09.640] Right.
[00:55:09.640 --> 00:55:11.800] And then, also, just regular maintaining.
[00:55:11.800 --> 00:55:26.360] I cannot recommend enough that every single person that has a website that they are currently using to run their business have a web person on retainer.
[00:55:26.360 --> 00:55:31.320] And not just on retainer for security purposes, but on retainer for maintenance.
[00:55:31.320 --> 00:55:35.960] If you are not doing this yourself, having them go in and check your stuff, make sure things are still working.
[00:55:35.960 --> 00:55:50.040] Like, even if they're just testing it, incredibly important because platforms change, new features become available, things get tweaked and broken, especially if you have, you know, a VA who's like, you know, nosing around in your email software.
[00:55:50.040 --> 00:55:57.160] Like, make sure someone is there who knows what it's supposed to look like to fix things when buttons accidentally get pushed, whatever it may be.
[00:55:57.160 --> 00:56:10.680] I do, I think it could be a potential first-ish hire, contract or employee, but definitely contract, I think, for 90% of the people listening.
[00:56:11.000 --> 00:56:21.280] Having someone on retainer to do these things for you, whose job is to know what your tech debt is to, but also to be constantly maintaining it is incredibly important.
[00:56:21.600 --> 00:56:33.280] I've had someone on staff or contract before that from about like my first six-ish figure year.
[00:56:33.280 --> 00:56:33.760] Yeah.
[00:56:34.080 --> 00:56:34.720] Right?
[00:56:34.720 --> 00:56:52.320] So, like, really early on, because when you're building websites, when you're building email marketing stuff, when you are building integrations, when you are moving from maybe not for the purpose of this, but like even someone who's going to move you from Trello to Asana or whatever it may be.
[00:56:52.320 --> 00:56:55.920] That's not a web guy or girl or web person.
[00:56:55.920 --> 00:56:56.240] Could be.
[00:56:56.480 --> 00:56:57.040] Could be.
[00:56:57.520 --> 00:57:04.880] But like having someone, having someone on retainer so that you can at least call them when something happens is incredibly important.
[00:57:04.880 --> 00:57:05.520] Yeah.
[00:57:05.840 --> 00:57:06.960] Amen.
[00:57:08.480 --> 00:57:20.480] So I think the last big one, the last preventative thing you can do is really just a mindset shift into how you approach creating new things and managing your to-do list.
[00:57:20.480 --> 00:57:27.040] And it's the agile approach, the agile project management or agile development of creating new things.
[00:57:27.040 --> 00:57:36.240] And this is the idea that you do more iterative development rather than trying to do one big thing all at once and just put it out there.
[00:57:36.240 --> 00:57:42.000] So the idea is that you get it to a good place, you release it, and then you plan.
[00:57:42.000 --> 00:57:47.280] You actually create a plan to do consistent smaller updates.
[00:57:47.600 --> 00:57:50.080] So you're constantly addressing issues.
[00:57:50.080 --> 00:58:00.000] You're constantly growing whatever it is that you built, but you planned for that to be a consistent, iterative approach to consistently maintaining it and growing it.
[00:58:00.360 --> 00:58:00.760] Yeah.
[00:58:01.080 --> 00:58:01.560] I love it.
[00:58:01.560 --> 00:58:02.440] Corey, this is great.
[00:58:02.440 --> 00:58:09.560] I also just had thought about all the tech debt I have both in my Dropbox and in Notion.
[00:58:09.880 --> 00:58:18.280] Just so much stuff hanging around that needs to be like maybe even if you're aware of it, it's kind of daunting the longer you put it off.
[00:58:18.280 --> 00:58:18.600] Yeah.
[00:58:18.600 --> 00:58:19.800] And it just kind of snowballs.
[00:58:20.920 --> 00:58:21.640] The debt gets bigger.
[00:58:21.640 --> 00:58:23.080] It snowballs into all kinds of things.
[00:58:23.320 --> 00:58:26.200] And finding things gets harder, not just for me, but for everyone.
[00:58:26.200 --> 00:58:30.040] I literally am paying interest on my tech debt, everybody.
[00:58:30.040 --> 00:58:30.360] Literally.
[00:58:30.600 --> 00:58:33.800] You're not paying your monthly down, your monthly minimum payment.
[00:58:33.800 --> 00:58:35.480] You're just accumulating that interest.
[00:58:35.480 --> 00:58:36.920] Yeah, I'm accumulating.
[00:58:37.240 --> 00:58:37.800] You're right.
[00:58:37.800 --> 00:58:38.360] You're right.
[00:58:38.360 --> 00:58:38.920] Okay, perfect.
[00:58:38.920 --> 00:58:40.200] Corey, this has been great.
[00:58:40.200 --> 00:58:53.560] I hope everyone listening to this has gotten a little bit of a push to deal with something in your technical existence that you have maybe been putting off because you're paying interest whether you like it or not.
[00:58:53.560 --> 00:58:57.240] And again, this does not have to be technical specifically.
[00:58:57.240 --> 00:59:02.520] Like this, apply these thoughts to just the way you run your business as a whole.
[00:59:02.520 --> 00:59:06.600] Just apply these things everywhere in your personal life, too.
[00:59:07.000 --> 00:59:11.320] If you're putting off doing those dishes in your sink, come on, that's taking up time from later.
[00:59:11.320 --> 00:59:13.560] Like, go, go, go, clean your dishes.
[00:59:13.560 --> 00:59:14.200] Go do your lunch.
[00:59:14.280 --> 00:59:14.920] Go do your lunch.
[00:59:14.920 --> 00:59:16.360] You're going to do a little lesson for today.
[00:59:16.360 --> 00:59:18.520] Go do your dishes, everybody.
[00:59:18.520 --> 00:59:22.120] All right, Corey, because this is a legit interview of you.
[00:59:22.440 --> 00:59:24.120] What makes you feel most boss?
[00:59:24.120 --> 00:59:27.000] Doing this episode where I actually know what I'm talking about.
[00:59:27.000 --> 00:59:28.440] Oh, I do love that for you.
[00:59:28.440 --> 00:59:29.560] This has been a good one.
[00:59:29.560 --> 00:59:30.520] A very good one.
[00:59:30.520 --> 00:59:34.280] Literally, the nicest agenda anyone has ever made for this show ever.
[00:59:34.280 --> 00:59:35.320] Nice job.
[00:59:35.320 --> 00:59:36.040] Yep.
[00:59:36.680 --> 00:59:37.240] All right.
[00:59:37.240 --> 00:59:38.520] Thanks.
[00:59:39.800 --> 00:59:46.240] All right, boss, because you're here, I know you want to be a better creative business owner, which means I've got something for you.
[00:59:46.560 --> 01:00:03.120] Each week, the team at Bean Boss is scouring the news, the best entrepreneurial publications, and updates and releases of the apps and tools that run our businesses and is curating it all into a weekly email that delivers the must-know tips and tactics in the realms of mindset, money, and productivity.
[01:00:03.120 --> 01:00:05.040] This email is called Brood.
[01:00:05.040 --> 01:00:11.120] We brew it up for you each week to give you the insight you need to make decisions and move forward in your creative business.
[01:00:11.120 --> 01:00:15.600] Check it out now and sign up for yourself at beingboss.club/slash brood.
[01:00:15.600 --> 01:00:20.320] That's beingboss.club/slash B-R-E-W-E-D.
[01:00:20.640 --> 01:00:23.280] Now, until next time, do the work.
[01:00:23.280 --> 01:00:24.560] Be boss.