Staffjoy V2

Text message based employee scheduling app

Would you recommend this product?
No reviews yet
Staffjoy is back on Product Hunt to launch the V2 of our work schedules application. We stepped back last this year to look at why many businesses still run on pen and paper. We found that offline scheduling was a symptom of deeper communication issues. Staffjoy V2 is a ground-up rewrite that focuses on sharing work schedules in less time. We do this by sending text messages to workers that tell them their schedules and notify them of changes. We chose to focus on text messages after doing user studies with restaurants. We found that many workers lacked email addresses, and operated on prepaid phones. Managers would text them photos of the schedule because it was the best way to reach them. To simplify things, we chose to automate this process. Moving forward, we will focus on improving the core scheduling experience. We plan to use text messages to engage directly with employees and create flexibility. We also have started integrating scheduling with other business tools. To do that, we will announce our first integration partners later this month in order to further our goal of lessening the burden for business owners. Finally, today we're announcing a $1.2M round of funding led by Caffeinated Capital! More details are available on VentureBeat: If you have any questions, let us know!
Awesome work Staffjoy team! @philipithomas & @kootommy! This iteration is really powerful and reaches a segment of the population that doesn't always get to be connected to their work the way many individuals are. Great job! Do you guys ever see yourself building out more into the scheduling ecosystem? Time-Off Requests, Sick Leave, etc.?
In the V1 of our app, we started building tools like time-off request, sick leave, clock in/out, etc.. The application started to get bloated, and we didn't do a fantastic job on any single feature. Plus, maintaining rules and features for users in different industries or countries became quite hard. We realized that, when customers asked for that data, we should integrate rather than build. So - we are already finishing up our first partnership agreements. You will see time-off requests and other data - but we're going to pull it from popular HR management systems and seamlessly show it in the Staffjoy interface with your scheduling data!
Congrats on the new launch. How many companies did you speak to doing customer research for this v2? I understand that you went to meet a few
@_jacksmith I've lost count - dozens! We did on-site interviews at restaurants, brought people off of Craigslist into our office for testing, remote interviews,, phone calls, and more. What we found helpful was creating an internal blog (which we call Signal). There, we logged all of our user interviews, dropped in any recordings, and added key quotes and takeaways. New employees have started going through all of the old Signal posts, which does a great job of bringing them up to speed on our customer persona. I highly recommend that companies set up an internal blog for user testing!
Congrats to you and your new partners on launching v2 @philipithomas & @kootommy! The text message approach is simple yet makes so much sense. Well done guys.
Thanks - we basically started doing user testing, and we found that many employees didn't even have email addresses. So, the managers still had to use a paper schedule so that the workers could see it. We found that they would take a photo and text message it to each other. So, we decided to focus V2 on better communication!
Congrats @Philipithomas @kootommy and team! What's the most surprising thing you learned in v1 that you've incorporated into V2?
We were surprised by two main things: 1. When customers ask for a feature, we should integrate rather than build it. We built a lot of features for V1 based on customer requests (time off requests, clock in/out, etc), but realized that we were not concentrating on our core scheduling product. We should have listened to the customers' problems, not the solutions they proposed. So, we did a V2 to refocus on scheduling. Relevant tweet on this topic: 2. Text messages and and an API were the two most popular features of V1. We doubled down on those in V2. You can learn more about our architecture here - Our V2 API is fully available too: (As of now, you need to be logged in to access it)