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
Wale Olaleye
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
Wale Olaleye has run Rails Fever on his own for 12 years. His clients are companies at least 10 years old, earning up to about $5 million a year, with no full dev team, and running on a custom Rails app. We get into how he found clients through Philly meetups, Slack communities and now cold outreach, why two solid people (one on sales, one on engineering) probably beat going solo, and why he left hourly billing two years ago for outcome-based retainers.
LINKS
- Rails Fever (Wale's consultancy)
- Buy Back Your Time by Dan Martell
- SPIN Selling by Neil Rackham
- The E-Myth by Michael Gerber
- Arkency
Questions or comments, email us at railsbusinesspod@gmail.com
today we've got Wale Olaleye with us. You're the sole owner of Rails Fever, the consult- Rails consultancy. Welcome to the show. Glad to have you
Wale:Absolutely. Thank you for having me here. It's, um, exciting to be on Rails Business Podcast
Brendan:Yeah. And, uh, I think pre-show you mentioned, was it 12 years of running the consultancy, or did, did I miss that number?
Wale:Yeah, that's correct
Brendan:Yeah. H- how, how has the consultancy been going, like overall, like from a… You don't have to go through the entire story, but maybe just like a little bit of background on how you got started doing consulting, maybe what you were doing before that, um, and kinda how things are now, you know, would be interesting to hear
Wale:Absolutely. Yeah. Um, I started at the time because, um, I, I got-- I just went through a layoff and I wanted to have more control over my time, have more flexibility. Um, and I-- before that I was working, uh, as a, working full-time at different companies. I'd done several different roles from, um… But my last job was as a Q- QA, QA automation engineer. Um, so I was leading a g- a team of engineers, um, automating tasks for, for a company. Um, so after that transition, I decided to learn Ruby, learn Rails. Um, fell in love with the language 'cause I did Perl in the past, and it was like a nice version of Perl. and, and yeah, I've been working independently, uh, since then. I work with businesses that either need staff augmentation on the, on the rail side, um, usually part-time, or businesses that, um, are generating revenue but are not scaling to the point where they want a full dev team. So been interesting. Um, it's always, it's been changing. Um, for the past 12 years, the market changes and I have to adjust to it. Um, the way to, to lead generation and find clients has changed over the years. And, you know, I've been in a-- I've been building software now for about 25 years, and now we have AI, and this is the biggest change we've all experienced. So now that's also changing everything.
Brendan:Yeah, definitely yeah, we just had, uh, Jeremy Smith on the podcast, uh, I guess it was the last episode we, we recorded. So there would probably be a little bit of overlap, but that's totally fine. Um, you know, 'cause he definitely was getting into how AI is i- impacting his business as a basically solo consultant as well. Um, uh, we don't need to jump into the AI part of it maybe yet, unless that's something that's on your mind, you wanna jump into it now. Um, but I guess before we even jump into that, I guess, Ryan, do you have any questions before we dive into AI like we always tend to do?
Ryan:Yeah. Well, I mean, I'm sure we'll get there eventually, but I, I wanna back up. You said, you know, things have changed over, you know, the, the course of your business, right? Like, we've seen change, and you've had to adapt your strategy. You-- Given that we're going through sort of an intense change right now with AI, you know, maybe a little history of what the other changes were and how you dealt with them would be an interesting precursor, right? Like, when you think back on it, were there, like, one or two, like, events, or was it, like, a steady, like, you're always just sort of correcting course, um, you know, a-as, as you go? Um, you know, that, that's my first question, so let's start there.
Wale:Yeah, absolutely. I think one of the, uh, major changes that happened actually within the first years of me starting the Rails was the rise of JavaScript, right? And that, that, the, how that just transformed the expectations and demand. So all of a sudden, this cool tool that I really enjoyed working with, like, you know, really within five years was starting to no longer be the default tool to work with, you know? Um, so the having a React and, and all that. So that I, I would say that was a, um, a major, one of the most impactful, changes that came, you know, before AI
Ryan:How did you sort of approach that from a business perspective, right? Like, was it, you know, you just sort of had to take on, you know, that, you know, uh, you know, that baggage, I guess, for JavaScript? I, I don't, I don't wanna put words in your mouth, but I don't have a lot of, you know, great feelings about the whole front end versus back end React split that happened in, in the Rails ecosystem. I tried to avoid it as much as I could, um, and still sort of fell prey to it at, at some point. But as a consultancy, you know, how did you have to adapt there?
Wale:I mean, I really just-- Just like I looked inwards and I, looked at where my strengths were and, and what I wanted to work on. and it was on the Rails side, so I really kind of just stuck with that. At the same time though, I did, um, try to adapt by improving like my JavaScript skills and, you know, making sure that I could handle, that work as well. So, you know, I survived it
Ryan:Yeah, sure. Yeah, I
Wale:Uh,
Ryan:did to some extent,
Wale:yeah, and you know, when eventually when the front-end technology changed, when, um, Hotwire came out, it was like, "Oh, yeah, now we survived. Now we can go back to doing things the way we really prefer to do it." So, you know, I knew it was, um, I had a feeling at the time that it was a, it was a, was a fad, um, that it did not make sense for every company, um, to adopt, you know, React in their code base. Um, so I just held to those strong beliefs and, you know, somehow I-- we came out of the end of that wave, so
Ryan:Okay. So pre-show we were talking about, you know, sort of your target right?
Wale:Mm-hmm.
Ryan:and if I remember correctly, it's y- you made the comment of we either work with, you know, startups or, you know, newer companies that need to augment their staff, um, or are just beginning to scale but not, know, scaling so much that, uh, you know, they're just gonna hire their own engineers. How did you come to that sort of dec- you know, uh, choice or decision of like, hey, this is the target audience? Like, was that dictated by the market? Was it dictated by, like, who you could get in front of? Or was it, know, like, these-- that's just the kind of work that you want to do?
Wale:Right. Yeah, it was mostly just dictated by, by the market of what, what I could find. After a few years, I started-- I was trying to define what my ICP was, and I was able to kind of finally figure out that this, this is where the demand for, for my services are, you know? Um, the, early stage startups are looking for co-founders, you know, and they're-- it's a hundred, usually 100% equity play. Um, and the, the larger companies, um, are looking for full-time employees, right? So there's this interesting space, Ryan, that you said you were at multiple years ago where… And I found that I've been able to define it is these companies are companies, usually at least 10 years old, are in about to five million recurring revenue without a full dev team. have a solid product, they have a solid business. They may or may not consider themselves a software company, but irrespective of how well they consider themselves, they are running on a custom, um, application that needs to be serviced that, you know, that if it goes down, the entire business goes down.
Ryan:Right.
Wale:Yeah.
Ryan:And that, that's scary when you don't have, like, a technical person available, Right to, to deal with that,
Wale:Right
Ryan:Uh, and we, in our early years, it was me and my business partner, you know, sort of putting our heads together and, you know, we're, we were good enough to keep the lights on, but, you know, any major code change, we had to wait, you know, sometimes days to get our, you know, contractor to have time to look at it, and then actually make the fix, and then do the testing, and then get it into production. So, like, those were, those were tough days back in the beginning. Um, a lot of… A lot more stress, I think, for sure
Wale:Yeah, absolutely. I mean, I think it's, it's, it's really interesting. I find, I found different kinds of attitudes, um, from business, those business owners o-over the years. There's some that, um, are just very reactive. You know, they just wanna keep running things until something breaks, and they only wanna deal with it. Um, I find success with businesses that have a more proactive because that's my mindset. I don't want you to have to call me and say there was a problem. I want to think ahead and say, "Well, this is what we need to do to prevent you having problems," right? Uh, in addition to sure that all the features that you want, eh, can be built. So, um, that, you know, when I do find those, those companies and if we do form a relationship, we end, we tend to end up working together for many years
Ryan:Yeah. Yeah, I mean, that, that's the, that's the perfect match when you can find it, right? Um, but i-it's hard. How do you, you know, find new companies to work with, right? What is, like, your pipeline and your, your marketing? And I, I, I fear we're gonna start to, to lean towards AI conversation, and that's fine, but, you know, how has that changed in the last, I'll say six months? That's a good timeframe right now.
Wale:Yeah, it's, it's change-- I mean, it's changing in the, I can even go further back, like I, I, um, the, in early when I started, um, just in this Philadelphia where I was, um, just going to events, um, we had lots of events. Ruby was still like a really hot thing, and it was easy to go to an event and have 200 people plus in attendees. And from going to those events, really within a few weeks was where I was able to find my first clients, um, from engineers that, you know, new comp- knew some of those companies, right? Um, the world has gone through a lot of change, so, uh, COVID came, all of that stuff kind of went down, right? But I also, just before that, um, there was a time where there was the advent of, of Slack, which was still new, and we had a lot of these communities all over the country, like these hubs. And so I was in those Slack communities and talking and having conversations, and that was also a good source, um, of, of finding clients. But all of that is, as we know, is now saturated and it's no longer working. So the way to find work over time changed. It's, it's not-- I would not say that's something I've been really great at. It's just something that I've, I've made work. But, um, I've done a lot of things. I've done cold outreach. I am doing, um, last six months again, still doing some cold outreach. I do know, you know, I can't have… I can tell if a company is, is my target audience, right? Um, so I do reach out to them. to find the right person to have a conversation with from a cold outreach is, can be challenging. So, and at the same time, I am doing, doing events in Philadelphia, trying to connect with local businesses, to connect with local chambers and things like that as well. Yeah.
Ryan:Yeah, that's, um, that's interesting. I've been-- like our, our software company is primarily outbound sales. Um- But I still feel like there's another way. I'm not sure what that other way is yet, but, um, I've been experimenting with LinkedIn a little bit. That seems to be the hot fad right now. I don't know if you've played around with that. I-I've also, having done outbound both with the software company and with my publishing company, I find that AI is really good at finding contacts now, right? I can just type into Google as like, "Hey, I need the marketing person at this company. Go find their email address, phone number, whatever." I'm actually having quite a bit of success with, with that in finding, you know, the right person to talk to, which is interesting. And then I, you know, just a anecdote is it drives me crazy now when I can't find a contact because the, the search says they don't publicly list anything. I'm like, "Come on, you're killing me." Um, but, uh, you know, m-maybe part tip and part question there.
Wale:Yeah, absolutely.
Ryan:you done anything there?
Wale:Yeah, I've, I've, um… So what I've found success in LinkedIn is if I've emailed-- If I've cold emailed someone like three times, then if I try to reach out with them on LinkedIn, they will probably connect with me. Uh, yeah. So, and then we possibly have a, a Um, I think every industry is different. I think if you're talking to like, uh, a marketing person, know, um, when I'm having conversations with marketing people, they usually like welcome conversations from like strangers, and they really wanna like engage because I don't know, I think that's just maybe because of the type of work they do. But when I'm talking with software people, it's usually a mix, but they usually tend to be like very reserved and y- they usually are, are not very welcome to like an outsider. You know, they almost like, you know, kinda wanna sh- you know, shut it down
Ryan:get that, right? Like, I have to flip back and forth, you know, day to day or even sometimes within the same day between, like, getting, like, deep programming work done and having to do sales calls. And it's a hard mental shift. And if you catch me while I'm in that deep work, I do not wanna talk to you, right? Like, just for-forget it. But if I'm in the middle of doing sales outreach and someone calls me, you know, I'll talk to someone for half an hour, right? For no good reason. Um, just to, you know, sort of shoot the shit and, you know, see how they're doing and, you know, build relationships and, and that kind of stuff. So Yeah, uh, that's a tough one. H-how do you-- I'm curious, you know, do you have that same problem of, like, context shifting between those two roles? Um, or, you know, how do you… I-if you do, how do you deal with it? Uh, you know, do you have any, you know, ways you try to cope? Um, and if not, then I guess we can move on.
Wale:Yeah, absolutely. I, yeah, I'm, so I'm this atypical engineer as well in the sense that I'm really outgoing and I'm an extrovert. And, uh, so yeah, when I'm at a conference, a technical conference, I'm usually kind of out of my element because I wanna meet everyone, and everyone is like, "Why do you wanna talk to me?" You know? So…
Ryan:Yeah
Wale:Um, but when I'm at a business conference, you know, I'm in my element, you know. But, but yes, I do, um, switch back from, from sales to engineering. Um, I prefer to switch my days. So if it's like an engineering day, um, and it's a deep thought day, that's all I'm doing that day, and I just deep dive into that. And if it's a, if it's a business development day, then I just do that as well. And yes, I do find that I am more receptive probably than average to people reaching out to me. Um, and I would at least respond to them and, you know, give them, you know, kind of feedback, whether it's positive or negative, instead of just ghost them, you know? So…
Ryan:Yeah. Well, that, I think that is also just a good habit, right? Like, be responsive. I mean, obviously you don't need to re- you know, I'm not telling people to respond to spam. But, you know, if you think it's a real person, treat them, like a real person, right? And just say, "Hey, you know? sounds interesting. Don't have time." You know, maybe touch back in a month or, you know. There, there's ways to deal with it, but I think that's something that doesn't happen enough, So… I'm saying it out loud if anyone's listening and, and cares.
Wale:Yeah, absolutely. I think LinkedIn is, is pretty-- is, is a good thing. Um, but I would-- I still think the best thing we could do right now, um, try to meet people in person. The challenge is finding out where those people are, and it's obviously a lot of effort. But, um, connections in person are like, you know, You know, we talk about 10X developers now, right? So connections in person are like 10X connections on LinkedIn, and connections on LinkedIn are like 10X maybe connections-- uh, email, right? So
Brendan:Mm-hmm.
Ryan:I think that's fair. Right? You know, if you can do it, if you're in a position to do, you know, face-to-face, I think that still wins. Um, you know, are, are you… I'm, I'm curious, is your clientele, you know, mostly around the Philly area, or are you all over the place?
Wale:All over the country. Um,
Ryan:Ja
Wale:I would love, for it to be more local so I can actually meet people in person. Yeah.
Ryan:Right. Well, that, that's why I asked is, right, like, you know, if you're a, a local, you know, uh, local geographically, you know, doing face-to-face is like a no-brainer. As soon as you're like, uh, national or international, like, the, it can be hard because it's expensive, it's time-consuming, right? So like for us, for the software company, we, like we go to conferences and we do, you know, trade shows and, and things like that when we can, but it's limited budget. So, you know, it's a, it's a balancing act for us, I guess.
Wale:Yeah. And I think, know, when it comes to the, the SaaS businesses I work with, the challenge with them is there are not-- You know, I, I, I was able to define the characteristics, you know, financially of the company, but I did not define an industry because every-- you know, they usually are in different industries, and I don't think it's a industry characteristic, know, per se. It's just like a s- it's more like a, a s- is this a lifestyle business versus is this a scaling business kind of thing. And, um, there's not a lot of events where they attend, except possibly maybe MicroConf. but outside of that, there is no… You know, it would be easier if there was, if I was targeting like, you know, all businesses in education space, right? And I could just go to those events wherever and I meet people in person. And so that's why also, one of the things I've been exploring the last few months is to uh, small, medium-sized businesses a specific industry locally. Still trying to explore to see where the opportunity is. But, but, um, to-- I think there's a lot of opportunity right now build custom software for, um, businesses. One that never had them before because it was really expensive, and now it's cheaper to build it. Or businesses that have existing SaaS software, and now there's opportunity to help them reduce those costs. if they're paying upwards of 20K a year in subscriptions, might be an opportunity to help them, you know, build something cheaper and maintain it for them. So trying to explore that angle as well.
Brendan:Speaking of conferences, I was gonna ask before, y- you just mentioned MicroConf, but like do you have other business conferences that you tend to go to? Maybe not regularly, but like, or do you go to MicroConf every year kind of thing?
Wale:No, I've been to MicroConf once. It was really, it was, it was really valuable. It was good. Um, you know, um, s- I have not attended every year. Um, the other business events I attend are like local, um, events that are happening in the area
Brendan:Okay
Wale:tilted on the, on the business side
Brendan:Got… Makes sense. H- have you gotten other, like, bigger b- business conferences too, or is it just MicroConf that one time and then kind of the local stuff for
Wale:Yeah,
Brendan:part?
Wale:Yeah, the one I've had on my target that I've not attended yet, there's one called The Business of Software, um, event. I think it's held in North Carolina, uh,
Brendan:I feel like I've heard of that one. Yeah
Wale:So I heard it's really pretty good as well.
Brendan:Okay Um, yeah, another question that I had just around your business stuff is, like, how many clients do you tend to work with at a time?
Wale:Yeah, I think the ideal s-sweet spot is around three, three clients. Um, with, with the way things are changing now, it could scale up to five, you know? Um, but that's like the sweet spot. Yeah
Brendan:Yeah. So you were also saying that, like, you, you tend to work with clients for quite a long time. So I guess maybe how often are you actually looking for new clients? If you've got three, maybe five, like you said, and you … Obviously they're not all gonna be long-term, but, like, how often do you feel like you have to look for somebody else versus, like, you're kind of fairly steady?
Wale:Yeah. changes, right, over time. So there's years where you have all these relationships, built and you just have, like, a full plate. Um, what tends to happen, um, to, uh, solo owners like me is when we have a full plate, we're not doing business development
Brendan:Yeah. That, that was kind of what I was getting at.
Wale:Right. And so we're just executing, which you know when you're doing that, that it's not good, but I guess you're giving yourself a break.
Brendan:Right
Wale:Um, and, and then, um, you will eventually get to a point where, you know, you're gonna-- it's gonna, it's gonna hurt, right? So those cycles, um- do exist. And, and so answer your question, I don't, I think ideally I mean, if I could get one new client a year, that would be really nice, right? Um, but you know When I reflect back on running this business, I think I've come to realize it's hard to-- It's just as, almost just as hard to run a solo business than it is to run, know, with a small team. Um, because when you, you don't ever wanna stop the sales and revenue engine.
Brendan:Yeah
Wale:the reasons you may stop it is because you feel like you're at capacity, right? so-- But then that comes and bite you later. But, yeah, it's, um, it's challenging
Ryan:That's a really interesting observation, right? So like, at any point have you ever been like, "Hey, I don't wanna be solo," right? Like, and that doesn't mean you have to build this huge company or scale to like, you know, hundreds, but it could mean a co-founder or two other people you're working with. Have you thought about it? Why have you resisted that so far?
Wale:Yeah, I have, I have thought about it. Um, there's been a few times in, you know, my early days when I tried to subcontract, um, to, to some people and, you know, I just didn't get that high quality of reliability service. You know, they dropped the ball on me. I ended up having to pick up the work. So that, that wasn't helpful. I think it was just, um, this idea or this thought that I had that this was the best way I could deliver high-quality service. Um, and, you know, some things you only learn as, as, as you look backwards, right? Um, I think it, it was trying to avoid complexity, um, maybe fear of complexity. but You know, so maybe some background. So my dad ran a business, right? He ran a manufacturing business and, and he had 50 employees, and he ran it for 30 years. So, but, you know, from the outside it was like, "Oh, this guy's running his business," and he was doing pretty well. But I lived with him and I was like this-- I saw the man that was so stressed out
Ryan:Yeah, sure.
Wale:So I, I've always wanted to avoid that, and I thought that being solo was the best way to avoid that. So I think maybe that's the best answer to that question
Ryan:And, and now you've been doing it for a while, do you feel, uh, still feel the same way?
Wale:I feel like necessarily that's the case because, you know, like you said, there's other options. You know, you don't have to go to a three- grow to a three-person company. Um, you could, you could scale up a little bit. I think, I think having different people doing certain key different roles is, would be a, would be a really good thing. Like if someone was focused on, on sales and marketing and someone was focused in, in engineering. Even, even two, I think two solid people, um, I would say it probably beats one.
Ryan:Yeah. I, I mean, it's-- if, if you ever find yourself thinking that, hey, that, that is something you want to explore and you're not sure how to approach it, I recommend the book, uh, "Buy Back Your Time" by Dan Martell. And, you know, to, you know, uh, paraphrase or just, uh, give a, a quick synopsis, it's like, all right, find all the things that don't give you joy, you know, hire an executive assistant to take those off your plate, and then use the free time to do the high-value activities that, you know, are important to delivering the quality that you want, right? And then just sort of rinse and repeat. And over time, you'll fill their plate up, up your time to focus on the things that you enjoy, and ultimately it helps you like, you know, level up the business, right? So like the first hire isn't like a, know, quote-unquote, "Another developer" or a marketing and salesperson. It's really an admin person to take the, the burden off. Um, and if you find that right executive assistant, I, I'm, I'm speaking from experience here 'cause we went through a few different people before we found, you know, our person. They're like a jack of all trades, right? They can do some sales, they do some marketing, they chase money, they do, you know, pretty much whatever we need them to do. It was a complete game changer for the business 'cause it allowed my business partner to sit down and be like, "All right, I'm just focusing on sales," right? that's… All I have to do is bring in new business because I know this other person is gonna take care of all the other stuff. And it allowed me to step away from customer service because they could take on some of that with the rest of the team and, you know, now I'm focused solely on product. So, you know, I'm not saying it, it-- you should do it or, um, you shouldn't. Just if you're thinking about it, I'd highly recommend that one.
Wale:Thanks for that suggestion. I have a of books I've been reading lately, um, the last few months. I'll add that to the list
Ryan:Uh, anything, uh, any-anything that you've read that is worth sharing that you think any- everyone else should read?
Wale:Yeah, it's called "SPIN Selling," um, by Neil Rackham. It's a maybe 30-year-old book or so, but it's, . it really breaks down the difference between small sales, um, and large sales, which is what, what most of us are doing. If you're selling a retainer, you know, you're talking five, at least five figures in a year, right? So, those are large sales. So the methods you use for selling something that's $20 a month is very different from when you're selling large sales. So he did a lot of research and collected a lot of data, and he shares that in that book. So that's one of the books I'm reading. And I, um, also just got delivered, um, "The, The E-Myth," um, which I didn't
Brendan:Yeah, I've read that one. Yep
Wale:So, um, but I was, um, watching a video by the founder of, um, Arkency. It's, it's a rail shop. Um, he's
Ryan:yeah
Wale:in, Europe. So he mentioned that book, and he shared his story of, um, of his history and how he grew up, you know, and his dad ran a business. out we're living parallel lives in two different continents 'cause my dad was running a business that grew to 50 people. His dad did the same thing, and the lessons he learned, uh, from that, and we're about the same age. So it's interesting. Um, so yeah, we've been talking a lot and, uh, connecting. But yes, he mentioned that book in, in that video that I saw, so I… And I saw it somewhere else, so I added it to my list, my reading list.
Brendan:Yeah, that, that's cool. And when Ryan, you mentioned, the book you mentioned, um, yeah, it, it made me think of The E-Myth 'cause I read that forever ago. Like, it was before I was even doing Rails or anything, and it was kind of like I was trying to figure out what… I didn't like what I was doing. I was trying to figure out what to do. Should I start a business? Whatever. And, like, it's been a long time since I've read it, but I do remember that it's mostly about, like, the processes and things and, like, set your business up if you're gonna do that so that you can pass it along to somebody else. So it's, like, similar to what you were saying, Ryan, about how you kind of figure out… I don't know that he specifically said high-value things and whatnot. It wasn't maybe the exact framework, but it, it was an interesting book. It stuck with me.
Ryan:one too. It, it's, you know, there, there's a, you know, a bundle of books in that space that, you know, kind of make the circulation. That, that, you know, there… I could list like three or four more that I feel are also good reads in that space, but we'll, we'll put that in the show notes or something. Um I'm, I'm curious, with the work that you're doing, you know, do you find yourself doing more feature development than sort of maintenance, or is it a, a mix? Does it really just depend client to client? D- do you specialize? Do you just come in and it's like, "What's next?" I'm, I'm curious just how it's played out in terms of, you know, the mix of work. And I ask, you know, selfishly because, you know, when I want to bring someone in to do something, it's sometimes hard to find the right project for them to work on. Um, you know, maybe part of that is my own head trash in terms of, you know, holding on to the product, uh, too tightly. Right? But we have a fairly complex, uh, app that is more broad than deep, so it touches a lot of… You know, it's a marketing platform, so it touches a lot of different feature sets. the, you know, part of the value we provide is the integration between all the different features. So like you, you, you do one thing and it touches a lot of other things just by definition. Right? So we, we struggle with when we're hiring a third party to be like, "All right, do we give them a greenfield feature? Do we give them bug reports? Do we give them maintenance work?" And I'm still trying to figure that out. So I'm curious from the consultancy side, you know, how, what your mix looks like and if you've seen any of those sorts of hang-ups, I guess, as, in your, in your client work.
Wale:Yeah. So, um, it's really varied from client to client. Um, when there is a, when there's a technical person-- when a client has a technical person on board, it does… There's some of these, um, things that you mentioned tend to be the, the case, like trying to figure out where to, to fit a-an external party. And yeah, I do… From my experience, it's because someone is Holding on maybe too much on, on how they feel things need to be implemented. I actually worked with a client where, there was a person kinda controlling things that kind of was like, like that into every little thing. And then someone-- they switched it to someone else, was like, "Well, I'm just gonna give you like a high-level overview of, of a, of a, of a goal, of an end goal, and you go run with it and deliver." Same company, different person driving, completely different experience. Um, so it made life eas- easier, it made my life easier because it was like, this is the end goal, you go figure out how you're gonna get from A to Z, right? Um, and you need to be responsible enough to know that, yes, whatever you're doing can break other things, but you own the, you own the result, you own the delivery, y- you know, make sure that you don't break anything, right? So that's, that's it. So, um, s- so some engagements are like that. Um, there are other engagements, where… And that's typically when there's not a really strong technical person on board. But where they, they, um… It's a mix, more like a 50/50% mix, where the client is suggesting the features that they want, but then I'm suggesting the other 50% of the, of the workload for the year. Because, you know, I'm advising them, I'm telling them, "Listen, yes, we need to do this, but there's a whole lot of things that y- that needs to be done that you don't know about, but I know we need to do this as well," right? So, um, and I want to be proactive. I want to prevent problems. So, and those work really, really well as well, and, um, they, they tend to be really nice projects because, you know, we build this trust relationship, And the, the, um, the business, you know, they end up getting like really high quality stuff. And it's really satisfying to me to, to really be helping someone that they really don't know better, you know? And like, you know, providing that, that level of, of service for, for them and their business.
Ryan:Yeah, I mean, that makes sense. Um, you know, I, I, I preface that question, which with, you know, I think I'm holding on a little bit too tight to certain things. But I think it's, it's also like, know, in addition to that, it's also, you know, budgetary and resource constraints, right? It's like I, I have a vision of what I wanna get done, and I have limited money to pay someone to do it, right? So how do I balance, give them-- giving them freedom with making sure that we're not, you know, wasting half a, a cycle or whatever you wanna call, whatever measurement you're using you know, getting up to speed or, you know, doing, you know, you know, maintainability, like refactoring sort of work, right? Like it's, it's always a balancing act, and clearly when someone new is onboarding, it just takes time, right? Like you can't really rush that. But, um, yeah, no, I don't, I don't… I mean, in full disclosure, Brendan is doing some work for us, so it's like, you know, uh, he, he's smirking here on the other end of the video feed because I'm talking about our relationship. But, um,
Brendan:No, no comment.
Ryan:to find a good, uh, a good project that both our schedules too, right? Um, which is, you know, when you're working with a full-time consultant, you know, that's one thing. But,
Wale:Yeah. I, I wonder if part of the challenge has to do with the billing models, right? think about it. If you have a full-time employee, you don't-- You, you gotta think of them as a fixed cost, cost, right? They're a fixed yearly cost, right? And obviously they can waste a lot of time if they spend four weeks doing… If they spent four weeks doing something they can, should be doing in a week, right? So you still have to manage that, But I, I, I find that people tend to be more VPs of engineers and CTOs, they tend to be, tend not to worry so much about managing full-time employees' time. But they tend to really, really wanna manage like a consultant's time because they're like, "We're billing you hourly and we wanna make sure that, you know, they're more…" That, that's just my experience, right?
Brendan:I, I, I've been there too. Yeah
Ryan:I, I think that's totally fair, right? Like you, you treat-- like even if they're not a full-time employee, but you're spending at that level, you treat it very differently than if you're doing a fixed bid project or an hourly project, right? It, it's just human nature. You look at those two things very differently. You know, and on top of that, you know, I feel like with AI, like I don't know actually what the right model is anymore, right? Like I-- the people I work with, I want them to leverage AI, right? It's a multiplier, right? I'm still paying them for their ex-expertise and, you know, know-how. Um, but if they're not using AI, you know, I feel like we're, we're, you know, now overpaying and, you know, under-delivering sort of scenario, right? But, you know, I don't know about your experience with AI, but mine is, you know, I might spend 20 minutes on a prompt and, you know, kicking off an agent, and then I walk away, you know, for a few hours, or I check in every 10 minutes or, you know, just to see how things are going. Well, how do you bill that, 'Cause it's like hourly falls apart, right? I've never loved hourly, but it's just the way things… You know, it's a proxy at, at, at best. Um, but now with AI, it's like it's even harder, right?'Cause an hour of, you know, wall time is different than, um, know, an hour of actual work when AI is involved. Um, you know, so that, that's just a new paradigm that I'm spending a lot of time thinking about. Um, like, you know, how do I, you know, how do I structure these projects now, right? How do we compensate, and how is it fair for both sides? Uh, I don't know if you're running into any of that with the consultancy and, you know, having to reset expectations about what… You know, I think the natural thing is like, "Oh, we're 10X more efficient." Well, then, you know, I should deliver 10X more value at the same price. But that's not really the reality either.
Wale:Yeah Yeah. So obviously it's not about just writing code, right? It's about writing-- It's about building that, that work well. So I've, I spent the last month working on a, on a feature for, for someone, and actual code writing time was minimal, right? But spent a lot of time with some refactoring and testing, make- just making sure the whole work would make sure that what was delivered, number one, worked right, and number two, I could live with the code that was produced, right? Um, and that it was gonna be maintainable and that it was in a direction that I wanted to code in the app to be going because it was a legacy system and there's some things that I was already, you know, it has-- still has some jQuery in there and, but it has some Turbo in there. And so the first version that was generated, the agent wrote it in jQuery, and I'm like, "Okay, well, we, we need to migrate this page to, to the way the, you know, w- the way we want our new front end to be." So doing all that stuff. So it wasn't just about getting it working, but it was getting it working in, into the level of quality that I-- that I, that I have, right? Um, so, but to really answer your question, um, I, I think the, I think we have to think about, we have to start thinking about outcome-based measurements. Okay? Um, not everyone-- I've talked with different agencies. A lot of people are still doing hourly. Um, some are no longer doing hourly. Um, I've been personally away from hourly for the last two years and just preferring retainers, um, where, um, at every X intervals deliver, de- de- determine end value that you want, And so your measuring stick becomes, did this value get delivered, right? So it could be make three-month plans or make one-month plans or make weekly plans. gonna be different for every com- company. But I think that works well because if you say in a week I, you know, if both parties commit to delivering N, and if they deliver it Then I think everyone should be happy, right?
Ryan:Yeah, I, I mean, I, I think that that is, like, true, and I believe that that is, like, the way to do this sort of work from a principle-- first principles perspective. I think in reality it's a little bit messier, right?'Cause the, the unspoken thing there is, you know, the, the onus shifts. You know, in hourly, like, the responsibility is on the employer, right, to sort of direct, right? And as the person delivering, you know, you don't care, right? Because you get paid by the hour, right? And in fact, you're probably incentivized to care less, right? Now that's a different moral, you know, thing that I won't go into, right? When you flip it around and do, you know, value-based pricing or retainer or whatever you wanna call it, the onus shifts to the person delivering, right? You know, y- the important thing becomes the communication between the two, right? Like, the, there's clear expectations as you start is like,"This is what I'm looking for. This is what done means. This is the, you know, the, the metrics that I'm judging you on," And if you guys agree on that, that's great, and if you deliver it in a timeframe that you is acceptable, then you feel good and they feel good. it gets tricky is, all right, well, think we all will admit that humans are pretty bad at judging, you know, how long things take. if you agree, like, "Yeah, that's the thing I'm gonna do," and it takes you twice as long, right? Well, you still make the same amount of money, right? And that's on you, and that, like… You know, I'm not saying that's bad. I'm just saying it makes, you know, running, you know, the person making the, you know, the solo decisions, it, it puts the, the, uh, onus on them to manage that. Um, and a lot of people just aren't comfortable w-with that
Wale:Right.
Ryan:general,
Wale:so it's just communication, right? It's, it's, it's setting, setting reasonable goals. So there's trust, setting reasonable goals, and communication. I think you need those three things to make something like that work, right? So, um, and integrity, obviously. So I can go to bed at night knowing I'm not cheating anybody So I have that, you know, and it doesn't-- Like at the end of the day, even if there's a dispute, I have integrity, so I, I'm gonna always follow that standard as a person, right? Um, but yeah, you have to communicate with people properly and, you know, if you're setting a goal like, oh, if your time frames are too little and you're setting goals of what has to be done every day, you may run into those kinds of problems. You still might end up micromanaging. You know, but if you, if you have long-term goals and short-term goals, right? It just really depends how, um, how much the management wants to get involved. And obviously that probably depends on how much money is involved, right? But, um- I'm not running a lot as much as I used to into cases where they, things take longer than I expected you
Ryan:th-that's good. I mean, like I'm not, I'm not saying that every- like I, I believe everything you just said, right? Like, and I wanna operate the same way. I'm just saying it's hard, right?
Wale:could be challenging.
Ryan:yeah.
Wale:Yeah, so
Ryan:it's not for the faint of heart.
Wale:I, have regular checkups with the people I'm working with, and we communicate. Um, and I have like, "This is a six-month plan, and this is a short-term plans." And, you know, my goal is just to make him smile. goal is to make him happy, you
Ryan:Yeah,
Wale:So
Brendan:And that can be a, you know, big challenge back to what you were talking earlier. Like you're, you're an introvert or sorry, extrovert. Um, but a lot of developers are introverts, right? And so like that communication can be really tricky for people. But I, I've learned that over my career and with all the people that report to me, I'm constantly trying to coach them on that. It's like you gotta give people that are expecting something at least enough to know like, "Hey, I'm working on it," at a minimum, or, "Here's a status update," like, "Here's, here's an ETA," whatever. Like those are important things that you're, you know, espousing here and I, I agree with completely. But I feel like for a lot of developers that's just a challenge to do that for some reason.
Wale:Yeah, it could be challenging, you know, but if you going to run a business and you don't do-- you don't communicate, it's gonna fail. You know, I've made those mistakes. I've had in the past and when I started, you know, clients that I, I wanted to have regular meetings with, and they were like, "No." Those projects always ended,
Brendan:Mm-hmm. Yeah
Wale:happened to me, I was like, "Okay, this… I'm not gonna do this. Like, it's not gonna work." Because there's-- when there's no communication, there's mistrust and, you know, all you communicating is only just invoices, you know. So yeah, I've learned from being, from being burnt that, yeah, you need that.
Brendan:Yeah, that makes sense Well, I, I feel like we've done a really good job of, uh, making it almost through the whole conversation without much AI talk. So, um, I guess is there, you know, before we wrap up and stuff though, is, are there topics that you wanted to cover at all that, you know, just around… Doesn't even have to be about consulting, but are there things that you wanted to, to cover?
Wale:Yeah. I mean, I probably like you guys, I follow on Reddit, um, and I see the, I'm gonna call it hysteria among software engineers, um, with AI is changing the world, right?
Brendan:Yep
Wale:And I've really been thinking about that, um And what, what needs to be done, right? So what, what do we need to do if we're worried about AI taking our job, right? Um, and I think That the answer is, if you are so terrified about AI cha- taking your job, then that means you need to increase your leverage, whatever that means to you, So people that have high leverage, I don't think they're worried about AI taking their jobs.
Brendan:Sure
Wale:know, people that are making the calls, like the closer you are to the top of, of, of, of a organization, you're not worried about AI taking your job because you're the ones make-- you're the ones, you're the ones, you're the one making the decisions, right? So, um, but it doesn't mean that… So it may mean that you need to start your own business, think it's much more achievable to do that. But it also just may mean that at your job, you need to be, you need to make sure that you're creating a lot more value than you ever created before, and that increases your leverage as well, know. Um, but that's my thought on that. Granted, I've not been a full-time employee for some time, so take that with a
Brendan:Yeah
Ryan:But I mean, just a, a gut reaction to that, right, is, you know, people that are near the top of their organization may not be concerned about losing their job. Uh, but I'll counter what they are probably thinking that they might lose their company. right, there's a lot of displacement happening. Now, the-- to do about it is the same, right? In-increase leverage, you know, create a moat, pivot, whatever, right? Like, and a lot of that to me, you know, is about, you know, embracing AI versus fearing it. Um, you know, use AI as a tool, 'cause that's what it is, in my opinion, is it's a tool that we use. And, you know, yes, it's a, it's a very powerful tool. That that tool is changing, you know, the, the world around us, the, the industries around us and, you know, sometimes good, sometimes bad. The only thing I think I'm sure of is if you don't adjust at all, you're gonna be in trouble. Um, To, try new things and, uh, uh, you know, make the adjustments, then think anyone has too much to worry about. Um, yeah, but I, I don't think that's different than any other major, like, uh, you know, uh, global level change of the past, you know, 100 years, other than the fact that it's happening at a very fast rate, right? So the rate of change is, is, is higher, but and that adds its own set of challenges, right? Like the… I think I, I alwa- when I have this conversation, we talk about like, you know, well, the Industrial Revolution took a lot of jobs away too, right? But it, it worked out just fine. You know, the-- um, I'm sure there were individuals that had it worse than others, um, and that's gonna be no different this time. Um, but as a whole, there is opportunity, uh, and I think that opportunity is going to increase. Um, maybe I'm being a little insensitive to, you know, the, the coal miners that all lost their jobs, but, it's more of a sentiment than, you know, the specifics there.
Wale:Yeah. I mean, we don't-- I-- When we think about Industrial Revolution, we all came after it.
Brendan:Mhm.
Wale:So it worked out well, right?
Ryan:that's true too, right? But history's important.
Wale:when we look back, well, "Oh, we're so happy we have the cars," right?"Oh, we have the roads." Like, things are much better for all of us, right? It's, you know, our lives are better. it's, it's, um… And then if we think about history and we say, "Well, should we have stopped that from happening?" We will all probably say, well, a large majority of people will probably say, it was a good thing because now we've moved, we've advanced. We don't wanna stay stuck in the past," right? may say, "Well, let's go back to the past," you know? Um,
Ryan:I, I like the horses and the farms and, you know, the buggies. And no, no bathrooms and no electricity
Wale:Right. I mean, I do-- When I do wanna disconnect from reality, I go to Lancaster County, and it's all Amish country, and I like that, you know? And some nostalgia there. There's some, there's some benefits to it, right? Benefits to everything.
Ryan:Mm-hmm
Wale:But it's hard to consider the perspective of the people that went through the change, the people whose jobs had to change, the anxiety and the stress that they had to go through. I don't know that we've considered that a lot, and that's what I was thinking when you were speaking is like, um, that's what we are all going through now. So it's harder to go through it, um, and the, the next generation, the kids that come after us, you know, probably, hopefully, will be better off than the ones that had to go through the change
Ryan:Yeah. I, I think that's fair, and as I was saying it, I was like, I-- this is gonna come off the wrong way. But I didn't, didn't mean it, uh, to, to degrade anybody. Um, but yeah, no, I think that's a, that's good perspective
Brendan:Yep. Yeah, I mean, one thing I think about too sometimes with that, like especially as I'm not doing that much consulting like, like you are, Wale, but, you know, it's like right now you're doing Rails primarily, but at the same time, like, what's gonna happen there, right? I- is … It's all gonna turn into React. Not that you're gonna have to write it, the AI's still gonna write it, but like, I, I just kind of wonder, like, where is coding going to go? Of course, there's tons of companies out there doing Rai- Ruby on Rails right now, but how many new Ruby on Rails companies, for instance, are gonna get created by vibe coders? And maybe that changes things, maybe it doesn't. I don't know. But it's just something I think about a little bit. Like where, where, what languages are we gonna be using, or is the AI gonna be writing primarily, say, in the next five, 10 years? May- maybe there's new languages, you know? Like, may- maybe they come up with stuff too that works better for them. I don't know. Um, and we don't need to even dive all-
Ryan:right? Back to assembly. Don't need
Brendan:May, may be, right? Like those layers of ab- abstraction that help for humans, like maybe it'd be easier to go back for the, the robots. But
Wale:Yeah. I I've obviously, language has become… Even though we all tend to be really passionate, especially Ruby, we love Ruby. It's like who, who says they love Python? Like, or they love Java? They just do it, right?
Brendan:Yep.
Wale:Like, I hated Java when I did it. Anyway, um, but yeah, as much as I hate to say it, it's, I think the, it's gonna matter less, and the products are gonna be what matters, end results is
Brendan:Yeah
Wale:what's gonna matter more. Um, and that's part of the problems that we're facing. That's the disruption that we're facing, that we're having to live with all this expertise that we've gathered
Brendan:Yep
Wale:seem to matter as much. It's kind of crazy, you know?
Brendan:Right. Yep. And that's a whole nother conversation. I don't wanna get us off on a tangent for another two hours here, but, um, just thought I'd touch on it 'cause it's related. Well, this has been fun. Um, is there anywhere you wanna point people to before we jump off?
Wale:Yeah, absolutely. I'm active on LinkedIn, so you can search for my, uh, first name, last name, or in, um, or linkedin.in/wale, all the way put together. Uh, also my website is railsfever.com, so that's a good place to find me as well. And you can send me a- an email directly, um,
Brendan:Awesome Cool. Well, thanks for joining us
Wale:Absolutely. Thanks for inviting me
Ryan:Great to have you
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