I've been working on disbug for past few months. You may say this is too long to work on a beta product without launching. But I am somehow convinced that releasing a better product helps getting more customers. I'm going for the Betalist launch this week.
I just finished working on my landing page. Eager to get some genuine feedbacks on Product positioning and messaging, Lifetime Deal CTA, Pricing page.
@vellip Thanks for the feedback. Glad you liked the tool..
Regarding rephrasing the headline,
Your point actually makes sense. I used passive voice intentionally to emphasise on the value rather than feature.. Maybe I think I should change it to
"Capture bugs with 10X clarity to fix them remarkably faster".
The value I see is in capturing bugs remarkably faster so I can get my job done faster, fixing them might be someone else's business. Of course, if you want to address big businesses, fixing them faster is important too. If its a freelance QA it's a different thing though.
Glad you brought this up. That really brings us to the core question. Who is your customer and who do you want to target ?
In my perspective, Disbug is gonna be B2B product targeting entire development teams.
According to me, the main USP of disbug is to be able to capture console logs and all technical logs of the QA's along with screencast with video and narration. One way it helps tester to report faster because of all the automatic integrations. **But the real value comes when the developer was able to fix the bugs without any chat or call with the QA requesting more details. **
Atleast that's what I believe how Disbug should be.
@vellip's posts and your last response hone in on what you should say up top. The goal with your tool is capturing. Fixing is an entirely separate issue and gets put in someone else's backlog, so while you may speed up the process of "eventually" fixing it by logging/detailing faster, you aren't making the "bug fix" process faster aside from maybe reducing rework.
Instead of "Fix bugs remarkably faster by adding 10x clarity to bug reports" I might say "Log bugs faster. With more detail. Reduce re-work." All three of those are targeting people who are saying things like "I need to speed up testing cycle time OR I need more clarity in my bug reports OR I don't want to have to circle back with questions on all my bug reports."
My other thoughts are around the (in my opinion) much overused 10x terminology. It's a buzzword that people use and when you're pitching your product that way, people might actually ask you how you're measuring that. I feel like saying "10x this or 10x that" is fine when you're blogging and talking about self improvement or productivity, but less so when you're marketing your product.
Hope this helped in some way,
Andy
Aswin, very impressive.
Is this 100% your baby? Or is it a project for a client?
Hey erezt, Yes, I am the founder of this product.
lovely + following you.
Congrats on launching your product!
Generally the landing page makes sense to me once I see the video but I agree with others that it could be revised.
Narration on the video might help and on mobile (iPhone X) there are several alignment issues. I’m guessing your product is desktop only?