We’re building rostering for the way hospitality actually runs.

Kaslu Work is rostering and clock-in for Australian hospitality groups, built by a small team who think a pub, a café and a function venue shouldn’t be forced to run the same way.

Who we are

There are four of us. Vinny and Renes write the code, Hugo brings new venues on board, and Libby makes sure they hear about us.

Engineering

Vinny Nery IIPhilippines

Vinny Nery II

Founder, Lead Full Stack Software Engineer

Leads engineering at Kaslu Work and sets the direction for the product: what gets built, how it’s built, and what comes next.

Renes ReyesPhilippines

Renes Reyes

Co-founder, Full Stack Software Engineer

Builds the features that keep the platform and the staff app steady through a busy service, and tests every release before it reaches a venue.

Business

Hugo AndersonAustralia

Hugo Anderson

Business Development Specialist

Finds the hospitality groups Kaslu Work is built for, follows up with the ones who want to know more, and turns first conversations into venues that sign up.

Libby McMurrayAustralia

Libby McMurray

Marketing Specialist

Runs marketing at Kaslu Work: getting the word out to pubs, cafés and restaurants, and making sure what we say matches what the app does.

Where the name came from

My mum loves cashew nuts. English isn’t her first language, so “cashew” has always come out as “kaslu”.

“Pass me the kaslu.” “Did you buy kaslu?”

When we were trying to name what we were building, she asked for kaslu again, and it stuck. It was short, easy to say, and it didn’t sound like every other piece of workforce software.

Then I told the name to a venue manager, who thought for a second and said, “Ah, like a play on words. Casual. Kaslu.”

I hadn’t meant it that way, but it fits. Hospitality runs on casuals, and most of what makes rostering hard is keeping every section covered when the team’s availability changes every week.

So the name has two stories, and we kept both. The longer version is on the blog.

Vinny Nery II, founder

A handful of cashews on a yellow disc, with two speech bubbles: “Pass me the kaslu.” and “Casual. Kaslu.”

What we believe

Most rostering software treats every venue the same. But a pub with a gaming room and a 1am close, a café that opens at 6am, and a function venue that only trades on bookings are different businesses, even when one group owns all three.

So in Kaslu Work every venue is set up the way it actually runs: its own trading hours, sections, rounding, approval rules and clock-in boundary. Staff clock in from their phone, and each clock-in is checked against that boundary. Head office sees every venue in one place. We’re also building the parts that meet teams where they already are, starting with rosters posted to the staff WhatsApp group and timesheets sent to Xero, MYOB and Employment Hero / KeyPay.

We write a build log most weeks about what we’ve shipped, including what didn’t go to plan.

Head office above three venues, each with its own trading hours, sections and clock-in boundary: a pub, a café and a function venue.

Where we are

Kaslu Work has a waitlist. We’re setting up the first pub group with the team, so we can set it up properly and learn from it.

If you run venues and want to talk, email vinny@kasluwork.com.au. It comes straight to me.

Get Kaslu Work for your venue.

Tell us about your venues and the software you use, and we’ll let you know when there’s room for your team.

We only use your details to tell you about Kaslu Work. Privacy policy