6 ms·
The worst thing possible is mixed messaging, so what I should do is draw a clear line between Mobile Jazz "the services company" and Bugfender "the product". So
by mindcrash 10y ago
The worst thing possible is mixed messaging, so what I should do is draw a clear line between Mobile Jazz "the services company" and Bugfender "the product". So each with their own marketing channels etc. However, to get traffic (potential customers) across I would think its a good idea to make some noise on the Mobile Jazz website (since it already is a strong brand) to get people across towards the Bugfender website to help build its own seperate brand. Also make sure that people can see that Bugfender is a product of Mobile Jazz (due to brand building), so I would make sure to include "Bugfender by Mobile Jazz" instead of just "Bugfender" in all my messaging. At least until it can stand on its own two feet.
My two cents. Hope it helps :)
- znq 10y agoThat certainly helps reassuring what we were already thinking. We're still doubting though whether we should go for option #2 or option #3. Because we still have a lot of great stuff that our developers produce (blog posts, experiments, open source) that could benefit a single brand targeted towards developers in general. It will be more difficult to share those "achievements" amongst multiple product brands.