81–86 of 86 posts
Front is probably doing 7MM ARR (I highly doubt more than that)
...what is this estimate based on?
Earlier quoted context omitted.
If you had said you were replacing outlook, I'd be less surprised. You seem more email focused. Front's front page slogan is "The shared inbox for teams." I'm always puzzled when they attack modern email in their PR. They should just stick to "universal team inbox". When I see missive, I see "team email with chat." Well, we chat on Discord already, so that's not the pain point. Front's main appeal to me at least was…
> When I see missive, I see "team email with chat." Well, we chat on Discord already, so that's not the pain point. Pain point here is when you start to have those internal conversations spread across many silos. There is beauty and simplicity to manage all your conversations whether email, chat or mixed of both in a one convenient place. > PS. Your logo reminds me of men's underwear. Firs time I hear that one. :)
No, exactly. But you are always at risk of being just another channel. So you need to beat the rest. Or be above them. Or at least consolidate a few.
Front does a better job of marketing themselves as such (not the outlook argument, their inbox argument).
If you could pull in "channels" or have an open API for adding custom channels where users can participate in helping build your catalog, I think that would help.
The beauty of discord is with webhooks. Slack has "integrations" but they needed 1st party support. And I'd use Zapier to bridge the gaps. But most API sets have webhook support. And Discord allows for postings via webhooks. So I have a simple REST webhook processor page that takes incoming webhooks and posts to discord and everything else.
Not that webhooks are your answer, but just an example of a common chat app setup with a drastically better/easier feature set than their major competition.
> Firs time I hear that one. :)
It's the combination of white and the curves. Reminds me of boxer briefs every time. An easy fix would be to sharpen the rounded corners, but it's none of my business.
Either way, I have nothing but respect for you and your business. I wish you only the best ;)
Earlier quoted context omitted.
While they have a few similarities, I'm not sure I'd put Zendesk as Front's main rival. They're doing similar things, but approaching them in totally different ways. Front is fully backing the shared inbox, while Zendesk's main messaging is to get away from that concept and move more towards Ticketing for a larger support team. Good to see more competition in the space though. Disclaimer: I work at Zendesk
I agree and disagree. I need ticketing, but I'd prefer Front add it as an option to specific email accounts. sales@company.com - shared with sales team normal shared inbox support@company.com - "add ticket option" first.last@company.com - private email @company - twitter account A shared communication hub is a big win. If they could take over some of the internal chat as well - I'd gladly cut them a big fat check. Ou…
I did extensive searching for customer support email solutions. I landed at Front. But, I haven't pulled the trigger yet.
Zen was an easy pass for us, but we arrived at Front because of what they do better than Zen. Consolidation.
But the commonality is that these services always charge more than Todo apps or even chat apps. Even G Suite is cheaper. For some reason Google's team mailbox was a joke. They seem to have every feature of every startup somewhere, but have it suck.
I doubt these guys would be similar in pricing unless they were competing for the same market.
Same with buffer.com. They are a bit pricey too, but they can target businesses that save money with their service. Pockets open immediately when that is part of your value proposition -- cost savings.
Earlier quoted context omitted.
Curious to know the "@company - twitter account" importance compare to the other one you have listed?
Thanks, make sense. At Missive, we have yet to integrate with Twitter/Facebook... but as you mentioned even if it's less important, it's still a big sale argument for a platform like ours.
As mostly a b2e we have SLAs and reporting requirements to a lot of our customers and automating that, but still capturing/transferring disparate information is just a royal pain.