Thanks — the gap issue was one of the first problems I wanted to solve with “smart” shift updates when someone cancels. Your comment made me realize I might be

Thanks — the gap issue was one of the first problems I wanted to solve with “smart” shift updates when someone cancels. Your comment made me realize I might be prioritizing the wrong MVP. If I pivot the product on shift coverage management instead, would that be more useful? Would you pay monthly for a tool that reliably finds coverage when someone cancels?