
Ron Hash (Skimmer) on bootstrapping a pool service SaaS to $1M ARR and 1,500 customers with zero paid marketing, then selling the company
Loading summary
A
It got to a point in the conversation where he ended up saying, the paper game is killing me. And at that point I knew, okay, this is, this is a real issue for people. It was $0.50 per serviced customer with a minimum of $29. No one else was doing that pricing. Everyone else was charging per seat. I remember I had this one guy, he called me and he said, man, I get happy every time I see my skimmer bill go up because that means my business is growing.
B
Hey, welcome to the SaaS podcast. I'm Omar Khan and this is a show where I sit down with real founders and dig into how they actually built their SaaS companies. I've had almost 500 of these conversations now, and I put out a new one every week to help you build and grow your startup. If that sounds useful, hit subscribe or check out SASClub IO to learn more. My guest today is Ron Hasch. He built software for pool cleaning companies, charged them just 50 cents a pool and grew it to over $1 million in ARR with around 1500 customers and zero ad budget. Then he sold it. The company went on to raise $79 million and now employs over 100 people. He'd never built a SaaS before and he validated the whole thing with one cold call to a stranger that he found on yellow pages.com in this interview, Ron breaks down why he charged per pool when every competitor was charging per seat. How he cut churn from 6% down to 2% by fixing onboarding instead of fixing the product and the one channel he taught himself that kept customers coming and why he's never regretted selling the company. So I hope you enjoy it. You've got a powerful product, but new users struggle to figure it out. They sign up, get stuck and leave before they ever see the value. And it usually comes down to one thing. Every user has a different goal, but they all get pushed down the same path. Product Fruits fixes that it adapts to each user and guides them to the result they want. That's how they help fitness player cut trial churn by 70%. Visit productfruits.com to book a demo. Mention SaaS Club and you'll get a free 30 minute onboarding teardown with a product adoption expert. They'll show you exactly where users drop off and how to fix it. Tell us about Skimmer. What does the product do, who's it for, and what's the main problem that it solves?
A
Yeah, so it's for pool service companies. I'm not sure how many in the audience where they live throughout the states, but especially in states like California, Arizona, Texas, Florida, places with a lot of swimming pools, you have lots of pool service companies. And it could be, you know, just a one man show, a one polar as they call them, or it could be a company with literally 50 people in the field. And so Skimmer is software for those companies to help run their pool service business. Basically everything they need, all in one. And one of the big things it solves is most of these guys were just running their business on paper, Literally three ring binders and sheets of paper all over. And so this is software that brought it all in one place for them.
B
Great. And so you bootstrapped the business, zero paid marketing. You grew it to over a million in arrangement, over 1500 customers. And then eventually you sold the business and stepped away. And since then it's gone on to become, you were telling me the business is over 100 employees, has raised $79 million. And I was just like, you look at something like pool cleaning and say, is it big enough for me to build a SaaS? And it's really amazing how much opportunity there is out there. So we're going to talk about that, we're going to share the story and how you came up with the idea, and then we're also going to talk about what you decided to do after the acquisition and what you're working on now, which is kind of a fun product that you're building and sort of very different to Skimmer. So why don't we start by like, where did the idea come from? What were you doing at the time?
A
Yeah, so I'm a software developer by trade, basically been programming since I was 17. And I had always wanted to do something of my own, build my own type of product. I was interested in things, but I just didn't know what product to build. And so there was this point where the iPhone came out, and once smartphones came out, I knew that there was an opportunity there. I just honestly didn't know what that opportunity was. I saw lots of people building mobile apps and there was kind of this gold rush on the app Store, but I didn't think that was it. And so I was just kind of keeping an open mind, looking for something that might benefit from that. And as a software developer, I had started to learn mobile development in addition to web development skills. But I had this buddy, I was living in Phoenix and that's where I am now as well. But he had a pool service company and one day he asked me how hard is it to learn to program? And I said, well, I mean, it's not easy. Of course, this was well before AI and all the stuff that's come out now. But I said, I mean, it takes time. It's doable. But I asked why he was thinking about it. I wasn't sure if he was wanting to get out of the pool service. And he said, no, you know, I've looked for some type of software or something to help me run my business, and there's just nothing good out there. And I thought about that and, you know, I just told him some things about learning to program. And honestly, I forgot that conversation for quite a while for like, six months. And then I heard another podcast episode where someone happened to talk about pool service. And it made me think back to that conversation and wonder whether or not there was an opportunity there. And I also wasn't sure if my buddy was the only one with the same problems he had, you know, finding a good solution, trying to run his business on paper. So to sort of validate it, I went on YellowPages.com and I searched for pool service companies in Texas. And I randomly cold called this pool guy, and I said, look, I'm a software guy. I'm thinking of building something for pool service professionals. Would you mind if I just ask you a couple questions about your business? And he said he'd talk to me. And so I was really just trying to see, how do you run your business? He ran it using paper as well. And he had multiple, they call them techs that go out and service the pools. He had multiple guys in the field. And it got to a point in the conversation where he ended up saying, the paper game is killing me. And at that point I knew, okay, this is a real issue for people trying to run a business like this while relying on paper. There's just so many drawbacks. And so from there, I started looking more into. Actually, I went all in on building it.
B
So were you looking at other ideas as well, or just kind of happily getting on with your day job? And this pool thing was kind of coming back and forth, and eventually you decided to pursue it?
A
Yeah, that's it. There really was no other idea I was pursuing at the time. One of the interesting things to me about this one, this idea was it was guys in the field, and I knew that mobile devices could work out in the field, and it was going to be an opportunity to do something there. And when I looked at the time at the other competitors, because there were at that Time, other people in the space, but it was all web based and they were responsive. But it really was not a great experience for the guys in the field. And so I understood that making a great user experience for the person actually out there doing the work in the field, not just the person in the office, but a great mobile experience, I understood that that could really be something unique in the market.
B
So how many people did you talk to before you were convinced that this was the idea that you were going to work on? And when you said you went all in, what, what did that mean? Did you go full time? How quickly did that happen?
A
Oh, yeah, good question. Really? It was after that one conversation where the guy said, the paper game is killing me. That was enough for me to know that the problem was real. And so at that point kept my day job, it was nights and weekends and coding away and trying to build the first version. And at the time I had only learned how to build apps on iOS, not on Android. And so I made it an iPad app because I figured, okay, well everyone can buy iPads for their guys in the field. And of course it wasn't too long. There was a lot of customer feedback that, no, we don't want iPads, we want phones. And so ultimately ended up developing it for both iPhone and Android. And that was a real turning point as well. But no, it was nights and weekends and trying to figure out, okay, how am I going to grow this thing? How am I going to get the word out there? And again, at the beginning, had no idea because I had never built a SaaS before.
B
When you said you started building the product, how did you figure out what features to build? This is not an area that you know that well. You haven't had a huge number of conversations if that one guy was enough to get convince you. So how did you figure out? These are the things that I need to have initially that's going to persuade my early customers to sign up. You can't build everything, right? That's, there's always trade offs. So how did you figure that out?
A
Yeah, so it was just conversations, you know, conversations and asking questions and really trying to understand how those businesses work and run and, and you know, the first version, of course, as you said, you can't build everything all at once. But once I got version one out there, then it was really about talking to customers, like really talking to them and asking questions. What's working, what's not working? And even with a day job, I would make welcome calls. I had heard a founder interviewed on a podcast. And he said that he was able to cut his churn by a third by making welcome calls. I thought, all right, I can do that. And so on my lunch break, I'd be in my car after work, I'd be in my car making these phone calls to people who had newly signed up. And I had built a little dashboard for myself where I could see what they had done in the app so far. So I'd know if they had started or if they had put customers in, if they'd built any routes, if they had actually used it or not. And then based on that, I could ask them questions, and if they were stuck, I could try to get them unstuck. But those conversations really helped me to learn, like, the parts that were working and the parts that needed help.
B
Tell me about your first customer. Who was it? How did you find them?
A
Yeah, so as first customer is someone in Phoenix. And yeah, so we just were able to build. Ultimately, I got good at one thing for acquiring new customers, and that was search engine optimization. I hadn't known how to do it before, and I certainly wasn't an expert, but I was able to learn enough to be dangerous. And I started ranking for pool service software and pool service app, and that became the way of getting customers. And so as those customers would come in, you know, as I said, there'd be welcome calls. Did my best to give great customer support. I had this idea from the start mostly because I had had some bad experiences with customer support of other software companies, software that I was paying for, where it was just very difficult to talk to someone and ask questions and get, like, real help. So I had the idea that if someone. And so I actually had a phone number front and center on the website, and if someone called, I answered. If someone sent an email, they got a response within 30 minutes. So, like, really giving great customer support became super important. So basically, that little bit of traction with SEO, we'd start to get people in. We treat them great. I work to make the product better and better over time and communicate that. And anytime they were having issues, they knew that they could call or email. And that ended up leading to a lot of really good word of mouth for us.
B
So the first 10 customers, how many of those were inbound versus people you had been talking to before you built the product? Your friend that started this off, the guy in Texas, these people that you kind of had randomly cold called, Were you able to close any of those, or was it just really waiting for SEO and inbound, you know, A lot
A
of it was waiting for SEO and inbound. I mean, this is early, early days. I don't quite remember all of those early days, but really the traction came from SEO. Once we started getting in there, it became the predictable way, the predictable way of getting customers. And as we continued to climb in the ranks, you know, it ended up the number of new customers just kind of kept growing. And because the word of mouth was so good, for example, I wasn't even on social media at all with this, but there were Facebook groups where these pool professionals would go. And in those Facebook groups, from time to time people would ask, hey, is anyone aware of any software or anything that can be used? And because people were having such a nice experience using Skimmer, they would actually do the marketing for us in there. Even though I wasn't on Facebook, I wasn't promoting anything online or on social media because the customers were having a good experience. They talked about us.
B
So I'm guessing it took a while for you to get those first customers then it's not like you were doing SEO and the next week you were getting people turning up to use the product. So just how long did it take to start getting acquiring customers? What did the first 6 to 12 months look like?
A
Yeah, it was slow. There's that expression, the long slow SaaS ramp of death, which in the early days, even if you're compounding, it still feels small. It took 12 months for us to get up to 76 customers. So a full 12 months for 76 customers. After the next 12 months we were over 370 customers. And then after the next 12 months we were, I think 906 customers. And then about halfway into that next year we were over 1500 customers. And then that's where the interest started to come in about the business of skimmer, you know, people wanting to either invest in it or think about acquiring it and things like that. So it was pretty slow. In the early days it was kind of interesting because we got to the point where we were growing more in a single month than it took the entire first year to grow. And that was just a matter of the compounding effect of the word of mouth and the SEO.
B
How much were you charging in that first year?
A
Yeah, so it was 50 cents per serviced customer with a minimum of $29. So everyone would pay 29 bucks at a minimum. And then so it was basically usage based from that point. So if you had 100 customers on your pool route, you were going to pay 50 bucks a month. And the pricing was interesting because no one else was doing that pricing, that, that model of pricing everyone else was charging per seat. But there was at the time a blog called Price Intelligently, if you remember those guys.
B
Patrick Campbell.
A
Yeah, yeah, right. And like, I, I decided when it was time to figure out the pricing. I read every blog post on his blog at that time and just went through. And you know, he talks about value metrics and making sure. The truth is, I was gonna do what most developers do. I was gonna charge like a one size fits all flat fee price. But after reading his blog, I was like, oh, I can't do that. You need to have pricing that scales. The other thing that was interesting that he said is you want your pricing to be as close to the money as possible, possible. And so some people could think from that, well, that means you should charge per seat, because when a company, a pool service company, has techs in the field for each tech is making them money, but in actuality, each tech kind of cost them money too. And so you're still not quite as close to the money as you can be. And so I thought, all right, well, how do you get the interest completely aligned? And another thing that Patrick Campbell had said about per seat pricing was that it actually contributes to churn over the long run because people have to think about, do I want to add this person onto my account or not? And instead, what you want is unlimited users. You want your software product to be pervasive and the company, you want every single person in the company to use it and for them not to even think about it. And in that way, it becomes stickier. And so by changing the pricing model and charging based on the number of customers that they actually serviced, it put everyone in alignment. It made everything good because they felt good about adding new customers into skimmer and they felt good about growing their business. I remember I had this one guy, he. He called me and he said, man, I get happy every time I see my skimmer bill go up because that means my business is growing. So. So yeah, that was about pricing.
B
Yeah, I mean, it's, it's interesting. I mean, you talked about like yellow pages at the beginning, and it kind of makes it sound like you were doing this decades ago, but, you know, you founded the business. I guess it was 2017. 2017. Patrick was very active at the time, and there was a lot of common sense there. And the chickens have come home to roost. Right. With how much pressure that SaaS companies are seeing with per seat pricing these days, they were able to get away with it for a long time. But a lot of things that he said and you just described are kind of a harsh reality for a lot of companies these days.
A
It's true. I think especially with AI and what's going on right now, usage based pricing is becoming. Even in industries that were heavily per seat, I think a lot of them are seeing the advantages of figuring out more of a usage based value metric.
B
Now a usage based value metric makes a lot of sense for the reasons you explained, but it can also become very confusing for customers if you don't present it in a easy, clear, concise way. How did you get around that? Because the $29 minimum. Great, I get that. The 50 cents per customer. Okay, how does that work? What does that mean in reality? Just, just how did you explain it to customers and how did you execute on that?
A
Yeah, so it would come up, the, the questions would come up. Some of the bigger questions were, is that like $29 plus 50 cents a customer or. And so we'd have to explain, no, it's a minimum. So you know, if you have 20 customers, you're going to pay the minimum of $29 a month. You know what it came down to in, in the conversations we'd have with people, I just ask, how many customers do you have? And they all know. And a lot of them, they'll say pools, like how many pools do you have? And pools is sort of synonymous with customers. So I'd say, how many pools are you running right now? And so they might say 100 or 150 or 350. And whatever it was, it was just so easy because it was 50 cents per. You just cut the number in half. It's like, okay, you're doing 150 pools a month. That means skimmer would only be $75 a month for you. $75 to help you run your entire pool service business. And if we ever got pushback back then, I'd just say it's a drop in the bucket because at the time many of them were charging at least 100amonth for pool service. And of course that number's gone up recently over the last several years, and different markets are different, but it was easy for them to do that math.
B
I'm curious, you mentioned there was some other products in the market already, but they were web based. Your biggest differentiator was coming in with a mobile product. And then all the other things that you talked about, doing the welcome calls and just trying to focus on great customer service to Drive the word of mouth. Were the majority of your customers coming from pen and paper or were they coming from these other products that didn't actually work as well for them as they wanted?
A
Yeah, mix of both, I would say, especially in the early days, it was mostly people coming from pen and paper because the other software products had not gained like a tremendous amount of traction themselves. So most of our early customers were coming from pen and paper then. It was one of those situations where as more people came to market, there's different ones, different software products that people were trying to launch in the space. Over time we started getting definitely more switching over from other software as well. But it was very interesting because the pen and paper crowd, it was so easy to talk about the differences. It was so easy to talk about the pitfalls of pen and paper. Obviously there were some great aspects to it because paper is infinitely adjustable to your own needs. And so everyone could do whatever they wanted on paper. And then switching over to software, well, you have to figure out how that fits. But there are so many downsides to using paper. Just as an example, they, many of them will bill extra for chemicals that they put in a pool. And so what that process would look like is a pool tech goes out, services a pool and he has to then manually write down on a sheet of paper what chemicals were put in that pool. And then he does that week by week. And then at the end of the month, all the binders, all the papers would have to come back to a central point and you'd have to go through page by page, customer by customer, manually total up all the chemicals and then figure out what to avoid invoice for for each customer. You just think about that. And I mean, software just immediately fixes all of that.
B
Yeah. You know, you and I were talking earlier and I said to you that, you know, I get emails every week from Skimmer from my pool cleaning company. And I kind of looked at, you know, and the email like the pool guy will arrive at the pool and literally like as he's walking away, I've got an email and there's a photo of the clean pool and the chemicals and the ph levels and all of this stuff that I can see. And I was like, I wonder who built this software? And I never actually followed up. So it was interesting when I got your email and I was like, ah, finally tracked him down.
A
That's incredible. Yeah, I love hearing that.
B
And actually I would say I switched pool companies and the company I was using previously was also sending emails in skimmer so it's all over the place. I wonder what do you think led to you having so much more traction? And I know the first year was slow. 76 customers doesn't sound that bad if you're working full time and, and you're bootstrapping a business. But at $29 a month averaging out is probably only 2 or 3k in MRR. What do you think led to skimmer getting so much traction around the country compared to some of these other products? And I'm sure as you got more success there were more copycat products as all as well sort of appearing.
A
Yeah, I asked myself that question early on as well and I mean I was very happy. I think it's because of a couple of things. One, it was really focused on creating the best user experience that we could. And I had this idea that the software should get out of your way. And when you're talking about guys in the field that are used to being able to maybe like quickly write down like you talked about the chemicals that, the readings as well as the chemicals they put in it, doing that needs to be fast. I mean these guys need to move, they need to go from customer to customer. They need something that makes it easy for them to do that and gets out of their way. And I'll just give you an example. When it comes to entering the chemical readings and the chemical dosages and if you looked at all the other software that was out there, again web based, and some of those things like you would be putting in, like how many, how much chlorine did you put in, how much acid shock, you know, just different things. And each of them would have different types of numbers. It wasn't just 1, 2, 3, 4, 4, all of them, some of them were wildly different ranges and numbers that you would need to enter. So the way that most other software handled that was they either just gave you a bunch of text boxes and you had to like plug in those numbers manually, which was a tap to get in the box, a tap for each, for the digits and then a tap to accept it. Or they would have drop down list of values. But for everything it was scrolling taps, multiple taps just to enter one thing. And it was slow. Well, we came up with a unique way of entering those things so that they didn't have to type anything. And it was literally just a tap per value and there was a slider that would come down and they could move values just in a quick slider to get to the exact value they needed and they could just tap Tap, tap, done. And so it just got out of their way. We understood the context, and that's just one example. But the idea was give them the information they need to make good decisions in the field, give them the ability to record what they need in the fastest possible way, faster than what they had before, and then just be out of their way. And I will say, I've never been a designer by trade, but I always enjoy looking at good UX ui. And so I really spent a lot of time, like with the colors, the layout, the white space, and thinking through how to make it visually appealing, but always trying to reduce the number of taps, the number of things that they manually had to type or do so that they could just get the work done. And the software got out of the way. And so I think that level of focus there was something else as well. We were the only ones that worked offline. And some of these folks even, like in the Phoenix area, there's areas where there's no cell signal. And so you could have these techs on site with absolutely no cell signal. So if it's web based, you can't enter anything. But with Skimmer, it would work offline just like normal. They wouldn't be able to tell the difference at all. And then when they were back in an area where they had cell signal, then it would be able to reconnect and sync up to the cloud.
B
That's cool. You told me previously that churn was around 2%, which is awesome. Was that. Was that just how where things landed, like organically, just people went from pen and paper, started using skimmer and never went back? Most of them. Or was Churn higher at some point and you had to figure out how to get that down?
A
Definitely had to figure out how to get it down. It was, I would say in the earlier days it was around 6% and then gradually got that down to around 2% and it was. Yeah, so it was a few things. One, no surprise we had more Churn when it was iPad only, but when switched over to phones where people could just use the iPhones and the Androids they already have, of course that helped. But then from there, you know, continuing to give the great customer service the welcome calls, that certainly helped. And there was something that I had. I don't know if I read it or heard it on a podcast, but they said, you don't have a Churn problem, you have an onboarding problem. So I really worked on a very simple onboarding flow, but it used sort of a little, A little Piece of psychology that it's been out there, it's written. There was like car wash companies where if you get a free car wash after so many car washes, they like, punch a ticket, punch a card. And they found that if you give a card that already has one or two punches for the people, they were far more likely to continue to completion, to actually keep coming back, to fully fill out that card and get a free car wash. So what I did was once people signed up, I took them to just one of those standard kind of onboarding screens where there was a little flow and there were five steps for them to complete, but the first one was already marked complete, which was essentially sign up. And then I understood there was a Stanford series where Y Combinator folks came in and they taught a lot. And some of what there was a lesson from Facebook, and they said, you want to get people to that magic moment as quickly as possible, figure out what is the point where they just go, aha, I get it. This makes sense. This is cool. Get them there in the fastest possible way. My little onboarding flow, the steps that I gave them, it was like putting blinders on them and just getting them to enter the customers that they needed to service the next day, building their route for that next day, and then that next day, actually running the route and seeing what it looked like, because I knew if they would get in the app and see what it was like to use it in the field, they'd love it. So working with that onboarding flow and continuing to make the product better got into kind of a cool cadence. I mean, early on, you know, resources were heavily constrained. It's not like we had a team of programmers. It was me. I was the programmer. That's it. And then eventually I was able to bring on more help. But resources were always constrained. And so I found this cadence where if I worked on one kind of big marketable feature, something that, you know, customers had been asking for, potential customers had been asking for, I would get that one big marketable feature done, email people, you know, let. Let the world know about it. And then after that, I would do a little stint of working on smaller projects, quality of life projects, where I would take all the feedback we had been getting from customers and fix the little paper cuts, the little things that were annoy, the little things that could just make it smoother and better. And we take time and, like, knock a batch of those out and then email existing customers about those things. And what's interesting is we got as much good word of mouth from that as from the big, more splashy, marketable features. And so we just did a cadence. And then I also found that if I had a big feature to release at the beginning of every calendar year, it worked out really great. Because as it turns out, pool service companies, new year starts, they're thinking, what can I do different with my business this year instead of that, that I didn't like about last year? And if you can show up with, you know, on their radar again, hey, here's skimmer. And, oh, they just released this new thing then. Now it's top of mind. And that really helped to kick off our growth every calendar year.
B
So you founded the business in 2017, bootstrapped it to seven figures, got SEO working eventually. Now, a founder who's struggling right now might listen to this and say, Ron hadn't built a SaaS before, didn't look at any other ideas. This was his first one, didn't raise any money, bootstrapped, and then ended up having a successful exit. Tell us about some of the difficult times. Give me one example of a tough moment that you had to go through. Because in every journey like this, it's never all easy, smooth sailing.
A
As an entrepreneur, you are on that emotional roller coaster. And when you have customers that churn out, especially ones that you thought were going to be big and helpful to your company. Yeah, I mean, it's just not easy. It's very hard at times to detach your emotions from the success or failure of the business. And so I would say it was just those ups and downs of what's happening. Are we growing this month? Are we not? If days would go by and you weren't getting the same number of signups, has something changed? Is something broken? And of course, there's always technical stuff, right? There's technical hurdles that you have to deal with. And at different points, it's like, man, are we going to be able to figure this out? Are we going to be able to solve this and be able to provide this next thing or overcome this thing thing. And you're right, it's not all sunshine and rainbows. There are tough days, for sure. But I would say looking back on it, there were definitely more positive days than negative days, for sure. And it's a very satisfying thing to be able to build software that people are using to run a business. And I really enjoyed pool service companies because they, you know, they're entrepreneurs, they're building their own businesses. They're. They're really trying to carve something of their own. And so they ended up becoming great people to work with but you didn't want to let them down, right? I mean, and so if there were something that, where you got something wrong or you put out an app update that broke something, now you got to apologize, you got to email everyone. And those days aren't fun, but certainly the positive days and the positive feedback you get more than make up for it.
B
So you went from zero to the first million in ARR in about four years, I think. And then you said it was around that time, as you got to 1500 plus customers, that you started getting interest and eventually you sold the business. Tell me about the acquisition. How did that happen and why did you feel it was time to sell?
A
I had no idea at the time that how business. I mean, I was aware of some brokers out there like FE International, that was the main one I was aware of at the time. And I would always kind of, I had started a relationship with them, talking to them to kind of understand what skimmer was worth by all of their, you know, metrics and accounting and everything. And so I knew basically what it was worth. What I didn't know is that there are people out there actively looking and searching for SaaS businesses to buy and they will reach out to you. And I just had no idea that that was a thing. And somehow as you grow and get bigger, you end up on their radar. I still couldn't tell you to this day how they all find out, but they do. So it was really a pretty cool experience. I ended up getting this cold call from someone from Unbundled Capital and his name is Pete Freeland. And it was a cold email wanting to talk about skimmer. And I looked at the email, I thought, I don't know, I don't know this guy. I'm not sure if I should respond, but something told me I should respond. So I ended up responding to his email and we ended up talking and at the same time there were a couple other companies that came and wanted to talk about acquiring skimmers and it ended up being sort of like a little bit of a shark tank moment. It was kind of cool having multiple interested parties and you know, seeing because I mean all the metrics were super healthy for skimmer. I mean everything was, was looking quite good for it. So it was, it was a good time and I knew what I wanted to get out of, of the business if I were to sell. And so for me it became, if the number was correct, then it was a good time for me to the right buyer. So ended up having more conversations with Pete at Unbundled Capital. And ultimately there was an acquisition there. It was an interesting process. You know, there ends up becoming a letter of intent. You know, you agree on all those terms, and then once that happens, you go through this due diligence period, which for me was about three months. That is not an easy time for sure, because you're fully opening up everything about the business and you're hoping everything goes through and everything continues to be good. It was definitely a stressful period, but ultimately it worked out. And Pete was colleagues with someone named Jack Nelson, who came on to be the new CEO. And man, I tell you, it's incredible how they've been able to take the business and move it forward. It's just been so cool to be for a while. I stayed on for a little bit for a transition period, about six months to transition things out. Stayed on a little longer as an advisor and then fully exited a couple years ago. But they have continued to grow the business. Jack as CEO now the company has over 100 employees, and they've just continued to grow. I mean, it's incredible. Incredible.
B
What a story. I mean, did you. If you had known how big, how much bigger the opportunity was, do you think you would still have sold?
A
It's a fair question. I will say I have never looked back with any regret on selling it. For me, it was the right time and it was the right buyer. Like I've said, I built a business. Jack, built a company. So to scale it to the next level, where you're really building up the team much more than I ever had, and you start really transitioning into company things. You need company values, you need hr. You need so much more infrastructure to support a healthy and growing company, which was certainly well outside my skill set. And I was able to be along for the ride and offer input and advice where I thought it would be helpful. But no, they were the right ones to take it from there. And, yeah, it turned out better than I could have thought. My pie in the sky idea was if Skimmer could ever get to 1,000 customers, it was a huge success. And I, well, passed that. And of course, it's gone on and continued to progress much past that at this point.
B
Yeah. So what are you doing with yourself now?
A
Yeah, so I have another little lifestyle software startup that I got. It's kind of keep me in the software arena a little bit. It's quickfax.com for online faxing. So been spending a little bit of Time with that.
B
I think we've all been there. I read your story on the site that you wanted to send a fax and every service out there wanted you to sign up for a subscription or something. And you're like, I just need to send this one document. And there wasn't an easy way to do that. So you decided to build something yourself. I've been in that situation, so I know what I would use now.
A
Great.
B
It's like no account, $50 to send a fax. You know, when I looked at that, I thought, do people still fax? And then I did a little bit of digging and I was blown away by how much faxing is still going on right now.
A
It's quite surprising really. Literally, like thousands and thousands of people have to fax every day. And of course a lot of that can be business related. Medical industry is pretty notorious on the faxing front, but individuals like, for me it was I needed to fax something to a title company for some real estate transaction. And there's a lot of people that just from time to time, like you said, just need to send a single fax. And it's early days with it. And it's interesting because it's so different from Skimmer. It's also not B2B, it's B2C which I had never done anything in the B2C space. But it is interesting. Some of the things that still come over like working on SEO and getting early customers through SEO and Google Ads as well, but a focus on the user experience. And I think the most enjoyable thing for me is we get reviews like on trustpilot and just seeing how people are delighted because they expect it to be a negative experience. They expect upsells, they expect getting forced into a subscription or a free trial that they'll have to remember to cancel. And when none of that's there and it's just kind of a delightfully simple experience, they're like pleasantly surprised and they leave us a great review and say they're so glad they found us. So it's been an interesting, completely different business from Skimmer, but also an enjoyable one to work on.
B
Yeah, I love that. And I think that, you know, it is very different to what you built with Skimmer. You know, maybe, maybe it will trickle along, maybe you'll grow it into something, you know, much bigger, who knows? But I think that the biggest lesson here, I think for me, people listening is, you know, I often get asked by people who want to get into software, you know, they don't it's easy to build software these days, right, with AI and everything, but what, what should I build? What kind of product? Which market customers, all of this stuff. And I think the simpler answer is this problem's everywhere. And sometimes it's just about finding something that annoyed you, frustrated you, and just building a simple solution. And instead of wasting time trying to figure out the TAM and the opportunity and researching and competitors, it's just like just go and solve tiny problems and see if you can make them better.
A
I agree. Yeah. And you're right. I mean, we're especially living in a very interesting world right now with AI and what can be built and by so many people. And there's, I think, a better opportunity now for everyone to do that, even if you don't have a background in computer programming to be able to start solving some of those just nagging little issues that you've dealt with.
B
Yeah. All right, let's wrap up. Let's get on to the lightning round. I've got five quick fire questions for you. Ready?
A
Ready.
B
What's one of the best pieces of business advice you've received?
A
It's from my mom when I was building Skimmer. She said, you got to toughen up because, you know, going back to one of your questions, you know, there's good days, there's bad days, it's, it's certainly not as easy as just working a normal full time job, but she said you got to toughen up. And she was one of my biggest supporters and helpers through the whole business. But that was some of the best advice that I got and came at a time when I needed it.
B
What book would you recommend to our audience and why?
A
Yeah, there's a book called Traction. I think it's Gabriel Weinberg, which for me at the time it was just really helpful thinking about what are the different traction channels for skimmer or for SaaS in general, for startups. And the first few chapters kind of lay out what those different growth channels, channels can be and gives you a framework for figuring out what to focus on. Something else in that book that helped was that it said really focus on one thing until that's no longer moving the needle enough. And so that was really helpful advice. Good book.
B
Yeah. Gabriel's been on the show and Justin Mears, I think is the co author and a lot has changed since then, but I think a lot of the principles in that book still apply today. So good recommendation. What's the best money you've ever spent on your business?
A
You know, since I was the only one programming in the early days, I think I'd have to say is being able to bring on people to help with the programming. That was some of the best money I spent at the time with growing Skimmer because that allowed me to start to focus on other parts of the business and not be the only one responsible for the code base.
B
And your first hire was a First
A
hire was customer support. But the first in terms of computer programming, there was a contractor that I found.
B
What's your favorite personal productivity habit?
A
I have to say now I'm really enjoying using Lovable. Lovable has just been so awesome. And wipe coding things that I've wanted to build for myself easily. I actually have stopped all the manual writing of code, letting AI do it. And to me, as someone who has been programming for years, the idea of being able to chat with AI and have it produce code is still to me incredible. So I'm loving, love and lovable right now.
B
Awesome. And finally, what's one of your most important passions outside of your work?
A
I have to say travel. Absolutely love travel. I. I've been to most of the continents. I've been to six of them. Still got to get to Antarctica at one time to get the 7 of 7. But absolutely love travel.
B
Awesome. Well, Ron, thank you so much for joining me. If people want to check out Skimmer, they can go to. I think it's get skimmer.com and quick facts.com is the other one. And if folks want to get in touch with you, what's the best way for them to do that?
A
Yeah, they can go to quickfacts.com and you can email me@ronquickfax.com it's the best way to get in touch with me.
B
Awesome. Thanks for joining me. Thanks for sharing your story. It's been a pleasure and I wish you the best of success.
A
Thanks Omer. Really appreciate it.
B
Cheers. It.
Host: Omer Khan
Guest: Ron Hasch, Founder of Skimmer
Date: July 16, 2026
This episode spotlights the journey of Ron Hasch, a self-taught software developer who built Skimmer: a SaaS serving pool cleaning companies. Ron shares how he discovered this niche, validated the idea with a single cold call, bootstrapped to 1,500+ customers and $1M ARR without paid ads, and ultimately sold Skimmer, which has since scaled dramatically. Key themes include pricing innovation, customer acquisition with zero ad spend, reducing churn via onboarding, customer-centric operations, and the emotional reality of solo SaaS entrepreneurship.
Initial Spark:
Ron was a programmer looking for a product to build when a friend who owned a pool business asked how hard it was to learn programming. The friend complained about the lack of good software for pool management.
"It got to a point in the conversation where he ended up saying, the paper game is killing me. And at that point I knew, okay, this is a real issue for people." (A, 00:00)
Market Validation:
After hearing another podcast mention pool service, Ron cold-called a random pool tech from YellowPages.com in Texas. The pool tech confirmed the same pain points — running everything on paper.
Decision to Build:
One conversation was enough for Ron to commit:
"Really? It was after that one conversation.... That was enough for me to know that the problem was real." (A, 09:10)
Bootstrapping on Nights & Weekends:
Ron kept his day job while building Skimmer, initially focusing on iOS/iPad with customer feedback quickly steering him to support both iPhone and Android.
Feature Discovery:
Features were determined by frequent, direct conversations with real users, including proactive onboarding and support calls.
"On my lunch break, I'd be in my car... making these phone calls to people who had newly signed up." (A, 10:47)
SEO as the Engine:
With zero ad budget, Ron learned enough SEO to rank for “pool service software,” gradually bringing inbound customers.
"I started ranking for pool service software and pool service app, and that became the way of getting customers." (A, 12:20)
Word of Mouth:
Exceptional customer support — fast response via phone/email — led to strong word of mouth, including recommendations in industry-specific Facebook groups (despite Ron not being on Facebook himself).
Long, Slow Ramp:
"It was pretty slow. In the early days... we were growing more in a single month than it took the entire first year." (A, 16:06)
Usage-Based vs. Per-Seat:
Skimmer charged 50 cents per "serviced customer" per month with a $29 minimum—contrasting with all competitors, who charged per seat.
"Everyone else was charging per seat... I remember I had this one guy, he called me and he said, man, I get happy every time I see my skimmer bill go up because that means my business is growing." (A, 00:00; A, 19:17)
Why Not Per Seat?
Drawing from Patrick Campbell's writing (Price Intelligently), per-seat pricing discourages usage and expansion. Usage-based pricing aligns directly with customer growth.
"You want your pricing to be as close to the money as possible... by changing the pricing model... it put everyone in alignment." (A, 18:04)
Clear Communication:
Pricing was made simple:
"I just ask, how many customers do you have? ...it was just so easy because it was 50 cents per. You just cut the number in half." (A, 21:52)
Mobile-First & Offline Access:
Most competitors only offered web-based solutions. Skimmer focused on a tailored, mobile experience for field workers and worked offline—critical in areas with poor cell coverage.
Extreme Focus on UX:
Ron obsessed over reducing taps/clicks, making data entry (like chemical logs) lightning-fast for pool techs on the go.
"The software should get out of your way... Give them the information they need... get out of their way." (A, 27:45)
Fast, Personal Support:
Phone answered, emails replied to within 30 minutes — a stark contrast to most SaaS.
iPad-Only to Full Mobile:
Churn dropped when product became available on users’ own smartphones.
Onboarding Optimization:
Onboarding was treated as the critical moment—using behavioral triggers and psychology (pre-filled “steps completed” à la loyalty cards) to get users to their “aha!” moment.
"You don't have a Churn problem, you have an onboarding problem." (A, 32:09)
"I took them to... five steps... first one already marked complete... just getting them to enter the customers that they needed to service the next day..." (A, 32:09)
Release Cadence:
Alternating between big marketable features (for new acquisition) and rapid-fire quality-of-life improvements (for delighting current users); timely annual releases to align with pool companies planning for the new year.
Ups and Downs:
Ron is candid about stress, uncertainty, and emotional swings — especially customer churn and technical hurdles.
"It's just not easy. It's very hard... to detach your emotions from the success or failure of the business." (A, 37:48)
Personal Support Network:
Best advice: "You gotta toughen up" — from his mom.
"She was one of my biggest supporters and helpers through the whole business." (A, 50:29)
How It Came About:
Unsolicited outreach from Unbundled Capital’s Pete Freeland led to a “Shark Tank moment” with multiple parties interested.
"Ended up being sort of like a little bit of a shark tank moment." (A, 40:28)
Scaling Beyond the Founder:
Buyer (with Jack Nelson as CEO) turned Skimmer into a real company—over 100 employees, $79M raised.
No Regrets:
Ron felt “no regret” about selling; he saw his contribution as building a business, while others built a larger company.
"For me, it was the right time and it was the right buyer... and it turned out better than I could have thought." (A, 44:19)
"It's so different from Skimmer... It's also not B2B, it's B2C... but a focus on the user experience." (A, 46:43)
“The paper game is killing me.” (A, 00:00)
The “moment of clarity” that set it all in motion.
“I get happy every time I see my skimmer bill go up because that means my business is growing.” (A, 00:00 / 19:17)
Illustrates the alignment between pricing and customer growth.
“You don't have a churn problem, you have an onboarding problem.” (A, 32:09)
Key pivot that drove churn down and product stickiness up.
“We got as much good word of mouth from [small fixes] as from the big, more splashy, marketable features.” (A, 35:48)
“It's just not easy. It's very hard at times to detach your emotions from the success or failure of the business.” (A, 37:48)
“I've never looked back with any regret on selling it. For me, it was the right time and it was the right buyer.” (A, 44:19)
“[Best advice:] You gotta toughen up.” (A, 50:29)
This episode is a masterclass in finding, launching, and scaling a niche SaaS, anchored by relentless customer focus, clear pricing innovation, and the patience to let compounding work. If you’re building a SaaS (or want to), Ron’s answers offer a blueprint grounded in lived experience, not theory.