What technical pain points do you see in seasonal businesses? (curious New England project)

QUESTIONS

Hey everyone. Very new to this subreddit. I hope this is okay to post here.

I’m part of a small team in New England where a huge part of the local economy runs on seasonal work like tourism, restaurants, shops, hospitality, you name it. I've actually spent some time working out in Yosemite for the summer which led to a lot of the hypotheses of what we are doing now.

We’ve noticed that a lot of seasonal businesses still run on spreadsheets, email threads, and sheer willpower. Training, scheduling, customer follow-up, and basic operations tend to be tricky when you are brand new to the tools you are using. That tends to create a lot of friction for seasonal workers, especially when you're coming in for a few months and have to “figure it out” on the fly.

So, we’re trying to build tools and systems that actually respect the seasonal model. We are trying to avoid enterprise software and instead focus on stuff that makes life easier for everyone who moves with the season.

If you're working in seasonal businesses (or have in the past), I’d love to ask: (These don't have to be in new England)

  • What are the most annoying or inefficient tech things you’ve had to deal with or wish were better in your seasonal tenure? (please don't call out any companies)
  • Who in your world gets it when it comes to making seasonal jobs work well? (A smart owner? A business you've worked for in the past? An ops person? Someone we should learn from?)

We’re not trying to sell anything in this thread. Just trying to make sure we’re solving real problems for real people. Totally open to DMs or comments here if you’re up for chatting more.

Appreciate your time and hope the season’s treating you well 🌞

Posted Jul 1, 2025, 4:27 PM UTC

11
Loading comments…