James: [00:00:00] Okay. So picture this, it's rush hour, thousands of commuters are depending on the bus system, right? And you're in charge of making sure everything runs smoothly, but all you've got is a mountain of paper schedules and a handful of two way radios. It sounds like a recipe for disaster, right? 

Katherine: Yeah, absolutely.

James: Well, that was the reality for a lot of public transit agencies, believe it or not, before this sophisticated software that we have today. You wanted the inside track on how these agencies are using tech to keep things moving specifically this whole debate around. SaaS versus custom built software. Think of this deep dive as your crash course, cutting through all the jargon to give you the need to know info on this complex topic.

Katherine: That's right. Yeah. 

James: And you specifically asked about SaaS software as a service. In the public transit world, we've got some great material lined up to unpack that for you. 

Katherine: Yeah, so it's a question we hear a lot, right? Is going with the SAW solution, is that the best route for these agencies? Or should they invest the time and money to [00:01:00] build their own custom software systems, you know, from the ground up?

There's no easy answer, especially with all this pressure on public transit to modernize. Aging infrastructure, you've got those ever increasing fuel costs and the constant demand for, you know, better, more efficient service. It all adds up to a pretty compelling need for tech solutions. 

James: Yeah, it seems like every other week we're hearing about another city struggling with these issues.

Katherine: Exactly. 

James: And that's where this whole SaaS thing comes in. It really is kind of like the easy button of the software world. You want to manage your bus routes, track ridership, or even handle passenger information. Yeah. All without needing a massive IT department, boom, there's probably a SaaS solution already out there waiting for you.

Quick to set up, relatively affordable to implement, understandably a tempting option for these agencies, right? 

Katherine: It really is. Yeah. And you know, what makes SaaS so appealing for public transit, especially for those smaller agencies, is that it really sidesteps those massive [00:02:00] upfront costs that you get with custom software development.

Okay. For organizations that are grappling with budget constraints, especially ones in smaller cities or rural areas, that can be a real game changer because it allows them to, you know, to dip their toes into the world of digital transformation without that kind of fear of completely, you know, derailing their budget.

Yeah. 

James: And then. That quick deployment. Right. That's huge for agencies who need to adapt on a dime to things like, you know, launching a new bus route or responding to sudden changes in demand, especially now with ridership patterns all over the place since we've come out of the pandemic. 

Katherine: Yeah, for sure. But you knew this was coming.

It's not all smooth sailing in the world of SAAS. It often comes with its own set of challenges. Think of it like this. You're trying to put together a complex piece of furniture, and the instruction manual is written in a language you don't understand. You might eventually get there, but it's [00:03:00] going to take a lot of time, effort, and maybe a little bit of luck.

A 

James: lot of 

Katherine: luck. And that's a pretty apt comparison for what a lot of public transit agencies are dealing with, right? It is, yeah. The reality is, you know, These agencies, they aren't built on this one size fits all model. They have unique needs, unique challenges, depending on, you know, everything from the city layout to the types of services they offer, even local regulations.

So trying to shoehorn their operations into a generic sauce solution 

James: Yeah. 

Katherine: Well, it can be a bit like trying to fit the A 

James: square peg in a round hole. 

Katherine: Exactly. Yeah. 

James: Right. It's like ordering a coffee at a new place. Sure, you can ask for a coffee and they'll give you something. 

Katherine: Yeah. 

James: Will it be exactly what you wanted, what you needed?

Probably not. 

Katherine: Yeah, exactly. And 

James: when we're talking about public transit, those specific needs can be critical. You know, a cookie cutter scheduling system. That might not cut it for a city with this sprawling network of interconnected bus and train lines. [00:04:00] Each with its own timetable, passenger flow. 

Katherine: Yeah, you've got that.

It's 

James: just, it's not going to work. 

Katherine: No, and imagine an agency that's trying to, like, you know, roll out a new fare payment app. Right. But their SaaS solution doesn't integrate with the city's existing smart card system. 

James: Right, right. 

Katherine: These are the sorts of issues that cause real headaches. 

James: In both the agencies and the passengers they serve.

Katherine: Exactly. And 

James: then, of course, there's the issue of data security. 

Katherine: Oh, huge. 

James: Which, in today's world, is mission critical. 

Katherine: Absolutely. We're 

James: talking about sensitive passenger information. 

Katherine: Yep. 

James: Everything from personal contact details to travel patterns. Remember that data breach a while back that crippled that city's entire transit system for days?

Katherine: I do. It was not pretty. 

James: That is a stark reminder of what's at stake here. And with saws. This data often lives on the vendor's servers. 

Katherine: Right. 

James: It's like handing over your house keys to someone you just met, you know? 

Katherine: Yeah. 

James: You're putting a lot of trust in their ability to keep everything safe and secure.

Katherine: It's a great [00:05:00] point, and you know, you're right to bring that up because that is a huge concern for a lot of agencies, especially with these, you know, these high profile cyber attacks on transit systems. Right. Becoming more frequent, it seems. Yeah. They need to know that their data is protected. Mm hmm. Mm hmm.

And that often means having more control over where it's stored and how it's managed. 

James: Exactly. Yeah, it's a major trade off to consider. Big 

Katherine: time. 

James: Now, with all that being said, we did find one company that's kind of challenging those one size fits all conventions of SAWs in the public transit sector. Oh, 

Katherine: interesting.

They're 

James: trying to find a different way to tackle these challenges. Have you ever heard of Passenger? 

Katherine: Passenger. Yeah, actually. So, 

James: passenger, it's a name we're hearing more and more in the industry these days. And what's really got our attention is how they're trying to bridge the gap between the convenience and affordability of SOS, right?

With the customization that public transit agencies, they really need. 

Katherine: Okay. I'm intrigued. 

James: So it's like they're this tailor who makes, you know, those [00:06:00] bespoke suits. They've got this secret weapon, this magic fabric that can adapt to any body type. So they've got this core platform that kind of addresses those common needs of most agencies.

Scheduling, route planning, real time information systems. That's the suit part. Right. But here's where it gets interesting. They've also built in a high degree of flexibility. That's the magic fabric. 

Katherine: I see. Yeah. 

James: Agencies can actually tweak and adjust certain aspects of the software to fit their unique circumstances.

So you've got this system that's both standardized and adaptable. Which, in the public transit world, is a pretty powerful combination. 

Katherine: Absolutely. It's like having your cake and eating it, too. Right? 

James: Ectrically, yeah. 

Katherine: And, you know, take the case of a, say, mid sized city that's decided, Okay, we're going to introduce a new light rail system alongside our existing bus network.

James: Right, which is a massive undertaking. 

Katherine: Huge. They need a system that can not only, you know, manage the logistics of both these modes of transport, but [00:07:00] also integrate their schedules, their ticketing, their passenger information seamlessly. Right. A traditional SAW solution might really struggle with that level of complexity while building a custom system from scratch.

I mean, that would be, you know. 

James: A hugely expensive gamble. 

Katherine: Exactly. 

James: So. Passenger is offering them that middle ground, a solution that's ready to go, yet adaptable enough to handle their unique needs and importantly, their growth. 

Katherine: That's a great point. And it's not just about, you know, accommodating different modes of transport either, right?

It's about catering to the specific passenger demographics in a city. Imagine an agency serving a large elderly population. They could use passenger's platform to create a customized interface for their mobile app. Larger fonts. Simplified navigation, you know, features that really address accessibility concerns.

Yeah. That's the kind of tailored experience that builds trust and loyalty among writers. Right. And, [00:08:00] again, you're not going to get that with a kind of generic one size fits all solution. No. 

James: Absolutely not. It's fascinating to see companies like Passenger kind of challenging the status quo. You know, finding ways to innovate and make software that works better for the people who actually use it.

Katherine: I agree. 

James: It's a good reminder that technology should be a tool for empowerment, not a constraint. A 

Katherine: hundred percent. 

James: But let's not forget about the other side of the coin, custom built software. It's the road less traveled. For sure. But for some agencies, it's the only way to get exactly what they need.

Katherine: Right. It's the ultimate expression of, if you want something done right, you gotta do it yourself. Right. And, in the case of public transit, where those needs can be so incredibly specific, Sometimes, building from the ground up is the only way to ensure that perfect fit. 

James: Right. But, it's also a decision with significant implications.

Katherine: Absolutely. 

James: We've talked about the advantages of custom built software, complete control, tailored solutions, the potential for innovation. [00:09:00] But going this route, it's like commissioning a world renowned architect to design your dream home. It is. It's going to require a significant investment. Of both time and resources.

Katherine: No question. And, you know, it's not just about those upfront costs of development either. Right. Agencies need to think about the long game. Yeah. The ongoing maintenance, updates, the potential need to scale the system as their city grows. Right. You need a robust IT team to manage all of that. 

James: And that kind of expertise, that doesn't come cheap.

Katherine: No, it doesn't. And you've also got to factor in the risk that comes with any large scale software project. Oh, 

James: for sure. 

Katherine: There's always the possibility of delays, cost overruns, even the project failing altogether. 

James: Mm hmm. Happens all the time. 

Katherine: It's a huge gamble. 

James: It is. 

Katherine: And for agencies already operating with tight budgets.

James: Right. 

Katherine: It's not a decision to be taken lightly. 

James: No. 

Katherine: So where does that leave us? With this mountain of pros and cons on both sides, 

James: What's up, fun? 

Katherine: How does a public transit agency, already [00:10:00] juggling a million priorities, Yeah. actually decide which path is right for them? 

James: Right. Is it even possible to make the Quote, unquote, right decision in such a complex landscape.

Katherine: Exactly. Yeah. There's no magic formula. But there are some key questions that agencies should be asking themselves, right? 

James: First and foremost, what can we realistically afford? 

Katherine: SOS 

James: solutions, with those lower upfront costs, might be the only viable option for some, especially those smaller agencies with limited budgets.

Katherine: Right. 

James: It's crucial to be realistic about those financial constraints. 

Katherine: Absolutely. Absolutely. 

James: But. Beyond the budget, they need to think long term. Where do we see our transit system going in the next 5, 10, even 20 years? Are we planning on expanding our services, integrating with other city systems, maybe even incorporating autonomous vehicles down the line?

Katherine: Right, right, right. 

James: These are the kinds of big picture questions that'll determine whether a SAS solution's limitations outweigh its convenience. Or if a custom [00:11:00] built system with its adaptability and potential for innovation is a worthwhile investment. 

Katherine: Exactly. And they shouldn't underestimate the importance of internal resources either.

You know, do they have a skilled IT team that's capable of not just, you know, handling that initial, you know, Build of a custom system. Mm-Hmm. . But also providing ongoing support and maintenance. Right? Or would they be better served by, you know, the relative ease and peace of mind that comes with this sauce provider handling all those kind of technical aspects for them.

Right. It's about honestly assessing their capabilities. Yeah. Yeah. And finally, circle back to what we talked about earlier. Data security. Right. Agencies need to carefully weigh the risks and benefits of, you know, where their data is stored, who has access to it, and how it's being protected. It's about finding a solution that aligns with their security needs and risk tolerance.

James: Right. Right. So, in the end, it really comes down to finding the right fit. Just like those riders searching for the right bus route to get them where they need to go. 

Katherine: Yeah. [00:12:00] That's a great way to put it. There's no single right answer, right? But by asking those tough questions, weighing the trade offs, and thinking strategically about their needs, their long term goals, agencies can make a decision that sets them up for success.

James: This deep dive has really taken us deep into the world of public transit, exploring this evolving role of technology in keeping our cities moving. 

Katherine: It has. 

James: Here's a final thought to ponder. This whole SAWS versus custom built software debate, it's bigger than just buses and trains. Yeah. 

Katherine: Much bigger. 

James: This is a dilemma playing out across industries from, you know, healthcare and education to finance.

So we're curious, where else are you seeing this debate playing out? What are your thoughts on finding that perfect software solution? Hop on over to our social media channels and share your insights. We'd love to keep this conversation rolling. 

Katherine: Yeah, absolutely. And you know, just as a final, final note, remember that the world of technology never stands still.

James: That's very [00:13:00] true. 

Katherine: So you've got artificial intelligence, autonomous vehicles, smart city initiatives. They're all continuing to evolve. 

James: Who 

Katherine: knows what kind of innovations await us down the line. 

James: Right. It's an exciting time to be following this. 

Katherine: It is. 

James: One thing's for sure, though. The future of public transit promises to be a fascinating journey.

Katherine: I can't wait to see what happens.