Why I built a standalone HTML menu builder for fine dining restaurants
I’ve been talking to a few friends in the hospitality industry and one thing that kept coming up was how annoying it is to update menus. They either have to pay a designer every time or use clunky software with monthly fees.I decided to build a standalone HTML tool where they can just edit the text live and export a clean PDF. No accounts, no cloud, just a file that works.I’m curious, for those in the industry or building for it – is 'subscription fatigue' as real as it seems, or do people actually prefer the cloud features?Happy to share the link if anyone wants to see how the live editor feels.
Trending on Indie Hackers
The positioning is sharp - you're not just removing friction, you're inverting the trust model. Restaurants keep the file, so they're not locked into a recurring relationship. That's a different conversation than just "we're cheaper". Have you considered adding an optional upgrade path for cloud backup or team access for larger operations? Keeps the core free while creating revenue for scale.
I think the more interesting question isn't whether restaurants dislike subscriptions.
It's whether they're actually trying to avoid recurring costs or recurring dependence. Those are very different problems, and solving the second creates a much stronger reason to choose your product.
Can you please share? Would you have to add whole menu once again you need to change a small thing?