incoming.chat

Learn how we spent our time in the past two weeks in this blog post https://link.medium.com/7P1O1QrGGW

Our day 2 was all about creating an (overwhelming) list of hypothesis. With that being done, we met our first customer. Read the new article to know how it went https://medium.com/@betaflag/building-a-startup-day-3-926d1cf920ed

Our first day was focused on listing our customer's needs and pains. The second one was about creating a list of hypothesis to be validated by them. You can read more about it this article https://medium.com/@betaflag/building-a-startup-day-2-3d469528d735

Our co-founder Nic shared an article on medium reflecting on his first day of work on incoming.chat, it's about customer discovery and making the right hypothesis. Check it out https://medium.com/@betaflag/building-a-startup-day-1-5ff734a8dd07

Incoming.chat is currently a pet project of two friends who spotted a need in customer support industry. Here's a bit more about them.

Sam created his own company in customer support a few years ago. He spent a lot of time listening to his customers needs and pains to help shape his service. He built a distributed team of agents, covering multiple timezones and languages, focusing on giving the highest quality. He strongly believes the best values of a brand is best communicated by humans and conversational marketing will shape the future of commerce.

Nic has 15 years experience in building SaaS. His first successful exit was an e-learning platform he developed at the age of 19. With a detour in AI and Machine Learning at Intel, his recent focus has been on e-commerce at Shopify. Nic is fascinated by the power of tribes (communities) as he also founded a nonprofit to help local tech and startup entrepreneurs. He received multiple prestigious awards from companies like NASA, Google and the MIT.

We believe that our two backgrounds combined together, make the perfect skill set to deliver a tool that will change the way brands will handle customer support through conversations.

It's often difficult to find the balance between developer experience vs cost of operation vs performance.

I doubt that any time spent on studying "which framework is the best" will really pay off later.

I find that spending time on defining the problem we are trying to solve and establishing what are the priorities really help and is a better use of our time.

Also, trying to stay away from shiny new technologies as most as possible. As we grow, we don't want to be the first to go through a minefield. There's plenty of great tools that support the actual giants who cleared them for us.

We got frustrated by the terrible experience of the current customer support chat applications, so we decided to create one of our own.