Q: Hi there, I was close to miss this deal but am left with an issue I am not even sure if I should ask it or ...
expect a honest answer given you want/need to sell grow MAU. But I give it a try and hope you remain as honest as you have been in the other response provided.
While Session Record is less of interest for me, HTTP Rules is a lot more. I underdtad I get the LTD on the basic plan by buying three codes. My core reason to go/stick with you is your UI & the efforts you (obviously) put into UX overall - literally a role model.
Q1: I wonder why you won't at least offer unlimited header modifications forr >= Tier3
With no offense in mind:
You are one of many .Admitting: at least visually you got the most appealing solution while I am not skilled enough to compare how you or the others excel in features).
Take 'Tweak' or 'ModHeader' for instance. They offer unlimited everything for a fraction(ok, 'Tweak' would be only ~4.5 years fr the price of Tier3 while ModHeader is $60 Lifetime) .
Q2: Would you be willing to explain how HTTP Rules is different to Tweak and ModHeader?
I am seriously sorry to sort of derail this offer since its mainly about Session Playbook - which is nice to have but not in focus (for me) while Http Rules is & I simply got an issue with the feature/pricing for that (already at Tier 3 & not even talking about considering Tier 10 just for the Advanced Version of HTTP Rules).
Maybe, if you can make me wiser on how you are different, I am able to justif the price - even for Tier 10.
Q3: I assume you are funded to a certyin point / about to request funds. Since we all know how much investors hate LTD deals used to pimp MAU & desperately try to get rid of LTD users: Is there a "FallBack" plan allowing LTD users using the self hosted solution but getting granted for a special key/version that allows them to maintain the team functionality and other features that sets the hosted solution apart from the Open Source solution?
Again, no offense in any way (which is rare in my case since I am a nitpicker). Its all about that I dont understand /see the difference to the many other solutions, especially those mentioned & simply need a justification for my brain. Also, be aware: My focus is seriously on MOCK & Header Mods / Response Rewrites locally (since in 95% of the cases, I reverse engineer specifc online Solutions to write scripts that bend those solutions to my will/requirements. (Spoofing Locales, Location, HostName, ... as well as tweaking Network response to get/set more granualr settings on a specifc solutions where the pre-sets offered aren't good enough for me - simplified: "Personalize a webApp to my needs in a reproducable way)
Sachin_Jain
May 15, 2024A: Hi there, first of all thanks a lot for raising these questions, I genuinely value your willingness to share your thoughts.
I initially built Requestly for myself in year 2014 while I was at my first job, for solving a single use-case. I put it on Chrome website and then my team started using it. And eventually it captured the interest in whole company. My motivation has always been to help the developers.
I see Session Recording is of no interest to you, and that's absolutely fine.
Thanks for your input on our UI/UX. While I'm always out picking flaws even in this, it's always great to see people appreciating the efforts.
It's really difficult to provide unlimited header modifications for >= Tier3 as it will coincide with our original product pricing, which is honestly already working well. "Tweak", "ModHeader" are great extensions and I have used all of them in the past but Requestly is way more than these. Requestly is probably one of the most expensive extension in this category and it successfully delivers the value. Our users use Requestly for the easiest UX, getting all modifications (Mocking, Redirects, Headers) done via single extension, team collaboration and pre-made templates. We have individual users who have little-to-no experience in dev to largest of the enterprises with 200+ users.
I do believe in having minimal version of everything. If your use case gets solved by 'Tweak' or 'ModHeader' extension, then that'a definitely a good choice and Requestly might be an overkill here. As your use case grows and you need a better management of modifications, Requestly comes in.
Yes, we're funded. And I don't really think we'll ever have a motion to get rid of LTD users. But to answer your question, we'll always try to keep it up and if required provide keys that allow LTD users using the self hosted solution.
Hope it helps. In case I missed anything to answer, please feel free to let me know.