Staffjoy is shutting down
blog.staffjoy.com
blog.staffjoy.com
It's even harder to be open and honest with yourself, your employees, your customers and everyone else when shutting down. Perhaps somewhat weird, but I find it refreshing to see posts like these. I think it's the sign of a good and healthy entrepreneur/team (albeit hard to write).
I'm sure you and your team learned a lot, and I love the gesture to open source your software.
Best of luck on the next step!
Our niche is really helping focusing the product enhancements and the marketing efforts. Scheduling needs are broad and we constantly have to refuse opportunities.
Good luck with your next venture!
If anything, the product surface area they were trying to tackle is really broad. Probably could have focused on a particular vertical and provided more value-adds.
I'm excited to see what gets open-sourced. Schedule visualizations are also hard. :-)
I do find that the exit, open-sourcing their platform, and not burning all the cash before exiting is very classy indeed.
[1] https://twitter.com/transitorykris/status/820009983601295360
[2] https://products.office.com/en-US/business/compare-office-36...
In hindsight, that was dumb, because we never got to anything near the scale where the scheduling would matter.
We didn't have a better way of acquiring customers, so efficiency never came into play. Conversely, if you have enough customers, operational efficiency doesn't matter that much.
Anyway, no profound insights here... just pointing out to people that if you have a great startup idea based on using a more elaborate scheduling algorithm than your competitors (an attractive trap for programmers, no doubt), then think again.
Any product that's premised on making a company's cost centers (e.g. HR scheduling) marginally more efficient is going to see very slow adoption just because it's not something execs will focus on -- they have so many other priorities that are higher on the list.
Also, SMBs almost never want to convert to pay cash for anything because they are usually so cash crunched.
Also, any attempt to make the cost centers more efficient (by introducing elaborate software and algorithms) will probably make them quite a bit less flexible, require higher skilled staff, etc.
Some of the investors have pledged to reinvest in this new project, that is completely new and separate from the old project.
Thats how it sounds to me, at least. Doesn't sound shady.
This /might/ be a nasty setting for lawsuits later, if newco turns into a unicorn.
Good luck on your next chapter!
It would be wildly unethical and probably also illegal to use investor money to 'compensate' the founders when shutting down the business.
I, too, found the post easy to read and straight-forward. If there was ever a great way to answer the hiring question of "Tell me about a time where you failed and what you did about it?" it would be this. Good luck in your next gig!
I'll also be publishing our YCF application and our pitch decks in the coming days.
The pre-V1 algorithms used the Julia JuMP package [1], which allows swapping of the backend solver easily. I don't think some of the functional tests would pass on the open source solver though (precutting and heuristics in gurobi caused a huge speed gain).
The later iteration of the algorithm used the Gurobi python library directly, which is closed source.
[1] https://blog.staffjoy.com/retro-on-the-julia-programming-lan...
I like to believe all open source code has value to someone, even if it's someone stumbling through working with said proprietary library, and trying to find something else that connects to it. ;)
I use WhenIWork for this area, which suits our needs. Not sure what would make me switch, probably not a text messaging. Most of my employees have smartphones, so a mobile app is fine.
Biggest problem for me (as a business owner) is managing schedules to a budget, and making sure we are being as efficient as possible with our staffing spend.
Most tools I've seen have a pretty weak budgeting feature. (You just put your budget in and it tells you how you did)
It strikes me as a very individualized problem; might be hard to generalize - or the markets you could generalize too aren't that big/don't need a solution all that much.
One of the issues that we encountered was that a generalized algorithm was tough. Different companies had different requirements for an algorithm, and it started to feel like a consulting company. For instance, if a big box retailer would rather be slightly underscheduled at peak time rather than adding additional employees (and being over-scheduled near the peak time). A high-end boutique retailer (like a diamond shop) might be the opposite - each sales brings in so much money that they overstaff at non-peak hours so that they can service customers during peak hours.
[1] http://pubsonline.informs.org/doi/abs/10.1287/inte.28.1.75
https://en.wikipedia.org/wiki/Nurse_scheduling_problem
Above is a nice example. There has been some nice contests with the above problem and the ILP solvers work extremely fast and great and solve them to optimality. Although Staffjoy constraints might have been more general.
Either way you could easily attack any custom problem with an ILP solver. It depends how long it would take to get a feasible solution and then how long to minimize the costs or fit the budget.
In order to speed up the solver you might use ML but that would require previous data. Probably the only way to speed up the solver is to learn it through reinforcement learning on a batch of data. Takes time and time and time. Not to mention that your ILP solver has to be equipped to merge with any ML machinery you are using.
Scheduling problem (the general one) maps easily to the vehicle routing problem. Vehicles are routed and service customers. On-demand requirements and scheduling are probably easier to conceptualize in that framework (think Uber but with ride-sharing bus sized cars, or team picking up and delivering food from restaurants to locations, or repairmen doing stuff at people homes).
All needs combinatorial search and machine learning is only one little piece of the puzzle.
ML includes optimization/search, dimensionality reduction (aka unsupervised learning), prediction (aka supervised learning), and reinforcement learning. And I'm probably forgetting a category.
IMO, ML is nowhere close to useful in these problems when most of the clients just use pen and paper. It should be fairly easy to beat that with some simple search heuristics.
In the old days, everything was a hard constraint. However, free trial users don't always put in problems that are solvable. I would get paged at 4AM about infeasible models, only to discover things like "this employee has zero availability but a minimum of 40 hours per week of work".
So, we turned into more of a "scoring" system where all minimums were soft constraints (e.g. minimum hours per week) whose violations caused a large point decrease [1]. Maximums were a hard constraint. The system made it impossible to input an infeasible model, and worked fairly well.
Splitting the scheduling problem into separate steps (forecast->unassigned shifts, then unassigned->assigned shifts) also sped up the algorithms (and allowed for people to create unassigned shift templates).
For a product company, sounds like a nightmare - no one's paying you by the hour to meet their unique requirements.
Thanks for sharing your story!
that's usually your first red flag. when management starts going after this market then things aren't looking good. low margins, sales dominated org if you're lucky can keep you afloat for a bit. long work days etc. avoid.
the real money is always in enterprise. liability is a huge issue. ain't no huge corp going to throw down millions on some random scheduling software run by a couple of dudes.
in the rare event that it does happened, raise as much money as possible and hire as quickly as possible. reduces risk and your work load.
they just didn't have the capital to compete. the market is there though clearly they just ran out of dough.
I wouldn't touch enterprise until you've hit some maturity with lower tier markets which are easier to sell to.
That was the moment we realized the reason our target industry was still using paper and spreadsheets. Because they're not just "good enough". In most cases, they're the best possible option. Maybe with enough iterating and testing we could've come up with a UX that could've put all that information in front of 4 people in one shot that quickly. But the odds are against it and even if we did it would've taken a long time to get there.
A lot of startup founders view "legacy" as a four letter word. But sometimes it's simply the best course. Not everything needs a high tech solution. And accepting that can be really tough sometimes.
I run a small nonprofit. I get emails at least weekly from some little tech company that has an app for some aspect of my operations. I usually ignore them, but when I do answer it's always some variation of "I can do everything I need for free with Google tools." And to myself I wonder why these companies are even targeting small organizations that have almost no money for technology.
Why? I might be totally wrong, but I guess those investors invested in you, more than your original idea.
Good for you for not burning the money in something you know eventually won't work, but why not try a different idea?
Man, I wish I had just a portion of that capital to at least validate my own startup.
So they're giving the money back, wiping out the corporate structure and starting fresh with one of the cofounders and what sounds like some but not all of the investors.
That's some nice common sense there!
Honestly, the hardest part of a startup is simply getting known and spreading the word that it exists.
It's really tough to "make stuff people want" AND willing to pay you every month for it.
I don't see what's the problem with prepaid phones. Do you mean feature phones?
During user studies, we saw that restaurants would still print out their schedules, and managers would take a photo and text it to employees.
This created problems when the workers treated this channel as two-way. For example, workers running late would text the manager, and the manager would not notice the message promptly while working.
So, the primary motivation isn't shutting down this startup. The primary motivation is moving on to the next startup which they believe is a bigger opportunity.
Not too awesome for current employees: hope they are getting taken care of.
Based on our user research, our primary markets (service and retail industries) freeze all of their software during the holidays. During the lull in January, they evaluate new purchases.
Launch is basically a one-time bump in inbounds that doesn't scale, so we timed it when we thought it would have greatest effect. However, we had been doing more scalable outbound - e.g. emails, canvassing neighborhoods with flyers, etc - for months.
Conversions to signups were remarkably low, and conversions from signups to paid were also low. We basically realized that we were not solving a core burning problem for these businesses. That's more what contributed to the shutdown.
I've had the luck of being on both development and marketing ends and high quality marketing can definitely sell a product that's slightly inferior to the competition 10:1
If you need big names attached to your product early the best way is to give it out for free to those first strategic customers. Why would anyone turn down something useful and free.
If you can't tell why another startup beat you out when you had a better product it's garaunteed to be marketing related.
In my experience spamming inboxes and flyers were a fool's errand compared to the marketing power of tageted online ads and customer referrals(offering free month for referring a new customer or similar). Non targeted "spamvertising" makes your company look cheap and desperate before people even try your product.
I expect to find a flyer illegally placed under my windshield wiper or jammed in my front door for a maintinence dude or a smoke shop, but not for any business software I would seriously consider using.
Do you have metrics on how many emails were actually delivered? Not how many the mail server reports, but which email services were actually forwarding your mail to places besides the spam folder? Where did you get your email lists? AFAIK, renting email lists is largely considered a joke in today's marketing circles.
Did you try offering a free trial period to start out? Target users at company domains over those @ Gmail or Hotmail? It's easy to code something that offers free trials only to people without a personal email address. How about sending mail directly to the target companies address to their hr manager? What about old fashioned cold calls? Sometimes they work better than you would think. Did you reach out to companies that expressed interest but didn't convert to paying users?
Did you try visiting local businesses in person to pitch your ideas and get feedback? Some business owners will be fairly helpful saying "yeah this sounds great but when I go to your site it doesn't look like we need this at all". Or "can I sign up my employees without assigning an email address to each one?" " I just want you to make the page printer friendly so I can post the schedule on the door like we've been doing for 20 years"
Was there A/B testing of all marketing materials including emails, flyers, page text, ad text, value proposition (free first month, 10% discount for year subscription, free use for less than 5 people)? Did you try getting individual franchisees to sign up then go to their main corporate office and talk about how much it's helping some of their restaurants?
Did you go to local chamber of commerce and small business leader meetups? Not start-up meetups, regular SMB meetups. This is generally how small business meet each other and is a perfect place for local vendors to get a foot in the door to the local B2B market. Even with the internet a ton of deals are made the old fashioned way between local partners. Dinner and a handshake is key to getting a lot of local businesses.
Why did it take until V2 to know you would need to use text messages? I used to work in the service industry for years and it's immediately obvious to me that smartphones cannot be a requirement. Did you think everyone working min wage as a greeter at Walmart when they're 60 would even know how to use a smartphone? This seems like a pretty glaring lack of market research.
I disagree that launch is a one time bump and that timing is of any importance. I find it rediculous that you ran advertising of any sort before the product was officially launched. Anyone checking out your site would do it the same day they saw the ad and discard you immediately if the product wasn't available. I can't think of a single start-up that would be materially affected by the time of year they decided to go live. Maybe if you're mowing lawns I guess?
It sounds like your market research amounted to asking people and googling things on the internet when this should have been done by getting hard numbers, aka trying to sell the product rather than predict something without data. I can tell you from working with numerous small business clients that low cost items (less than around 400 a month) are purchased at any time of year by lower level managers with little oversight. In the grand scheme of things the monetary investment is low enough that the companies are unlikely to care about budget whatsoever. We worked with small businesses of all kinds and this is common across any industries I've seen.
Not to completely trash you guys, but announcement says little about the actual cause of failure besides "yeah marketing didn't work good". It also mentions considering pivoting with different co-founders!! As if the other founders were part of the problem. That's a pretty scandalous thing to say about the other guys that poured blood and sweat into this with you for over a year.
That, combined with giving up with a mil in the bank and the, IMO, bad marketing blunders makes me think this shutdown is more an issue with co founders not getting along than anything else.
You could have easily scaled back operations to make that million last several years to give you some time to work out your conversion rates. Giving up when you've already built the project because you are having trouble selling it seems like a poor use of the rest of your investors money. Selling an existing product is far easier than building one that doesn't exist.