I've been a victim of this too and it sucks. People will flat out copy your business, and while they're at it, they'll go and copy and paste your painstakingly-written documentation as well. This really leaves a bad taste in my mouth.
I always try to go with the OG when I find these types of instances, since they're likely the one actually innovating (I know nothing of FireHydrant, so this is just conjecture).
Apparently not just FireHydrant either. Someone posted on YC about 8 months ago Chris Evans from Incident.io calling them out for copying their Slack and Changelog formats literally word for word.
FireHydrant was my worst experience out of every incident manager I experimented with - literally nothing worked during our tests - and after two months of asking they're still refusing to remove our account; we still get a weekly email dashboard.
Tickets #1452, #1454, #1588. Was told "the account has been removed" on March 22nd, but I continue to receive "Last week on FireHydrant" emails specific to our org, most recently on May 29.
Sorry to hear that. I'll do my best to resist asking if you'd like to chat instead ;).
We try to take a very "partnership" centric approach. What that looks like day-to-day is our engineers/success/leadership team collaborating in a shared Slack Connect channel on new features. For a lot of our customers we get deep into the problem and bring in outside speakers from the industry to come do workshops, AMAs, etc. that might align well with the challenges.
I always try to go with the OG when I find these types of instances, since they're likely the one actually innovating (I know nothing of FireHydrant, so this is just conjecture).