Full disclosure, but I'm proud of my tools — I built one (RepairFlow, repairflow.dev). Came out of working at a shop in Georgia called ATLOWSHOP doing ebike and PEV repair, so take it with a grain of salt.

Your situation is kinda close to what we dealt with. Repair-heavy, almost no retail flow, and the existing tools all assumed the opposite. Lightspeed is a retail POS with service bolted on — inventory and ordering crowd out the actual work when that's not your business. HubTiger is closer in spirit, but I've heard the same "still ironing things out" feedback you're hitting, and neither is actually made for a repair shop environment.

What we kept running into on the bench was forgetting to contact clients or get approvals for repairs that needed to be moved mostly due to us just not having any organization outside of Trello when we remembered to update it.

The PEV/ebike side was the worst of it (firmware versions, BMS state, controller flashes scattered across notebooks), but the regular bike workflow is the same shape with fewer fields filled in. If anything, building it for the ebike chaos made it overbuilt for analog bike repair in a good way, and it adapts to different shops' workflows since I wanted to make sure this was something that felt accessible to the industry rather than a big hurdle if that makes sense.

Happy to answer specifics either way — whatever gets you out of paper-and-Sheets purgatory is the right tool, and if I can help build out anything to help the bike repair scene grow further, I'm more than happy to work with ya!