In this episode of PROMPTED, Kyle James sits down with go-to-market strategist Kat Hill Contag to talk about the experience that completely changed how she thinks about AI and building products.

Kat is a GTM consultant who works with SaaS companies on product launches and market expansion. Like many operators, she was curious about AI but did not come from a technical background.

Then she decided to try something new.

Kat entered a women’s AI hackathon using the platform Lovable, gave herself two days to figure it out, and built a tool called AI Recess, a Duolingo-style platform designed to help teams learn practical AI workflows at work.

What happened next surprised even her.

In this conversation, Kyle and Kat explore:

1. What it is really like to participate in an AI hackathon
2. How non-technical professionals can start building with AI
3. Why operators may become the next generation of product builders
4. The mindset shift required to experiment with AI tools
5. Why more women need to be part of the AI conversation

If you have ever wondered whether you could actually build something with AI, this episode might change how you think about it.

Connect with Kat

1. LinkedIn - https://www.linkedin.com/in/khillcontag/
2. TikTok - https://www.tiktok.com/@kathillcontag
3. Personal Website - https://kathillcontag.com/
4. Try AI Recess - https://ai-recess.com/

Kat, let's just kind of start at the beginning because I want to kind of paint this before and after picture, kind of before you really became a vibe coder and now a famous one for kind of winning this hackathon. So what was it like before? Like, clearly you don't have a technology background. So like, tell us a little bit about that to kind of help people understand where you come from and kind of how you got into all this.

Yeah, so I always like to share that

where I grew up, because I think that's important to my mindset and my life. So I was born and raised in the Bay Area in California, before it was Silicon Valley, before things got crazy over there. But I grew up in this environment where the mentality was, let's learn, let's problem solve, and let's explore and try new things. And that's always been core to who I am, even to the point where when I was seven years old and started a lemonade stand, and I was like,

I'm going to be an entrepreneur. That was just where I grew up. But professionally, I started my career at Walmart, so in their finance department. And so I have an e-commerce retail background. I have always loved technology, though. So even though I was in retail, it was on the tech side. I started at walmart.com and then eventually moved to what I call Big Walmart in Bentonville and then went to business school. And after business school, that's when I decided, okay, let's get a little bit deeper.

into the startup world and started a couple companies. One in the consumer product space. I have worked for services companies, built a services business using implemented HubSpot. So that was my first foray with HubSpot and a big fan. And then now I run my own consulting practice where I work with SaaS companies and services businesses, primarily SaaS, around their go-to-market strategy. So

launching new products, going into new markets. And it's been a really interesting time to be in that space because with AI taking over, right, a lot of companies are wondering how do we weave that in to everything we do, including go to market and sales.

It's interesting here, do you tell that background because a lot of builders and a lot of the

people that are getting into this space, the core thing with all of them is they're curious and they're not afraid to try stuff. I don't know how many times I've told people, How do you get up and start doing Claude code? Have you just gone and asked Claude how do you set up Claude code? It really is that simple. Most people are just like, I can't do that. I'm like, Why can't you? But it's like the same people that 10, 20 years ago didn't realize,

I could just go Google something instead of asking somebody you're not assuming, right? So it's like that mindset is definitely a core thing that the people that are really starting to move ahead with this are the ones that are kind of, realize that. It seems so obvious, but it's not obvious to a lot of people.

And that resonates particularly because I'm just really getting into Claude code right now. But every time, especially with AI moving so quickly, every time

I literally have a list running of like, I need to learn this. And I want to, agents are on my list, right? I want to do more with agents and build with them. And my first thought is usually, oh gosh, I'm not really sure how to do that. And that's a big undertaking. And I've learned now to kind of cruise past that thought and you can shape your second thought, right? And so my second thought is now just ask, just like one little baby step. And so with Claude Code, it was, you know, installing it, but then

Asking Claude, how can we work together to build to do this right? And that's for me has been, I think it's a really important takeaway from all of this is just try

totally. So let's go to the like, all right, how did you decide you were gonna sign up for a hackathon, find the hackathon?

what put you out there like, I'm going to do this thing? Was it this kind of like curiosity, can I? Or did something lead up to that?

Yeah, so just rewinding a little bit, if you think about like the landscape of AI, you had ChatGPT came out and then there was Claude and those were kind of the two, you know, now there's Gemini, right, and all these other ones. But people were really starting to use the, if you want to call it a chatbot or, you know, just tinkering with that. And so I started doing that and I found a

a lot of value in using both ChatGPT and Claude, I would compare with questions, and starting to use them as thought partners, whether it was work or literally building a meal plan for the week, right? Like just weaving it into a lot of things that I was doing. And that's where the curiosity sort of sparked. And as the AI landscape changed,

Then I even start hearing about different things and vibe coding was the new thing that was, people were building things, building apps. And I thought that was so cool, especially as an entrepreneur at heart, being able to build whatever sort of comes to mind. But again, my initial thought was, okay, put it on the to-do list, like we'll get to it at some point.

But then Lovable posted on LinkedIn. It was through Elena Verna. She's our head of growth and I follow her. She's big in the product space. And she posted that Lovable was going to host a women's only hackathon. And you can submit an application and they're going to choose 60 people or whatever and join this two day hackathon. And again, my first thought, you'll see a pattern here, right? My first thought was,

I've never done that before. I don't know how to do it. And then I literally, literally remember looking at myself in the mirror and saying, you have been wanting to try this. Like just throw in an application. What's the worst that can happen? You don't get included, right? And the demand was so overwhelming. They ended up letting 200 people join out of like 3,000 applications. And it was amazing for a lot of different reasons. But

At the very early start, that application process forced me to think about, well, what are some problems that I see through my work? I wanted to do something that was business focused. What are some problems that I'm seeing with my clients? And what could I build that might be a solution that could benefit either one of them or many of them, ideally many of them? And so that forcing mechanism to write down what is the problem that you're going to solve and build for?

was such a big unlock for me because now that is how my brain works when I'm building anything, right? It's what are the problems that I see and how can we build a solution that might benefit?

You just unlocked the product owner mindset. That's what that is. Yes. But have you ever thought about you becoming a product owner before?

You know, it's funny, having gone through this hackathon process, I realize, and this is one of

my sort of North Stars right now is that because of AI and because of vibe coding, people who are operators, who don't have a technical background, we can now all become product managers.

no offense to anyone who is truly trained in product management. I do think that you can't just jump in and call yourself a developer or call yourself a product manager. I respect the years of experience that people have.

So I'm going to push back on that. As someone who has been a product owner for 15 years, I had no formal training in becoming a product owner. And I don't think most of them did because, and once again, leave a comment down below if you disagree, but I know a lot of product owners that came into product as a second career.

Or like me, I was at HubSpot in customer success, and Brian Halligan, the CEO, said, I want you to run an engineering team. I'm like, I can't tell the CEO no, okay. And that's how I got into product and realized, oh my God, I really do love building stuff. But I didn't know that I could before. And I think a lot of people, the best product owners don't go starting out as wanting to be a product owner at a college. They come from

Somebody who works directly with customers because they understand the pain and the empathy and the problem statement. And they're a subject matter expert, right?

Yes. And I think that's a really great point. And I now, we're saying the same thing. I say it a little different. I now, I speak to a lot of people, particularly women, who have gone and gotten their MBA and they're really smart and really great operators.

And they want to learn, they want to do vibe coding and want to do more with AI. And my whole thing is operators are the new developers. Maybe operators are the new product managers, but it's this sentiment that if you are close to the business, close to customers, and you know really at an intimate detail the problems that people are experiencing, you are the person that needs to go build. Or you are the person that should be interacting with the engineering team. And it's interesting because one client that I'm working with right now,

I have become the product manager, and you're right. I don't have formal training, but I understand the problems they're trying to solve for, and I can speak clearly and communicate effectively with the engineering team and the developers who are trying to build out this product for their clients. So yeah, we could spend a whole episode on the shift that's happening in product management, but I think it's just unlocking that mindset, as you said.

has been such a game changer for me.

So let's get back to the hackathon. You got accepted, you got narrowed down to these 200 people. How long did you have? Talk us a little bit, you figured out what you're going to do. I'm sure you probably put together a scope of work or something, put on your consulting hat. I know how to do that. I'm really good at that. Talk us through how long did you have? What did you do? How do you think about it?

Yeah, so this is really, this is where I think the product manager mindset unlocked for me. And so I got accepted to the hackathon.

And I realized, shoot, I don't know how to use Lovable. So I had two days for this hackathon, okay? It was a Monday and a Tuesday. And I had blocked, I did have client work, but I blocked most of the days. And I also leaned hard on my community, my village, right? So I could, you know, I have a son, but I needed some time to build, right? And so we shifted duties around the house and all that good stuff. So

On Sunday before Monday, I realized maybe I should play around with this thing and learn a little bit about best practices for product management. Honestly, that's what I thought. Because previous to the hackathon, the only thing I had built in Lovable was a landing page for my application to the hackathon. So I'm very new to this. And so anyways, I had a friend reach out to me who, shout out to Adam, who is a product manager and has very deep

and product and he is very into lovable and he said, hey, I have a few resources. Look at these two things. One, learn about PRDs, so product requirements documents.

I didn't know what that was.

Love those. They're scope of work. That's how they are.

Yeah, fancy way of saying that. I now will not, we can get into that, but cannot do anything in Lovable without a PRD personally, and I can explain why. And then the second piece was design systems, which I wasn't familiar with either. And that's just a fancy way of saying,

What is your brand palette? What's your typography? What are all the different frameworks for the different design that you're going to use for your project? Those were two really important things that I learned about before jumping into Lovable that I think

A made the process a lot easier because I wasn't spending hours debugging things. Because if you set up your PRD properly, the AI knows what you're trying to build and why you're trying to build. And then the design system, any future iterations that you make after that first prompt will follow the same design, which makes it a cohesive look.

Yes, you're absolutely right. It's, yeah. Like as a product, like, yes, you need those two things.

And it's so obvious, but I don't think the last few things I've designed, like I've done the design framework. But now you got me thinking, oh my gosh, I probably should be doing that. That's a great.

And that's the big unlock. One of the big unlocks there is, so I.

Again, I'm not trained in product design. I would love to go down that rabbit hole. I think it's fascinating and I love brand and all that kind of stuff. But the default on at least Lovable and I think several of the other platforms is this design system called Shad CN. And it's what you see a lot of these vibe coding projects look like. If you want, especially in a hackathon, if you want to stand out, you've got to do something different than Shad CN. And so my AI recess is built on a framework called

neo-brutalism, which is similar to Gumroad, if anyone knows that website. And it's this kind of retro video gamey vibe, which I love. I think it's super fun. And it's just an instant way for it to stand out. And also, you do get a dopamine hit when you build your first prompt and it comes back.

And it's like this beautiful, cool-looking thing. You're like, All right, let's go, let's keep building.

It's that first like, Oh my God, I just did something. Yes, yeah, I built something that I didn't think I could even do, yeah,

and it looks good, right? 'Cause I think there's a distinction between I can build this versus like, and it looks like really good.

So, talk about AI Recess, right? Like, you got two days, you figured out what you're gonna build, this is what you build, tell people what it is and kind of like what it does.

So, I came up with the idea for AI Recess because I was working with clients again in that go-to-market space and realizing that their team members on sales and marketing.

weren't using ChatGPT, weren't using Claude to build proposals, to review call transcripts, to do discovery right before getting on the discovery calls. Just those sorts of little, I call them little, but little things that it's not like you're cheating or anything by like writing an email that isn't in your voice or anything like that. And I mention that because I think some people have hangups with AI. They feel like it's like insincere in some way. But I saw this issue that

Teams could work more efficiently and deliver better, like better products to their customers, faster timelines, all those sorts of things, if they embraced just some few workflows that could be implemented in a Claude or a ChatGPT. And so my thought process is also...

Everyone's really busy. Do not tell them to go take a course because they're going to give you the middle finger. Just say that I got to do my work. And so I was trying to think, is there a way that we could integrate learning AI with the actual work tasks that people have to do? And so that was the genesis for AI Recess, and I call it the Duolingo for learning AI at work. And so it's these little bite-sized challenges. They don't take more than three to 5 minutes, and you can learn how to build a proposal. We have

some around design systems for how to implement different design systems in your lovable project. And so it's just a quick and easy way to learn what's happening in the space of AI that's changing so, rapidly.

So you mentioned that first kind of moment when you turned it on and you're like, oh my God, I built this thing. Was that the moment? Was that the unlock for you? Or were there other ones where you kind of overcame this, like, I don't know, this imposter syndrome that you couldn't do it and you could?

Yeah.

was that it or were there other moments through that process?

There were two others that come to mind. I think the second one was, okay, first you can build it, right? The second one is you can fix it really easily too. So let's go back to the landing page example, because that's a very basic thing. I had videos on there and I wanted them to link to my Loom videos that was part of my application. It had like an arrow, but it didn't link properly. And so all I had to do was say, hey,

videos aren't linking properly. Here's the link again. And it fixed it like that. And so it was like, okay, it doesn't have to be out of the gate perfect. Like it's not going to be. But if you do some of the frameworking of that PRD and set things up properly, then it's really such a pleasure to fix and build on top of that first prompt that you send in. And so the second one was how easy it is to figure things out that you want to build in a

a Lovable or a Bolt. So for example, things that I've built on after AI recess after the landing page is adding in APIs, right? Like how are you supposed to do that? Well, you know, for people who have done this a bunch, it might seem routine right now, but you can go, you can either ask Lovable as you're building, hey, I want to add this kind of API, what's the best way to do it? And it'll tell you. My format of doing that is I have a browser with Claude and I am like, it knows all about my project, it's got the PRD, it's already

helped me write the PRD, so it's got all that knowledge. And so if I say, usually it's within that PRD process, but oftentimes I'll go back after the fact as I'm continuing to build and say, hey, I want to add in this automation, or I want to add in this API, or even maybe I don't even know if it's an API or an automation. I just say, I need it to do XYZ, and it'll help me think through how to build that. And then it'll either

Write me the prompt or tell me the code to copy and paste into Lovable.

It's funny you describe it that way, because that's exactly how I do it.

Yeah, right.

I have one that depends on if I'm in Cloud Code or Codex, playing with either one. It's like I've got one that's like the LLM and the other that's like the engine IDE. And it's like, all right, what do I say here? Yeah.

What do I do? Here's what it told me back. What do I do back?

Exactly. And I like having the separate sandboxes. I call them sandboxes. I like having the separate spaces because some people love.

to do it all in Lovable, but I just find having the, it's like 2 minds, right? Like, why wouldn't you want 2 minds? So.

Yeah, it's two different perspectives and sometimes I catch ones that the other don't.

And I'll give one other little plug too, going back to the PRD and how important it is. I built, I use this every time I build in Lovable now. I didn't one time and then I had to debug for four hours because it was a mess. But I have a literally on my website copy and paste prompt that I put into Claude.

It takes about 10 minutes. It asks you questions about what you're building, and then it gives you a PRD that you can go paste into Lovable. And we just used it at the International Women's Day Build-a-thon, and people said it was really helpful. I literally, I cannot build without it. So it's there if anyone wants it.

All right, two days. You built AI Recess. Like, how did you find out how you did and how long did it take them to announce winners and all that stuff?

So it was such a fast process, honestly, like hats off to Lovable. I don't know, and Whitney and Elena and the team, like, I don't know how, I joke that they don't sleep. Like, they just start, they don't sleep. But so.

They might have AI helping them too.

Maybe. So they announced the hackathon.

Four days later, applications were due. Three days later, they announced who was joining. We had the hackathon. And then I think it was like another four days later, they announced the winners. They moved very quickly. In case people are thinking about hackathons and mindset and all that kind of stuff, because I've had a lot of questions about that since. I am a very competitive person. I've worked in sales. I've worked in marketing. I am like, I'm a numbers person and I want to win. I literally said to my husband the night before,

I'm getting really competitive. I want this to be fun, though, right? And if I don't want to have completed this, and I mean, the chances of winning are so slim, I don't want that.

Yeah, half a percent to 200 people.

Yeah, I don't, yeah. And I don't want that to ruin the experience for me. And so I really, I share this with a lot of other women who are now doing hackathons. I had a post-it note on my computer that I just said, fun.

it has to be fun.

The whole point is that you're learning something.

I mean, if I hadn't gone through that hackathon, it was like a forcing mechanism for me to get really good at building.

And that and then the community that comes along with it and just the feeling the sense of empowerment.

And that is the real win.

And so

I think that's important to share.

It might sound a little pie in the sky, but I think hackathons are going to become the new webinars.

Really, I see a lot of hackathons.

That's a hot take.

I like it.

Yeah, I see a lot of hackathons coming out and hackathons that are geared.

There's one I just saw announced that's for specifically for creatives.

So artists who are learning to vibe code, right, for their business that they're building.

I think that's going to be the

a hands-on way for people to learn and embrace all of this technology that's being rolled out.

Which goes from passive to interactive, right?

Because, I mean, people always talk about webinars, like, what is the actual engagement and how many people are doing three other things?

And do people show up and, yeah.

And so I think that that's a really interesting.

I've seen a lot of other tech companies do that.

And it's a fun way because then it's not just a one, it's not just a 30 minute thing, right?

It's like, it could be a day, it could be a couple days, but then you have the winners that come out of it, they're super psyched and they talk about it and then they are helping.

I've learned from other hackathon winners on other technology, you know, it's just like nice ecosystem that's built.

So I think it's important to say it's not, you know, yes, I'm competitive.

I love to win, but there's so much more that came out of it.

And I think that's why I get on my soapbox, right?

Because I want other women to jump into these hackathons, right?

And know that they should show up, not because there's going to be a winner chosen, but because they're going to be a lot better at whatever that platform is after they go through the hackathon.

They can teach other people about it, and they're going to have a seat at the table for whatever conversation is happening around that sort of technology.

Yeah, let's double click into that a little bit, because I know you've mentioned it a couple of times, like empowering women, and you're a lovable ambassador.

It's on your LinkedIn.

And I remember it was that you wanted to support women operators, I think was a specific line.

And it reminded me of an earlier conversation I had on this podcast with Kate Reed.

Shout out Kate Reed.

where she really talks about like, she was a customer success and now she's able to do things in this field dominated by men, right?

There's not a lot of women in the tech space, especially when you get into engineering and product teams or product even less than engineers.

But like, talk about that a little bit, like the empowering element of this that you feel and like getting other women to like, feel like you could do this too.

Yeah.

I think if we zoom out for a second, right?

We look at the world, we look at conversations that are happening, things that are happening.

In leadership positions, there aren't always a lot of women, right?

And I think specifically we're seeing a lot happen in the AI space.

OpenAI and Anthropic have been in the news recently with conversations with the Pentagon.

Things are moving, things are happening.

And I feel very strongly that women need to be involved in those conversations.

so that we're represented in whatever decisions are made.

I think the world would be a much better place if we had more representation, not just from women.

Let's be honest, women are more empathetic than men.

You just are.

You know, we're sometimes more like, go, go, go, get her done.

And you need that balancing out a little bit.

And y'all tend to be a little bit more artistic, creative, where we're more logical and numbers focused, right?

And there's a ying to yang there.

And it's there for a reason.

Well, and I think too, it's not just diversity,

from men and women, but I think it's also diversity and experience.

And so that goes with people of color too.

I think there just needs to be more general representation.

And so that's my sort of macro take on things.

If we zoom into, okay, well, how does that tie back to building with Lovable or learning AI?

That's, in my opinion, that's the first step to having a seat at the table, is you need to understand

what is happening in the space.

You need to not just read the headlines, but hands-on keys, right?

And how does this technology work?

How am I using it personally in my workflow, in my day-to-day?

It doesn't have to be at work.

It can be in your, you know, like I said, building a meal plan for the week or whatever, but just again, shifting the mindset, being maybe more of a product mindset, but how can we integrate

these technologies with what we're doing so that then when higher stakes conversations come about, we can participate, right?

And yes, there's a long line between building with AI for the first time or experimenting with AI, but.

Still, you can't do step three until you do step one.

Exactly.

And more people need to take step one.

A mix of representation, right?

So we're seeing a lot of communities coming up supporting other women who are interested in AI, and that is going to just facilitate more people getting involved and more people learning and not being scared of the technology or worried that it's going to take our job.

Like there's so much opportunity that can come from it that I just, you know, I want more of us to be there.

Love it.

So

What if I not ask before we kind of get into a lightning round of what are practical steps for first-timers?

What if I not ask you what?

Can I share about that journey and experience and how can we get people excited just to try these things and knowing that they can do it too?

Yeah.

I could speak a little bit on the importance of community because I do find that that's very important for my journey.

So yeah, I guess just on that note of there are other communities

popping up to help women learn AI.

And I think that has been such an important part of my journey.

So if we think back to, I mentioned that I started dabbling with ChatGPT and Claude, right around that time, this was before the hackathon, there was a group, I'm located in Minneapolis.

And so there was a group that organically came about for women who are interested in AI.

We started meeting monthly, we had some happy hours.

And

Honestly, that group encouraged me, not specifically, but just having that support encouraged me to keep taking next steps and apply for the hackathon and learn more and ask questions when I don't understand something.

And so now I'm in like four other women in AI groups.

And I think that that's

been a really important support side of this because things are moving so fast.

Like how do you keep track of it all, right?

And who do you ask questions of?

It's really hard, I think, to work in a silo or, be, if you're at a company, just see other people using it, but not really know how to use it yourself.

And so, you know, Women Defining AI is another group that I really love.

They have

workshops right now on cloud code and how to use that.

And they're doing stuff around agents as well.

And so I just think having that space where it's encouraged to play and you're encouraged to experiment and ask questions and that there are other people there who can help, who might be a couple steps ahead, that's been really important to just continuing to adopt the new things that are coming out.

I love that.

I think

What I'm really hearing, Yuki, and I was like, find your tribe where it's okay to be curious, and not okay, but encouraged.

Because that's the theme from the beginning, right?

It's like the level of curiosity you need with these things to continue to move forward to be successful, because they're going to leave you behind.

But yeah, that where's a community where they can help you, know, friends that you have, or sounds like there's plenty of them online.

I've got my tribe, and we've got our signal groups that we like throw stuff at each other all the time.

Like find your buddy.

It can be one person.

It doesn't have to be a whole group, but like find someone.

Yeah.

So, all right, kind of wrapping up here.

I want to like get into anybody out there that's thinking about doing a hackathon.

You've kind of alluded to a couple of like advice tips, right?

Like learn what a PRD is a little bit, learning your design system.

What other advice or tips would you leave them?

And it even sounds like knowing your time frame, right?

If it's only two days, just block two days away, stuff like that, right?

Yes.

Well, and on that note, my other like biggest, biggest thing if you're doing a hackathon is don't bite off more than you can chew.

And so that was one of the things, again, I did my PRD working with Claude and I said, I've got two days.

And I literally even said, I've got, you know, because I

would like to sleep, right?

So I was like, I have two, I think it was 2 10 hour days.

So I got 20 hours for this thing, right?

What can I build realistically in that amount of time?

And so that was really helpful because then by the end of day one, I had accomplished actually more than what was on my list, but at least

You don't go way off into the weeds trying to build this like enterprise grade platform.

You really do an MVP, minimum viable product, and you can always add more to it.

But if you go into the hackathon, bite off more than you can chew, then it's just not going to be a fun experience.

And you're going to be trying to, you know, it's a race against the clock.

So.

What do you build next?

What's next?

Oh my gosh, if you were to look at my lovable portfolio,

I've got like 10 other projects going right now.

I have truly a mix of things.

And one thing I like to share with people, because sometimes I hear from people new to Vibe Coding is, well, I just don't know what to build.

And I get that.

So start with your own website.

Build a website for yourself.

That's like my

sort of, throw, it's not a throwaway because it's actually something that you're going to care what it looks like and you are going to think through, well, how should it be structured?

It's a great first project and something that you'll probably use, you know?

So I have my personal website that I've built and I'm constantly tinkering with it and uploading different things.

I have some personal projects.

So one pain point for me is anytime I go on a trip, packing my suitcase is just...

And I'm very type A, so it is like I spend, I could spend hours packing it, which I'm sure people are cringing at.

But I now have an app on Lovable where I punch in the dates I'm gone, where I'm going, an API pulls in the weather for the location.

for each day.

And then I can add in different events and build out my packing list.

And it takes me, 30 minutes to pack now instead of hours, which I'm really embarrassed to admit.

So a lot of things on the fun sort of personal side.

On the work side, like I said, I've kind of become a product manager for one of my clients.

So we work with a dev team.

to build out the SaaS platform, but I've got a whole mocked up version in Lovable and I'm able to chat with the leadership team every week and say, this is the product that's on the roadmap for the next couple of weeks.

This is what it's going to look like.

And usually it wows them and they're like, oh, that's great.

And so it's like this instant, like, okay, great, we're moving, let's go.

Sometimes they want it to work a little bit differently than I had thought it was envisioned and we just change it very quickly.

And then the dev team

has a clear line of sight for what we're looking to build.

And then the thing that's really exciting, I think that is sort of on my horizon is doing more internal tools for clients.

So sales teams who might need an ROI calculator when they're working with customers.

Dashboards are a big thing, right?

So a lot of clients, they want a dashboard that pulls in their HubSpot data and their financial metrics, and they want to be able to see everything clearly

week, maybe weekly, monthly, different timeframes.

As a business owner, I wish I could have done this for two of my companies previously, that kind of weekly reporting that just is all synced in one spot.

So I think there's a lot in that space that's going to continue to evolve, but I would love to work with more companies doing that.

I think it's a really cool space.

Who do you want to work for?

Or if people that are listening to this, like, you know what, I would love to work with Kat.

How do they find you?

What's your lat and long?

What's the best way to connect?

Where can people find you?

Kind of share all that good stuff.

Yeah, so I post a couple times a week on LinkedIn, so you can find me there.

DMs are open.

I'm on there pretty actively.

I'm also just starting a TikTok channel.

So along the theme of bite-sized content, people can learn things in the AI space fairly quickly, playing around with that space as well.

So Cathill contact at

on TikTok.

And then my website, cathillcontag.com, for anything you need.

You can e-mail, speaking engagements, that sort of thing.

I typically work with companies, like later stage companies that are launching a new product or going into a new market.

I just find that that's a really cool space to be in because they already have a pretty robust team.

But this new venture is exciting and they're not really sure how to navigate it.

And so I like to come in and help build, I typically work with the CEO or senior leadership to build out what that go-to-market strategy looks like.

So Kat, I'm going to leave you with the final thought here.

What is the last thing you want people to kind of take away or a last piece of advice you want people to kind of remember or just to go try or do or learn or just ask?

I think the biggest thing that's on my mind right now is this sentiment that AI is coming for our jobs.

I think it's such a Debbie Downer point of view.

And you know, I understand where it's coming from, but I am someone that really sees the glass as half full.

And there's so much opportunity that's coming right now as an operator, as someone who's curious and passionate about what you do.

you can really set yourself apart because now the ability to build what's up here in your brain is, you can do it.

You don't have to wait for a development team.

You don't have to wait for a budget.

You can share your ideas with the world, right?

And so I think people who are curious and want to learn and

courageous enough to figure it out are the ones who are going to find a lot of joy in this change that's happening.

There we go.

Stay curious, everybody, and just go try stuff.

I mean, I think it is kind of that simple, but Ken, I really appreciate just your optimism, your whole story, and just sharing that with everybody else, because we all need a little bit more optimism right now, for sure.

And I think part of that is just leading by example, and we all just need to go try stuff.

So thank you for taking the time to talk to me.

I really appreciate it and I really love hearing your story and excited to share it with everybody else.

So until next time, everybody, keep building and stay curious.