In this episode I talk with Raphael Masson, CTO of Missive, and Craig Kerstiens from Crunchy Data. We cover bootstrapping Missive from a side project (Conference Badge), growing from 3 to 15 employees, migrating off Heroku, and why most developers underutilize Postgres. Links: Missive Crunchy Data Nonsense Monthly
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
SPEAKER_01Hey, it's Jason, host of the Code with Jason podcast. You're a developer. You like to listen to podcasts. You're listening to one right now. Maybe you like to read blogs and subscribe to email newsletters and stuff like that. Keep in touch. Email newsletters are a really nice way to keep on top of what's going on in the programming world. Except they're actually not. I don't know about you, but the last thing that I want to do after a long day of staring at the screen is sit there and stare at the screen some more.
SPEAKER_01That's why I started a different kind of newsletter. It's a snail mail programming newsletter. That's right, I send an actual envelope in the mail containing a paper newsletter that you can hold in your hands. You can read it on your living room couch, at your kitchen table, in your bed, or in someone else's bed. And when they say, What are you doing in my bed? You can say, I'm reading Jason's newsletter. What does it look like? You might wonder what you might find in this snail mail programming newsletter.
SPEAKER_01You can read about all kinds of programming topics like object-oriented programming, testing, DevOps, AI. Most of it's pretty technology agnostic. You can also read about other non-programming topics like philosophy, evolutionary theory, business, marketing, economics, psychology, music, cooking, history, geology, language, culture, robotics, and farming. The name of the newsletter is Nonsense Monthly.
SPEAKER_01Here's what some of my readers are saying about it. Helmut Kobler from Los Angeles says thanks much for sending the newsletter. I got it about a week ago and read it on my sofa. It was a totally different experience than reading it on my computer or iPad. It felt more relaxed, more meaningful, something special and out of the ordinary. I'm sure that's what you were going for, so just wanted to let you know that you succeeded.
SPEAKER_01Looking forward to more. Drew Bragg from Philadelphia says, Nonsense Monthly is the only newsletter I deliberately set aside time to read. I read a lot of great newsletters, but there's just something about receiving a piece of mail, physically opening it, and sitting down to read it on paper that is just so awesome. Feels like a lost luxury. Chris Sonnier from Dickinson, Texas says just finished reading my first nonsense monthly snail mail newsletter and truly enjoyed it.
SPEAKER_01Something about holding a physical piece of paper that just feels good. Thank you for this. Can't wait for the next one. Dear listener, if you would like to get letters in the mail from yours truly every month, you can go sign up at nonsense monthly dot com. That's nonsensemonthly dot com. I'll say it one more time nonsense monthly dot com. And now without further ado, here is today's episode.
SPEAKER_01Hey, today I'm here with Raphael Mason and Craig Kirsteins. Gentlemen, welcome.
SPEAKER_03Thanks for having us. Hi guys. Excited to be here.
SPEAKER_04Yeah.
SPEAKER_01Let's do some intros. Let's start with you, Raphael. Tell us about yourself.
SPEAKER_03Um CTO at Misiv. Missiv is a team inbox app uh for SMBs. Um it's basically an email client living in the cloud. You connect email accounts, also other channels, SMS, uh messenger, Instagram, but mostly email. And we sync your emails so you you read your emails, you send emails, you manage it, but as a team as well, you can configure an email account as a team inbox where you can assign coworkers, and in any email thread, you can you have an internal chat where you communicate with your coworkers, so you get you have your little Slack room in every email thread, so everything is in context, is so that's that's the the elevator pitch.
SPEAKER_03Um and I'm CTO, I'm co-founder ever since uh 2015, 2014, 2015 was the first uh year, the first launch, public launch of the product. And we're bootstrapped. We started as three programmers, we're all product people and still are today. We we it was still the only the three of us. By the way, do you want uh Craig to go on his presentation before we I go longer on this?
SPEAKER_03Sure, yeah.
SPEAKER_01Let's hear from Craig and then we can come back and hear the full story.
SPEAKER_00Yes. Uh I'm Craig, uh, the chief product officer at Frenchy Data, kind of all things Postgres, like support large enterprises and like large self-managed deployments, but then also have Frenchie Bridge kind of our equivalent to like a you know Heroku Postgres or Amazon RDS that's multi-cloud. Um I I joked that this is my my third time doing this, you know, was early at Heroku and then at CITUS Data. Um third time is the charm of really just trying to build an amazing Postgres service that you kind of don't have to think about. Um like fades away into the background so you can really just get back to building apps.
SPEAKER_01Okay, great. Um so Rafael, um you've been uh missive has been around since I think I heard you say 2014 or so, so that's a good bit of time. Um 10 years or so, and you're bootstrapped. You started bootstrapped. Did you end up taking any funding along the way or bootstrapped the entire time?
SPEAKER_03We did not actually the same founders uh a year or two years-ish before we started Missive, we started another business, which is was called is still called ConferenceBadge.com, which we no longer own, we no longer uh run. We sold it three uh two years ago. Um, but for like a year or two in Conference Badge started paying the bills, and we could start working on another project that would be our let's say home home run or whatnot project.
SPEAKER_03Conference badge was very good, was a nice little cash cow. Um but uh yeah, we quickly started working on Missiv and hired someone to manage Conference Badge for us, and then that's how we've been able to bootstrap Missiv. It's funding from ourselves, but from another product. And uh no, no uh no investment outside investment at all.
SPEAKER_01Okay, this is interesting. I I gotta hear about conference badge.com. What was yeah, what is what was that?
SPEAKER_03Yeah, it it was um it's it's for organizers, conference, event organizers, anywhere from 10 people's, like just a fancy dinner to like conferences with thousands of attendees. You would either connect your Eventbrite account with your list of attendees or upload in a spreadsheet, and you would design uh badge, uh like conference badge, and we would automatically generate the full list of you know, like a mail merge, a fancy mail merge, but maybe you don't even know what mail merge is.
SPEAKER_03Which there's kind of a funny story about that. We did apply to Y Combinator with this product, and uh we were convinced that there was a market for it, and and sure enough, there there was, but they called they asked us what it what does it do better than mail merge? And we did we did not even know what mail merge was. It's this like ugly Microsoft Word plus Excel feature where you you design some stuff in Words and automatically from an Excel sheet you you your your thing gets replicated and generated, and but like it it's it's stupid, but just the font does not resize in mail merge.
SPEAKER_03If you have someone with a long name and with a tiny name, the font so it never works, it's never pretty with mail merge in in Microsoft Word, but we did, and yeah, so we charge like 25 cents to print just the PDF print at home yourself, or a few bucks to print ourselves and ship it to you, maybe with an optional lanyard, and uh that was it. A nice little little product.
SPEAKER_01Okay, interesting. So I'm sensing that this was kind of uh to use the baseball analogy um metaphor, uh, this was your base hit and then you went for your home run after that. Um I'm curious how you like got customers for conference badge. It seems like not necessarily a super easy, straightforward thing. How'd you accomplish that?
SPEAKER_03Yeah, well, um at the very beginning when when we were only just querying the Eventbrite API for ourselves, our testing, developing the the product. Uh someone responsible for like uh third-party developers relationship at Eventbrite saw us. He just saw the the name of the product conference badge, and he said, wait a minute. He contacted us and he said, We're gonna push you guys if your product works well, because we're interested in that.
SPEAKER_03Because for like you say, listeners don't know, maybe Eventbrite is an online registration tool for events. You can host both free events and paid events, and they get a cut, and it's pretty much that. It's you manage attendees, you don't you don't do, for instance, badges on on Eventbrite, unless not built into Eventbrite. There are add-ons with third parties, but at that point in 2013, there was not.
SPEAKER_03And for bigger customers, they did do some in-house manual stuff, like they they had a Google form and they they they asked what did you want to have on your batch design, and someone at Evenbrite would do that and ask approve, do you approve? And they of they did it, but they did not want to pursue doing it, and they saw it as an opportunity to offload this this work to us, and which they did. And so we had some leads right from day one.
SPEAKER_03And also, I think we we had a great home page. It's still good, it's it's over 10 years old, this design. And this was one of our we were four co-founders at the beginning, and the the designer left, but his his spirit still lives. It's a beautiful design, also in missive.
SPEAKER_00Um I I think I knew about conference badge from like from Twitter years ago, like years ago, or at some point you mentioning it. I don't know that I remember the website, but I just went, and it's it is a lovely simple design. Like it's well excited, like it's plain, simple. Um, it gets the point across really clear. I love it.
SPEAKER_03Yeah, and you I I mean you you maybe you had at some some point a conference badge design badge on you because we had some big conferences, like big events and with developers and whatnot. It was cool.
SPEAKER_01Um, and what made you decide that this wasn't gonna be the thing that you're gonna ride off into the sunset with? This was just gonna be like the the opening act. What made you decide that?
SPEAKER_03Well, it's really that missive was then uh scratch your own-ish, your own itch thing for us because while running conference badge and doing the customer support, um maybe we were not like smart enough to configure uh proper help desk, like like I am Zen Desk, Help Scout. They they existed back in the days, and but we did not. What we did was just like info at help at conference badge.
SPEAKER_03We set it up as a Google group. Uh so each of us would receive a copy in each in our individual inboxes, and we had it was not even Slack at that point, we were on hip chat, um and we would say, Oh, I'm picking this one, I'm replying to this one, and that was how we did customer support, and of course it was some par. And then we what if we could do and like uh he he wouldn't mind me saying that, but my co-founder, our CEO, Phil, um he kind of uh does a lot of typos.
SPEAKER_03Well, no longer nowadays with open AI and the open AI integration in Missive, but he did some typos, and we were like, oh man, do better. And we were like, what if we could collaboratively, just like a Google Docs, we could craft drafts, replies to emails together, and we our third co-founder, Etienne, couldn't help but start work working on a prototype, and and we were like, let's do it.
SPEAKER_03Maybe we'll we'll be the conference badge is gonna be the only user, but let's do it. And then it quickly felt like it took a while before it missive on its own went profitable, but we just believed in it. It was just more fun, well much more more fun and uh yeah, and the potential. I mean, nowadays we have I can't even tell you one niche niche we have in our customers base customer base is who doesn't do email, right?
SPEAKER_03In any industry, so it's all over the place is the uh T Tem. Total addressable market is kind of infinite. And even if we're not big into marketing, like we we we hired our first marketing uh people uh maybe a year ago. We we actually grew the team quite a lot. Back two years ago, it was still the three of us only, and we were now fifth 15 in a year and a half, two years, a here in a year and a half.
SPEAKER_03We went uh 12, I like uh five times the the headcount. Um so it's different. At some point we figured it's not the the day to day is not is not a problem. We still love doing it, but what if one what if something happened to one of us that can we build a great product now? Let's build a great business uh around it that that can sustain itself and yeah.
SPEAKER_01Okay, so it sounds like Ms. got started in parallel to conference badge, yep. And and it became clear that the potential was higher than conference badge, and it sounds like it was more fun. What what made it more fun?
SPEAKER_03Oh well, I mean conference badge is still so good today, but it did not really evolve. It's kind of a finished product. I mean, it it's always a lie to say that you can you could always expand on a business, but like it's it's so great just as it is, and whereas Missiv, and it took you could look at missive.app.com slash changelog, and it's an infinite flow of stuff. It's it's never-ending nowadays with AI, of course, tons of stuff we we could do.
SPEAKER_03Um like just at the beginning, um, we were so proud to put it out uh into the world and so innovative. You could have your email, you could chat uh within email threads, you could collaboratively compose emails, but from day one it was but but I can't snooze my emails. Well, I I cannot send later, schedule an email to be sent later. I cannot undo send when oh I I I I noticed a mistake. Like all those table stakes, email, client features we did not have.
SPEAKER_03We had some some innovation, but we didn't have that. So it was just a couple of years to just get on par with the email experience on top of the innovation. So endless stream of work. Uh but nowadays it's still quite a mature product, but still tons of stuff to do.
SPEAKER_01Yeah, it any project that has any kind of success, the backlog just gets longer and longer uh the more time goes on. Um okay, so you you built it for yourselves, and then at some point you got your first customer. Can you tell me just briefly about that? Like where did that first customer come from? How did that go?
SPEAKER_03Um man, I can tell you that this customer is still with us today. Uh I think he's still alone. He's uh a lawyer, and maybe he has an assistant with him, but he's a lawyer in the US. Um just just using it for himself because Missiv has customers from one seat to 200 seats, and very varied on that level. And um I I don't recall how we I mean it was just we we how do you publicize uh uh product when you start out?
SPEAKER_03Post on Reddit, post on Hacker News, post on Twitter, like do some Twitter searches, follow some Twitter searches, poke some people around, and I don't know. I don't I have no idea through what channel exactly that first customer came from. Um well I mean this he was the first paid customer. We've been in like free only beta for several months, and yeah, tech at the early adopters were the first ones through Hacker News to yeah, Reddit.
SPEAKER_01Okay, okay. Yeah, I'm always interested in that phase because that's one of the hardest, hardest stages of the business when you're trying to get your first customer because you don't know if you're ever gonna get any customers. Yeah. Um I'll I'll share what I'm working on, which which I've talked about on this podcast before, but um surely you guys aren't aware of it because nobody knows about it. Um it's it's a except for people who have heard this podcast before, um, it's a CI platform.
SPEAKER_01The name of it is Saturn CI, and I built it because I was and still am deeply frustrated with the existing CI offerings like Circle CI, GitHub Actions, uh Jenkins, GitLab, all those. Um, every last one of them, I just find them so awful. The the UI is just painful for all of them. And not just the UI, but like the conceptual model of the product, if that makes sense. It's just painful.
SPEAKER_01Um, and so I had the idea to build something better, but I'm like, that's like kind of insane. Like one guy building a CI platform in his spare time, like that doesn't sound realistic. So I like told myself no for at least a couple years, and then I'm finally like I got so frustrated with I forget what it was, GitHub Actions probably. I was just like, fuck it, like I don't care that it's a bad idea, I'm just gonna do it and see what happens.
SPEAKER_01Um, and I did it, and that was about two years ago. Um, and I've been working on it fairly lazily over those two years. Um, and then I got a few like free users using it, um, at least to test drive the system and make sure that it's viable from a technical perspective. Um that, of course, uncovered a lot of technical problems, which I addressed one by one as as people tried it out.
SPEAKER_01And then I'm like, okay, I've done the vetting with free users. Uh not much good can come from just like letting more people use it for free and and eat up the virtual machine resources and stuff like that. Um, I'm not VC backed, so I can't afford to just give away a bunch of compute time. Um, so now I'm working on getting my first paying customer. It's been a bit of a roller coaster. Um, and and maybe you've had experiences like this too, Rafael.
SPEAKER_01Um first customer, uh, he gave me the thumbs up, said yes, but we're still working on like getting him over the finish line. At this point, it's been a few months. Um, it's like, all right, I still expect it to happen, but like it keeps it hasn't happened yet, you know. Um, and then another customer, I'm trying to get him on board, but it's like a 10-year-old app, and it's like just really uh there's some problems independent of my product that really need to be fixed before it can get on my product, and so it's like okay, that one's that one's a tough one too.
SPEAKER_01And now finally I have a third person with a pretty small, clean, relatively new app that's easier to set up, and so I'm working on getting him him set up now, and so that might finally be the one. Um, but a lot of kind of false starts on the way to getting this first free customer. Do you have did you have any difficulties like that, Rafael, with with getting the early people on board?
SPEAKER_03Uh I can't I I've never it's never been one of my worries, as I've always been we've always been busy with the code, and we always had enough like users coming in and trying it out. We are quite uh uh cheaply priced compared to the to competitors, which makes the barrier for entry kind of not so bad for for smaller teams.
SPEAKER_03Um and yeah, it's always been a constant stream of feedback and ooh, bugs to fix, and never really had to wonder what to do next. It's we've been quite lucky on that front. Yeah, I can I cannot say that we we struggled with uh bringing more people in.
SPEAKER_01Yeah, that's good. That's good. Um, and I myself will probably uh put more gas on the fire once I get at least one paying customer on there. Um because the bottleneck so far has been like technical, you know, each one of these customers has posed technical problems to me. And then like I was the bottleneck. Um, but if and when I get this most recent guy on there, then it's gonna be time to time to get a bit more public about it.
SPEAKER_01Um okay, so now you're like 10 plus years in, and you you've scaled from like uh three or four employees or whatever it was, just the founders, um, to like 15 or whatever. Um I assume you're dealing with a lot more scale at this point.
SPEAKER_03Um yeah, well this the scale as uh in terms of customer count, it's always been kind of steady, healthy growth, we like to say. We've never been uh we never purchased uh not purchased, pursued, sorry, the the the like hockey stick kind of kind of growth. We just we are more uh makers than businessmen, I would say. Um and like um and sorry, your question was like the growth, yeah.
SPEAKER_03We're we're we're at uh 4,000 and some paying customers, ranging from one seat to 200 seats, and it's uh yeah, it's curious on the other side of scale.
SPEAKER_00Like for me, it's it's fascinating when you scale the business and customers, but man, going from three folks to 15. No, like going from three to fifteen, right? Like the three of you are together for how long? Like you probably didn't have to like like finish each other's sentences, right? Like it's like you're all on the same page, and now you have 15, like like the like you know, how's a team meeting happen now? I'm like, uh oh, we need notes, and we need like you know, summaries of things, and we need all hands. I mean, like like I'm always fascinated by that piece, which actually I find every kind of inflection point, like when you get to a 2x or 3x kind of growth of each stage, it's like all your processes break.
SPEAKER_00Yeah, it's like wait, this is how how hard can this be, right? Like, yeah, we we just know what to do. It's like wait, we have these people and they don't know what to do, and how do we report, you know, uh vacation time and all this like that's the fascinating part to me.
SPEAKER_03Yeah, well, we the when we decided, okay, we need to not only make a good product but a good business. Our first hire was a COO, uh, who is Jenny. Maybe you saw her in the a few emails, I don't know, with your team. She's the one. If our credit cards uh gets blocked for the Crunchy Bridge charge, for instance, that's it's Jenny hand handles this with uh whoever's on the billing side at Crunchy.
SPEAKER_03Um and um uh so she's the one doing a good part of whatever it is we don't really want to do uh as product people. Like she she handles she scheduled at all hands the the like performance reviews, self-reviews with with uh she deals with uh contracts with employees.
SPEAKER_00She's uh who knows how doing that when you did like I always call that like you want to have like an an adult in the room, not to say like as engineers were not adults, but like we'd rather write like when in doubt, right? It's like alright, how can I be happy and we can write code?
SPEAKER_04Yes, right?
SPEAKER_00Like versus like, oh, one on one-on-ones are important, right? And and your reviews and all those things, but it's like when in doubt I want to write code. So like I hear those on like make like hiring your adult in the room early on versus like, oh, we've got all these folks, and like we're not, you know, doing the processes we need to. That's smart.
SPEAKER_01Yeah, and there's something to be said for recognizing your strengths and weaknesses, and like as I get older, I get more comfortable with my with with admitting what my weaknesses are. Um, and I have personally I have some serious weaknesses. Um like, for example, I I this is not technical at all, but like I've been kind of tired the last couple months. Uh, and also I like stopped taking my like vitamins and other pills and stuff like that. Um and I know myself well enough by this point.
SPEAKER_01I'm like, I asked my wife, like, hey, can you like help me start taking my pills again? Can you like put them in the little pill thing that has the days of the week so that I'll actually take it? Because like I know that if I rely on myself to do that stuff, I'll never get it done. I wish that I could just hire like a um, what is it? I don't I don't know what you call the kind of person, not exactly a personal assistant, but almost like uh kind of an assisted living kind of situation. Uh I don't need the person to like feed me and stuff like that, but basically, like do all the stuff for me that I'm like not capable of doing because I can't overstate it.
SPEAKER_01Like I have some huge weaknesses, like, can't if I need to like schedule a haircut or something, just like can't do it. Cannot do it. Um, anyway, I'm not saying that that kind of stuff is is true of you or anything like that. Um, but like recognizing those things that you want somebody else to do is obviously really good.
SPEAKER_03Yeah, yeah, yeah. We're very happy with yeah, yeah, how it went. It's it's pretty good. Also on the developers side, uh, we we went pretty much all remote from the start. We just had a lot of success with the Ruby focused job boards, and uh we have quite a few Eastern Europeans. We love those guys, they're hardworking people.
SPEAKER_01Where in Eastern Europe?
SPEAKER_03Um we have someone in Poland, uh, we have a Ukrainian living in Portugal. We just hired uh Slovak. Um and well, also we have one in Mexico, but he's French. So yeah. Uh and we have one uh on the front end. And all of those are back-end uh engineers, those I work with most, and we have a front-end engineer um who's in Quebec, same office as us, but yeah.
SPEAKER_01I had um Mike Parham on the show years ago, the sidekick guy. Um, and he said something that stuck with me. He was like, When you when you want to hire a developer, don't hire just one developer. Wait until you're ready to hire like four developers, because hiring just like one developer, it doesn't get you like if you're one person and you hire another developer, that absolutely does not get you to 2x productivity. It gets you to maybe like 1.1x or even like 0.9x or something like that.
SPEAKER_01Or a few months, yeah. Yeah, it takes so much more time. Like keeping somebody occupied is like almost a full-time job. It's crazy how much work it takes just to give work to somebody else. And so I'm sure that was a night and day difference from like I'm sure like each of you could pull your own weight and like you didn't have to tell each other what to do when it was just the three of you. But then when you had a team, now you have to spend all this time, you have all these mouths to feed in terms of like setting up for setting up work for people.
SPEAKER_03Oh yeah, absolutely. And I mean uh eight, nine years-ish, only three people with such a complex product. Missiv is quite something in terms of algorithms, email sharing, and whatnot, and just the the scale, the the load. And so it's like the more we go, it was kind of exponential the the the amount of knowledge that's on only one or two or three people's shoulders.
SPEAKER_03Then that in order to offload this, it's it's so much effort, but now we're in a good good place because our new our high hires, our first developer hires from a year and a half ago. Now, after one year, they started to get quite autonomous and very good. I have a strong confidence in them. Um, and but yeah, it's still it's one year. One year is kind of a long window to to to to feel like okay, like we're we're on par.
SPEAKER_03Like I trust you fully, and uh but yeah, it's I feel like that advice from Mike is good advice.
SPEAKER_00Like I don't know that I've heard that stated that way, but when you think about it, it makes complete sense, right? The that overhead to ramp up an engineer, it's it's almost the same as if you're ramping up four versus one. Like, yeah, I'm sure there's some added costs, but it's not dramatically different. But that zero to one is huge in hiring another one. So it that makes a lot of sense.
SPEAKER_03Yeah, indeed.
SPEAKER_01Um, yeah, and I I worked at a startup that was kind of at a similar stage. There was the founding engineers, and I think I was the second hire who was not on the founding team, and so they were total bottlenecks. Like, we couldn't do anything hardly without going to them and being like, hey, a thing happened. What do we do? Like, where do we find this thing? And I need this credential and and that kind of stuff. Did you go through a period where it was just like a painful bottlenecked scenario?
SPEAKER_01And and how did you deal with that?
SPEAKER_03Um, yeah, yeah, yeah. It's uh it's well, just these past few weeks, we at the very beginning, of course, there was this bottleneck uh situation, but it it became a bit better over the months, but these past few weeks, we've been kind of we had to rush our like project of moving out of Heroku to uh Amazon ECS. Um and because our Heroku uh yearly contract was ending, so we kind of had this hard deadline, and things took a bit longer than I than we would have hoped, and I really had to focus on this this Democles sword that was hanging above our heads, and uh so yeah, I had to delay reviewing pull requests and and stuff, and uh it's it's still still real, still real, but now it's done.
SPEAKER_03We're happy running on on AWS and um uh so yeah, I'm I'm happy to get more into the daily stuff, feeding mouth and getting the stuff out. Yeah.
SPEAKER_01Yeah, yeah, that's great. Um okay, and and Craig, you're here, but I've been kind of neglecting you so far. Yeah, sorry, Craig. Well, where does where does crunchy data come into the picture?
SPEAKER_00Um, so we run Postgres, we run message database. Um, they migrated, I believe it was from Heroku over to us. Yep. Um no, it's it's funny. Running databases, it took me probably 10 years to get used to this because usually like you have a product and you ask customers for feedback, and like you get so much feedback. Like, I I imagine, Rafael, when you ask customers, they tell you what they like and what they don't, and you have ideas to work on. When you ask, when you're running a database and you ask people to like have feedback, they're like, nope, it's good. And I'm like, it took me 10 years to get used to the idea like uh uh, they're leaving us tomorrow.
SPEAKER_00They're like, they're about to migrate off. They just they didn't give me any feedback. Like it's it's like thanking your security is kind of thankless. Like if we're doing our job well, like I don't hear from our customers. Like, you don't you don't want to be in the database. Like, you want to put your data in there, you want it to be up and running, you want it to be like, you know, production ready and backed up and everything for when something does go wrong. But for the most part, like you don't talk to your database provider. And so um, I I love like all the conversations that I've had with Raphael because he's like he's he loves the database.
SPEAKER_00And you know, we I think we were talking about this a little bit earlier, right? Like Rails developers, we you know pretend we're opinionated and we're so I mean we are opinionated and we're so like well thought out in our opinions, right? And if you ask most Rails developers, they'll say, you know, Postgres. And then you ask them why, and they're like, Well, I I didn't mean to actually need to defend it, right? Um, I I love that like Rafael pushes it like to its limits. He's like, Oh, yeah, I'm using this and this and this in Postgres, which I wouldn't say it's the average Rails developer.
SPEAKER_00Um, but yeah, he's been a great customer and you know a great evangelist for us of like his experience and like you know letting us touch this database so he doesn't have to worry about it.
SPEAKER_03Yeah, no, definitely we're very happy with the crunchy product and service as well, because I know a few several of Craig's co-workers very well. Uh Jesse uh and and John. Um they've they've been great from the the very first day with the migration and to uh even nowadays still whenever we we upgrade the database we we always double check with the guys.
SPEAKER_03Oh are we should we take this opportunity this opportunity to change like uh AWS disk generations or CPU architecture or whatnot? Some of the things that some of the knobs are still hidden from from the the crunchy uh the crunchy dashboard.
SPEAKER_02So I love to have very great and responsive service from the crunchy guys. That's great.
SPEAKER_01Um that's that's interesting about the lack of feedback. It's logical, it makes sense, because it's like, oh, how's your database stuff going? It's like good, I guess. I I don't, you know it's it's an absence of problems, is all that I'm looking for out of my database, pretty much. Um have you have you devised ways to like try to try to prod more feedback out of people so you can like get ahead of issues, so it's not just like one day they're you discover they're migrating away?
SPEAKER_00Uh I d I don't know that I have yet. And I've been doing this for you know since the early days of Heroku for for almost 15 years now. I I don't know that I've found the answer to that. I think like, you know, the the common product things, you know, watching people juices patterns, what are they doing, kind of the load. Um, I mean, what if you're doing a good job of hosting someone's database, I we don't have many customer sleeve. Um uh for a while we didn't have a single customer leave Frenchie bridge ever. Um that record finally changed when one customer went out of business.
SPEAKER_00So like today, like and then you know, what are you gonna it was amazing? The customer sent us like an apology letter saying, like, I'm sorry, y'all are amazing, but like we're shutting the business down, but like I, you know, we'll use you in the future. I'm like, you don't have to apologize. I'm sorry you're shutting your business down. Like they they were like so you know, sorry and apologetic, and just like like I feel for you, like you're setting down your business. And and they're like, you know, I I almost want to keep paying. I'm like, this is that's that's flattering. Like that's that's really flattering, um, which is a huge testament.
SPEAKER_00And and so, like, you know, we hear that from time to time, and it's it's great. Um, but yeah, I haven't, it's it's kind of like, you know, if we were a bank, right? Like you don't hear from your bank, and when your bank's like, can we do anything better, sir? Like, no, you keep my money safe, right? Like that's it. Like, when you hear from your bank, it's because they you know lost your social security number and you get free credit monitoring for a year. And so, like, in the data world, no news is kind of good news. Um, it's it's it's really different, I think, from a product development standpoint. But uh, you know, for me, it's definitely rewarding.
SPEAKER_00I think like hearing both of you go back and forth, right? You know, Jason on the CI stuff, it's like, man, you're building for engineers and you're an engineer, right? So it's rewarding from that side. Raphael, it's like, man, you've got like lawyers as customers. I wouldn't even know where to begin selling to a lawyer, but like being a platform, the customers like building stuff. Like, we have a customer that um it's like one of two people that like survey the snake population in Canada. So it's like geospatial data sets of like goes out into the field three days a week, catches snakes, you know, keeps account of them so to like know if they're trending up or down.
SPEAKER_00I'm like, that's a pretty cool use of technology. Like, I'm I mean, I don't actually want to go catch snakes, but it's kind of cool, right? And like running a platform, I I get to see like all sorts of ways that technology is used, right? Like it's it's kind of exciting, but for me, I love building for engineers, right? And so I I wouldn't know where to begin at at some of these like selling to these other markets. Um, but it's fun to like learn and see it like as they exist and people build for them. Yeah.
SPEAKER_03Yeah, I I love that our product that feels the needs of anyone in any industries is first and foremost a product for ourselves. Because if I were to start another business, um it would still be about scratching my own itch, probably a developer thing, most likely. Yeah.
SPEAKER_01Um so just so people understand what crunchy data is, um I I I've talked with a couple crunchy data guys at at conferences. I feel bad because I don't remember his names name, but one of your colleagues, Craig, um, he was definitely at Rails World in Toronto. I'm guessing it was Rails or Brunder.
SPEAKER_00Brunder or Chris? I guess it's one of the two.
SPEAKER_01I think Chris. Yeah, he's I believe he's from Alabama. Yep, yep. Okay, yeah, yeah. Yeah, so I talked with with Chris. Um, I like him a lot. We had some some good times. Me and Chris and uh Colin Gilbert were hanging out at uh at RailsConf in Detroit when that happened in Detroit. Um anyway, I think the way he described it to me was that it's kind of analogous to like um AWS RDS or something like that.
SPEAKER_01Um, instead of hosting your database yourself, you can connect to a hosted database service, but there must be some key difference, you know, some reason why people would use crunchy data instead of RDS or something like that.
SPEAKER_00Yeah, there's a number of like, you know, you jump into the technical reasons. One is like we give you full Postgres super user, which you don't get on RDS, right? Richer set of extensions, like price to performance. Like we've benchmarked ourselves pretty much against every provider from Heroku to Cloud SQL to RDS, and head to head can beat on price to performance, right? Same-sized instances. Like I was very lucky to be kind of that original Heroku team that built Heroku Postgres. And you know, Heroku Postgres isn't bad. It's just it kind of froze in time when a bunch of us left, you know, almost 10 years ago.
SPEAKER_00Like it's a fine product, but didn't kind of it's still kind of the exact same product. And you know, I joke that this is an unfinished business that, like, hey, we're picking up where we left off, but it's also kind of true, right? Um a bunch of us having that developer background, um, like the dashboards, the tooling, the insights is like targeting an application developer, not a DBA. Like, how do we express things in a way that you understand without like you know, I mentioned this, like the Rails community, we love Postgres, but it's like if I were to email you an explain plan, you're like, hang on, hang on, I like I don't love Postgres that much.
SPEAKER_00Like, let's not go crazy here, right? Um, I work with Postgres all the time, and it's still confusing to read an explained plan. How can we give you that in like an understandable, digestible way, right? Um like support is another big one. Like we hear about that all the time, quality support. Um it's I mean, why why can't we give good support in industries? Like you go from you know, airlines to hotels to like where is this good support exists? And we definitely pride ourselves on that. That you know, um our team loves to dig into complicated issues and not say it's not our problem.
SPEAKER_00It's like, hey, it's interesting. Like we've got a rockstar team that like wants to do interesting work, so like show us the hard problems and we'll dig in with you.
SPEAKER_01Um we we got just a few minutes left, but I want to make sure we we touch on everything we want to. Um Rafael, I took us in all kinds of different directions related to you know the the business aspect of things and and even before this business. Um is there anything that we haven't touched on yet that you want to touch on in these last few minutes?
SPEAKER_03Oh well um well good question. Like what do I want to talk about? Like um um I don't know, maybe maybe uh Craig said something about um um having uh sorry, what did you say? You you said we don't want to many people they they don't they love Postgres but they don't love it that much that they want to to think the whole day about Postgres.
SPEAKER_03But like yeah, I I I feel that um you you do a good job at at Crunchy making it like you do great blog posts uh as well, and you um like and yes, you you your support. Sorry, I don't have a clear idea of what of w where I'm going through, but um like yeah, I think it's good to like it's you know um for me, right?
SPEAKER_00Like I don't want the database to be scary for for developers, yeah. And it's it's easy for it to be. And like to me, you're like um, I'll I'll pick on you, you're like total nerds. You're like, I love the database, and I'm like, jump in there, right? And I don't think that's every developer, but I think like how do you just you know not make it scary, create good education around it? Um, I mean, we we didn't get into the deep, deep, deep white Postgres, right? Like I could list off features, and if people aren't familiar with them, like go do like um per per transaction asynchronous replication.
SPEAKER_00Like Postgres can be async by default, but you can toggle it to be synchronous, right? On a per so like your shopping cart, not sync, but your purchases sync, right? Things like listen notify, which is pub sub in your database. Yeah, yeah. Um, like SQL is not a pretty like if if you read other people's SQL queries, like you you're like, oh man, this is horrible, right? Like um, I know a few people that like reading, like writing SQL, but I don't know of anyone that likes reading anyone else's SQL, but like common table expressions for readable SQL.
SPEAKER_00Like, it's like, man, there's so much in there that it's like you don't know, like it's it's so funny. As engineers, we we're curious, yet it sometimes stops when it comes to databases. And it's just like we should just encourage that curiosity more and more. And so, like, that's why I love every time Raphael we get to chat that you're like, oh, I've learned something new about the database. I'm gonna go dig in and see if I can use this. It's super exciting. So I I just love that enthusiasm. I hopefully like that shines brightly to others. Like you don't have to be scared of your database, you can know you can be curious just like we are with all the other things around the Rails world, right?
SPEAKER_03Yeah, and and and the funny thing is that like I I realize that it's it's crazy how yes, we use Postgres as developers, we are not DBAs. And one day I asked myself, like, what would it take to be a DBA? What do DBAs have that that I don't like? How much experience do they have? Do you need? And I just I was browsing around the Postgres website, and I found that for every version, we all know like the online Postgres docs, right?
SPEAKER_03Very exhaustive, but very good. But you always only read that one page that you you get a link through through Google or Stack Overflow. And but they publish a book, it's a PDF in the form of a book for every version. And man, it turns out how many pages would you guess there is in the full Postgres documentation book? 2000. Yeah, it's near 2000, and like okay. I I it's a fun read.
SPEAKER_00I highly encourage it.
SPEAKER_03Yes, I mean I would bet that if I actually read through all of this, I would there would no longer be so many secrets like in Postgres. Like for me, like I I wouldn't have experience, but still I I would if I have enough memory in my brain to to remember all of this. Well, I can see what a DBA is, what being a DBA means. There's so much stuff. Um but yeah, it's always cool to dig in.
SPEAKER_03And you mentioned like stuff like common table expressions, listen notify, just unlog tables, for instance, can be so useful when you can afford a table to be unlogged, possibly huge performance benefits um for read uh both read and write heavy tables. Uh no, Postgres is so yeah, it's uh so deep.
SPEAKER_01So I'm gonna I'm gonna ask this question of each of you individually. Uh I'll start with you, Rafael. Um, is there anywhere you want to send people online to learn more about um Missive and you and all that stuff?
SPEAKER_03Um well Missivapp.com would be the place, definitely. And uh from there you'll get links to various channels. We with a marketing team nowadays, we we have a uh Reddit community we we we we we work on. We have YouTube channels, we have everything, and uh also we have an official designer nowadays, so the website is much nicer than it was before. But yeah, anyone who's interested in um getting more productive at emails and just trying a nice, nicely built product.
SPEAKER_03I think it's gonna be uh interesting for anyone.
SPEAKER_01Yeah. Okay, we'll put that in the show notes. And Craig, any links for you?
SPEAKER_00Uh I think if you want to people want to follow me anywhere, I'm Craig Kirstein's on Blue Sky and Twitter and LinkedIn and everywhere, and then you know, crunchydata.com. Like we um like I am proud of our blog and the content we create. It's like highly technical Postgres stuff, but targeting it app developers, not DBAs. So uh we've got like an interactive Postgres playground where we put Postgres in the browser with tutorials, and then you know, uh if if anyone's ever happy, unhappy with their you know existing database hosts, like happy to run databases for them. Um I won't be offended if you you know don't give us feedback and you just quietly run your database on us.
SPEAKER_00I've gotten used to it. So um if anybody you know wants to change of database provider, we're always here.
SPEAKER_01Awesome. Well, Craig and Raphael, thanks so much for coming on the show.
SPEAKER_00Thanks so much, Jason. Thanks for having us.
In this episode I talk with Joel Hawksley, Staff Software Engineer at GitHub and creator of ViewComponent, about whether AI is making us dumber, why blocking code reviews struggle under a flood of AI-generated code, and...
In this episode I talk with John Athayde, designer-developer and co-author of The Rails View, about what architecture school taught him about software design. John tells the story of a user test at LivingSocial that...
In this episode I talk with Riccardo Carlesso, Google developer advocate and co-founder of Rubycon, a Ruby conference held in Rimini, Italy in May 2026. Riccardo explains how a joke about PyCon became the conference's...
In this episode I talk with Travis Dockter, organizer of Blastoff Rails in Albuquerque. When Sin City Ruby and RailsConf both ended, Travis decided to start his own conference. We discuss how cheaply you can run a...
In this episode I talk with Julien Danjou, CEO of Mergify, about merge queues: why PRs that pass CI separately can still break main together, and how testing changes in a queue keeps main green. We discuss how Mergify...