Rails Business
Brendan Buckingham and Ryan Frisch talk about developing with Ruby on Rails and how to leverage it to build a business.
Rails Business
Colleen Schnettler of SaaS Marketing Gym
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
In this episode, Colleen Schnettler, co-founder of the SaaS Marketing Gym, shares the challenges and successes of building SaaS businesses, and her current work coaching technical founders on effective marketing strategies. The conversation also covers various other topics like AI role in marketing content, Rails Upgrades and more.
00:00 Introduction to Colleen Schneller
00:14 Colleen's Journey into Programming
02:49 The Birth of SaaS Marketing Gym
05:32 Challenges and Insights in Marketing
08:44 Tailoring Marketing Strategies for Founders
17:43 The Role of AI in Marketing
19:41 AI Struggles with Nuance
19:56 AI in Cold Emailing: A Disaster Story
20:48 Using AI for Research
22:48 Rails Upgrade Challenges
23:29 Active Storage Encryption Issues
29:07 Front-End Framework Dilemmas
32:25 Maintaining Software vs. Rewriting
33:40 Conclusion and Contact Information
Notes
Today we have Colleen Schnettler with us. Colleen is one of the founders of the SaaS Marketing Gym. She has also had various other products including Hello Query and Simple File Upload. Welcome Colleen.
Colleen:Thanks for having me guys. I'm happy to be here.
Brendan:To start off, How'd you get into Rails? What is your origin story with Rails or even programming Before that, we've had a lot of people answer, we did PHP first or whatever. So where did you start?
Colleen:My background is in electrical engineering, but it was more on the hardware side, so I was literally working at a shipyard like. Putting together PLC program, programmable logic controllers like programming, programmable logic controllers that's, a whole different world from web development. I just wanted to work from home. And this is like 2010, right? I'm doing this. So back in the olden days of 2010, no one was working from home. It was not a thing. And and way back then, there was a guy who. He had an app on the iOS app store and he made like a million dollars. It was something really stupid too, so I was like, oh, I got this. Like I'm gonna write an app and put it on the iOS app store. So I did that in like 2011, and that was before Swift was a thing, like that was objective C. app made $60, so the overnight success I had been aiming for, but that really did spark, like that was the first money I'd made on the internet. So that really sparked this idea of I can stay at home and write software and make money. So that's how my, like software journey started. and they opted so poorly that I thought. Not everyone needs an iOS app, but everyone needs a website. And I was literally listening to a podcast again, this is like 2011, so before podcasts were a thing and it was one of those kind of tech bro guys, but he was like, Ruby on Rails. And I was like, okay. So I started learning Ruby on Rails and very slowly got into it. yeah, so that was kinda my path to Rails.
Brendan:Interesting. Yeah, that I remember the objective C days. Those were not
Colleen:Yeah. Did you do anything with it?
Brendan:tried a little bit. My brother got into it more than I did, and it just seemed harder than it
Colleen:Yeah, that's how I remember it. It's being way harder than it needed to be. Rails was such a breath of fresh air.'cause it was like MVC and you were like, yes, I can finally like understand how this works.
Brendan:Yep,
Ryan:didn't make it past the setup for objective C in getting may, I actually, now that I said it, I think it was like early days of Swift and I had a PC and it just was not happening.
Colleen:gonna work.
Ryan:I also had never made it. I started out as a computer systems engineer it for my undergrad degree and I made it one semester. So you made it much further than me in both cases.
Brendan:Yeah. That's awesome. And maybe we just talk a little bit about what you're currently working on, the SaaS Marketing Gym, which I guess my first question is this a Rails app? What is it?
Colleen:What is it?
Brendan:The marketing parts. So
Colleen:It's funny.
Brendan:us
Colleen:Yeah, it's funny 'cause it's like the pendulum of my. Rails to startup founder journey has swung, completely the other way. So I'm a very technical person, obviously background double E, and so swinging all the way to SaaS marketing, gym, it's actually coaching essentially. So basically I coach technical founders on how to do marketing. And I can tell you the whole journey, how I ended up there.'cause like I said, it's very different from where I started.
Brendan:to
Colleen:Yeah. So what happened was, so I got into rail, started working, traditional job. But the goal was always to have my own business. Always. That was always the end game. End game has always been having my own business. And so I started, I have, I started a few things, built a few apps. My last company I raised a little bit of money for the thing the last company was called Hello Query. And the thing that's interesting about that is I spent that whole year just learning how to do marketing. And I think as technical founders. Some of us get lucky in the beginning. Some of us don't, but we don't wanna do marketing because it's fuzzy, right? Like it's squishy, like what is it? And when we're product people or engineers we're like, you do the thing A, you put an A, you get out B.
Brendan:Yeah.
Colleen:Whereas marketing is this weird, squishy thing people hate to do. And so I spend a year just learning how to do it. Like things that we, I'm using. The royal we to mean like technical people like cold outbound. Have you guys done cold outbound?
Brendan:I have not. horrible.
Ryan:We do.
Colleen:You do,
Ryan:yeah.
Colleen:And I think what I learned while I was building my last business is it actually kind works. And so I think, that's some of the stuff we do in like SaaS Marketing Gym, but essentially like technical founders who've had, they've raised a little bit of money or they've had some early success, and then they're stuck because I think as technical founders we're only comfortable in like this small circle of things we can do. And then it's like, how do you expand outside your own network? Like how do how do you reach more people? And so that's how I went from like technical. And I'm still a technical founder, I have another project, I'm gonna build new things. But yeah, basically it's a community and coaching of technical founders who need to do more marketing.
Ryan:I have so many follow up questions just from that, that, that little preamble. But first. What was your reason for wanting to go into business for yourself? I find that people have very differing viewpoints on that, and I'd be curious to hear what yours was.
Colleen:I wanna be rich, like
Ryan:That's a good reason.
Colleen:Make
Ryan:Yeah.
Colleen:a year, but outsized. The only way to have out, I think unless you're in investment banking. Maybe you can speak to that. But only way to have outside returns, I think, financially is to have your own business. I also think it's a calling because I make, I could wake, like I have had people offer me so much more money to work for so much less work, right? As a 'cause I could just go get an engineering job at a company. Make a lot of money, not work all the time. and that would be the smart thing to do probably, right? So I do think there's this thing about wanting to work for yourself where it's, I don't know, I feel like it's a calling there is nothing else I wanna do, even when it's really hard.
Ryan:Yeah I think the term I use for it is empire building, right? I wanna build my empire, right? What, and, I wanna have more than one company or more than one product, right? I want to, divers, we've talked a lot about diversifying, our income streams as an entrepreneur on past episodes, but, I think that's first. It's nice to hear other people say what we're all thinking, which is, yeah, you go into business to make money. It's okay to say that out loud.
Colleen:Yeah.
Ryan:so that's great. My, my second question for you was, you work your coaching technical founders, what's the one thing you wish they knew about marketing, like before they got started?
Colleen:Ooh, if I had to pick
Ryan:Or two things I, you can gimme a couple if it's easier.
Colleen:It, it never ends. It's not like building a feature. I think it's twofold. Like the big, you have to like, you have to feed the engine of marketing. It's not like where you build the feature and it's done and you can just come in every once in a while and bug fix, like if you are doing marketing is like a continuous cycle and you have to, you will see returns if you continuously put in the work, you can't just do it for a week. expect it
Ryan:Right.
Colleen:work. And also it's not, the feedback is, like I said, it's not as, it's not as direct, right? Like the feedback, again, I think people come in with a technical mindset and they're like, oh, if I do this thing, I will get this response. But you don't really know. You have to comfortable being uncomfortable with you're gonna put stuff out there in the world and people might hate it, or you can't be embarrassed. Like you just have to remove your fear. Put your nose to the grindstone, if you will, and commit to doing it for a long time.
Ryan:Yeah. You gotta fall in love with the process.'cause if you don't love the process of business in general, not just marketing but you always gotta be working on the business. In the business right.
Colleen:Yeah, if you're trying to grow your business and some people aren't, I know I have friends, they have great businesses that are, they work very well for them. Some people don't wanna grow their business, but if you are here to grow your business, you have to work on the business. that's how that works.
Brendan:The thing that I think is interesting too about your journey and of course marketing and all this, is that feels like quite often there's an opposite approach or like a journey where starts doing something. Maybe it's not programming, but maybe it is, don't end up doing like marketing like you're doing, or at least coaching of marketing, which is not your, original intent. You, you wanted to build a company, which this is, But I, I don't know if you have anything, if there's really even a question there, but I thought it was just interesting to point out how,
Colleen:Oh yeah.
Brendan:like a lot of
Colleen:Go the other way. Yeah. It feels like a lot of people go the other way. Yeah, think I think the reason it works is because I went technical to marketing.'cause I had a friend who is a pure marketer and. You could tell she was upset. She hadn't come up with this idea on her own. And it was because marketers already know how to do marketing, right? They don't see, no one saw this blind spot because they assume people know how to do marketing. But having literally lived it, I was like, oh, no. And I think as ambitious founders, what we see every single person who comes to us, okay. know they have a list, right? It's not that no one knows what to do, it's the actual work us is boring and repetitive and like it's doing the actual work and it's overwhelming. I. Since it's not an A and B, like a black and white situation, like product building, it's just overwhelming with, we all have, like I, I'm sure either of you could spit out like 15 things you should be doing right now that you're not doing right. Did I email my list? Did I send a survey? Did I post three times on LinkedIn this week? Did I do educational con? And so people are overwhelmed. So
Ryan:Is way too low.
Colleen:You like literally people have come to us with these lists and I'm like, how many things on this list have you done? And they're like, none'cause I'm overwhelmed. and so I think what we do really well, or what I do really well because I am technical, is I can put that into a framework they can understand,
Brendan:yeah, totally. gonna be one of my questions is do you have a special sauce? Maybe you don't wanna spill all of it, but do you have a framework like you just said, that I. Helps, and it sounds like you do, which, that's one thing, just even with the podcast, we talked pre-show, like this is, I think our ninth episode we're recording here, maybe 10th, I forget. But we haven't done a whole lot and I have been looking into more marketing stuff for this podcast now than I have for anything else so far. haven't had to do cold outreach. There's no reason for that
Colleen:Yeah.
Brendan:still, like was just thinking things just the other day okay. post this episode or every episode on Twitter I think Bluesky, but that's like it, that's all I do. Like then I, if I have a guest like you, I'll, at you and say, Hey, the Colleen's episode's out, and if I'm lucky, then I'll have the guest will have more followers than I do, and they'll retweet it or
Colleen:Yeah.
Brendan:I, that's all I do. And to your point, like you're just said like post three times or whatever, like I'm not following anything. So a framework would be really helpful for me even for this, which is interesting.
Colleen:and that's what we try to do. We try to take away the stress of the list of 50 things and like systematize it a little bit so people feel more comfortable.
Brendan:Yeah, totally makes sense.
Ryan:How do you go about helping the technical founder? I'll say cut through the noise, right? I think part of the struggle in marketing is just the number of options, right? And any one of those options could be a great, marketing channel for the business.
Colleen:Yeah.
Ryan:If you're small and I don't know what your client size is, but let's just assume they're, smaller than a Fortune 500 company, right? If you're not focused on, if you don't have focus, you can quickly burn out and get no results. So how do you help them cut through the noise and. Find, help them find the channel that I guess is a good fit for them, right? Not everyone loves to blog. Not everyone likes to do video. Not everyone likes to do a podcast. So you gotta find a fit for the technical founder or the person doing the work, and you also have to have a fit for the industry and the business. You have any thoughts on how you go about figuring that out?
Colleen:So we do, I mean we do, it's very there's only eight people in a cohort, so we know all of our founders really well. But we do try to pick the correct channel. Most of the time it's LinkedIn, like 90% of the time it's LinkedIn for us because we are B2B sales, B2B SaaS. so most of our people, most of our founders are on LinkedIn, but like we have one founder who was in this super niche industry. And so he was on Facebook. so yeah, that's pretty much we try to find the right fit between the founder and what they like to do.'cause some people hate video. Like I'm big on short form video right now. I think that is performing the best. So if you came to if you came to me with your business, I'd be like, short form video is the only thing that's working right now. But if you're like, I hate video, like we wouldn't make you do video. We'd find something that like was not so terrible for you to do. Yeah, we try to tailor the experience for each individual founder.
Ryan:So you,
Brendan:to hear.
Ryan:I see on your LinkedIn profile it says I teach SaaS founders how to do marketing and then make them do it. But earlier on you shared your vision of, I. Sort of growing your I used the word empire. That wasn't your word, that, that concept of being Yeah. Of of being bigger. So are there any situations where you tell technical co-founders is like, here's the plan, but you need to find somebody else to do the work? Or is it always teaching them how to do the work and where do you stand on that? Because there you can go either way,
Colleen:this is such an interesting question because we have been, we have. Most of our founders are sub 1 million a RR, but we have two that are over 1 million a RR and so they have other employees. So it's always been like, how do you split up the work? Who's gonna do it? I think your question though is maybe more tailored towards the smaller single founders or one or two contractors. go ahead. You look like you're thinking. Yeah.
Ryan:Yeah, I don't necessarily qualify it like that. You could be a 10 million a RR company and depending on, what you want to accomplish in the future, you could have there's a another SaaS coach that I'm familiar with called his name's Dan Martel, and he pumps out content, like up there with the best of them, right? Hundreds of videos like. And it's all him. But he has a team of 20 people working behind him to do like everything. And he basically just has cameras falling around so he can record like whatever thought pops into his head and he is taking all of that content and other people edit it and put it out and he doesn't have to do it right now if you're, that's pretty extreme, right? And go all the way to the other side where you do all the work regardless of what your a RR is. I feel like. There, there's varying degrees of how involved, a founder or a technical founder can or should be. And I just, it just depends really is like the answer to anything, but
Colleen:Yeah. I think it's interesting because now that we have a SaaS marketing gym, we get pitched these done for you services all the time,
Ryan:Sure.
Colleen:had a few founders try some of them with very mediocre results. And but to your point yes if you were in a position where you were like, we're doing founder-led marketing, so we're really big on founder-led marketing because we're working with small companies. And again, I think with the prevalence of ai, building trust is getting so much harder. So founder led marketing founder's face the whole thing. If someone could afford that, I would absolutely be like, yeah, don't edit your own videos. You don't have time for that. Just be the face. but practically speaking, like we were just talking about this today, it's like the J curve, right? Like when you hire someone, your productivity, your productivity goes down like for a little while until it goes back up. So practically speaking, it's not that easy. Because let's say you wanted to turn out 20 shorts in a day. You're like, I'm just gonna have this guy follow me around, video me all day. And then he's gonna cut this into 20 shorts, like finding that person and then they're gonna charge you a lot. So for us, mostly it's easier for them to sign up for script or something and just do it themselves. I would still recommend, if you have the budget, have someone else do all that menial work, like that seems like a waste of a founder's time.
Ryan:If it doesn't bring the founder joy, I would say find somebody to do the parts that you don't enjoy, right? Keep the parts that you either enjoy or have to do as founder led,'cause it's your face, your voice. But if you don't enjoy editing, find a part-time editor if you don't enjoy
Colleen:who
Ryan:doing the social posting. Sign up for a service that automates it or uses some AI to at least help speed it along so that it doesn't take all day. And I guess that's a good set. You brought up AI, and I know everyone's talking about it, from a marketing standpoint, I'd love to hear where you stand on the use of AI and marketing.
Colleen:I have so many And
Ryan:you pro, are you against, it depends on what it is.
Colleen:Okay. It depends on what it is. I love ai. I had an AI company, right? However, comma, if you do not let AI write your content, like that is like a line. The sand. It is. Especially if you're going hard on LinkedIn, which we have everyone going hard on LinkedIn, It is. The thing about AI is there's so much AI slop out there, because of that, it's so easy to stand out. we use AI for, all kinds of things, but like the big things would be like, you don't idea generation outlines like the blank page problem, right? Like especially with people. founders aren't as good at words 'cause they're technical. That's a terrible, maybe thing to say. But that has been my experience. So the blank page problem is a big problem. You're like, I'm supposed to post on LinkedIn. Like what? What do I say? I don't know. And so we use AI for that, but then we're always like, you need to change that copy. Like you need to be modifying that copy because AI is terrible at copy.
Ryan:I feel the same way with technically, like I, I cannot, I don't think I can code anymore without ai'cause it speeds up things so much, but. If I don't edit it before putting it into my code base, there's a problem. And part of that is just, it's not very good, right? There's still a lot of errors or just poor design choices, but it still does speed things up. And I think that's the important thing, right? If you're, in my opinion, if you're not using AI to be more efficient, then you're gonna fall behind. But I also believe that it's not replacing anybody anytime soon. Just because there, there's uniqueness that it just cannot capture. And there's nuance that it struggles with. That's been my experience and I think a lot of people are backing that up. But yeah it's nice to see someone say, don't use it to write your copy.
Colleen:I tell you what, like I don't wanna. I don't wanna out any specific services, but there was this one service that we got pitched and one of our founders signed up for it and it was AI emails based off of social cues. So it was cold email with AI based off of social cues. So their promise was they would monitor your IC your customers, your ideal customers socials. And then they would send them a personalized email and it was like a disaster, guys. Like it was, I was like, like it was, So you gotta be really
Ryan:There,
Colleen:the
Ryan:just so many ways that could go wrong, right? Not
Colleen:Yeah. It was not good.
Ryan:the obvious one is people probably don't want you spying on them and reaching out with, from that context, right? So like I imagine they get a lot of angry people right off the bat. And if it was a poorly written email, that just makes it worse.
Colleen:Yeah.
Brendan:This is an interesting thing that I found in researching you a little bit before we talked here. decided, and I've done this a few times, actually started with Ryan Castillo. I used AI to just do a summary'cause of Knowatoa and what he does,
Colleen:Yeah.
Brendan:and so I've just used it for other guests and for you did a pretty good job. It told me about Hello Query, which I already knew about. It told me about simple file upload, which I already knew about. It told me you were a ship builder. I said, what?
Colleen:That's so funny.
Brendan:said, this must be either a different Colleen. And then I think it also said you wrote five books.
Colleen:Definitely
Brendan:Colleen Schnettler that's
Colleen:didn't read my,
Brendan:but I didn't think it was you,
Colleen:it was definitely not me. Don't you love how confident it is when it's wrong too? You're like, I do this all the time. Like speaking of code, it'll tell me something. I'll be like, no, that's wrong. It's oh no. Are you sure?
Brendan:Oh my God. All the
Colleen:I look so confident.
Brendan:and usually my brother, he also is a programmer and he taught me this one a while ago. If it gets it wrong like three times in a row, you usually say make it work like your job depends
Colleen:Oh, I like that.
Brendan:it works, sometimes it
Colleen:Yeah.
Brendan:it actually like at least seems to think harder
Colleen:Yeah.
Brendan:on it when you say that.
Ryan:I usually just start over. New chat,
Colleen:New
Ryan:memory.
Brendan:That's what I
Colleen:I was
Ryan:It's
Brendan:one I
Ryan:Let's level set here. Or I say, forget everything we talked about. Focus on this one thing and start from here. That also is a sort of a trick that usually straightens it out.
Brendan:about. About the reset recently that if you're even like a couple prompts in, just go to a new
Colleen:yeah.
Brendan:maybe ask for a summary out of the original one.
Colleen:Of the context.
Brendan:Bring the sum. Yeah, exactly. Bring the summary over, but then start from scratch. Yeah.
Ryan:Like it's, that's getting into some real, like prompt engineering right there.
Colleen:I'm started running clo so I run Claude Code and 4.1 side by side now. Which has been fun just 'cause you get different answers and when one like craps out, the other one will sometimes come through. It's oh, Claude Code said this. What do you think about that four one? I'm like, whoa.
Ryan:Yeah. So you, you,
Brendan:going, that's good for it.
Ryan:yeah. You mentioned pre-show that you're in the middle of a Rails upgrade I believe you said six to seven. Is that right?
Colleen:Six to seven. Yes, I
Ryan:Have you relied on AI to sorta help you troubleshoot those things? I'm curious the different models if one is better than the other in, in that regard. I just went through a huge four, two to almost eight. Oh. Now
Colleen:Really?
Ryan:almost there. It's taken me over a year.
Colleen:Yeah.
Ryan:I'm. I see the finish line. So this is a topic that is near and dear to my heart right now.
Colleen:It's, I think it's, I, it's okay. My experience was, it was okay. Sure, it's
Ryan:Yeah.
Colleen:the really basic stuff, but my goodness. Why is no one talking about the fact that with active storage, they changed the way they're doing the encryption? So if you have active storage or I think however, anything encrypted, so this is, sorry, this is like a bit of a tangent. I'm gonna rant on 'cause this happened to me yesterday,
Ryan:let's.
Colleen:okay. I have simple file upload, which is literally a file uploading and storing service. And so I use the proxy controllers, so I use the proxy URLs, so the proxy URL. So if you direct upload a file in rails to active storage. You get a signed ID and you the blob is I is you know which blob it is based on this thing called a signed ID in rail 6.0 and before it was like S-H-S-H-A one I think. I don't know anything about how you signed things. It was signed a certain way. It rail seven. They changed the way they sign things. So all of your rails, 6.0 signed IDs, which are in your permanent URL now, you lose all those files. Like it can't resolve them'cause it can't decrypt them.
Brendan:That's
Colleen:It's horrible. Like why is no one like screaming about this? Guys, I was so mad. I was like, so AI could not figure that out. That was like deep in the GitHub issues. I finally found a GitHub issue where people are like, why are all my files gone? I was like, oh my God. So you have to It just to use the old encryption, which is fine.
Brendan:That's what I was just gonna
Colleen:Yeah,
Brendan:You must have had to go back to the
Colleen:Yeah. You have. But if I guys, if I hadn't. Thousands upon
Brendan:service
Colleen:the whole surface would've been down, like thousands of images people would not have been able to access. It would've been terrible.
Brendan:Oh wow.
Colleen:anyway, AI couldn't help me with that.
Ryan:Upgrade that are you just I'm living on the monkey patch for now.
Colleen:I think I live on it forever. There, no, because what I have, 'cause my users have hard saved, like the URLs with the signed IDs in their
Brendan:Yeah.
Colleen:literally no way, like I am on this. And it's not a big, I don't know enough about encryption decryption to know how big of a deal is it? I don't think it's a huge deal. Anyway, it like blew my mind. That's all that happened to me yesterday. Rail's,
Ryan:I.
Colleen:super fun.
Ryan:I was coming from so long ago with four two that I never actually went to active storage. So I've just skipped all of that. Yeah we ended up and this is the story of my life, right? That is that we, every time we build something rails six months later, a year later, come out with something very similar, right? So we rolled our own. I won't say a version of active storage, but it was meant to solve some of the same problems. And then of course they come out with active storage and it's like, I just waited six more months. I could've, saved myself a lot of headache. Of course then I would've had to upgrade and migrate and found that monkey patch. So I'm glad I didn't have to do that. But
Colleen:Next I have to get off a web packer, so if anyone has any tips, I'm like
Ryan:again,
Brendan:quite there yet.
Ryan:I'm skipping right over Webpack. Yep. I'm, I still use the asset pipeline. Our image upload was direct to S3 and then we put it behind CloudFront and serve it from the Edge. So it's like pretty much the same idea. And then we dropped some, basically a lambda AWS lambda node function to do all the image transformations that we need. So we just do it in the, over at AWS and we can say, Hey, sort like Cloudinary for Cloudinary existed, if you've ever heard of them. So we skip, we skipped active storage. We skipped web pack and web packer. I'm happy about that at this point.
Colleen:So the reason it was such a struggle for me is because I, so I gave active storage. I don't remember when it came out, but it was like 2017 maybe. maybe it was earlier than that. But anyway, I. I gave a talk on it, I think in 2018. But anyway, it doesn't matter. So I was on, I built simplify upload and I used active storage before storage had a proxy controller. So what that means is in the early days of active storage, you couldn't put a CDN in front of the URLs'cause Rails gave you expiring
Ryan:Right.
Colleen:and so I, so there was like a guy working on the pull request while I was building simple file uploads, so I like. Basically have all these monkey patches in my code base because it was before active storage supported this stuff. So that's why it's been so hard because I'm like, oh, I have to
Ryan:Sure.
Colleen:this stuff they've added and pull out all of my special sauce. And I have CDNs everywhere. Like I have this really robust, I will say architecture with subdomains and CDNs and everything. And so every time, so it's just like getting up to speed on everything that has changed.
Ryan:Yeah, I can see how that would be difficult.
Colleen:Yes, but hopefully it'll be worth it because it'll be way easier and more fun to work on. That is my goal.
Ryan:And that's, I think as a technical people like that should be always be, our goal is to make it, software maintainable. There's, that's another good podcast. But I spend so much time just trying to make the code base easy to work with.
Colleen:Yeah.
Ryan:And I. I found, at least with rails, the more you can stick to the rails way, the better off you are. Even if it means like you can't do a thing that you wanna do. Every time I reach outside of rails like convention, it ends up biting me. So I don't, there's no question there, just a general statement
Colleen:you say
Ryan:for people listening.
Colleen:yeah, so I have this big thing. So Hello Query was a chat bot built with, not built with Hotwire and Turbo. it felt I think the user interface was okay, but it felt clunky to me 'cause it was like. Turbo broadcast from background jobs everywhere and replacing stuff with turbo frames in this chat interface. And so for whatever I build next, I want a different front end experience. So now I'm looking at inertia and by the way, super excited about inertia. But to what you just said, like I am concerned about like building something with React and inertia and rails and in a year, two years, five years, they decide to stop. The inertia guy is I don't wanna do this anymore. You know what I mean? Like you always, to your point, if you go too far away from Rails conventions, it can really bite you. I don't know. I'll report back in five years.
Ryan:Please do, and I'll share that. We went down that path of using React as our front end. And this was before where you had the separate front end and back end. This was like react inside of Rails,
Colleen:yeah.
Ryan:and that just got so messy. As we went along that we ultimately ripped it out and went back to vanilla rails, right? We said, all right, we have a web builder component of our marketing platform. It probably does need a better user interface, right? That probably would lend itself to, react or some other front end framework. But we also we look at our, ideal customer. They're local businesses, non-technical, they don't have a lot of complicated website needs, right? So when we look at it in that lens, I'm trying to tie this back to thinking of it from a business owner or an entrepreneur perspective instead of a technical person. It's like, all right I would love it to be like really polished and have that, very instant feel and it's just smooth all over. But the truth is our customers. Don't mind. A little bit of clunkiness, right? Like it, it's this over perfectionism. As a technical person that's yes, I could see that would probably deliver a better product, but the cost of doing so is not justified given our ideal customer. And that's not to say our customers aren't sophisticated or want the greatest thing, it's just that it's not a big enough deal to them. Why justify the added complexity, the added cost? There's a lot of things that go into introducing react front end, right? You need developers that know react if it's not you and. If nothing else, even if you do know React, you're introducing complexity, which, takes time away from marketing or sales or other 500 other things you need to be doing as a, technical co-founder. So I think there's always a place for it. I think it just depends on the use case and the business. But again, I'll just say that, my experiences every time we've gone outside of the convention, it tends to be like, all right, I just wanna be really sure that it's the right choice if we're gonna go outside of it now. And it could be.
Colleen:And I think your point about, it's funny you just said that about making smart business decisions as a developer because as I think I was. I don't, I told you guys before we started recording so I'm Simplify, upload is an app I haven't touched in like literally years and this month I'm like, okay, I'm gonna make it fun to work on again. I'm gonna do all these things with it. The desire to rewrite it from scratch is so strong
Ryan:Oh, so strong.
Colleen:I'm like, I'm like, I could just start over. I'm like, no, don't do it.
Ryan:I think every technical person fights that urge, and if you don't, you're crazy. And, but very few times does it actually make sense? I think financially, right? We, yeah, we greatly underestimate how much work it's gonna be and how long it's gonna take. Even with the best intentions, quadruple it, maybe more whatever estimate you come up with, and that's probably being too generous is probably worse than that. There's always a path to refactor and make it better. You're gonna run into the same problems if you try to rebuild it. That's my. My take on that. You didn't ask, but I feel
Colleen:I'm not gonna
Ryan:strongly about it.
Colleen:want to
Ryan:Yeah. Meant you didn't the question, but I wanted to share that with the audience.
Colleen:I think that's a good point to share, right? Because you're absolutely right.
Brendan:Cool. This has been great having you on, Colleen. Is there anything else you wanted to talk about with SaaS marketing, Jim, or anything
Colleen:No. But like to everyone who's listening, if you're a technical founder and you want daily marketing coaching, it's a lot of Colleen. But we do an hour and a half every day. We are actually full through August now, so we're not opening up spots till September. But you can go to sas marketing gym.com and sign up for our wait list to be notified when we open new spots.
Brendan:Cool. And is there anywhere else that people can find you on the
Colleen:Yeah.
Brendan:To the whole
Colleen:yeah. I'm on the internet. I really need like a webpage. It's ridiculous. I don't have my own webpage, but whatever. It's such an obvious thing. I'm Colleen Schnettler on LinkedIn and leenyburger on Twitter, X, whatever it is now. Bluesky, everywhere else on the internet.
Brendan:All right. Cool. It's been great having you
Colleen:Yeah. Guys, thank you so much for inviting me. This has been a lot of fun.
Brendan:Yeah, thanks. It.
Colleen:Bye.
People on this episode
Podcasts we love
Check out these other fine podcasts recommended by us, not an algorithm.
Code with Jason
Jason Swett
Standing in the Fire
Very Good Software
Remote Ruby
Chris Oliver, Andrew Mason, David Hill
IndieRails
Jess Brown & Jeremy Smith
Startups For the Rest of Us
Rob Walling
Vibing with AI Code
Brendan Buckingham