I work for a company that does automation for warehouses and distribution centers (think conveyors and robots). For years we have tracked our system testing and user acceptance testing using shared spreadsheets. I got tired of dealing with this so I built TestStack.
This is a good founder itch, but I’d be careful not to position TestStack too broadly as QA or bug tracking.
The sharpest pain in your post is not “teams need another test tool.”
It is that warehouse automation/UAT work gets messy fast when critical testing lives in shared spreadsheets.
That is a much more specific buyer moment, and probably easier to sell than a general QA platform.
Happy to put the tighter positioning angle in writing if useful. I think the risk is making TestStack sound broader, but less urgent, than the original pain that made you build it.