6 ms·

I love the concept and I will evaluate your tool soon! First comment, not on essence: the difference between your starter and pro plan is $5. If people have fe

I love the concept and I will evaluate your tool soon! First comment, not on essence: the difference between your starter and pro plan is $5. If people have fewer than 85k runs / month, you're asking them to commit to $500/mo spend to get longer retention. That's... fine, but you can probably charge more for that. For people with more than 85k runs / month, you're only charging them $5/mo for that retention - and making the pricing page more complicated. One option: Increase your base price from $40 to $45, and say longer retention is only available for customers paying >$500/mo. You'll get what you have today but simpler. Another option: Charge more for longer retention! $10/1k-runs makes sense, or even $15. If retention is the differentiation between the two plans, charge for it like it's worth being an upsell.

mikeshi42 4y ago
Thank you for the feedback! Definitely agree with you that we still need to iterate on our pricing to strike a good balance. Right now we're likely going to be exploring the latter soon to better differentiate where the business plan is (ex. additionally gating richer analytics is what comes to mind - as some analytics only make sense once you hit a certain scale and frequency of tests). Let us know when you get a chance to play around with it as well! Would love to hear what you think when you get in app.
- rsstack 4y ago
  I saw that your Recorder works with Playwright, but it seems that the main product is only for Cypress? Am I missing separate instructions for Playwright? Also, minor typo in HTML title: Cypresss -> Cypress (3 s')
  - mikeshi42 4y ago
    my spidey senses were tingling last night feeling like I had a typo somewhere... Maybe it's time for me to build that spell checker Cypress plugin I've been thinking about. Fixed, thank you! Our main product is indeed only for Cypress today, I'm assuming you're using Playwright today? If so I'm wondering if you've had a chance to try out their trace viewer feature as well (https://playwright.dev/docs/trace-viewer https://playwright.dev/docs/trace-viewer). We're itching to build on Playwright as well, but want to do it once we've built out a set of features that can provide a few times improvement over the existing trace viewer. So I'd be curious if you've used the trace viewer, and if you already see our product as having a few legs up on it :)
    - rsstack 4y ago
      I never tried the trace viewer and maybe I should. It seems more limited than what you offer, no?
      - mikeshi42 4y ago
        I would indeed say the trace viewer is more limited (I'm obviously biased) - especially when you compare the fact that we not only collect the telemetry but help integrate it into your workflow very easily (as opposed to setting up your own workflow via artifacts/S3 uploads in your CI pipeline) and the biggest being around aggregating these builds/statistics over time so that they're easily retrievable :) If you're open to it - I'd love to chat more on what your experience has been debugging Playwright tests and seeing how we could help there! I'm at mike [at] deploysentinel.com

mikeshi42 4y ago

Thank you for the feedback! Definitely agree with you that we still need to iterate on our pricing to strike a good balance. Right now we're likely going to be exploring the latter soon to better differentiate where the business plan is (ex. additionally gating richer analytics is what comes to mind - as some analytics only make sense once you hit a certain scale and frequency of tests). Let us know when you get a chance to play around with it as well! Would love to hear what you think when you get in app.

rsstack 4y ago
I saw that your Recorder works with Playwright, but it seems that the main product is only for Cypress? Am I missing separate instructions for Playwright? Also, minor typo in HTML title: Cypresss -> Cypress (3 s')
- mikeshi42 4y ago
  my spidey senses were tingling last night feeling like I had a typo somewhere... Maybe it's time for me to build that spell checker Cypress plugin I've been thinking about. Fixed, thank you! Our main product is indeed only for Cypress today, I'm assuming you're using Playwright today? If so I'm wondering if you've had a chance to try out their trace viewer feature as well (https://playwright.dev/docs/trace-viewer https://playwright.dev/docs/trace-viewer). We're itching to build on Playwright as well, but want to do it once we've built out a set of features that can provide a few times improvement over the existing trace viewer. So I'd be curious if you've used the trace viewer, and if you already see our product as having a few legs up on it :)
  - rsstack 4y ago
    I never tried the trace viewer and maybe I should. It seems more limited than what you offer, no?
    - mikeshi42 4y ago
      I would indeed say the trace viewer is more limited (I'm obviously biased) - especially when you compare the fact that we not only collect the telemetry but help integrate it into your workflow very easily (as opposed to setting up your own workflow via artifacts/S3 uploads in your CI pipeline) and the biggest being around aggregating these builds/statistics over time so that they're easily retrievable :) If you're open to it - I'd love to chat more on what your experience has been debugging Playwright tests and seeing how we could help there! I'm at mike [at] deploysentinel.com