Helm
Merchant operating system for small businesses
Visit Website
May 30, 2026
Building Helm as a merchant operating system for local businesses
I am building Helm because most local service businesses end up running on a messy stack: a website builder, a booking tool, spreadsheets, invoice software, review requests, and manual follow-up.
The goal is to make the day-to-day workflow feel connected. A merchant should be able to publish their site, take a booking, keep the customer record, send the invoice, ask for a review, and follow up from the same place.
The first version is focused on websites, bookings, CRM, invoices, reviews, and follow-up for service-led businesses. I am using this launch to test whether the positioning lands better as “merchant OS” or as a more direct alternative to website + booking + CRM stacks.
3 Comments
I like the connected-stack framing because the messy handoff usually shows up right after the invoice goes out and somebody still has to remember reminder 2. I started with Stripe nudges and a sheet for client work, now I'm building ChaseFlow for that chase layer specifically, tbh keeping the first promise concrete feels right here.
This feels like a real pain point.
The idea makes sense, but “merchant OS” is still a bit abstract. On first read, I had to read twice to connect it to local service businesses.
Curious if you’ve tested a more direct framing like “replace your booking + CRM + invoicing tools in one place”?
This is a strong wedge because the pain is not really “local businesses need another website builder.” It is that the whole customer journey is split across too many disconnected tools, so owners end up managing operations manually even after buying software.
I would probably keep testing “merchant OS,” but make the first promise more concrete: website, booking, CRM, invoices, reviews, and follow-up in one connected operating layer for service businesses. That makes the category feel bigger without becoming vague.
The naming is worth thinking about early too. Helm is clean, but it may pull toward navigation/control rather than local-business workflow ownership. If this becomes the operating system for service merchants, Xevoa .com would carry the product more naturally as a broader workflow/platform brand before customers, docs, and assets lock around the current name.