
Hewitt Tomlin (TeamBuildr) on building vertical SaaS around one job function, charging NFL teams the same as high schools, and bootstrapping to $10M ARR
Loading summary
A
Welcome to the SaaS podcast. I'm your host, Omer Khan. AI has changed the playbook for building and growing SaaS. Every week I talk to founders who are writing the new one. My guest today is Hewitt Tomlin, the co founder of Team Builder. They build software for strength and conditioning coaches. Hewitt has bootstrapped this business to over 10 million in ARR with a team of 45 people today never raised a dollar, but it took five years to get to the first million in ARR. And their pricing is a little unique. They charge NFL teams the same price that they charge the local high school team. Hewitt built software to make coaches better at their jobs, but his biggest competitor is betting on AI to replace coaches completely. Hewitt's betting the opposite. One of the hardest things about building a SaaS product or an AI agent is is not having a technical co founder or CTO to guide the decisions. That's where Gearhart comes in. They can act as your fractional CTO and technical team. They bring AI expertise from projects for Meta and Google and they have strong Silicon Valley connections with founders and VCs. And since they're a Ukrainian born company with offices in San Francisco and London, you get senior level talent at an offshore pricing model. Right now they're giving our listeners the first 20 hours of development for free. Go to Gearhart IO to book a call. That's Gearheart IO. If you're building or investing in a SaaS company, you already know security isn't optional. One breach and everything you've built can be at risk. That's where ThreatLocker comes in. Imagine having the power to decide exactly what's allowed to run in your environment and blocking everything else by default. No guessing, no hoping your existing solutions catch it. Real enforceable control. ThreatLocker is a zero trust platform that locks down your environment without disrupting operations, gives you total visibility, and stops unauthorized applications before they become a problem. If you want stronger security and tighter control, visit threatlocker.com that's threatlocker.com you're putting in the hours, but your SaaS isn't growing. It's not your product, it's not your pricing. It's the way you're wired as a founder. And once you see it, everything changes. Every founder has a blind spot. The builder ships great code but forgets to sell. The visionary chases big ideas but can't execute. The optimizer tweaks endlessly. Instead of finding customers. Which one are you? I created a free quiz that identifies your founder archetype and gives you a specific playbook to fix. What's holding you back? Take the Quiz at Sasclub I.O. quiz. That's Sasclub I.O. quiz. All right, Hewitt, welcome to the show.
B
Thank you for having me.
A
Yeah, it's my pleasure. So for people who aren't familiar with Team Builder, can you tell us what does the product do, who's it for, and what's the main problem you're helping to solve?
B
Of course, we are a classic post iOS SaaS company. The iPhone came out my freshman year of college and lucky for me, my roommate and my teammates got the iPhone right away because he was a computer science major and he just couldn't help but get it. Remember, when the iPhone first came out, it was not as ubiquitous. BlackBerry was a very big thing and other smartphones were out there much more commonly than they are today. So when the iPhone came out, it changed how we thought about distribution. We as college athletes received our training program on a workout card or paper packet in the summer. And we thought that at this paper packet in the summer, if it was an app, training in the off season with your teammates could be a more social experience if we had a mobile app. So originally Team Builder was supposed to be kind of a team centric social app and we didn't know it at the time, but we were a product of our environment. Facebook was really big when we were in college and building social apps was like the coolest thing you can do out of college. So naturally we thought about building a social app. And did the world need another one? Probably not, but lucky for us, we pivoted pretty quickly thereafter.
A
Cool. So you've got this idea, how did you get started? What, what did you do? Like, did you guys, did you, had. You guys had any experience with building software? Did you just start building, did you say, we're going to go and talk to people?
B
My partner James was experienced in building front end and lucky for us, started building some back end things as we got into senior year. And Team Builder is an intensely backend heavy app because of all the data that it stored. So that was a good thing. More importantly, we didn't have experience other than building some gimmicky websites, which is good experience to just build things and put them out there. What we did not have experience with is we had working with a customer, an audience, understanding that side of things. But lucky for us, a university is a very friendly place to start a business. That's kind of the whole point, right? To put people together to give them access to one another. So when we reached out to our campus strength coach, they took a meeting with us just to hear our idea and explain their process to us. And it didn't take very long to realize that this coach was not necessarily interested in a social experience for his players. He was more interested in accentuating or improving his workflow for how he built and distributed these training programs. So he didn't know it at the time and we didn't know it, but he kind of pivoted us to being like a true B2B SaaS company, which was a really good thing because I don't know if I have the appetite for being anything other than a B2B SaaS company.
A
Yeah. So I think that's a really interesting part of the story. Before we get into that, just give us a sense of the size of the business, like where are you in terms of revenue, customers, size of team?
B
Today we are almost precisely on the dot, a $10 million a year revenue company. We, we have 45 employees. And what's unique about us is our structure, our leadership structure. James and I are the two original owners and we use the same operating agreement from 2012 and it's 2026, so that's very rare. But that's one of our most unique aspects.
A
Yeah, you guys are 100% bootstrapped and you've hit 10 million in ARR.
B
Yes, exactly.
A
So, so tell me a little bit about this journey you went on that you originally built the product, I think for athletes and this coach conversation that you had eventually got you to this realization point that you were building for the wrong customer. How much time had you invested? What had you built up until that point? Many founders are in that situation. They sometimes confuse go and talk to customers by validate the thing you've built. And it's really hard to throw away what you've done. So I'm curious, how far along were you and how easy or hard was it to make that decision once you had this conversation with the coach?
B
Well, lucky for us, we were still in school, so we didn't have the capacity to build all too much. So what we had at the time, I think was designs for mobile, what we thought was a very mobile centric experience, but not very much built. And when we made the pivot, we essentially pivoted from focusing on a native social app to being a heavy web based portal for the coach. Now back to your point. Yes, many entrepreneurs have an idea. Marry it in the words of Brad Feld and do more faster. He's a techstars co founder, which is a great book. Entrepreneurs marry their idea and you can't marry your idea. So if you're validating ideas to people and you've actually started building, you have a very strong incentive built in to fish for what you want to hear. And that doesn't always happen. So I see it a lot, I hear it a lot. I sort of like the idea of someone who is publishing and shipping and just seeing what happens. If it's a social app, like when I was back in college, just put it out and see if anyone's on there and what they're posting. It doesn't matter if they're doing exactly what you designed it to do. But if someone is doing something on there, that's validation of something. Maybe not what you originally intended, but that's what you ought to be looking for, is what are people wanting to do, what are they finding a way to do, Whether it was my idea or not.
A
Yeah. So tell me about this, this conversation with this coach. Why was it so pivotal? And, you know, why did it push you in this direction of a different icp, different customer, a different product? Many people would have had that conversation and said, yeah, that was nice, interesting, let's go back to the plan. Right. But you guys didn't do that. So how did, what happened in that meeting?
B
Well, for one, this coach shared their professional workflow with us. This is their job function. It's part of what they get paid to do. It's necessary to delivering their value. For two 21 year olds, 22 year olds, that was pretty good. That was pretty meaningful to us. So I don't think it was difficult for us to necessarily pivot because I think we were honored by the fact that someone was letting us into what a real job looked like. A real job, responsibility with a salary attached. It may not sound like a big deal now, but that was a big deal to two college students. So I think we just understood the gravity of what was able to be optimized was much more important with this coach's professional job than it was to create a social experience that we wish we had. Right. So I think that's number one. Number two, James and I have uniquely never brought a lot of ego to the table with each other. I like to tell this sort of like made up story. If James came to me and said, hey, we're getting into pet food, we're no longer team builder B2B SaaS, I believe that we ought to be doing pet food, I would never say no. Right. Off the bat, because we always make room for each other and give each other time and space and respect for any thought or conviction. So I think when we went out on this journey to build this company, we always had a good habit of listening and being very open and less dogmatic about what we thought something ought to be. And we're still like that today. And it's one of the strongest lessons I can teach younger entrepreneurs. In fact, even this morning, before we got on, I worked with a young entrepreneur named Jacob, and we were working on a piece of feedback from a prospective customer. And I had to share with him, you know, James and I, we don't think this way about this current situation. I had to sort of rearrange that for him. And it takes a lot of reflection, which is sort of counter to an entrepreneur's extreme urge to do right.
A
Okay, great. So you've now got some clarity. You see a real potential customer in front of you. What type of product? What was that first version of the product that you guys built? And how long did it take for you to have something that you could sell?
B
I think we started building towards an MVP in the summer of 2011. We made our first dollar in the summer of 2012. So that's the timeline that first dollar was. The first dollar is always hard to come by, but harder things take place before then because you want people to use your product and not you really do. If you're out there looking for the first dollar, I think it's great. However, the first users are so much more valuable than cash in the bank. Those first 10 customers, I'm really grateful for them. But I had so much more people of value prior to that who were willing to try things and speak to me about it, because people's time is worth money. If I'm asking someone to switch off of Excel, which is what I was doing, and asking them to try my brand new MVP product instead, well, this is my time. I have to climb your software's learning curve. This is money out of my pocket. Right, so the first dollar, yeah, that's how long it took. But it was a lot of arm twisting to get people even to get on the thing and tell me what their genuine experience was.
A
So sometimes founders give away the product for free initially because they don't want to ask for money, or they don't want to sell the product, or they're, they're, you know, scared to do that. When I do agree with you, I think that people giving their time is also a fair value exchange. And is very, very important in those early stages. How did you make sure that those people actually used the product and actually gave you feedback? Because when we get stuff for free, sometimes we don't value it as much and we don't put in a lot of time and effort to use it.
B
Yes, giving away your product for free, freemium, private beta, whatever you want to call it, trust me, I know. I think what. What folks sort of get wrong sometimes is the free product relationship is not passive. It's still very active. When I gave away Team Builder for free, I made sure that it wasn't just opening a software license, that it was my time and services and consultation in the process. So I was sort of acting as a companion on that as opposed to you try it on your time and I'll wait for your response. So a private beta where someone just presses a button to join, too much of the burden is on them. When I did my free period, if you will, I wasn't looking to send over a login and a password. I was looking to build a relationship with the person. I was looking for a partnership with them. And I wanted their critical thoughts on what I had built. People just don't give away their critical thoughts because critical thinking takes work and time and effort. So when I first called these coaches, I very rarely emailed and expected a lot over email. I would call a lot of coaches and introduce myself and make myself available. I showed up in person to a lot of conferences and clinics. I was more or less building a network while simultaneously giving my product away for free. My earliest adopters I still know today, the very first customer, Dr. Steve Smith, is someone that I could call right now, and I send him some gear every once in a while. So he wasn't just a user. Right. He wasn't just an early adopter, someone that I was seeking to glean information from in order to cross the chasm. I really was looking for early partners in my business, just a different kind of partner. And I think that's an important part of it, is that these folks are not just sounding boards for feedback. These folks are going to be your early adopters, your early partners, your early collaborators on your business.
A
This whole idea of having free users, I love the relationship thing. And I wrote down what you said, that I wasn't looking to send out a login and password. I was looking to build relationships. How did you also set expectations with them that the product wouldn't always be free forever?
B
That's a good question. I don't think I Did you know I was too young, 22, 23. I wasn't necessarily thinking, thinking that way. I probably thought that rightfully that I was so novice to this profession, this industry, that I had a lot to learn and a lot of people to listen to. That was my prerogative at the time. So I think probably the decision to begin charging just sort of came organically. I think intuitively we just knew that we had been doing a lot of listening, a lot of building, and maybe it was time to see if we can get a purchase. And that took a little while, maybe call it another six months from the time that we decided on a price and a license. And again, that first dollar in, it's a milestone. But that's when the real work begins. Now you're contractually obligated to deliver services and they're relying on you and they're entitled to your support. So it doesn't change anything from the free mode. In fact, the stakes just go higher. That relationship matters even more. And the listening needs to be even more intentional and the critical thought needs to be very critical. One anecdote, for example, is there's what the customer says and then there's what they really want. And words are mostly inadequate expressing what they want and then the context doesn't really allow for it. So customers, because you're a software vendor, will speak within the context of your platform or what it can do and what it can't do, but the outcome they're looking for is a little different. Different, Right. And that's exactly the conversation I was having with this young entrepreneur earlier today. He was thinking solely within developing the product based on this prospectus, customer's feedback. And I said, no, no, no, you got to read between the lines. They're only talking about a missing feature because they don't know how to express to you how their problem can be solved. But our job is to peel the layer back and say, look, this person is looking for a specific outcome and, and what feature we build or don't build is up to us. We're not going to build what the customer wants verbatim. That should never happen. The customer is always right. There's more to it. The customer is not always right when it comes to guiding your product development. The customer is right in terms of understanding which outcomes they want to be better at their jobs, have a more successful career, have an easier day to day workflow. Those are the things that you really have to look out for. And they're never obvious, because if they were obvious Then we would all be really prolific at building SaaS products.
A
Yeah, it reminds me of that sort of analogy about drilling a hole in the wall. And if you just focus on that and what the customer wants to do is to make a hole in the wall and we have a drill bit and we can talk about the different types of drill bits and what type of hole they can make and all of this stuff, but ultimately if you take a step back and say, what, what are they doing? Is it about they. They want to renovate the kitchen and put cabinets up, they want to have a more beautiful looking house, they want to build a better office? Right. Then maybe you have a different type of conversation as opposed to just the hole in the drill. Right.
B
It's a completely different type of conversation. And maybe they're willing to have it with you, maybe not. They're much more willing when your relationship looks like someone who is interested in helping them as opposed to interested in perfecting a product or selling a Service.
A
Building a SaaS company from the ground up is tough. Protecting your data and securing your environment shouldn't be. With ThreatLocker, you can deploy application control in days to weeks, not months to years, and enable your IT team to decide exactly what's allowed to run and deny everything else by default. Lock down your environment without disrupting operations and operate with confidence. No guesswork, no reactive solutions, just true proactive control. ThreatLocker is a zero trust platform that mitigates the risk of downtime, reputational damage and cyber attacks, including ransomware and zero day exploits. If you want stronger security and tighter control, visit threatlocker.com that's threatlocker.com if you're building a SaaS product or an AI agent, there's a good chance you're about to spend weeks and thousands of dollars on the basics. Things like AWS setup, authentication, admin panels, dashboards. Gearhart built something called the Basement platform that covers around 80% of the foundational needs out of the box. That alone can save you 5 to 10k in development costs and get you to market way faster. One of the products they help build is SmartSuite, which raised $38 million and is used by companies like Capital One. They only take on a handful of new projects each month, but right now they're offering our listeners the first 20 hours of development for free. Book a call at Gearheart IO. That's Gearheart IO now. Back then, were coaches looking for software like yours? And how were they currently solving that problem? Were they using some other software or app Were they using pen and paper, Excel? How are they doing things?
B
The answer is no. They were not looking for my software product because they just didn't know it existed. That category was very, very young back then. So sport was initially impacted with the specific sport coaches solving for film, watching film, trading film, that being digitized and huddle was the one who did it. H u D L They're like a giant in our field. HUDL did it. So sport coaches were sort of catching the first wave of like, of SaaS. Efficient, real efficient. SAS strength coaches were on the back end of it. Also, the profession itself was narrow. It's very narrow and vertical. So the people at the top of the profession, the decision makers in charge of the budgets, they had been there a long time and they were using Excel based processes that were more or less refined over years and years and years. So when a legendary strength coach with many, many interns would then put these interns out into the wild to go find their next job or whatever, they were using this Excel system that they learned under this legendary coach and that was very important to them. And the whole industry was essentially that. So the hardest thing that I had to do was try to talk someone out of using like a long standing Excel based process because it was like trading in long standing institutional knowledge for a very novel product. Now as the years went on and on and on, it got easier because more jobs were stood up for newer, younger coaches. And then SaaS just became more ubiquitous and better understood and coaches became more open to it. To where I think of a strength coach now, took a head job and was starting from scratch. They would more or less expect that something existed out there. So now all the inbound traffic is people looking for SaaS tools to do this. However, back in the day it was dominated by Excel.
A
So how difficult was it to sell the product? And I'm curious, what did you try that completely failed? Like maybe an approach that you thought would work and it didn't?
B
Oh, it's a good question. Well, I remember the biggest pain always was and it was also the opportunity, right? You had a number of athletes that were being served in a program. Right. A very small high school looks different than a big professional program. And then you had sort of different levels of functionality that each coach sort of wanted. So we had variables to work with to sort of comprise these packages. And still today it's, it's not that easy. Like I look at our pricing and you can really slice it up a thousand different ways. It's like a Never ending process. So right Now I carry 13 years of experience to that conversation where back then it was really kind of the wild west. So one thing is that your market will sort of determine your price point. You ought to know pretty soon how much you're able to charge and how little you can charge to keep a viable business. And that's your ceiling and your floor. And then within there you have to create a system that. One of my big things when it comes to pricing and packaging is is it easy to understand? If it's not easy to understand, it makes the sales process just a lot harder. And I'm not talking about for your icp, because in an athletic budget, the strength coach will probably ask a sport coach and an administrator to pay for it. So there are other stakeholders. All the stakeholders need to find it easy to understand. And you have to work through that. And if it makes sense to everyone, then your sales process will be a lot smoother. So did anything like prolifically fail? I don't think so. And you know why? Because that giant that I mentioned earlier, Huddle, was doing a lot of the groundwork for us. Huddle was selling a lot of licenses into colleges. And we did not want to deviate too much from Huddle because we saw that it was working for them and felt like it could work for us. Now what Huddle did is they charged by the team because they were selling the sport coaches. So if one or two or three sport coaches could get together, they could bundle their school subscription. Whereas for us we only worked with one strength coach usually. So it was a little bit different, but we really were not in the mood to reinvent the wheel all too often.
A
Now it took about five years for you guys to hit the first million in ARR. And I'm curious what was happening during those years that maybe didn't show up in the revenue numbers? What were you doing? How were you spending most of your time and energy those first five years?
B
If you look at our revenue growth on the way to a million, it was always trending up towards a million. That's a good thing, I think. Call it 20 to 50, 50 to 100, 100 to 500. 500 to a million. That was off the top of my head, what we did, numbers wise. Now our business is bootstrapped. Zero to a hundred took three years and I worked full time. I worked at startups, I was a sales and marketing associate. Then I worked in sales and I took a more senior position in a marketing team all in that three year span. So Those numbers were mood lighting a business. When it went from 100 to 500, I quit my job and I put my full time effort into team builder and then the full time effort resulted in 100 to 500, 500 to a million. So that's a big part of the puzzle is what does your current situation look like? If I was full time and I was doing 20 to 50, 50 to 100, it still could have worked, would have worked. But that's a lot of time on your hands to understand why did I only grow this business 30k this year? Why did I only grow it this, this much? So I, you know, I'm really trying to think back. It's been a little while. I don't want to just make things up for your podcast here. You know, I'll tell you what my most recent experience is with other younger entrepreneurs and they're not, a lot of them are not hitting the same trajectory on the way to a million. I see a lot hovering around 20 or sorry, 200,000, maybe doing half a million back to back years. That to me is a problem because if you're going back to back half a million years and you're putting in a lot of hard work in that one year span, you're still unlocking product market fit, right? I don't think it's go to market, I don't think it's a branding issue. It's not a branding issue. It may or may not be your capacity, but if you're putting in a full time effort for a year, it's probably not your, you know how effective you are as an entrepreneur. You have a product market fit problem and that is what you have to unlock. And we unlocked product market fit at a pretty early stage for our company and we rode it all the way up to a million and beyond.
A
When did you realize that you had product market fit?
B
When people were coming to me when I was no longer the one making the cold calls, sending out the emails, just begging people to do a demo. And when people came to the team builder website and filled out a form asking for a call, a demo, the best one, a quote, that's when product market fit is being achieved. And then I saw in SaaS a period where you were going to get that anyway with enough, you know, elbow grease. If you put together a good looking website and you mocked up some really good images of product on your website, then you started getting the inbound. Luckily for us, our product was always much better than our marketing. And then at some point I Noticed a lot of companies were really good at marketing and they were probably getting inbound, but that's not product market fit. I knew that my inbound was product market fit because they were coming in because of our reputation, because of what they were hearing and seeing with our product and not necessarily our marketing apparatus or our go to market apparatus.
A
So getting to the first million, how much of that was driven by outbound versus this inbound engine that, that started building up?
B
Very little. My first job out of college, what I would consider my real first skill set that I built out of college was inbound marketing, thanks to HubSpot. And as our product was doing better and our customer relationships were becoming really strong and we were having more customers, I was leveraging that for, for inbound. I think I was a strong, always a strong storyteller with my customers, a strong storyteller with what we were doing with our customers and turn that into inbound. Team builder to date, I would say has never been like a strong example of outbound. I think we've always been a good, strong example of inbound.
A
But what about in those early days, like getting to the first 500k or beyond? There's probably not a lot of activity unless you were very intentional about building inbound before you started building the product.
B
Yeah, that's a good point. I did mention quite a bit of cold calling and cold emailing as a bootstrap company. James is doing the building. In the beginning, I am doing all outbound. Yeah, you pick up a couple customers, now you're doing some customer support, some relationship building, and you pick up a few more customers and you're doing a little bit more customer support and relationship building. And eventually I think it just seesaws over from doing a lot of outbound into service. And then like I said, somewhere in the middle, inbound marketing sort of took over. And inbound marketing is just much more potent when you have a customer base to work with. Because HubSpot, to their credit, always instructed their inbound marketers that the best inbound always originates with your customers. Right. So it was just a transition, I think, away from outbound to inbound. And the growing customer base allowed us to do that.
A
Now, from what I understand, like about probably about half of your your customers are today are high schools. And when I read that, I was like, do they even have budgets to spend on software? Especially a business that's now doing eight figures in ARR? Was that again an intentional thing that you did to target that market or is that something you discovered along the way and how to sell and how to figure out where the budget was that they could use.
B
Well, you figure out pretty quickly that at our price point, in order for this business to grow, it has to be a volume business. So one thing that we did is we built a product around what I call a job function, the strength and conditioning job function. And in high school, the job function of a strength quotient does not differ that much from when in college. Your athletes are not as sophisticated, not as progressed, but you have seven days a week to train athletes to play a sport that relatively looks the same structurally right. In high school as it does in college. So building a SaaS company around a job function as opposed to a vertical, in my opinion are two different things. And we always believe that building to the job function that was going to allow us to unlock all the verticals. College, professional high school, international rugby, football in Europe, so on and so on, cricket in India. So when we built for the job function, I think that we were building towards volume. And in high school specifically? Well, one, there were macro tailwinds. More high schools today have strength coaches being paid to work than they did 10 years ago. We just simply rode a profession that grew in size. And then a lot of the high school strength coaches got their start in college. In the US Especially, college is where you go in order to train formally to be a strength coach. And that's where we were born. So there were all sorts of synergies that were there. But, you know, one interesting thing that you noted before we got started was that we don't necessarily charge colleges more or charge the professional teams more than we charge the high school teams. Well, the fact of the matter is, is that there are not that many pro teams out there. We could find a way, sure, to go charge more money in the professional ranks and the college ranks and work our way down. However, we were pragmatic with the fact that we're a bootstrap business, James. And I don't necessarily want to steward all these different products across all these different verticals for all the different people. We didn't really have the time and bandwidth to. So we committed to treating our big logo customers as people who were going to get a deal from team builder, still get value, get an impact, and then in return we could use their logos to use as social proof with the market that really matters, which is the high school market and the small college market.
A
Yeah, because I mean, we were talking about this that what you charge a high school is the same that you charge a customer, like the Tennessee Titans, an NFL team and VCs would probably be telling you you should be going up market, you should be charging them 10 times as much and all of this. But you didn't. That's right. And was it an intentional thing again that you said? You explained that right. One, it adds complexity when you go up market. Maybe a different type of product, but also maybe, maybe the logo was the most. One of the most valuable things to get out of that because it helped drive sales with your core market, which was high schools.
B
Yeah. The progression was. Number one, we had to be pragmatic, being a boo shop business. Number two, we understood that there is this dynamic of social proof with bigger coaches and logos giving us validation with the larger market. And then number three is, and I only learned this in retrospect, it was the absence of an investor and the inclusion of a customer as a stakeholder in the room that allowed for this. My business is me, my employees and my customers. That's it. When there's an investor in the room, they have a mandate. They have to return the fund to the partners. And it's their job. I get it. But that is very different than my job as an entrepreneur. I have a family. I've got to make a living for my family. That's different than returning a fund. Let's be honest. It's a household, it's not a fund. And what ended up happening was when we work with big colleges, big professional teams, and they see our price point and they. And they see the level of service that we give in exchange for that price point, it feels like there's integrity there. And I'm not using like integrity in the context of moral or ethics. Right. The coaches don't necessarily think it's nice that team builder is not charging the Tennessee Titans the most that they can get from the Tennessee Titans, but they feel like there's integrity because it's whole. And the fact that the strength coach problem that the Tennessee Titans need to solve is very similar to the strength coach problem that this high school needs to solve. Therefore, the solution looks pretty similar and the price point looks pretty similar. And that I think feels integritus. Again, not morally, ethically, but just in terms of being whole. And that has been really good for reputation. So that's, I think the last part of the progression is that team builder now reputationally is important in the space because it's been proven to solely solve this one profession's problems and it will only do so in an economically viable way, not just a. Not a way that also is economically viable and creates a positive return for an investment vehicle.
A
So let's talk about AI. What I think is interesting about your story is that you have a competitor, Vault, who from what I understand, is building this whole brand around this idea of AI generated workouts and this sort of stuff. And they seem to be basically building a product which is saying you don't need a human coach, whereas you with team builder are betting on the human coach as the solution. So just tell me a little about how you think about that and what's happening in this space.
B
Well, first things first, know your place. Google and the like need to have been building AI a long time ago. Understanding it, building it incorrectly. It's always important for them to do that with any new novel technology that potentially has large impact and own the infrastructure around it. I run a small ass company. My job as the CEO, as a steward of this business is not to go out there and just start building on top of novel technologies to be first to market. It just doesn't work that way in small niche markets. My job is to listen. So right now I'm very keen on listening and watching. If Volt wants to build AI, I think that's great. If the coaches want AI, I think that's great. And eventually I'll be faced with the decision to build something with AI. But I am only building with conviction at my company. I cannot build AI for the sake of building it. I just don't build anything for the sake of building it. So so far I love being really decisive with where I listen to, you know, things about AI. I think anyone listening to this podcast read Derek Thompson at the at the Atlantic. There are other good sources too, but. But start with Derek Thompson and take out a subscription and support the Atlantic. There's a lot of talk about it and it's a lot of noise. And if I spend a lot of time listening to all the noise, then I don't know how I would have turned out. I like watching my industry talking to my customers and I like listening to a few selective voices. And this is where I've arrived with it. It's been around for a little while now, a couple years, and the time has come for every company to take advantage of AI internally. I think that is, you know, getting close to being table stakes. So I'm very enthusiastic about my employees learning how AI can make them better at their jobs. And I don't just mean faster, I mean faster and better. Right. We still want to produce quality work. So Microsoft Copilot for the developers, we're not going to let them use AI to write code, but if they can write a little bit better code a little bit faster, we're very happy with that. And when it comes to my customers, again, I want to know what outcomes they're looking for. I'm not slapping an AI chatbot. And remember, AI is large language models. Right, Language models. If my coaches are looking to do some very, very critical thinking about tweaking training programs or modifying training programs technically, AI may or may not be able to do that right now, but what we can do is we can bring and synthesize large amounts of information to inform decision making processes. I'm really keen on building AI as something that really enhances the profession. I am not interested at all in understanding how AI can take away from the profession or replace it.
A
Right.
B
I've built this business for 13 years, is way more than a business at this point for me. I am like a lifelong supporter of the strength and conditioning industry in that job function, that profession. So I will do anything I can to support it with or without AI. And now it becomes a matter of principle as opposed to a matter of can I be Machiavellian with the leverage that AI provides me as a SaaS owner? I just won't go there. I've been building the business for too long now.
A
Yeah, I think there's this temptation right now of people just adding something with AI, throwing a wrapper around an LLM and just saying, okay, we have some AI functionality here with a lot of great innovation happening as well. It's not just these things. But are your customers even asking for AI features today?
B
Nowhere near close to what I would consider a critical mass. Yeah. In fact, I think my customers expect me as a long standing vendor, a technology vendor in the space to provide the guidance on how AI is going to impact their profession. We've been around a long time now and we are a big stakeholder and a big voice in the room. So I think a lot of them are looking to us to understand how this fits in, which is an honor and a massively exciting opportunity. So I was even going as far as tweaking the homepage on our website. Yes, we have 45 employees, but I still tweak the homepage because I'm still a psychotic Bootstrap founder at the end of the day. And I look forward to kind of putting out a statement on AI on our page. And again, I'm sort of inspired by this idea of the Industrial Revolution and man working alongside machine, I just think that was such a great story. And Peter Thiel talks about how technological innovation has been largely flat at a macro scale since I think the 60s, 70s, and the industrial Revolution was pretty big prior to that, and what it did for creating jobs and professions was just unbelievable. And this is my little corner of the economy, strength and conditioning, and I just can't wait to see what we can come up with to make the profession unrecognizable to someone who worked in IT 30 years ago because of AI.
A
That's awesome. If this episode got you thinking about building your own product or scaling what you've already started, check out Gearhart. They're not just a dev shop, they're a full product development studio that handles everything from strategy and design to engineering and launch. They've done it over 70 times for B2B SaaS, products and AI agents. And as serial entrepreneurs themselves, they know what works and what's a waste of your time and money. Head over to Gearhart IO and grab 20 hours of redevelopment before their slots fill up. That's Gearhart IO. SaaS companies move fast. Most teams are focused on building and optimizing, not thinking about vulnerabilities, ransomware or zero day attacks. But they can strike without warning and put your entire business at risk. With the Threat Locker Zero Trust platform, you can get ahead of these attacks and stop them before they start instead of allowing everything and trying to spot the bad. ThreatLocker blocks everything unless you approve it, giving your IT team full visibility across your environment. The result is stronger security control and your business keeps moving without interruption. Visit threatlocker.com that's threatlocker.com you've built the product, you've got a few customers, but 10k in MRR still feels miles away and you're not sure what to do next. That's the hardest part of the early stage. Not building, figuring out what actually moves the needle. SaaS club launch gives you a clear plan, weekly coaching, and direct access to me. So you're not guessing anymore. Apply at SasClub IE launch. That's SasClub IO launch. Okay, we should. We should wrap up. Let's get on to the lightning round. I've got seven quickfire questions for you, so you ready?
B
Great.
A
What's a piece of business advice that you commonly hear given to founders that you disagree with?
B
Start with the end in mind in regarding an exit. Now I'm biased because I didn't there's something really fulfilling about building a business because you love what you do and you love the customer, and that can be way more important than having an exit planned.
A
What book would you recommend to our audience and why?
B
I've always loved Do More Faster by Brad Feld and Cohen. I forget the other author, the tech stars guy. It's so short and it's such a classic and it was really impactful on me at 22 years old.
A
What's one skill you've gotten significantly better at since you started Team builder?
B
Probably listening. I'm an extrovert to the bone and a salesperson to the bone. Love sales. And only to find out that 10 years later good salesmen are the best listeners.
A
Right? What's a tool or habit that helps you stay productive?
B
Breathing and grounding. I work with an executive coach who works on specifically energy hygiene. Whether you know it or not, you emit energy. It can be good, it can be bad, and neutral energy is not always good. They can bring someone down who's riding high. So being conscious of my energy, breathing and grounding does that and I use her specifically for it.
A
If you had the time and money, what's a new or crazy business idea you'd love to explore?
B
Oh, that is such a good question. I am obsessed with golf, and I've always envisioned a second chapter in the golf industry. I think golf is so good as a sport, but the industry has largely looked the same for so long that I just think it's ripe for some new ways of thinking.
A
What's an interesting or fun fact that most people don't know about you?
B
Well, some people do know this about me, but I am obsessed with cacti. I have probably two dozen real and fake in my room right now. I even have one tattooed onto my body. It's just every time I see one, it makes me happy and that's all I need.
A
And finally, what's one of your most important passions outside of your work and cacti?
B
Well, I have three children. Raising a family is hard. It's not a passive passion or an easy one, but it's very fulfilling. So it's a cliche answer, but I'm giving the answer without the rose colored glasses. It's very, very hard and very fulfilling and it's my passion.
A
Love it. Well, Hugh, thanks so much for joining me. It's been a pleasure. If folks want to check out Team Builder, they can go to teambuilder.com without the E on the end. So it's teambuildr.com and if folks want to get in touch with you. What's the best way for them to do that?
B
Well, fortunately or unfortunately, I'm very active on LinkedIn, so that might be the best place.
A
We will include a link to your LinkedIn profile in the show notes. Great. Thank you so much. Congratulations on everything that you've done so far and I wish you and the team the best of success.
B
Thank you so much. Thanks for having me on.
A
It's my pleasure. Cheers.
Episode Title: Vertical SaaS: $0 to $10M ARR With Flat Pricing for Everyone
Podcast: The SaaS Podcast – AI, Growth & Product-Market Fit for SaaS Founders
Host: Omer Khan
Guest: Hewitt Tomlin, Co-Founder of TeamBuildr
Date: March 26, 2026
This episode features Hewitt Tomlin, co-founder of TeamBuildr, a SaaS company that serves strength and conditioning coaches. Bootstrapped from scratch, TeamBuildr reached $10M ARR with a 45-person team without any external funding. What makes their journey unique is their flat pricing model—they charge NFL teams the same as high school teams—and their strategic focus on supporting (not replacing) coaches in an AI-dominated industry.
Hewitt shares his founder story: from iterating on product-market fit, to fighting inertia in an Excel-dominated vertical, and making unconventional choices about pricing, go-to-market, and the integration of AI.
The episode reflects Hewitt’s humility, thoughtfulness, and commitment to customer-centered, principle-led entrepreneurship. His responses are candid, introspective, and packed with specific tactical lessons for other SaaS founders—especially those bootstrapping or building vertical SaaS.
This episode is a masterclass in patient, principled SaaS growth. Hewitt’s journey with TeamBuildr offers powerful lessons on finding product-market fit through deep listening, how to stake your growth on customer relationship-building, and why the “boring” verticals and flat pricing models can compound to unexpected success—especially if you stay true to the needs of your core users in a world fascinated by shiny new tech like AI.