Hey, how's it going? This is Craig Cannon, and you're listening to Y Combinators Podcast. Today's episode is with Mathilde Collin. Mathilde is the co-founder and CEO of Front.
Front is a shared inbox for teams, and they're part of the YC Summer 2014 batch. You can check out Front at frontapp.com, and Mathilde is on Twitter at CollinMathilde. All right, here we go. I think the most pressing and important question is this first one from Tomas Granos about Lego.
He asks, what's your favorite Lego theme? Yeah, so my favorite Lego theme is something that a lot of people know. It's called Ideas. And so basically, you can submit.
If you have an idea of a new Lego set that should be built, then people can vote. And then if it gets enough of votes, then they build it. And so one of the sets that I just got is three birds. It seems boring, but they're actually super beautiful.
And they came from a random person submitting this idea. That's so cool. I was just reading an AMA the other day with a Lego master builder. Did you see that one on Reddit?
Yeah, yeah. You probably knew all that stuff. What kind of birds are they? So that will be really hard for me to not tell you in French.
Yeah, that's next level in my learning of English. So I know what a friend is just because I've been around YC. But for the average person who doesn't know what it is, how would you describe it? So I would describe it as a shared inbox.
So you can think about it as what Gmail or Outlook does, but we've added collaboration features and workflows so that it works better for teams. So we have a few different teams that are using the product from recruiting teams, support teams, accomplishment teams, client services teams, operations teams. And what they have in common is they have a lot of emails coming in. And inside their company, a lot of people inside the team that needs to handle these emails.
And they struggle managing that as a team because email was a major team. So that's what we do. And when did you add the personal email to it? Actually, pretty early on.
Really? Yeah. The thing is, it wasn't working that well. Meaning you weren't getting users?
Yeah. Meaning in order to have a product that people will use for their individual emails, you need to get to a level of feature parity with Gmail or Outlook that's pretty intense. And so even if you could do it four years ago, it's only about two years ago that we started having the features that would allow people to manage both shared inboxes and individual inboxes as well. So today we have, I think, 40% of our daily active users who are using Front both for shared inboxes and individual inboxes.
And we're releasing a brand new version of Front at the end of October that we've been working on for nine months. And the goal is to make sure that people can enjoy the individual inbox as much as they enjoy the shared inbox. Can you be more specific? Meaning, so today when you have a shared inbox, let's say support, ad, sales, ads, it's obvious that they require collaboration.
Otherwise, you wouldn't have a shared inbox. But for individual inbox, so messy.front.com, they also require collaboration. So I will collaborate with my assistant, with our sales team and specific deals, with our recruiting team and specific candidates, with our product team and product feedback. And so tomorrow with Front, you can also add your individual inbox, messy that Front app, and then assign messages, have internal conversations around these messages, integrate it with whatever tool you're using, so GitHub, Salesforce, Trello, Asana, et cetera.
So it becomes a full replacement for Gmail Outlook. Got you. Okay. How do you feel about Gmail, or rather Google, wrapping up Inbox?
I think it's zero surprising. So first of all, I wasn't a huge fan of Inbox. I think Inbox brought a few things that were great, like the group notifications, they had great snooze features. But I think that if you want people to change how they deal with email, the amount of innovation that you need to bring needs to be super high, because it's very disruptive to change.
So then the value proposition needs to be 10x better, and I didn't feel like Inbox was 10x better than Gmail. So I'm not surprised. And then when they rolled out their new Gmail version, and you could see that it was pretty similar, then I knew that that was coming. It kind of brought over the better stuff.
Yeah. And then also, if you are going to have two different products doing the same thing, then they should be super different, and they weren't super different. Did you find that when you started to integrate individual emails into Front, that people were asking for all these vestigial features of Gmail, that you're like, this is going to be ended at some point, but they still want it? Yeah.
So yes, they want a lot of features, but I think that's normal, and we should provide them. There are a few ones that are harder to implement, just because I can't be convinced that they're better for the world. So for example, sub-subfolders, and you can try to build that again, and maybe it's a good thing, or maybe it's not. Yeah.
Okay. How did you end up weighing that out? It was just if enough customers complained, or enough people gave you friction about signing up, you would build it? And the question, I saw that a lot of people asked on Twitter questions about how do you prioritize features.
So I can talk a little bit more about that. So there was one thing that's unique that we did, which we did in YC four years ago. We built a Trello roadmap, and we made it public. So we're like, here is everything we're thinking about building, and you can avoid the thing that you want, and you can see what we're working on, and you can see what has been shipped.
So that gave us a ton of insight on what people wanted. The second thing that we did was, so obviously we used Front to manage incoming inquiries, but any tool that you're using should be able to provide analytics on the kind of requests that your users have. So you should be able to see in the past month, for example, I don't know, 20% of incoming inquiries were about folders or better analytics or whatever. So then we can look at that.
And then arrives the moment where you have so many inputs, plus there's also what I personally believe we should build, and you need to make a decision. And I feel like the decision will be based on two things. One is, what's the intensity or how much complexity it is to build a certain teacher? And then is, what's the uptake?
What can we expect from it? Will it, I don't know, increase our market? Will it make our current users happier? Will they pay more?
And so you always need to balance these two things. And so for us, we just have a scale of one, two, three. So in terms of how good it will be for our users, one, two, three, like game changer or slightly better than it is to have, and then how complex is it to build? And so then you have nine different scores depending on these three things, and that's how we can prioritize what we build.
And we should always put that in perspective of what our vision is and making sure that we're not doing something that's against what we want to build, and then making sure that we remain focused, because I think that's one of the biggest things that you need to achieve when you're always being super focused. And of those features you've rolled out in the past four years, were there certain ones where you really noticed a giant uptick in usage or growth? So there is one that we released where it's really changed how Front was used. So it's specific to what we do, but basically the concept of Front is whenever you have a message that comes in, you can comment on it.
So you have an email, and you can have internal discussions about it. If you have a tweet, you can have internal discussions about it. And so before, you could comment on one specific message. So if you had three messages, you could decide to comment on message one, or message two, or message three.
The bad thing about that is it was really hard to have a conversation that was flowing, because you could comment on message one, and then someone commented on message three. So then an email came in. Yeah, exactly. But we wanted to let people have conversations that were fluid around.
So we decided to do two things. One is reverse the order of conversations. So now the most person is at the bottom and not at the top. And then that would allow us to have conversations, not associated to any message anymore, but that would just flow into the conversation.
And so that was a huge disruption, because when people use email like five hours a day, and they've got workflows around commenting on messages, and you're introducing that huge chance, they're pretty upset. But then what we saw is the number of comments that was made per daily active user, that was running that way, and then it grew that way. And so I feel like most of the decisions, practice decisions that we made that led to a significant change in behavior were the most painful. And another example is we're releasing a new version of Front in October.
I can't tell you how upset our customers are going to be. And I can't tell you how excited I am that we're rolling this out. But it's going to be super disruptive. So a bunch of people had questions about how you guys were getting customers in the early days.
So I think what would be helpful is, for context, what did Front look like when you guys launched? Because I'm sure it's different now. Yeah, I mean, so Front sucked when we launched it. I remember we were in YC, and our batch next would come to me and ask, can I use the product?
And I was like, no, you should use a competitor. Our product is really not. So it wasn't great. But you should launch it as soon as possible, because that's how you'll get feedback, and you want feedback in order to make sure that you're making something people want.
So the product was bad. Now, what I remember is building an MVP in the email space is tough, because people expect a lot of features. They will expect attachments to work. They will expect tags to work.
You should be able to CC people, CC people, forward emails, et cetera. So basically what we did was we had the most basic version of Front without attachments. But we would still try to see if some innovation that we had brought, where you could assign emails to people and have comments, would be enough for people to give up on a few of the features. And I remember that something that we did when Front was super early is I was writing a lot of content.
And so I think probably our first 300 customers were coming from content that I was writing on Medium and then sharing on Hacker News or guest posts or on our blog and writing about email, which I think was a thing that people like reading about or communication, collaboration, Slack, things. And then people would sign up to our beta, and then I would call them and manually onboard them and try to have them use the product. And then they would use the product for maybe a few hours and then stop using the product. But then I would know why.
Then I would talk to my co-founder and tell him, we're one feature away, like Aditrance, and then we're good. And we'd build it, and then I would take the customers, and they were like, no, that's missing. We're one feature away. And really, the only thing we did for the first year, at least, was just doing that.
It was writing content, onboarding users, and building features. And every other distraction that you could think of, we didn't do. Okay. So I was emailing with Wade from Zapier about their content marketing.
Kat and I are doing a class at Startup School this week. And one thing he said, which I thought was really interesting, was in the beginning, they found themselves getting trapped by writing content that would do well on Hacker News, but not actually convert to users for them. Were you able to differentiate that in the beginning, or were you just trying to get any kind of attention? So it might be true.
The truth is, first of all, I had no other idea. So yes, in an ideal world, I would find a lead gen source that's as effective as possible. I knew nothing about paid acquisition. Sharing back is not something people are looking for, so I felt like that wasn't working.
We had a horizontal product, and we weren't sure who was going to use it. So outbounding wasn't necessarily the best thing, because we have this general tool. And so for me, yes, the truth is, I would agree with them. I think from our beta, we had 3,000 companies that signed up to our product.
And I think, I don't know, 10 of them ended up using our product. So the conversion rate is not high. But anytime I was onboarding someone, a person who was not interested, I learned a ton. And so if I were to look at it again, I think I would do it again, just because that was my best guess to have a lot of people sign up.
And then I had a few tricks. Whenever you were signing up, you had an auto-reply that said, why are you interested? What problem are you trying to solve? So at scale, content is not at all how we get users today.
But in the early days, it's still the way we get users, but not the main source, which is the acquisition. Versus in the early days, it was the main source for us to get users. And I don't forget it. I don't think it was scalable, but I think it was doable and confronted us with the market.
What was the most successful piece? It's like an email well-lessed forever. Okay, so it's kind of like this opinionated. It was a lot of leadership and a lot of sharing my journey as a founder.
And how far did that get you? So you said out of 3,000 companies, you got 10 maybe. How did you get to fund it? So we hired our first marketing person in January 2017, so two and a half years after we launched the product.
So that's where it got us. So PR and content was 90% of what we did in the first two and a half years. Which is how many customers, roughly? So it got us to probably 1 million in AR, and so that was probably 1,000 customers, maybe?
Something like that. That's great. Wow. Less customers, yes.
500. You guys started making this in some kind of startup lab thing, right? Oh, yeah. Can you talk more about that?
Because we haven't had someone on the podcast that's been through one of those. Yeah. So when I graduated, I joined a startup. And then I knew that I wanted to start a company.
But I think for me, the main thing is I had to borrow money to good school. And then I had to give back the money. And so starting a company was pretty tough. So I took a job in a SaaS company, and I was doing sales because I figured that I could probably make a lot of money if I was doing my job right.
And so two things happened. One is I made some money, so that was good. And two is I learned more about SaaS and softwares, and I loved it. I really loved the idea of building a product that could then be used by some people, and then their life of work would be drastically different because of the product that we had built.
So at that point, I was working on a contract management software, and contracts were super archaic, and then they had this beautiful tool, and it was wonderful. But I wasn't using contracts. I was using email, and I was as frustrated with this tool that had not evolved in the best 10 years, which clearly wasn't made for businesses. So a year after I joined the company, I was lucky enough to meet with these.
So they're called eFounders. They're a startup studio. And what they do is they either find technical co-founders or business co-founders, and they try to have people meet. And then if a great relationship comes out of it, then they're happy to fund them.
And so that's where I met with my co-founder, Laurent. And so when I think about my journey at France, where I got most lucky was meeting with them and with them five years ago. And so I met him, and for two months... Wait, wait, wait.
How did you meet? Was it some kind of speed dating situation? No, it's like they host events. I eventually quit my job, and so I spent a lot of time in their startup studio helping on lots of different projects.
And Laurent was there, and it was the same thing. He had quit his job, was working on one specific project, met him, and then really liked him. And I think the thing that we tried to do for two months was asking ourselves all these tough questions that can happen in the journey of two founders. Like, what happens if I want to fire you, or you want to fire me, or you want to sell, and I don't want to sell, or whatever.
Should we have the same ownership in the company, and things like that? Like, would you move to San Francisco? And I think we agreed on everything. And so then after two months, we're like, okay, let's do it.
And it worked out so well. So it was super lucky. But so I think for us, a startup studio was great for two reasons. One, the fact that we met, and two, the fact that we got initial funding.
Now, a few months after we met, we decided to go to YC, where we got additional funding. And so then we weren't very close to them. So it was super great in the first few months, and then YC was great, and then other things were great. Everything's great.
At different stage of the company. Yeah. I'm sure things were painful, too. Yes.
Yeah, yeah, yeah. So did the idea come about before you even joined? So Front is at the intersection of two things. One is, I was willing to innovate in the email space.
And Lauren, my co-founder, had been in two companies before, where they had a lot of users. They were forced to implement help desk solutions, like Zendesk or Freshdesk, et cetera. Hated them. And so what he wanted to build was a lightweight support tool.
And so, in fact, Front started as this email tool, but with the go-to-market being shared in boxes. And the reason was because Lauren wanted to do that. I wanted to do that. We thought, okay, but email is impossible to start from scratch.
No company has managed to build a business starting with any more products because it's super hard to build. It's super hard to have people pay for it. So I was like, okay, what if the good market is shared in boxes, but then we expand, as we discussed, into a full email client that can be used by individuals and teams. And that's why Front is this combination of this very big vision, but this very simple pain point that we addressed at the beginning.
And just to go back really quickly, what happened in the hardest moments so far? Of Front? Yeah. I mean, so I can share one that's business-related and one that's more personal.
So 18 months ago, my co-founder was diagnosed with a cancer, so that was the hardest moment by far. And so then when I reflect on the journey, it's really hard to say, oh, this moment where, I don't know, we didn't get the term sheet we wanted, or this deep customer turn. It's really hard for me to tell that it was the hardest moment, because that's far harder than anything you can conceive, and now is great. And so all of it turned out in a super positive outcome.
But I think when that happened, it was my lowest. And then you start to realize that founders are always very committed to making their company work, and it's good, but they should also realize that their company is just a company, and you have a life outside of your company that's also super important, and you should enjoy every moment that you have, because things should be very different tomorrow. Yeah. And how do you maintain that balance?
You mean, you're a good friend of Legos, play soccer? So when I'm super deliberate myself, and then I try to implement a lot of things out front to promote this healthy work-life balance, and clearly it's been influenced by the fact that Laurent got sick. So I personally meditate every day. I log out of every app, Slack, Front, et cetera, every weekend, and any time I'm on PTO.
I don't have any notifications, so I'm never distracted by work. And then I exercise, like I play soccer, I run, I kitesurf, I bike. And I just make sure that when I stay late at the office, it's an exception. I sometimes do it, and when I work during the weekend, it's an exception as well.
So that's what I do personally, and I sleep at least eight hours a night every night. That was the biggest game changer for me, actually, in terms of feeling better. I know it's so dumb and obvious, but it's prioritizing that. Yeah, for sure.
I've always felt more proactive. And then, at Front, there are a few things. So last week, we had health and wellness week, and every day you could meditate so that you learn, explaining the impact of eating healthy on your emotions, and we organized a few runs. And so also, whenever people join, I explain what Front is about, and I explain that I care about it.
So that's in our culture as well. Yeah, and you're just kind of trying to lead by example. Yeah. In the same way.
And in the hard moment for your company, what was that? So the thing is, so every single moment is super hard. And so one of my biggest learnings from YC four years ago, when the company was super small, and every Tuesday we had people coming and talking about all kinds of things, and we had the founders of Stripe, of Facebook, of Facebook, of Dropbox, which are super successful companies, and they were telling us how hard it was, and how many times they've wondered whether the business would go anywhere. I mean, that's the story of my life, like, you know, it's super easy to think about France as, you know, this company that has, you look at our metrics, because they've published everything, we've consistently been doing well in terms of revenue, our retention of employees is high, you look at our funding stories, we've always raised money super easily.
Okay, cool. Like, that's what you can read about it. The truth is, every single day, I wake up, and there is a list of 10 questions where I don't have answers, and I need to figure them out, and I know that the more we grow, the more is at stake, and so I absolutely need to find the answers. And so every single day is hard, and we still have customers that turn, and I'm extremely sad about it.
We still have employee situations that aren't as easy to deal with. I still have, you know, moments where I'm wondering if we should do what we're doing, and that's true for every single founder I've ever met, as successful as they are, and so I think nobody should wonder whether it's hard or easy, like, it's just consistently hard. And do you need help reminding yourself of that, or were the dinners enough? No, so I read, you know, the hard things about hard things, and a lot of founders have read it, but for me, it was, like, really game-changer to just read about the fact that it's hard, you should stop wondering about it, just a given, it doesn't mean anything about the health of your company.
So I just need to remind myself that it's normal, and it's just a job. Yeah, excellent. You said something interesting about retention, and that's, like, something you guys are particularly good at and proud of, I'm sure. Do you have kind of pro tips in that category?
Yeah, so I'm preparing a talk about that, so I've been thinking about it. So here is, I think it's a super complex question, because if the answer was, let's do that, and you have a great retention of what it is. So yeah, but we have super high retention and super high NPS inside the company. So I think that there are three categories of things you can do within your company to make sure that that's happening.
The first one is, like, how do you hook people? And I think that's by having a mission-driven company. So at the end of the day, so I was asked to do a talk about retention, and so then I emailed our employees, and I was like, at the end of the day, why are you engaged, motivated, happy, why do you work hard, and a lot of them were saying, because we care about the mission. And so I think you need to make sure that you have a mission, it's clear, people can integrate it in the way they want.
Our mission statement is work happier, and it means different things for different people, but if people can relate to it and can feel like they have a purpose when where I come from, then it's good. So making it super clear, and as your company scale, just making sure that you say it over and over, and everyone knows what it means, everyone has examples of what it means, is super important. Then I think that there is the push, what will enable them to go above and beyond, and I think that for that, it's really the quality of coworkers. So one advice that Patrick Collison gave me when I was hiring our first employees was two things.
One, when you hire your first employees, you should think about every person that you bring with a bar that's as high as, could this person be my co-founder? And that was super helpful, because then you hire people that are really great at the beginning. And then the second advice he gave me was, when you hire someone, you should wonder whether you want 10% like this in your company, because the truth is, they will hire people like them, and so then if you don't want 10 people like this, then you should probably not hire this person. And so I think we did a really good job in the early days at hiring super talented people that were a really good match with our values, and so then as we grew the team, I think the team became really good, and good meaning they're talented, but also they are, we have some values, they are low-ego, high-standards, liberative caring.
Transparent, that's, I think, something that contributes to us having a really good culture. And I like to think about every single employee that we bring as someone bringing something new on top of all the baseline, the baseline being here. And then the third thing is, I think, so people want to see and understand that they have an impact, because if they care about the vision and the mission, and they have great co-workers, so they want to do their best, but they don't know how to contribute, then at the end of the day, they will probably not do as good of a job or be as happy. And so for that, I think there are a lot of things that you can implement within your company.
So one of them is transparency. So it's a word that's being used a lot, but it's super easy to claim that you're a transparent company. It's super hard to implement, and it gets us harder as you scale. So for us, being transparent means you have dashboards that show everything.
Every Monday morning, we go over all our metrics. Every quarter, I do a presentation. Last quarter, I review everything that has been going well, not going well. Every board meeting, I send a board deck.
Every inbox is accessible in front. So you want to see what customers want to say, like good things and bad things, you can access it. If you want to see why a candidate didn't accept an offer, you can know why. Whatever you want to do, if you want to know what's our runway, you can also know what's our runway.
And when you say every inbox is accessible, does that mean personal inboxes as well? No. So if you are a manager, you have access to your direct reports inboxes. And the truth is, we tried to make as many inboxes as possible public, but the truth is you have to implement some rules because there are HR emails that shouldn't be shared.
There are financial emails that shouldn't be shared. So we try to share as much of the personal emails, name, account, as possible, but not 100% are shared. So I think transparency is just a really good way to have people understand what the impact of their work is on all these metrics that are displayed. So these are a few tips.
Yeah. What else don't you share? So the way I think about transparency is if something is going to create more problems and raise more questions, then bad use of transparency. If something is going to answer a lot of questions and solve a lot of problems, then good use of transparency.
So what don't we share? We don't share the salaries of everyone. It's why. So I can give you an example.
There is a person at France that might have health issues and our insurance doesn't cover it. So we might pay this person an additional, I don't know, a few hundred dollars a month instead of paying for the insurance. And so then if everything was public and then people would be like, whoa, why did this person pay this much? And then I would have to explain.
And so that's, and I don't care. Like it doesn't bring anything great to the company. So the way I think about compensation is if anyone knew everything tomorrow, I could explain and it's fair. And that's what matters.
Now it doesn't mean that I will share it because it's actually not super helpful. And I mean, another example is, you know, when people leave or are let go, usually we don't share why. And we try to be super transparent about our performance process, making sure that people understand why someone might be let go and making sure that it's fair. Now, privacy of employees is more important than transparency.
And so then transparency doesn't mean that they will share, oh, this person wasn't good at doing this and that, and that's why we let this person go. Right. And so do you guys now have employees overseas as well? In an office in France?
Yeah. So we decided to have an office in Paris in January this year. And so now we have about 20% of RT in Paris and 80% here. Okay.
Everything we're super deliberate about is, so every employee in France starts with an onboarding in San Francisco. Twice a year, we have company-wide offsites and everyone is coming. We have all hands where we make sure that it's a balance between SF sharing insights and Paris sharing insights. My co-founder went back to France, so like having one founder in each team is super important.
We have a lot of people from SF who go to Paris so that they can also share more about the culture here. And so far, it's working really well. I mean, we're still improving other things, but... And he's there full-time now?
Yeah. Oh, okay. That's great. Yeah, that helps.
That's cool. Yeah, that helps a ton. You got a ton of questions on Twitter. Yeah.
So there was one that I wanted to bring up now. So KP asks, what is one unique insight about the problem, meaning the problem you're working on, you didn't have at the start, but only discovered later after launching? Yeah. So I think there are a few things.
One thing that I always find interesting is one of the reasons why I think we were successful building an email product, and I'm successful so far, is because we actually had... We didn't have a lot of insights. So I had been working for a year, and so it's not a lot. And so I think...
And my co-founder was very technical, so we didn't choose email like many, many hours every day or had not built any email product. And I think having a new pair of eyes on this problem that has existed forever, I think was something that was really good. So when people sometimes ask questions about the insights that you have and other people don't have, the fact that you don't have any insight, a new pair of eyes is actually super insightful. Now, the truth is, everything that we discovered about France is things that I didn't know before.
So for example, we have these use cases where logistics companies and travel companies love France. I knew nothing about these industries, and now I'm going to tracking conferences, and I understand exactly how they work. And so I think it's just, we've been super, super honest with ourselves on what we knew and what we didn't know, and then talking with our potential customers so much to understand their insights. And so the way I would answer this question is 99% of what I know today, I didn't know when I started.
I just felt like, for sure, something could be improved in that space. And I felt like we had a good team to do it. That's the only thing I knew. I mean, you were committed to the problem, right?
I was committed to the problem. But I cared more about, like, I want people to be more efficient at work, and I feel like email is the tool that people use to get work done. And so I care about that more than, you know, adding collaboration to email or assigning emails or commenting on emails. No, I care about people spend their lives in their inbox.
And this has not evolved in the past 10 years. And it was not made for businesses. So for sure, something can be improved. TV how?
Like, we knew that we would start with sharing inboxes. One funny story that I sometimes hear when I go to YC for the years is we try to have these insights. Like, we were looking for them. So, for example, PB, who created Gmail, was one of the partners at YC.
And so when I joined YC, I was super excited to meet with him. And I was like, so here are all our ideas. So we can go in this direction, this direction, this direction. What do you think we should do?
And it was like, follow your growth. And I was like, okay, cool. I'm glad I took to all my friends about the fact that I was the person who created Gmail. But at the end of the day, that's the best advice he could give us because he has some insights on what problem Gmail was trying to solve.
But that's very different from what front he's trying to solve, and that's a different time in history and a different set of wrongs. Yeah. I mean, he also, well, I mean, there are multiple ways to tackle this. But there's so much pattern matching that happens at YC that it's almost like you don't want to get too prescriptive with this stuff because you can negatively pattern match.
Yeah, yeah, yeah. And do the wrong thing. So there's another question. Jordan Jackson asks, email, at least for me, has taken on a different meaning in life in the context of messaging apps and chat platforms.
It's almost more serious in a way. How do you see email evolving and the ecosystem that encompasses it in people's lives? Yeah. So I think it's a good question because you hear so much from companies like, for example, email is dead.
So here's, like, the way I think about email is, first of all, for your personal email, so, like, you're emailing friends and families. I don't think that email will last forever. So if you look at the growth year over year, it's actually decreasing every year. Whereas if you look at work emails, it's increasing year over year.
So I believe that email will remain in a work environment. I'm not convinced about your personal life. And I think, like, WhatsApp and Facebook Messenger and all these other tools can actually be better or be used for more than they use. Now, in a work environment, I feel like email, the protocol, is actually perfect because it's the only protocol that you can use to communicate with people outside your company.
And so even if you have great tools like Slack that enable you to message people internally, the truth is it will not solve 90% of your communication, which is happening externally. And however, I think the interface for email is not perfect. So the protocol is great, interface is not great. And so if you have a tool that has a good interface and can be inspired by other apps that are doing amazing, like, Slack is great because they have a really delightful product that's really fast, that works across the platform.
And I think if you can apply some of the things that made these companies or these tools successful and apply them to a protocol that, in my opinion, is the best, then I strongly believe that people could spend 90% of their time in their inbox versus today, it's probably not as high as 90%. No. If you could, like, wipe everyone's memory of email context and, like, restart, what would you wipe out and, like, create anew? Like, if I was to start, like, a new email product?
If you could just, like, delete email from everyone's mind and just have, all right, this is a new email product. Yeah. So, you know, I think I would probably wipe out most of the structural features because when you think about, you know, the main things are you have a subject, you have a signature, you literally carbon copy and blank carbon copy. So I think I would remove all of that.
So I don't think you need a subject. I don't think you should see CBCC forward, reply, all these things. But I would keep the fact that it's universal and you can have a message that's being sent somewhere else. And then that's what I would do.
So it would be similar to SMS. Yeah, but then the tricky thing is SMS has zero concept of workflow. So you still need workflows. And so, for example, everything around the fact that you can assign messages, you can share a message and you can collaborate on a draft, you can comment internally, you can create automation and say if-then.
Like, that's super important, that doesn't exist in SMS. But today these features, CBCC forward, like are used as workflows, whereas really don't have a design for that, so then that leads to a lot of inefficiencies. Okay, so there were just a handful of other questions about product market fit. I think it's funny because based on the startup school lectures, I think like the questions are changing with every week and there were just a bunch on product market fit.
When did you guys feel like you hit it? Yeah, so it's a good question. Very late, actually. So when we raised our seed, we had just a few numbers.
I think we're doing like 10K MR. So not a lot. We might have, I don't know, a few, like 100 companies using the product. And clearly, I didn't feel great.
Like, you know, it was ultimately a good investment, but I didn't feel like we had product market fit. And I think when we raised our Series A, and so we raised our Series A, we were making, I think, 1.5 million in AR. So a little bit over 100K MR. I think that's when I felt like some companies were using the product.
And even if I had demoed all the alternatives, Front was actually a better solution for them. And then I felt like the market was big, but didn't really know how big, but at least big enough. And so that was in three years after we started. So pretty long time.
Yeah, it took a while. And so when founders, I mean, imagine like you've given talks and stuff, now people are asking you for advice. And when they're looking to find it, what do you tell them? Or what do you even point them to to read?
Like advice in product marketing or advice in general? Product marketing. So the thing is, at the end of the day, you need to be convinced that you're doing something that people want. And so I feel like you need to be, and it's a bit of advice that you're in general, you need to be so brutally honest with yourself and with your team about what's working and not working.
I think startups are so hard that there is almost like, as a human being, you want to be happy. And so you don't necessarily want to face every reality because it can be really hard. And so if you're working 12 hours a day and the thing that you keep hearing is, I'm not super interested in your park, whatever. And then at a point someone says, oh, it's pretty good.
Then you anchor so much on the fact that someone says it's pretty good. And then you tend to ignore the fact that, yeah, so 95% told you that it was not good. And so I think making sure that the only things you do is talking to people using the product, talking to people that might be interested in using the product, and then building things so that these two things can change. And then communicating that or sharing this information with your team and having one metric in place that will show you whether you're making progress on it.
So for us, it was revenue, because we felt like people were willing to use the product, they would pay for it. That's the only thing that matters. And that's the focus you need to have, both in your head you need to make sure that you're super honest, and also from just a process and communication standpoint, you should make sure that every single day you share how many more users revenue, whatever you have. Every single week you can calculate your growth and you can look at it, because I think it's basically said that.
The first way to have anything in free is to look at it and just be super honest about it. Yeah, I think that's your cross support. You're scared of the truth. I'm curious about all this in the context of your meditation practice.
What does that look like on a daily basis? And have you been doing this for a long time? So I've been meditating for every day for, I think, 500 days. So it's not forever, but now quite a long time.
So 500 days is when I got a realistic. So it was a more challenging period of my life where I think I was overwhelmed, but I think whether I was overwhelmed for that reason or other reasons, I think when you're a founder, in general, I'm pretty convinced that 99.9% of founders would benefit from meditating every day. So that was the trigger, but I wish I hadn't before. So the good thing about meditation is that as boring as it sounds, and I have an active mind, and so I'm not thinking about anything for 10 minutes, I do 10 minutes every morning.
So that's it. So again, your process is when you wake up and you just get in it? No, so I wake up, have a shower, because otherwise I fall asleep when I'm meditating. So I wake up, have a shower, and then meditate for 10 minutes.
Do you meditate? Do you have a pillow? Do you sit down on something? What do you do?
No, I have a couch in my living room, and I just sit there. Great. So I meditate. You meditate?
Yeah, I just sit, and I have an app, Headspace. Okay. So you do a guided meditation? Guided meditation, and then 10 minutes, and then put myself on it, and then live for a week.
How long did you have to do it before you felt that it was effective? So many weeks. I think it's nothing magical. It's really a muscle that you're training, and as anything, you will notice the results in probably a few weeks or a few months, not a few hours or a few days, but really the thing that I get out of it is now when an issue arises, it's like, okay, cool, the issue's here.
Before, it was, okay, so it's 90% of what's in my head. It's like taking all my attention. I'm super upset. Nothing can make me less upset just because I constantly think about it, and now I feel like there is a distance.
It's really Headspace is the name, and really what it gave me is more Headspace, and I can identify all the things that I need to do, and there are different elements, and it doesn't permit me from being upset, but then I feel like context switch more easily and be in another state of mind for another set of problems. Fascinating, right? It's awesome. I've gotten into it a little bit.
I've always found that exercise has been my go-to strategy, but I've done some meditation, and it's a little bit different. It's very different. I do both. You do both.
Yeah, it's very different. Yeah, there are only so many hobbies and habits that you can motivate yourself to keep up. Sure, but at the end of the day it's something that you can do. Of course.
And I feel like at least everyone should try it for a few weeks because I feel like it can be such a game-changer, but it's clearly a discipline that you need to have. It's really hard to have. Yeah, absolutely, but you just got to want it, and then you do it. This has been great.
Thank you for coming in. Of course. Thank you for having me. All right, thanks for listening.
So as always, you can find the transcript and video at blog.ycommodator.com, and if you have a second, it would be awesome to give us a rating and review wherever you find your podcast. See you next time.