Building a SaaS bug tracking tool for SaaS companies
Hello everyone, all through 2010s I worked at various small B2B SaaS product startups. There's one thing common at all these places - we used JIRA and do not want to give access to non engineers (sales & support) teams to JIRA - it being complex and expensive to add more seats. So we were using Slack channels to post run bugbash programs and one of the devs get to copy paste these into JIRA.
I thought there's some market here and partnered up with a friend to get bugbash.io built. It's almost MVP ready now and I'm looking to validate this idea.
I know this is very cluttered market. Do you think there's scope for another bug reporting and tracking tool? With integration to JIRA and a chrome addon to screenshot, annotate and attach to the issues during creation and a very startup friendly pricing ($10/mo), I'm hoping I will find some customers.
Any GTM strategies are appreciated.
Thank you!
J
First of all, I suggest you drop the "cheaper than JIRA" angle... why? Because there are many free or cheap project management/bug tracking tools.
But I do think there is a room for improvement in submitting bug reports. Usually people are either lazy or technically not capable to submit a proper bug report. So if you make it much easier, I think there is value there.
Agree, thanks - I removed the cheaper than JIRA angle on the landing page.
And as others suggested, added a screenshot to the header section. Will refine the screenshots as the launch gets closer.
I think this is a good idea.
Since you are at MVP/pilot stage, you may want to consider
Thanks for the feedback. Yes, native integration with Github is planned. Others I'm thinking will do with Zapier so it can connect with 1500+ apps. But agree, integrations is a GTM for this.
Screenshots and demo video should come in a week or two - once I also have the chrome extension is ready (WIP now). Will add these to the landing page.
I think you're wasting a valuable space with the headline "bugbash.io for every team.". It doesn't tell me anything about the product.
From your sub-headline "Slack, Spreadsheets and JIRA are not built to run company wide bug bashes.", my assumption is you're catering to a market that uses all of these 3 things.
It seems like your audience will be Jira users. I did some research and there are a 2 fb groups with 1k+ members on Jira, have you tried pitching this there?
Thanks for the feedback! I updated the header section and fixed the headline.
Didn't know about fb groups (I'm not on fb) - will check them.
Hey Jagan, how is it going with this product? I see the site is down, what went wrong?
Hey Jagan,
here's just some feedback after visiting your landing page...
Do you have some screenshots you can show? I was immediately looking for screenshots to figure out which workflows you support.
Don't list features, show your future users what pains you're solving with your software and how they'll benefit from it. You can use the features to help them back-up their buying decision later on. We humans make emotional buying decisions and are looking for ways to justify our decisions based on "logic".
Add some testimonials to your social proof section and put it above the CTA button.
Update the copy of your CTA button to something other than "Coming soon" (maybe "Join the beta" or something along those lines) and track how often people click on it. I for example read that and immediately thought that it's not ready yet so I better leave and check back later. You should also collect their E-Mail address when the click on the button.
Regarding your positioning I'd explore the possibility to be an anti-JIRA. Especially developers are not all raving JIRA fans. You could tailor your service towards that audience and start from there. JIRA is usually a Managers best friend because they get an immediate 10.000 foot view of the project. A lot of times it just gets into the developers way...
Thanks for taking time and giving these inputs.
I update the byline to reflect on the problem - to reflect a little towards anti Jira.
Updated the CTA copy to "Signup for beta" on the pricing columns. Takes to the top to enter email.
I will think a little more about positioning and pitching the problem statement.
The screenshots are a little crude, will be adding them this week. It's a good idea about having a social proof / testimonials. Noted.
Thanks again for the help :)
Sure thing. Keep us posted on your progress!