
SaaS Backwards · 2026-04-24 · 25 min
Key moments - from our scoring
Substance score
59 / 100
Five dimensions, 20 points each
Dylan Ochner, founding partner of Oak Group and creator of Siterise, explores how professional services businesses can spawn SaaS products by solving recurring client problems. Oak Group works in retail construction, and their experience managing store rollouts for Apple, Tesla, and Enjoy revealed a market need: retail companies lack centralized document management, consistent nomenclature, and cross-functional reporting for site selection and construction projects. Siterise addresses this by combining document storage, a unified location database, and project-level reporting - turning what was once a cost center into a strategic, data-driven function. Dylan discusses bootstrapping Siterise through services revenue to maintain product-market fit without venture pressure, the symbiosis between consulting and SaaS (services validate product-market fit; the app accelerates client growth), and go-to-market tactics including conference visibility, LinkedIn monitoring for executive moves, and a creative headshot-giveaway campaign that drives platform signups and engagement tracking. Essential listening for founders considering services-to-SaaS transitions and retail-focused operators seeking efficiency gains.
Siterise provides centralized document management, a single source of truth for location data (eliminating naming inconsistencies across departments), and unified project reporting - replacing fragmented Google Sheets, email attachments, and siloed departmental reports with one organized platform accessible to real estate, design, construction, and executive teams.
After building internal database solutions at Apple, Tesla, and Enjoy that enabled rapid expansion, Dylan recognized the pattern: every retailer faced the same organizational chaos. When starting Oak Group's consulting business, he found six to seven retail clients all lacked cross-functional development reporting and naming consistency, confirming market demand for a packaged solution.
Bootstrapping enabled slower, deliberate growth focused on product-market fit and solid foundation-building without investor pressure for rapid scaling. It also prevented outside opinions from diluting the product and allowed Dylan to avoid the reporting and governance overhead that typically comes with venture capital.
Watch for broken nomenclature, inconsistent data sources, and siloed reporting across teams. When multiple independent reports feed into each other and departments can't speak the same language, that's a symptom the market is ready for a unified platform - not just a one-off solution.
Siterise enables planning and forecasting of store rollouts by allowing executives to map locations, allocate capital and personnel evenly across regions, and track milestone dates, enabling predictable capex and revenue forecasting for investor communications.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode offers some useful operational insights about the services-to-SaaS transition and retail construction workflows, but frequently circles back to high-level concepts without adding novel depth. Dylan's observation about nomenclature breaking first and the sandbox metaphor are valuable, but most claims are either restated or lack substantive elaboration. The discussion of changing from founder-led to hired sales, and the conference ROI challenge, are sensible but not particularly original or densely packed with non-obvious ideas.
when you have reports feeding off of different reports, you start to be very complicated
if you start to stress one more on new store openings or new clinic openings or new, you know, new location openings, that sales is going to drop
The core thesis - that services can validate and fund SaaS - is well-trodden territory. Dylan's specific journey is credible but the frameworks (slow growth, bootstrapping for product-market fit, finding internal pain points) are standard SaaS playbook moves. The headshot booth tactic is a clever execution detail but doesn't constitute fresh thinking. There is little contrarian or first-principles reasoning; mostly sound conventional wisdom.
let's go slow and grow
the biggest key. Anyone in sales is going to tell you the same thing. How to find that person is really the discovery
Dylan is a legitimate practitioner with meaningful hands-on experience at Apple, Tesla, and Enjoy in retail development, and is actively building both a services firm and SaaS product at material scale. He has direct domain expertise and is not a career podcast guest. However, Siterise appears to be early-stage and bootstrapped (not yet major exit or hypergrowth), which limits his seniority relative to later-stage operators. Still, he is substantively relevant and credible for this domain.
I spent most of my career working in construction development, from Apple to Tesla
When I left, we were in five countries with over two and a quarter million square feet
Dylan provides concrete examples (Apple, Tesla, Enjoy, west coast brand expansion to Southern California, Arizona and New Mexico) and describes specific workflows (PDF markup, CAD uploads, version control loops). However, he rarely quantifies traction: no ARR, customer count, pricing, churn, or detailed metrics are mentioned. The conference headshot ROI is described narratively but without hard numbers. This leaves the episode relying on operational specificity rather than business metrics.
When I first was at Apple in 2009, 2010 in the retail development team, I started using a product they had called Bento
When I left, we were in five countries with over two and a quarter million square feet
Ken asks solid foundational questions and does follow up on key tensions (symbiosis between services and SaaS, how to know when to productize, ROI of conferences). However, he rarely pushes back on claims or digs into uncomfortable tradeoffs. When Dylan says bootstrapping was better than VC, Ken doesn't probe the opportunity cost or growth ceiling constraints. The interview is competent but not sharp - it accepts Dylan's narrative largely at face value and doesn't create productive friction.
And I'm wondering what's the symbiosis there though?
how will founders know when a repeated internal solution is actually an opportunity for a software product?
Computed from the transcript - who did the talking, and the words that came up most.
Send us Fan Mail Guest: Dillon Okner, Founding Partner of The Oak Group / SiteRise - In this episode, we look at how a services business can become the proving ground for a SaaS opportunity. Dillon Okner, founding partner of The Oak Group and creator of SiteRise , joins us to talk about building software from the inside of a professional services business. SiteRise was born from repeated problems Dillon saw while helping retail brands manage construction, store openings, document control, reporting, and cross-functional planning. We dig into why Dillon chose to bootstrap the SaaS product through services revenue instead of raising venture capital, how his team identified product-market fit, and why messy spreadsheets, inconsistent file naming, and disconnected reports are often signs that a market is ready for software. Dillon also shares what is working in SiteRise’s go-to-market motion, including outbound, conferences, relationship-based selling, LinkedIn Sales Navigator, and a creative “headshot-led growth” tactic that turned trade show engagement into product interaction.
Transcribed and scored by The B2B Podcast Index.
Speaker A: Welcome to the SaaS Backwards podcast, where we reverse engineer the success of fast growing SaaS firms and explore strategies CMOs and CEOs are using to drive their businesses forward.
Speaker B: Uh, welcome to SaaS Backwards, a podcast that helps SaaS and AI CEOs and go to market leaders accelerate growth and enhance profitability. Our guest today is Dylan Ochner, founding partner of the Oak Group, a professional services firm in the retail construction space. And they've also created a SaaS application for this industry called Siterise. Hey, Dylan, welcome to the podcast.
Speaker C: Hey, Ken, thanks for having me. I'm, um, excited to be here this morning.
Speaker B: Yeah, I'm excited. I think we're going to have a lot of great stuff for our listeners. Just before we dig into this episode, could you please tell us a little bit about yourself and your company? Yeah, absolutely.
Speaker C: So, uh, we started the OAT group back in 2022. Prior to that, I spent most of my career working in construction development, from Apple to Tesla and enjoy technology. Having the opportunity to build retail stores and spaces and warehouse alongside building process, focusing heavily on how to reproduce and make things more efficient, open your doors on time and really functioning under, uh, you know, a budgetary restrictions.
Speaker B: Yeah, I imagine that the retail industry very focused on meeting their deadline, meeting their budget, being able to start generating revenue as soon as possible from when they sign a lease.
Speaker C: We hear this frequently, the quicker you can roll the eight ball back and start planning is the quicker you can open your doors, the quicker the customer can walk in, the quicker you can make money. So a delayed project really has a lot of implications that we try to avoid and get the doors open as fast as possible.
Speaker B: Yeah, and such a competitive business, so, you know, getting, getting to revenue can't be any more important anywhere else.
Speaker C: Isn't that why they have Black Friday?
Speaker B: So when we did our prep session, you told me that you bootstrapped siterise and you funded it through your services business. And I want to know what that unlocked that venture capital wouldn't for you. You know, where did it make the journey easier or harder? And how should founders think about using services as a proving ground for an application versus a, uh, crutch for it?
Speaker C: It's definitely a pretty long internal debate. And the biggest part of the debate is growth and how fast you want to do it. Right. Taking on debt allows for faster growth, but also allows for a lot of reporting nightmares and a lot of opinions inside the platform. And so we took the step back and strategy of, hey, let's go slow and grow. And as it continues to work, we can continue to grow it as opposed to pouring gas on the fire right away and making sure we had something that was viable. And we really wanted to build a good foundation of a product to make sure it was a market fit and really ready to grow. So we went slow, we bootstrapped. We just brought on, in the process of bringing on our first account executive on, you know, fully trained sales individual to really help accelerate the business. I think the biggest determination for us was really making sure we had a product that has, uh, solid foundation and making sure that we've built this platform before several times, that we could actually use the product that was a market fit for companies and not have an influence of a PE firm wanting to run at a faster pace.
Speaker B: Yeah, I mean, obviously when you take investor money, it comes with a lot of responsibility. Right. And expectations. And you already had a solid, uh, professional services business. And I'm wondering what's the symbiosis there though? So like, does having your own application help on the professional services side or does having the app, you know, does the app benefit from, you know, a professional services kind of foundation? Is there some synergy?
Speaker C: There's absolutely. We wedge it back and forth both ways. Maybe not to say it that way, but oftentimes as our customers are starting to grow with us on the professional services and construction side, they have no retention or no data synchronization, no nomenclature and no structure to their file management. So we can then offer a platform that allows them to do that, that's customized to them, allowing the brand to have a single source of truth. From the day we start with them. We just brought a brand on, west, uh, coast based brand, have one location, it's planning to expand and our ability to give them a prototype is going to allow them to expand exponentially as they go from, you know, up north down to Southern California, Arizona and New Mexico. And having a place where their documents can be stored and transmitted back and forth is perfect for them. And so we run that both ways.
Speaker B: That makes uh, a lot of sense. And it's not the first time I've seen professional services, you know, give rise, if you will, to a, uh, software application. And I think for professional services listeners who have thought this might be a path, I mean there's some clear evidence here with Siterise, but also there's plenty of other evidence from small integrators to even global giants getting into the software business. So good for you. I think it's a great opportunity. I want to dial you back A little bit to kind of how this kind of came up for you. And you told me that you saw these kind of problems that Apple, Tesla and others I think enjoy. Also, before building Siterise, I want you to kind of zero in on what was the aha moment that made you say this has to be a product, not just a workaround. And how will founders know when a repeated internal solution is actually an opportunity for a software product?
Speaker C: Yeah, so it's kind of a two part answer, Ken. When I first was at Apple in 2009, 2010 in the retail development team, I started using a product they had called Bento, which was like their family sized version of FileMaker database structure. We quickly outgrew that, went to FileMaker, quickly outgrew that, and then a development team came in and built what Apple uses today as the retail tool. About the same time I left and went to Tesla with a director from Apple and he said, hey, we, we need that database thing. We're about to start building all these stores, we want to catalog them. And right about then it was synchronous that I was like, hey, we have the ability to build a tool that's going to give a company like Tesla a foundation for the rest of their career and growth path and allow them to expand. When we repeated that same thing at Enjoy, I joined enjoy. They had two locations in 1600 square feet in Northern California. When I left, we were in five countries with over two and a quarter million square feet. And we were able to do so by producing drawings, relationships, and allowing for users both internal and externally to play in the same sandbox, which brought us speed. And so at that point in time we were like, this product has got to be able to help other retailers out there. And so as we started the professional services company, we found retailers that uh, needed help building, but also had no central source of truth, from reporting to document storage to everything we kind of offer today.
Speaker B: Yeah, M. This might be a good time for a little detour for you to describe the Siterise app and what it does for retail.
Speaker C: Yeah, absolutely. So siterise is the best in kind of three worlds document storage. So it's an organized way to control your construction documents and file management, bringing that DMS platform to life. Right. Document management, storage solutions out there. It's a source of truth. Where are my locations? You know, oftentimes we go in as a professional services team to companies and we ask their finance team for a list of locations and uh, I get a different list from their retail team and I get A different list from their new store opening team. And they're synchronous, but they all have a different nomenclature. And some people are talking about, you know, third Street Promenade and some people are talking about Santa Monica. And so although it may be the same source of truth, application starts to define those, those really critical points from the beginning. And then we were asking how you report on dates and opening. And every company I've ever worked at has a, you know, milestone report or a uh, development status report or a construction weekly report. And so our ability to take all that location based data along with planning and put a reporting level on top is what made Siterise really come to life for us. So kind of wrapping into a bow. Ken Siterise is an intelligent project management solution with a source of truth front end that allows it to be your kind of master database of retail or site selection as you grow.
Speaker B: Awesome. And now I want to bring you back to the question that I sort of segued out of. So uh, how were you certain that this was actually an opportunity worth investing in? Because it's, it's not not inexpensive to go build your own software?
Speaker C: No, not at all. You know, and I had the joy of been backed by Apple or by, by Apple and Tesla previously as those ventures continued and enjoy. And so now to bring it on my own, I was working consulting for a PE firm and working through a lot of different vendors and trades and companies realizing, wait a minute, we have six or seven retailers that we're building for as a consulting team, we need to start, you know, uh, organizing this data. And so we started to bring site rest to light when we found that they had no cross functional development reporting and name. And I was like, we have an application that's done this before, let's bring it to light. And then as it started to fit and started to sell it, we started to see market fit for it pretty quickly.
Speaker B: Awesome. So it's a matter of just sort of being present in the business and in this case you had built something already for others or part of a team that had built something for itself.
Speaker C: So uh. Correct.
Speaker B: Yeah, exactly. Kind of moving on. I think that, you know, retail build outs probably often looked at as a cost center. Right. And not necessarily a strategic function. But how does that mindset limit growth? And how can better data flip the conversation into a boardroom level discussion?
Speaker C: We used to say the same thing like retail. And retail development is definitely the biggest cost center that most companies are going to see besides manufacturing. And so with the ability to give them Quality reporting and data on top of that to say, hey, you know, because if you think about this, if you have a data engineer or a data scientist and you're running a sales organization, a marketing organization and have a retail development team, you're going to put that person into sales quickly to help drive data. Well, where siterise can provide that value and bringing that data to light for you allows you to not be an additional cost center looking for a data engineering team or a tableau team or you know, a uh, BI team. We can actually bring that data to light and allow you to go into the boardroom and show value into your store, your timeline and how that capital expense is really going to get allocated properly from, you know, when are we going to recover the cost of this? When did this start? You know, going into the black. And so having the data to, to analyze that from site really brings your education and conversational knowledge of uh, retail one step further.
Speaker B: Is there a CEO message in here in terms of predictability of store opening? If you're opening a lot of stores, obviously that has a capex component and then it has a revenue generation component. Does this get you into helping them do a better job forecasting and communicating to investing publics for private uh, and
Speaker C: public companies 100% on the planning side? So Sitterise allows you to plan the application and put your dots on the map as you get ready to plan and allocate person power, which is critical because if you're looking at your entire organization, you can't stress one region more than another. Right? Because if you start to stress one more on new store openings or new clinic openings or new, you know, new location openings, that sales is going to drop. You need to dedicate the time and experience across your entire portfolio. So siterise allows that person plan to happen so you can evenly distribute your capex, but also your manpower as well.
Speaker B: Hey, great. And I want to just take a break for our listeners for a short sponsorship message and we'll be right back with Dylan Ochner.
Speaker A: If you're building a SaaS company, here's some data that's certainly worth paying attention to. According to Kyle Poyar's research, across 6,500 software companies, only about 1 in 5 ever reach 5 million in ARR and just 1 in 10 make it to 10 million. Now those are some pretty sobering numbers. If you've got funding and a solid product, but you're still missing revenue targets, the culprit is almost always somewhere in your go to market. Now, uh, maybe you're Losing too many deals to no decision. And many times pricing hasn't changed and it's opened the door to competitors. And often sales and marketing are hitting their activity KPIs. But that's where the good news ends. Now, these are all solvable problems, but you have to know where to look. And that's exactly why we built the SAS Doctors Go to Market Checkup. It's a free diagnostic where we assess 12 critical components of your growth engine, from positioning and pricing to your sales, tech and metrics. We'll come back to you with a clear picture of what's holding you back and what to prioritize next. No 80 page decks that you'll never implement, Just a sharp, actionable read on, um, why you're stuck and what needs to change. So if your product should be growing faster than it is, check out the link in the show notes and let's talk. And now back to the podcast.
Speaker B: And welcome back, everybody, to SaaS backwards. I'm here with Dylan Ochner of the Oak Group and Siterise. Hey, Dylan, before the break, we were talking about CEO applications and the impact on the C suite, but I want to get a little down and dirty here in terms of the life of the people in real estate. And you told me that you're targeting retailers that are still in that kind of messy Google sheets to scale phase. I'm wondering why this is like an important trigger for you, uh, like an important moment. And what breaks if these folks don't modernize their systems?
Speaker C: Yeah, I mean, process breaks quickly, but so does timeline. And the two things that we preach pretty frequently are if the real estate broker goes out and tours a site and gets a lease, uh, outline, dimension from the landlord on the PDF, he or she marks it up, they email it over to an architect, Architect puts it into CAD format, they upload it to Google Drive or OneDrive or Box, and they send that link. We download it, it's redlined, we upload it. Then that whole version control and journey goes on and on as we continue to develop the drawings, 50, 60 different times, back and forth. Well, in Siterise, you can do all that in one shot. I can take a picture of the PDF directly on my phone, uploaded to my deliverable. I can redline it in the tool, I can tag my architect. They can then make their adjustments to their CAD drawing, put it on site right as a new version. And so you start to see the sandbox getting, uh, very full of everyone playing in the same tool, and the transparency really getting elevated. So, uh, from the day the real estate broker tours the site, the project management team can get insight into the tool and start developing budgets, initial cost estimates, and really, like I talked about in the beginning, rolling that eight ball forward and allowing the planning to happen while the lease is being developed. So on day one, when you open your doors or your lease is signed, you're ready to start building, you're not ready to start planning. We bring that way back in the journey.
Speaker B: I want to step out of the retail space just for a moment and ask you, can you offer any advice to other founders, like how can they know if a market is ready to move from this kind of duct tape and paperclip environment, if you will, you know, the sort of unsystematized space to something where a solution is provided? Is there a way for you to know that this could be a market
Speaker C: when you start looking at kind of duct tape and paper clipping everything together and linking sheets together and really having a non consistent source of data? The one thing we found that breaks first is nomenclature and the naming of files and certainty. And so I think, you know, we forced as much organization on teams as much as we can to allow them to not only see an optimized process, but to see tools that are successful. And in doing so, when we can all start speaking the same language, from, you know, real estate design, construction all the way through to new store opening and the C suite, we've been successful. When that starts to break is when people start to silo and make their own reports. And when you have reports feeding off of different reports, you start to be very complicated. And so I would say my best advice is really drive it simple, live with one stack and organize your files from a nomenclature and a consistency standpoint as much as possible.
Speaker B: Fair enough. So the symptoms are people managing their own data sets, their own reporting, and uh, as you had said, something really interesting in there that I just want to highlight, Making reports from other reports seems like there's an opportunity for things to get out of sync, maybe not mean the same things.
Speaker C: Without selling this here, one of the things we focused on last year was building one reporting table called our projects tab that allows every dependency or every kind of role in construction to slice and dice the same data. And so you can see a master data view of all the deliverables and dates, or you can cut down to what's important for you, Kenny. So for us, it's not a report on top of a report, it's just a different view of the same report.
Speaker B: Awesome. I want to talk go to market now because, uh, I think there's probably nowhere software people are more stressed than revenue generation now. Not only traditional revenue generation, but also what is the impact of AI on how they're going to go to market. But when we did our prep, you told me that, you know, it's pretty heavily based on outbound and relationships. You go to conferences, you're watching LinkedIn for when people move from one company to another doing a lot of direct outreach. And I'd like you to reveal, if you would, what's working for you and where. Do you think others might underestimate the value of some of these tactics?
Speaker C: You know, Ken, in the early days what worked really well was people who had been on our platforms, right? And um, hey, you worked on Wink at, Enjoy. You worked on TRT at Tesla. This is the same product but more advanced. And so finding the internal expert and champion is really the biggest key. Anyone in sales is going to tell you the same thing. How to find that person is really the discovery. We focus a lot now on pain points. Is a data organization like we talked about, is it reporting like we talked about, is it schedule management? And so the hardest part for us is finding the internal pain points in the company, showing them how we can strengthen that and bring to light something that's going to be a much easier process. Now the next thing that's natural in any SaaS application against you introduced to any company is change management. And I always tell people you can build a store on a Honda with a broken window and no H Vac and a donut on the tire, right? But I could put you in a Lexus that's going to drive. You're getting from A to B for sure. I don't need a Lamborghini. I don't want to pay out the nose for it, but I think so. It's definitely a happy medium to integrate process and allow for something to be streamlined. That's going to bring everyone to the same sandbox and play faster, which ultimately opens your doors faster.
Speaker B: So let's dig a little into things like conferences. Not every founder CEO is supportive of in person events, trade shows. Tell us a little bit about your experience there.
Speaker C: The hardest thing in platform to measure an ROI and anything we do in this business, the question is, you know, what's the ROI on this? Well, it's impossible to measure the ROI of a conference unless you can come out of there and say you booked 16 deals directly from here, which is very hard to do. I'd Say it's hard to do. I think the biggest benefit of conferences for us is really the visibility, the facetime with customers and getting their name out there. Someone who walks by and then gets an email from us a week, two weeks, three weeks later, oh, I saw that booth site rise. I remember getting my head shot there. Or you know, everyone's got their gimmicks at a trade show. We really want to interact with it. And it did something actually kind of unique this year. Uh, uh, I'll share this, this idea of giving away free headshots. Everyone loves a new headshot. We brought a photographer in, he gave away headshots. You walk into booths, very interactive and very bubbly. But to get your headshot, you signed up for site rice and then when you logged into siterise 24 hours later, when you got your headshots ready email, you were walked through the platform and then ultimately ended up at the download button. And so it's kind of a give and take. You get your headshot for sure. We, I think we gave away three or four headshots per individual, but you also got a tour of the platform and we can see how you interact in it, how long you've spent in the tool and start to measure engagement. And so for us, the biggest ROI out of a conference is the list of contacts we get out of it and the interaction we have with our current and future customers.
Speaker B: So I like that we've found something brand new here. Headshot LED growth. Forget plg, forget the enterprise sales motion. It's headshot LED growth. I love it. And, but I think you've touched on some important points. First of all, you can't expect one for $1 in, $out for everything you do in go to market. Right? That's just not realistic. And some things can't have a straight line to attribution. But I think any salesperson who's been around a while will tell you, if somebody knows my brand, it's a lot easier for me to penetrate that organization than if they don't. I think the other is, and it's amazing, here we are six years after the pandemic. I think that people are just beginning to realize how important face to face is and um, how much events can actually drive opportunity. And love the headshot and the booth thing. I've done things similar to that in the past, you know, getting people into your booth for something of value to them. But I also really love this idea of you got to download it through a login to our application that's a good one. So if you've listened this far, you probably feel pretty good about it as
Speaker C: a, uh, SaaS practice listener. If you get nothing out of it, there you go.
Speaker B: Is there any other stuff you're doing like this? Monitoring of job changes? How are you guys actually managing that? Is that done by your people or do you have some tools that are helping you with that?
Speaker C: Uh, LinkedIn Sales Navigator does a great job of doing it off the bat. It does monitor people of interest and lists that we compile and we have lists for different segments of retail or manufacturing or uh, quick service. And we're simply just looking for job changes or when people highlight a new career or position change, we go through that route as well. But LinkedIn Sales Navigator does a great job of doing that.
Speaker B: Last topic I want to talk about, we touched on it very briefly, but you were as an organization moving from founder led sales to hiring this account executive for site Raz. So what's changing for you operationally and culturally at this important moment in the company?
Speaker C: You know founder, uh, led sales are great, right? People love to hear the story, people love to understand the platform view my eyes. But technical sales is not something I'm trained in. So bringing in a technical salesperson is going to really help operationalize that and allow me to focus more on developing a business to grow from. Feedback from our customers, interacting with current customers, working on support anywhere, I can really help grow the business. I'm going to sit on as quick as I can, I'm still going to sell, I'm still going to be on as many sales calls as I can. I personally love it. The passion for our software I think bleeds out of me day in or day out. And so I think for someone to hear about it for me is great. But for someone to do discovery with a client and understand the pain points, the solutions, we're going to let someone who can technically do that better than me bring that to light for us.
Speaker B: Where do you see the biggest opportunity with the freed up time that you're going to have, which may or may not actually occur? Where do you want to um, next?
Speaker C: I would say a little bit of automation and I don't want to say AI deeply because that's a big trigger work for people, but I think automating some of the tools we use internally to support some of our customers, but also measuring the quality of our support back to our customers to make sure they're getting what they need, a lot of the future growth that we do. Ken is by request of customer. You know, we're a boutique firm and so if I can take your direct request and something you need and measure it against other clients and say, is this something you need? I have a product fit right off the bat. And so a lot of my time is going to really be diving in deeper with our customers, you know, engaging with their teams to make sure the tool is productive for them, how we can enhance it for them and really build it on a way that's going to allow them to be more successful with what they have that we've offered.
Speaker B: Hey, and that's a great place to land the episode and I think a great focus for you as you build a sales function dedicated to Siterise. If people want to reach out to you, learn more about the OAT Group or siterise. How can they do that?
Speaker C: Yeah, dylaniterise app or Dylan llc, either one. Love to hear about it.
Speaker B: That's awesome. Thanks so much for being here. Really appreciate your time on SaaS backwards.
Speaker C: Likewise, Ken. Thanks for having me.
Speaker B: Yeah, and if people want to reach me, I'm on LinkedIn ins. Ken Lempitt my demand generation advertising and strategy agency for SaaS companies is Austin Lawrence Group. We're@austinlawrence.com and if you haven't subscribed to the SaaS Backwards podcast, we'd love to see you do so. It's available almost everywhere. Podcasts are distributed and full video episodes are on YouTube. Hey Dylan, thanks again for being on SaaS Backwards.
Speaker C: Thanks, Ken.
Speaker A: Thanks for listening to the SAS Backwards podcast brought to you by Austin Lawrence Group. We're a growth marketing agency that helps SaaS back firms reduce churn, accelerate sales and generate demand. Learn more about us at www.austinlawrence.com. you can email kenlempittinlawrence.com about any SaaS marketing or customer retention subject. We hope you'll subscribe and thanks again for listening.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.