Arjun Vora

So when you're building software, you're building software from the lens of the blue collar workforce.

I'll give you one example.

We get paid bi-weekly or weekly, right?

The white collar workforce.

That's okay because for multiple reasons.

We have money in our banks.

You mostly know what you're going to be making at the end of the week or the end of the two week period.

You mostly have fixed salaries.

For a blue collar worker, it's extremely expensive and inconvenient to get paid weekly or bi-weekly, right?

They don't even know how much they're going to get paid at the end of the week.

Let aside, they live a lot of times paycheck to paycheck.

So it's expensive because they end up taking payday loans.

So when me and Tito looked at payroll, you're like, hey, we need to unlock instant pay for them.

If a janitor at the Levi's Stadium finishes their job, they should be able to clock out and cash out and put food on the table for their families.

So when you're building product, you've got to look at it from the lens of that real world blue collar worker.

When you're doing sales, selling into someone who's not very tech savvy is very different than selling into a CTO of a large multinational organization.

When you're doing customer support, you're supporting thousands of hourly workers in one organization, millions of hourly workers who are on the field in real time trying to get their job done, right?

So I think one of the key aspects, Noah, we looked at is the innate passion in every employee to solve for this real world.

We learned the hard way when we didn't realize when we were building TeamBridge how the mission critical aspect would significantly raise the bar for performance and reliability of the software.

One way to think about it is think about what if the Uber driver app went down?