Personalized AI Language Education — with Andrew Hsu, Speak

Hey everyone, welcome to the Latent Space Podcast. This is Alessio, partner and CTO at Decibel, and I'm joined by my co-host, Wilkes, founder of Small AI.

Hello, hello, we're back in the studio with Andrew Hsu of Speak. Welcome.

Thank you for having me.

I have to start this off. I didn't prep you on this at all but you were a Thiel Fellow in twenty eleven.

First class. That's right.

First class?

Yeah, yeah.

Is that, is that the one with, um, SBF?

No, he was, I think, several years later, actually.

Okay.

Yeah, yeah.

What was it like? Just talk about the-

That's a good question. Haven't been asked that one in a while. It was a really crazy idea at the time and very controversial, and I think the first few years of the fellowship were definitely, "Let's just find twenty people under twenty and give them a hundred thousand dollars to drop out of college," and it could be-- It was no holds barred.

You could do anything. You could be doing some crazy research idea, a startup, anything. Um, and, uh, I actually met my current co-founder at Speak. He was in the second year of the fellowship and-

Ooh

... made many, like, very close friends from the first, uh, few years. But, I mean, for me, it was life-changing. I, I had a very unusual path where I was actually-- I did finish college, unfortunately. I was in grad school at the time because I went to school really early.

Yeah, I was like- ... "Aren't you, aren't you too old?" You know? Thiel likes them young.

I was

I was nineteen at the time and in grad school. It was a very accelerated path, but I think, like, I knew at the time that I was going to leave grad school and do startups anyway, and the timing lined up really well.

Yeah, yeah.

Yeah.

Vitalik, I think.

He was also in a later year.

Ah.

Yeah.

Damn. Okay, anyway. The, the-

But the first two years had-- I mean, there were some crazy s-successes. You know, Dylan from Figma. Uh, I mean, yeah, like, a lot of people.

Awesome. Well, you know, feel free to bring in those stories as and when-

Cool, yeah

... because obviously only, only you know, like, those kinds of people. You are now CTO co-founder of Speak.

Yes.

Uh, I would say from a very early stage, like, one of the most successful and prominent OpenAI partners that, like, anyone would know as, like, doing, doing well and, like, teaching English to Koreans is, like, your, your, your rough, um, remit at the time.

How did that all come about?

It's funny that you say that because despite our- ... current sort of revenue scale and objectively, I think, how successful we are, we've always operated in a market, at least initially, on the other side of the world and been much, much more popular in the sort of Eastern world and a bunch of Asian markets and relatively unknown in the West.

So it hasn't really felt like we've had that sort of awareness until, you know, the past few years really. But brief story is that my co-founder and I back in twenty sixteen were fascinated by the promise of AI, and we spent a year sabbatical basically learning everything we could.

We talked to Karpathy back then actually when he was, like, just finishing grad school and did a lot of sort of self-study research, and we were just so convinced, I think fundamentally, that speech models were going like this, language models were going like this, and in the five to ten year span they would become superhuman.

And we were utterly convinced of this future, and we saw that the way people learn things and specifically learn languages, which was a very sort of human-based thing if you really care about fluency, that would completely change and we'd be able to build language tutors that were pure software, pure AI.

So that was kind of the genesis story of Speak. It took much, much longer than we expected to build a great product and find good PMF. The first few years were very painful, and I think without this really compelling vision of the future, we would've quit.

We actually, like, never pivoted. Last year, we brought the entire company to Taipei. We do this company trip every year. And we played our original YC application video on screen, and it was really funny because the things we were saying in that video were the exact same things that I still say today about the long-term vision and what we're building towards.

Um, so that was really cool to see.

Can you summarize the long-term vision again?

It was that as speech models and language models become superhuman, that would let us create an AI language tutor that would help you become fluent faster than any human could. And I think we're like eighty to ninety percent of the tech is here now.

And you have this big focus on, like, speaking. Obviously, it's in the name of the company.

Yeah, that's right.

Uh, and I think the speech models were maybe a little delayed compared to the text models. Did you ever think about, okay, maybe speech is just not gonna work for this use case? Or like, what were kinda like the valleys of, you know, discomfort, and then what were maybe some of the pivotal releases and models that you were like, "Okay, it's gonna work.

It might take a little longer, but it's gonna work"?

So we've always done custom speech stuff. The first act of the company, if you will, was before LMs, right? Before twenty twenty-two when Whisper came out, when ChatGPT came out. In the years before that, you know, like roughly two to three years is when we feel like we found PMF in South Korea and then started growing still only in that market, still only teaching English.

And we developed custom speech recognition models, and users were speaking into the app all day, so we had a ton of this non-native English speaker data, and we would use that to fine-tune models, understand our users better. We still do that today, and it's important for us for the core recording loop in many of our lessons that it's extremely fast, so we're very latency sensitive.

There's many other sort of product surfaces within the app today that are more LM-powered, where it's more open-ended real tutoring, where we actually give you feedback on what you said and the semantics and so on. So that stuff is more like Whisper-powered, more LM-powered.

But we've always had like a very fast core ASR loop that's been fully custom.

I just onboarded to the app earlier today.

Yeah.

Unlike other apps, there's kinda like this, uh, tutor conversation that you do for onboarding.

Yeah.

I'm guessing that is mostly LLM-based, and then you're kinda judging the person respond. So I selected Spanish, and the conversation was in Spanish via text to start, and then from there started to create lessons for me.

Yeah.

Was that all unlocked from LLMs where now you can kinda have these conversations and then bring people into the speech flow?

Yeah. So before that, so we call that Magic Onboarding.

Mm-hmm.

And it was a new thing we built that was more conversational. We wanted it to feel more like you were talking with a tutor, and they were, uh, sort of learning things about you, and we would use that later to personalize the experience.

Before that, we had a, like, a much more traditional app onboarding. There's still a lot of open questions, interesting questions around what is the proper onboarding UX because a lot of people start using Speak, and they're not in a situation where they can actually speak aloud.

So we have, like, you know, fallback outlets and so on, but it's something we're, like, super actively experimenting with.

Is there a structured output behind that? You know, anything that you found implementing Magic Onboarding? I think people always wanna improve onboarding. What's the uplift? Or was there one? We still don't know yet.

The interesting thing is that, in general, because it's speaking based, which is a much higher barrier than just, like, tapping a multiple choice button, what we see is that install to sign-up rate is a decent amount lower, but trial start rate is higher.

It's still something that we have an active experiment that, um, that's running, and we're trying to be v- super agile about testing many different sort of, like, formats of this. I don't think I have, like, the final answer yet.

Yeah.

But I think the intent, the really, like, vision that we're going for here is that as soon as you download the app from the App Store, maybe you see it in an ad, the first thing that... The first interaction when you have, like, a fresh open of the app should feel pretty futuristic.

It should feel like, okay, this is, like, the new AI-native, next gen way of learning a language to fluency, and that's kind of been always our ambition. Like, we want to build something that wasn't possible before without LLM and, like, AI technology.

Yeah. I, I think, um, I wanted to go back on the onboarding soon, but there's a general idea of, like, when you replace a form with a voice bot, that you need to have some kind of state machine behind the hook.

The thing to drive, like, what else don't, don't I know about you? Let me proactively ask that. And I'm just wondering if you had any insights there, or is it literally just a state machine?

We tried both, actually.

Yeah.

Right now, I think probably what you saw is a state machine, but I think that-

Trust the AGI.

Yeah. Right. I think that things should move in a direction where it's much more of a natural conversation.

Yeah.

There is a general sense of a goal in the prompt that you can specify, and part of the hard thing here is all the guardrails, right? Like, once you start talking about what you had for breakfast yesterday, right, and trying to be, like, antagonistic to the system, then things start, like, really going off the rails.

So for a bunch of these experiences, we're pretty careful about the fallbacks, and we have a lot of evals around that. But I think where it should end up is just feeling like you have a quick three to five-minute conversation with your tutor, and then it knows a lot about you, and then you create your account, et cetera.

And you create memories? Like-

Yeah.

Yeah.

So we, we store what you're saying. We summarize. In the experience, the way it works is the tutor will ask you some sort of question like, "What are your goals around learning English or the language?" And then we will basically use a separate LM prompt to summarize, so it's not the, like, full transcript for what you said that you see.

It's more of, like, an abstracted, "Okay, here's what you care about," and we think that's a better product experience.

What were some of the other key tenants on the product? Obviously, language learning is, like, one of those consumer markets where, like, dozens of companies always try and get started, and you get these old companies like, you know, Babbel, and you got Duolingo.

Um, so speak- speaking, the, the act of speaking was, like, a big part of it. I think this memory stuff is great. I, I think if you tried some of the other apps, it's like they always try to re-ask you the same things that you got wrong before, but you're not really learning.

Is there anything else that is maybe, uh, not as obvious from the outside in the design of the app and the product that is, like, you think is really different?

I would say from a macro level, this is actually a pretty new product category, AI-powered language learning. And all these apps that you mentioned, Duolingo, Babbel, et cetera, they're more of, like, the Gen 2 of language learning. So, like, if you think about Gen 1 was Rosetta Stone if you, you know, if you remember, right?

CD-ROMs in airports. And then Gen 2 was basically mobile, so you have these very casual, massively popular mobile apps like Duolingo that I think the comp there is probably closer to a mobile game, something that feels productive, something that's very engaging, very gamified.

And-

Duolingo's very leaning into it, the gamification.

And they've done an amazing job of that, to be clear. Um-

Yeah. They, they might be the world's best people at it.

Yeah. Um, and our view is that LLMs and AI now enable Gen 3 of language learning, which is something that is very AI-native, very focused on functional fluency, which is why we do all these role plays and let you practice Spanish by talking to your Uber driver.

We don't teach vocabulary and grammar. We teach sentence patterns, and we try to get you to just repeat and drill and drill and drill, almost like you're in a gym, until it's automatic 'cause that's what speaking is, right?

Like, it has to be spontaneous and automatic. In terms of the other aspects of the design, though, we went through many, many iterations over the first few years of starting the company. This is kind of what I was mentioning about it was, like, really painful in the first four or five years, and in fact, the current version of the Speak app is not the first thing that we launched.

We had something that we call internally the Red App, which was, like, a red app icon, still a similar logo, and it was more around packs of content instead of courses where you could sort of choose any topic that you wanted to learn.

It was for many different languages for learning. It was essentially, like, not a very directed experience, and it didn't really work. It was free. It was a very basic thing. But we, in 2018, tore everything down and realized that we had to really fully change what we were doing, and that's when we decided to focus on South Korea specifically on teaching English.

We built a bunch of new lesson types, and we created our courses so that the experience was much more on rails. We realized people don't want to choose. They're already using some of their motivation on a daily basis just to open the app.

They don't wanna make another choice after that, right? Just tell me what to do, right? Like, you know, give me a big button, and then I can tap it and just start a video lesson or whatever. We also, pretty critically, I think, abandoned the free version and just went straight premium, and we kind of sidestepped the motivation question that way because we knew that there were a ton of users that really wanted to learn English and were already really motivated, so we wanted to basically filter for these users.

Um, so they... You know, like it was... I wouldn't say there was one silver bullet. It was kind of the combination of many learnings over three or four years, and then that started really growing in South Korea. And from there, I guess like phase two was really 2022 when LLMs came out and Whisper came out, and that allowed us to go from this more supplemental speaking practice tool to more full-featured language tutoring where we could use LLMs like 3.5 Turbo back then to give you direct feedback on your wording and on, you know, like that was kind of a weird thing to say.

A native speaker would say it this way or use a different word or whatever.

I always do a poor job of doing this, but, uh, can we get some headline numbers, like just to get a sense of scale? Because I think maybe some audiences don't know-

Yeah

... where you're at now in terms of your reach.

So we're now the biggest English app in South Korea.

Yeah.

We do billboards, big celebrity campaigns, that sort of scale. Like we're, you know, very popular there. I think like 6% of the Korean population has tried us. Um, we're, you know, like well on the way in a bunch of other Asian markets like Japan, Taiwan.

Mm-hmm.

So the Asian markets are currently our mainstay. We also teach English in 40 more countries. We're coming to the US as well, launching... I mean, we, we have Spanish, French live, and several more languages are coming this year.

That's a huge focus of the company right now. Um, in terms of revenue scale, well over 50 million ARR. It's a pretty simple business model. It's like mostly consumer.

Subscription. Yeah.

The B2B stuff is super, super exciting, and that's also growing really fast, and I think it'll be a really meaningful part of the business.

When did you start B2B?

About a year ago. It w-

Okay

... it kind of... It was like very much a side bet/experiment at first- ... and then it just started working. And-

Of course it's gonna work .

Uh, yeah. And now it's like, okay, you know, this is part of the future, right? This is a real thing. Yeah. So that's exciting.

What's the B2B race between learning language and like real-time AI translation?

Uh-

At Google I/O, they're like one of those like Google Beam things for like, uh, you know, for conferencing. They do real-time translation, like-

Yeah. Yeah. Yeah. So people always ask this, right? They're- they're always like, "What happens when the Babel Fish comes?" Right? When the real-time translation comes.

And Babel Fish is the Hitchhiker's Guide.

Right. Yes, exactly. The counterexample that I always have that I think is quite illustrative is in German, the verb is at the end of the sentence, right? So if you're trying to do real-time translation from German to English, as an example, you can't actually make any progress on the English until you hear the whole German sentence and you know what the verb is at the end, right?

So like the minimum latency there is, is the full sentence. And that, that's like an example of the technical blocker for- ... like why it'll never be truly, truly perfect. But also, I think besides that, if you talk to all of our users in Asia, they don't want a translator.

The reason that they are trying to learn English is to make themselves a better person, to connect with other people. Like, they wanna be able to look you in the eye and speak English, speak the same language as you, right?

So it's actually like a very different thing. I think what will end up happening is that we will build a real-time translation feature into Speak and have it integrated into the learning experience.

And also, like there's always that human side, right? Like I'm dating a Romanian woman.

Yeah.

Uh, his wife is trying to learn Italian. Like, there's always that-

Yeah, absolutely

... which is gonna keep happening. I wanna double-click on Korea.

Yeah.

I think it's like a very insightful, smart decision. Maybe people only know Korea through K-pop. But actually, I think a lot of Americans learn Korean because of K-pop. That's a, that's a side thing.

Yeah.

But like you could have done Taiwan, you could have done China. I saw... I remember seeing a d- documentary about how China was crazy about English or mad about English. I think that was the title of the documentary.

Was it obvious? D- Were you sure when you went into Korea, or was it just a test?

We visited a bunch of Asian countries when we were thinking about how do we relaunch things, how do we focus in, and we almost chose Taiwan, actually.

Yeah.

Um, but I think it was a little bit serendipitous. So our first employee is Korean and was my co-founder's college roommate, actually.

Mm.

When my co-founder visited Seoul to check out the market, he asked SJ to come along as essentially a translator and to like, you know, facilitate. And I think that just went really well, and it was just very obvious from being on the ground in the market that Korea is pretty obsessed with learning English, and there is every human-based solution possible, right?

You know, like English academies, classes, skyscrapers full of classrooms, stuff like that. And our logic was basically, if we can really make headway and win this market that is chock-full of these human competitor products and all these people that fundamentally care about fluency, then we probably have something pretty real and strong PMF that we could win other markets with.

So that was the original logic and, you know, so far it's been working.

It's retroactively obvious, which is the best kind of obvious. But, like, it's so counterintuitive that you would be the team to do this and not a Korean team, right?

Yeah, yeah.

Where they would be... They would know because they had personal experience of, like, "I started in Korean, I learned English. Here's how you do it."

Yeah. In hindsight, super weird, right? Like, we, we were definitely s- you know, sitting in an office here in San Francisco- ... operating with users in a market all the way on the other side of the world. It would not have worked without Soonjae.

I have to give him a lot of credit here because we paid a lot of attention to the specific wording of button text in the app and locals, you know, like-

Yeah

... like localized strings. We had a lot of reports from users pretty early on that they were shocked that it was an American company. Like, they thought, dude... Right? 'Cause you can always tell. There's always some weird wording or whatever, but there wasn't in Speak and I think that probably had, like, a large sort of non-tangible effect.

Yeah. Focus, attention to detail.

Yeah.

Tech stack. You... This was 2018. What were you rolling? You, you just did ASR and there was no LLM, so BERT maybe? I don't know.

We actually had really no LLM component of it.

Yeah.

So all the content... Oh yeah, another thing we did that I forgot to mention was we decided we needed to fully own all the content. So the way that we teach all in-house, all sort of thought from first principles, we build this thing called the Speak Method, which is basically like a pedagogical philosophy around teaching sentence patterns that you drill and then sort of combine into higher order patterns.

And all of that was in-house with, you know, our content team and our teachers. Um, and we built a lot of internal tooling to make this possible. There's just a lot of operational overhead, I would say. This is something we've struggled with to scale to many more languages, and that's, like, a big research effort within the company right now.

We're building a mobile product, right? My co-founder and I have always just loved apps and been big iPhone users, so we cared a lot about the app being native, feeling great, being high performance. The DNA of the company was always consumer.

Frankly, my co-founder and I had never worked in a real company. I dropped out of grad school, had a few failed startups, and then eventually started Speak, and he had never worked in a real company either. He, uh, just startups in the past.

So we didn't know anything about enterprise, enterprise workflows or, like, what sort of software real companies used. Um, so I think frankly, consumer was the only path. Uh, I don't think we could have done anything else. We just didn't know enough.

Um, and I think that has served us well, though, in terms of just really caring about the craft of it and wanting to build something that felt not 90 to 95%, but 95 to 100% in terms of polish.

Was it hard to build an engineering team that did that at the time? Because ML engineering is-

That's another... Yeah

... is very academia driven-

Yeah

... back, back then, and then you have, like, the more consumer stuff that it's maybe more nascent.

And it's mobile. I'm now realizing that our story is very weird. So in addition-

You only just realized?

Yeah. In addition to the market on the other side of the world, our first iOS engineer that we hired through a YC referral was in Slovenia. If you don't know where Slovenia is, look it up on Google Maps.

But it's, you know, it's like a pretty obscure little country, right?

Middle of nowhere.

Yeah.

Yeah.

And then we needed to hire a backend engineer, and one of his best friends was a great backend engineer and we hired him, and then this happened four more times, all in the same city. And then we were like, "Okay, we should probably just open a physical office."

So for-

In Slovenia?

Yes. So for several years, we had an engineering office in Slovenia.

What?

And then a few people here in San Francisco, and we still do. Now we have 90% of our core product development team in San Francisco here, office in Fidi. We're really only hiring here. But for the first, like, several years that, you know, that was, like, another very interesting sort of cultural aspect of the company, I guess.

I think a lot of early stage founders have to do that. It's, that's the only people they can afford or whatever.

Yeah.

Um, what are your, your tips that make that remote stage work?

For us, it wasn't really a price thing.

Yeah.

I think legitimately thought he was the best person that we interviewed, and then it just kind of happened-

Yeah

... that way when you roll it out.

Yeah, it's not a price, it's more about remote work, right? Like distributed team-

Yeah

... early stage. Like, a lot of people say, like, "No, you have to m- you have to move everyone to SF or your startup will die."

Yeah. I don't think that we were good at remote work. I don't think that my personality or my co-founder's personality is inherently very good at async, just to be perfectly frank. I actually think that almost, like, in spite of it- ...

we made it work. It was a little bit brute force. Like, I would just sync with them every single day, right?

Yeah.

And there was pain because the time zone overlaps. Like, it was, like, exactly the most inconvenient.

Yep.

But I think for several years we did that. We got really good at the cadence of it. I think they were excellent engineers as well, so it worked out. But if I had to do it over again, I probably wouldn't do it.

It's hard to say. Yeah.

Shall we move to phase two on the, the LLM side? Um, that's when-

Yeah

... OpenAI started opening up, and when did they invest?

This was 2022.

Okay.

So that was also when Whisper dropped. And-

Yeah

... Whisper was a really exciting moment for us. It was actually since we started the company and made that prediction of, okay, in five or 10 years, speech models, language models will become superhuman level. Whisper was really that magic moment for us where we were like, "Oh, shit, I think what we predicted is here."

And I pretty distinctly remember this moment in the office when we got access to the model, and we were testing it on an audio clip of, like, a very beginner English learner in Korea saying something. And it was-- If you close your eyes as a human, you'd have no idea what they were saying.

There were four of us in the room, we all closed our eyes, and none of us had any idea, and the model got it right. So I mean, superhuman. I think that was the moment that we had been waiting on, and at the same time, LLMs were on the ascendancy.

ChatGPT would come out, I think on Thanksgiving of twenty twenty-two, and three point five Turbo came out. And I think like we kind of realized very quickly that all the pieces were clicking now, right? Like we have what we need at our fingertips now to go from something that was listen and repeat, where the user would see something on screen, hear a reference of the teacher saying the thing, and then they would just repeat the thing, right?

It was like very simple. Still a great product, by the way. You know, it still grew to like several million ARR in South Korea. Um, so clearly there was like a big market need for that.

Pre-Whisper?

Yes.

Wow.

This is from like twenty nineteen through twenty twenty-two. And then-

Yeah, that's, that's the grind.

Yeah.

You needed, you needed to hang in there.

Yeah. And again, I think that if we... There were many moments when things weren't working from twenty seventeen through twenty nineteen. We were looking in the mirror and we were like, "Why are we doing this? This is, this is crazy."

But I think we were so convinced about the vision. We just like couldn't believe that the vision would not-

Yep

... come true. So we stuck with it. So fast-forward to twenty twenty-two, the pieces started coming together. We realized that we could start building something that felt more like a language tutor, that could give you feedback, that could start explaining to you why you did something wrong.

And that was act two of Speak, a true English tutor.

This is something that a lot of founders struggle with today. It's like I'm kinda building something hoping that the models get better later.

Yeah.

How did you feel once the models got better? Did you feel like, "Okay, I am ahead of the curve because I built all this history of building product and like doing all this work?" Or did you almost feel like, "Okay, we spent all this money and time building these models, and now we're just gonna use Whisper"?

It was purely positive for us. We still kept using our custom ASR system because it was streaming real time really fast, really well fine-tuned. Whisper wasn't streaming, so it was a different use case. We used it for the more spontaneous stuff, and I think in almost every way, we were just really excited because pretty directly as the frontier of model intelligence improved, it would just unlock things on our roadmap that were locked before, if that makes sense.

And we still really operate in that mode today, where we take a model and then we try to think about, okay, how do we saturate model capability by building product on top of it? And then it happens again, right?

And then we build and saturate the model capability again. I think that's a really cool paradigm to like, you know, think about. But all the LM stuff basically allowed us to build a tutor for English, and we still didn't have like real-time voice, for example, right?

But the barriers are coming down now. Obviously, it's a really hot topic. We're actively building out a real-time voice platform that we can build a lot of more verticalized specific lesson experiences on top of that I'm super, super excited about.

I don't think they're going to replace our current lessons. They're going to be more immersive, just a different thing probably for more advanced learners.

Still language learning, though, not broadening out from language.

Yeah. So I think that language learning is interesting because it is so universal. Ninety-nine percent of people you know have certainly tried to learn a language, and it's so hard, right? Becoming fluent just has a huge failure rate, and it's something people are willing to pay for.

So I think that has been just like a pretty amazing beachhead for us, and I think we'll be doing language learning for a long time. There's a huge, huge, huge company to be built here. But our even longer-term ambition is really this idea that even beyond language, we think AI will reinvent how people learn anything, right?

It already has for me, right? I use ChatGPT to learn things every ten minutes, and I think I'm just naturally like a very curious person, so whenever I'm thinking about something, I want to know more about it, and then I'll naturally go to ChatGPT, and then I'll learn about it.

It's unlocked this like entirely new dimension of learning, and I'm spending way more time learning as well as an adult, which is really cool, and I wanna bring that in a more sort of structured, systematic way to everyone.

So I think that that's like the vision beyond language.

I'm curious to sort of double-click onto just the tech side.

Mm-hmm.

We talked a little bit about the c- the content that you, that you own and develop in-house.

Yeah.

And we talked a little bit about the onboarding memory. I assume that you have conversational memory as you, as you go, right? As y- And any other major pieces of the puzzle that really unlocked it for you?

So there's a few things I can talk about. I think one thing is, in order to go from teaching English to teaching a bunch more languages, we needed to really figure out more direct AI content generation. That was a pretty-- Right?

Because it's hard to scale, like our little studio in LA where we shoot a lot of the video lessons. Um, all of the scripts were written manually before by our content team. But we want like a hundred x more content, right?

And ten x more languages. Eventually a hundred x more language pairs, which is how we think about it. It's like, what's your native language, and then what language are you learning? And really, the only way to do that is to make it more AI-generated and, you know, very much like a AI-native company.

We wanna be on a frontier here. We want to keep a small team and to have as much leverage as possible through these types of tools. So that's a big active area where we're building out, I think, using...

You know, people overuse the word agent, but we have a tutor agent, we have a curriculum writing agent, we have a giant LM-based pipeline that creates curriculum, scaffolds it in the right way, writes the lessons themselves. That's a big active area that Will basically help us to scale to a lot more markets and a lot more languages.

So that's, like, one big thing. Another big thing is we care a lot about fluency, obviously. Specifically, we want to be able to quantify how fluent you are. So if you're learning Spanish, it's like, okay, what, what does it mean to be fluent, right?

And-

There's no real-world test for that.

We care about real-world fluency, your ability to go to Mexico City and go to a street taco stand and actually order, right? That's very functional fluency in one aspect. You might be really good at that, but be completely unable to, like, talk about your family, right?

So the frontier of fluency is very jagged, but we're very pragmatic, and we care a lot about meeting user goals and helping them become fluent at what they care about. And we're thinking a lot about, okay, how do you quantify that?

How do you actually store a knowledge graph of everything you know about Spanish in terms of the vocabulary you know or you don't know, the s- you know, the patterns that you know or you don't know, the mistakes you made using Speak over the last month that are clustered.

You said the magic word of knowledge graphs. Uh, is that-

Yeah

... live? Is, is that experimental?

There are aspects of it that are live, and it's, it's a very sort of multidimensional system where we think of it as there are many aspects of fluency, right? There's many subscores. And we have a few of them that are currently live, and we're actively developing other aspects of it, and then all those will fold up into a more holistic fluency score.

The idea is that eventually, once we have a complete enough picture, everything will fold up into a number that we call the Speak score, that is a very sort of holistic measure of just, like, how good are you at Spanish, right?

And obviously, fifty-four is kinda meaningless by itself, but it does give you a general sense, right? Like, being at fifty-four versus being at five is very different, right?

Yeah.

And I think everyone can kind of, like, intuitively understand that.

And surprising- like, I, I would've grounded it more in real world, like, we will get you to pass this exam that is a standard, that is, like, the ESL standard or whatever.

So the way that we think about that is-

Yeah

... we don't really teach for the test. I think it's possible in the future that we'll do a test-prep product. But in general, we care about real-world proficiency in various functional situations. So the way that we think about it is, if you're at this level, then these are the things you can do, right?

So it is exactly that.

We have that a lot in Italy. I grew up in Italy, so-

Uh-huh

... English is my second language, and there's a lot of people that pass a lot of tests and, like, get high grades in all the classes, and then they travel to the US and the UK, and it's, like, hard to speak because-

Yeah, totally

... they don't. Uh, you know-

Yeah

... I, I feel like the, the hard part is, like, being in the conversation, you know? It's, uh ... I, I think, like, when I started, my written and reading was, like, much higher than my conversation-

Yeah

... which, like, doesn't really help you if you're, like, traveling somewhere.

That, that's me for Chinese because my, my parents spoke Mandarin to me growing up, so I can understand, like, a nontrivial amount, but I, I'm very bad at speaking.

Mm.

Yeah.

Oh.

I heard there's a good language learning product for this.

I have one question on the course generation.

Yeah.

How do you eval that product? Like, uh, when you're asking the AI to generate courses, how do you figure out the courses are gonna be good?

Rely very heavily on our content team, and we are trying to build out an eval suite. It's really hard.

Right.

There's ... The illustrative example here is that as we try to hire and train new content writers on our content team, it's so nuanced. There's many different aspects of training them in the Speak method and how to write the right types of lessons and articulating why this form of lesson, which is subtly different from this other form of lesson, is better, right?

So we try as hard as we can to articulate that. So I think, like, forming, like, a sense of evals, using model graded evals like that, that's one piece of it. And I also think, like, in the future, a really good curriculum or lesson writer agent will probably be, like, reinforcement fine-tuned on a lot of our internal data as well.

Yeah.

That's something we're experimenting with, but it's still pretty early.

This seems like a great example of, like, you know, AI removing jobs, which is like, oh, you're creating the courses with AI, you don't have a person. But it's actually like instead of one person creating two courses, like, reviewing fifty courses-

Yeah

... that the AI generates.

Yeah.

That's kinda how you're seeing the content team.

The way that we see it, really not just for cr- for our content team members, but also I think it's perfectly applicable to engineering, is that it's, it's leverage. It just allows you to do a hundred x in the same amount of time.

We still need human review of the syllabus, the curriculum, the specific lines, et cetera. But the hope is that this will allow us to launch a hundred x more courses.

A lot of, um, language is colloquial. I think the, the way that you put it on one of our episodes one time was the Italian that is taught in school is not the Italian Italians speak.

Yeah.

How much of that do you adjust for informal versus formal?

Entirely. That's one of our fundamental tenets, which is that we don't teach textbook English or textbook language.

Oh.

Like, we try very hard to-

Teach Gen Z slang.

We don't go quite that far, but-

Like slaking.

But we, we try to teach very casual conversational language that is actually what real people use. And like you said, that's usually very, very different. Like, if you pick up, like, a typical English textbook in Korea, it's all really traditional and weird formulations, and it's not how people actually speak.

Yeah.

I know you're gonna release Italian soon, so I can give you a hand on that. I know in the US there's not that many dialects. There's, like, accents, but, like, most of the language is like ver-- like, the words that people use are similar.

Because I know, for example, Spanish is like, you know, Spanish spoken in Argentina is, like, very different than Spanish spoken in Mexico. How do you kinda adjust for that? Or maybe you don't, but-

So I would say that- For example, currently we teach American English, standard American English. We don't really teach other accents or other dialects. For now, given how small we are, we just have to be pragmatic and teach in the direction that most people want and most of our users know.

So we've made those decisions, like, on the content team side for American, Spanish, every language that we're teaching. But I do expect that in the future we're gonna get a lot more sharply differentiated. Like, if you wanna learn British English, then we'll teach you British English.

We'll teach you how to pronounce it, et cetera. I think all of that feels like something that Superhuman language t- you know, tutors should be able to do.

I just think it'd be very funny if all the Koreans had, like, a very distinct Southern accent.

Yeah.

Uh, it'd be, it'd be great. Make that happen.

Yeah.

I do think about this because, uh, me, you know, obviously there's a moving of the goalposts. Like, now that we have this, now we want the next thing.

Yeah.

And obviously people who are English as a second language always have an accent. Like, I haven't ... Like, a lot of people think I don't have an accent, but if you know any Singaporeans, you know I'm, I'm Singaporean.

How much accent training is important, right? Like, I think, like, actually that does help a lot with f- for people.

Yeah.

And you cannot tokenize accents yet.

Yes, that's right. So I have two main thoughts on this. I think the first one is that communication and your ability to speak spontaneously and get a s- a concept across, an idea across, is almost fully orthogonal to pronunciation.

You can be really bad at pronunciation but still communicate effectively. So a lot of the current core product experience is about just speak as much as possible, make mistakes, don't worry about screwing something up on the accent or the pronunciation side.

Yeah.

The important thing is that you literally move your mouth and you make the sounds, right? And it turns out there's, like, a really key psychological barrier there where people are just not willing to do this in front of a human, even if it's a human that is a teacher that you're paying, right?

So a lot of the core message of our marketing campaigns in many of our, like, biggest markets is along the lines of, like, you can make mistakes in this private space with Speak, and I think psychologically that's extremely powerful.

And then you can go and get it right more confidently in the real world after you practice with Speak. Now, having said that, people do care about their pronunciation and their accent, right? So we w- we have for English only right now a pronunciation coach that is basically like a fine-tuned version of wave2vec, which is a meta model, but we basically fine-tune it on a bunch of our own phonetic transcripts, like fine-tune data.

It works pretty well. It's currently for single words. We're going to expand it to full sentences, to more languages, et cetera. But I think that just if you look at, like, the pure market opportunity, our sense is that we really want to push people to just speak very freely as much as possible, you know, just get that volume up.

Yeah. Yeah. In terms of immersing language learning in the real world, one of the more interesting approaches that people keep trying is to have, let's say like a Chrome extension or something on top of a page. I think Toucan was doing this.

There's a bunch of those, yeah.

Yeah.

Yeah.

And then there was another one I saw recently which was like watch a YouTube video and it'll transcribe for you but randomly mask out words.

I saw that too, yeah, yeah. Yeah.

Uh, that was like a h- Show Hacker News.

Yeah.

Do those work?

There's kind of the question of is, you know, is that the right product, right?

Yeah.

I don't think-

So, so basically the difference is your content or real world content, right? Obviously you want real world content.

I think that for work, right? So for Speak for Business, for the, for the B2B product, another part of the vision is really, like, what should a Superhuman language tutor be able to do? It should probably be able to handle kids as well as a Samsung employee that wants to transfer to the US office and wants to use Speak for work, right?

So our view there is that it's the same product. It's a different distribution mechanism, right? Consumer versus B2B. And I think that we will eventually build something like a Mac app. Maybe it'll be integrated with a browser in some way.

We're not really sure yet. But obviously in order to apply it to your day-to-day, there needs to be some way to hook into your actual sort of work documents, whatever. That's a whole can of worms. Um, we are actively thinking about it, but I think my sense is that it's not clear to me that any of these products have really taken off, and I think that there's many other approaches that are possible.

I don't have the answer, but like another example, very hypothetical future world is maybe OpenAI, you know, the, the new Jony Ive thing will come out with some hardware that-

Ooh

... will be listening to you all day and then we can, you know, give you some sort of like very deep analysis that is integrated with the Speak app at the end of the day or like-

Yeah

... you know, the end of the week, whatever. I don't know.

Okay, one more time since you brought that up. I'm sure you don't, actually they haven't told you anything, but what-

I don't know anything

... what's it gonna be?

I don't know anything.

It's like a very, like this is the number one topic in all the parties I go to now.

Really?

Yeah.

What's the most compelling idea you've heard?

Okay, so there's, there's people that say Jony hates wearables.

Yeah. I've heard that too.

And I'm like, if it's not a wearable, then you've just made a second phone. I- in that case, just make a phone.

Yeah.

I thought they said it was g- I mean, didn't Sam say that it was g- he wanted to do a phone in the past?

That was in the far, that was like in the far past.

He says a lot of things.

He does say a lot of things.

Yes.

Okay. Anyway, I think wearable makes sense. I think the, the, the race is to capture context.

I mean, I, I have a wearable on.

Yeah, I, I've, we have a wearable here too.

Yeah.

Transcribe everything.

That transcribes everything?

Yeah.

That's cool.

Yeah, it's a previous episode of ours with, with the-

Oh, cool

... um, I can hook you up if you want.

Yeah.

But yeah, I think, like, it's something that a lot of people are interested obviously 'cause it's a huge bet by them and, uh, yeah. Curious. Okay, you mentioned video. I just wanted to double-click on that a little bit.

I'm sure engagement very high for video because people love to watch video. I thought that Speak would be one of those places where, like, you just kinda leave it in your pocket, you walk, you take, you take a walk, learn to speak.

Probably that's not true?

What we've done so far is part of the course experience is a teacher video. We've tested other, more audio-forward types as well. We found that, of course, like you said, video is very engaging, but at the same time, we have a lot of users that do want to be able to walk around with the phone locked in their pocket.

So doing something that is more like voice mode with optional v- uh, you know-

Yeah

... visuals, I think is really good. I think there's huge opportunity for a better way to learn things like listening comprehension. So I took German in grad school for two years, and I thought I was getting somewhere, but any time I listen to a native German speaker, it's so fast, it's, it's completely on a different level.

Mm.

And I think you can imagine a plethora of really cool experiences that feel kind of like you're listening to a podcast, but it's all AI-generated, it's fully controllable, it's integrated with the app. You know, there's something there for sure.

Yeah.

Don't wanna do AI podcast, man. We're cooked.

It's okay. We'll, we'll document, uh, the, the own ending. I, I, I mean, I think when that happens, we just end the show. Like, why not? Like... To zoom out a little bit, in the pretty near future, multimodal models will cross the threshold where they will be able to generate images a lot faster than they currently are, maybe somewhat close to real time even, right?

And audio at the same time, text at the same time, and you can imagine just like a very powerful multimodal tutor that can kind of do it all at once where there's an audio track, and then if the teacher's teaching you something, with the right timing, it chooses, "Okay, at this point, I'm about to introduce a new concept, so I'm going to show the word on screen so that the user can see how it's spelled," right?

There's a lot there. You can do generative UI. A lot of nuance there where it's easy to do it badly, but to do it well requires a fair amount of reasoning and mental modeling of what the user knows.

Yeah.

Which feeds into what you need to show at what time. So that's probably gonna have to be like a pretty parallel set of systems.

Have you spent any time looking at this like, uh, you know, like V03, where you do video plus audio at the same time on how you can tweak the audio part versus the video part? Because I can imagine you might work on a video part, and then you wanna change the audio generation model.

I don't actually know how the model works inside on like how much you can tweak just the language.

We haven't really looked at the video stuff much. We basically think that we're very bandwidth-constrained, right? So we're just scaling and trying to hire as fast as possible like everyone else is. And as a result, we're really focusing on just like the most in-reach, highest impact things.

I do think that the barriers are coming down very fast for all of this sort of stuff. I'm just so excited about multimodality and where things are going here because imagine if you're learning Spanish, being able to look at an image that the model generates for you and then doing Q&A on it, right?

Like a beach scene, and then the model will ask you like, "Oh, how many people are running on the beach?" And then you have to sort of respond in the target language that you're learning. Very traditional language learning exercise, but you can imagine it being fully generative, which is really cool.

Awesome.

Lots of stuff like that.

The engineer in me worries about inference costs, but I think you can just kinda sweep that under the rug for now.

Yeah.

See if it works first.

Yeah.

And then, and then you can worry about costs.

Yes.

You mentioned a real-time voice platform. Uh, I just wanna give you the platform to, heh, platform, to talk more about that. Just like, uh, you mentioned, for example, that you're a very heavy user of the real-time API from OpenAI, and you build a bunch of tooling around it.

Yeah. So we, last year, had early access to the real-time API, and there's a very obvious sort of use case for language learning. I think one common theme that has just been pretty awesome since LLMs came out is that language learning as an application is just a really good fit for LLMs, all these model types, in almost every way, which has been just really great for Speak specifically.

For real time, I think the audio piece promises to really like infuse almost every surface in the app. You can imagine this is the primary way that you talk to your tutor, right? And an additional complication is that it needs to be multilingual, and there needs to be code switching.

So that's a pretty frontier problem right now, right? So like, I should be able, if I'm learning Spanish, to speak both English and Spanish and vice versa from the model. That's a pretty hard TTS problem today. It's actually like only a few models are able to speak two languages in the same sentence-

You can have a router model-

And then, and pronounce them properly. Sorry?

You can have a router model, like a tiny little router model guess which language first and then route.

Well, the problem is that there's, you can have a sub-word in- ... in a single sentence-

Yes

... in a different language.

Yeah.

So you can't just concatenate either-

Yeah

... because it won't sound right.

Yeah.

Right? It won't sound natural. That's not how humans do it. So this needs to be like a, like a very native, controllable audio, you know, function.

Yeah.

But we are in the process of building a variety of experiences on top of the real-time API. I wanna clarify that actually nothing is in production yet, mostly for price reasons, frankly. The pricing model of the real-time API makes more sense for something like a customer support agent, where you're very directly replacing somebody that you would pay hourly otherwise, and that's how you're seeing the price model for a lot of these initial agents work out.

For us, we want our users to be able to do these real-time role plays and have these conversations for many hours a day, right, if they want. Getting cost under control is definitely a pretty key consideration right now, but we are pretty close, maybe actually a- Even by the time that this episode is released, we'll have something live.

But we have a, what I think is a really cool application of the real-time API, which is basically a new instructional lesson where it's the model actually teaching you something, like a new language concept, and it's intended to sort of augment slash play the same role as our current video lessons, which are the instructional lesson type.

And it's interactive, obviously. At certain points in the three to five minute lesson, you're interacting with the real-time API. It's semi on guardrails. There was a lot of scaffolding we needed to build to basically, number one, switch between the interactive and non-interactive portions of this lesson properly, if that makes sense, right?

There, there's, there's some portions where you're just listening or looking, and then some portions where you're actively in a short conversation, and we kind of swap back and forth. And we have, like, a bunch of sort of custom architecture and info around that.

And then there's also making the cost make sense or at least, like, semi make sense. And then there's a bunch of WebRTC infrastructure. We're at sort of, you know, not huge, but non-trivial scale either. So we definitely just-- it'll cost us millions of dollars if we do something wrong.

Yeah.

Yeah.

Do you do inference in Korea because of the, you know, latency and all that?

It's something that we have been increasingly paying attention to for all the real-time paths. Like, I would say two or three years ago, when real-time stuff was still quite nascent, users didn't really care as much. But I think now the standards have risen, right?

Like, latency has to be low. Everyone cares.

Do you have a hard latency budget for responses, or do you just kinda work it out? So for example, right, like, you have a knowledge graph that you're accessing, you have content that you're retrieving. There's a lot of stuff there.

And then, like, I, you know, maybe you're using a reasoning model, probably not, but, like, that all eats into the budget.

I will say that from the, like, real-time engineering side, everyone talks about, okay, submit user request to get agent audio response, like, first bytes, right, first audio bytes. What's that latency? And then we try to get that as low as possible.

I would argue that's actually, like, a vanity metric because what you don't take into account is how the VAD works. How do you do turn detection to detect when the user is finished speaking, right? Because that can easily add, like, another second if you do it badly, and nobody talks about that for some reason, right?

Like, what you need to measure is actually when does the user stop talking to when does the model first audio come, and usually that number is much larger. That is a very domain-specific problem. You can use, like, the semantic VAD on real-time API for regular English conversation, and that will basically classify at every token how likely it is that you're done speaking as a sort of normal conversational English speaker, like in this conversation.

That's fine, but it doesn't work at all for language learners, right? If I am trying to respond in a language that I'm learning- ... I'm gonna be hesitating halfway through- ... for ten seconds or more. Right? So it needs to be fully custom probably.

This is something that we're also actively working on, but that is actually, like, the dominating factor in perceived latency.

Coding, do you use Cursor, Windsurf, um, other autonomous agents?

It's kind of all of the above.

Yeah.

So I think, like, as the CTO, I view it as part of my responsibility to really set expectations, push everyone on the team, show them what's possible. We've been trying everything.

Yeah.

And I think we try to basically set the expectation that the frontier is moving so fast, it's deeply non-intuitive.

Mm-hmm.

If you've tried coding tools six months ago, and they weren't that great, especially if it's not TypeScript or Python, right?

It's like most apps are the most popular languages.

Yeah.

Like that's all it is.

We try to set a culture in the engineering team where usage of these tools as much as possible and as a default path is the expectation. And in hiring, we are now explicitly asking about this a lot, thinking about what are the types of people that are gonna be better, higher agency at trying these types of tools.

It's so important.

Before we zoom out, anything we missed about Speak that you really wanna highlight or something that people underrate about it?

One thing that I've always been really excited about is that I feel like a lot of the foundational pieces that we're building around knowledge graph, for example, a lot of these concepts should be applicable to not just learning language, but also other things in the future.

We're already starting to see the very beginnings of this on the B2B side, where a lot of it is more like management skills and hospitality skills, communication skills, more like true L&D for enterprise, less like core pure English proficiency.

So I think you were, you know, that's like obviously immediate neighborhood. But you can imagine many academic subjects, math, biology, et cetera, you know, schools work for. Um, super excited about that.

If I knew my employer was giving me a language tool, but then he was evaluating me on my management skills while learning the language- ... I might use it less just, you know.

Fair. Very fair.

You know, you wanna, you wanna, you wanna separate that out.

Yeah, very fair.

I agree overall that the knowledge graph problem is very important. We have a whole track on it for, for the conference, and I think that the amount of data can be so high. And actually, like-

Yeah

... you want to, you wanna generate relevant triplets. I, I assume you use the normal subject, predicate, object type.

It's a bit more custom than that because it's a bit more domain specific around the way that we conceptualize the vocabulary you know-

Yeah

... and the sentence patterns and so on.

Yeah.

So it's, it's more specifically around, like, language learning concepts, if you will.

Yeah.

Yeah.

But what I think we can extract from Speak, or as it is generalized as a framework, is, um, what I've been calling sort of like the Bloom's 2 Sigma Problem type thing, like the level adjusting tutor. Like, where are you at, let me adjust my thing to where you're at, and then I'll push you up to the next level.

And I think the knowledge graph is, is a part of it, but I don't know if th- that's all of it. I've never seen a working example.

We are approaching that problem from a few different angles. I think part of it is knowledge graph. Part of it is being very careful in how we structure the curriculum so that you're placed at the right level, so that the learning path itself, which has a foundational backbone because beginner to intermediate English learners actually, like, all need to know a bunch of similar concepts.

It isn't really until you get intermediate and more advanced where that starts to, like, more sharply diverge. And A0 through B1, I would say, there's a pretty well-defined, like, sort of linear path actually. A lot of the deep thinking that we've done around how do we structure the pedagogy is also s- super useful in terms of just, like, matching people to the right level.

And then you can take this backbone and then basically modify it based on the knowledge graph, on your system's knowledge of what the user is, like, bad at versus good at.

I think a lot of startups or ed- especially edtech, like, that is the core engine. Like, you know, once you do that, you can kind of teach anything.

Totally, yeah.

We have a few more broader fun questions.

Yeah.

Um, so speak.com.

Yeah.

Great domain. I looked it up. Voice.com got bought for $30 million in 2019.

Oh, my God.

Really? When?

2019.

Okay.

So-

Wow

... I don't know if you wanna share how much you paid for it, but-

It was a lot less. It was a lot less than that

... I, I figure it would be a lot less, but I'm curious if-

Uh, my estimate was 100K, but-

It was, it was more than that.

More than that. Wow.

Okay, I'm not gonna say any more about the numbers.

So what, what's the... Yeah, what was the sort? Was it easy?

Yeah.

Was it, did you use a broker? Like, we had, uh, you know, Dharmesh Shah from HubSpot, uh, who sold chat.com to OpenAI-

Yeah

... and he has a lot of very fancy domains.

That was like a $100 million deal or something, right?

That wa- that was very big.

Oh, wait, no, that was ai.com. Whatever. Um-

Uh, chat.com.

Oh, chat.com, okay.

Yeah.

We bought it several years ago. It felt very expensive for us at the time. It was a little bit of a crazy move, but I think we were very convinced that we needed a super strong consumer brand that was scalable globally, and that was just always our ambition.

Like, we want to be the way the next billion people learn languages, and we need speak.com. So we don't regret it.

It's, it's such a, such a great word, makes for great swag. Very nice decision. Yeah, a couple other fun, fun questions. Any fun Korean celebrity stories 'cause you work with so many influencers?

We have a bunch baking right now.

Okay.

But I think it was, you know, some- something more generally that has just been so fun on the journey. So we, we would visit Seoul every year.

Yeah.

And seeing Speak go from nothing to the first time we saw somebody on the street using Speak. To now our main teacher in the app is, like, a mini celebrity. People come up to her on the street as she's just walking around Seoul and recognize her from the app, which is really cool.

Now we do a lot of advertising. We do billboards, TV commercials. We work with big influencers and so on. So just, like, seeing the scale of that has me kind of, like, in awe. It's, like, really cool, um, just to see something that used to be nothing.

Yeah, I wanted you to name drop, like, Blackpink or I don't know.

I don't know.

Look, there, there's, there's some stuff baking right now.

Yeah, okay. All right.

We talked about the Thiel Fellowship.

Yeah.

On your LinkedIn, you kinda have this hole between 2012 and 2016-

Yeah

... which you talked about. You did some startups. Any of them that you wanna share? Like, ideas that you worked on that you thought were cool.

Maybe it was just early, but, you know-

Well, yeah, what people should revisit

... try again.

I've always been interested in learning and education. One of the other failed startups that I did in that time, um, was... It feels silly to even talk about this because it amounted to nothing, but it was called Bloom.

You know, the Bloom's 2 Sigma Problem.

Oh, yeah.

It was actually, like, named after that, and we were trying to, to basically build, like, a better adult learning platform and have really cool interactive JavaScript widgets for various concepts that you could learn. Didn't find PMF. I was young and didn't really know anything about business at the time either.

But I think that the common thread through actually, like, everything that I've been interested in since leaving grad school has been how do we build software, build tools that help people learn things more effectively and better and faster.

And now I feel very lucky to be in this position because obviously AI is the ultimate version of that, right? And it's been completely transformative for me personally because I just get a lot of just inherent fun and pleasure out of being able to, like, think of a concept and then, oh, now I can talk to this omniscient LLM that can tell me more about it, and I'm really good at asking the right follow-up questions that I want to know.

Um, so that, that's been completely transformative for me.

Do you get a lot of, like, people using Speak for therapy? Like, you know, 'cause it's not meant to be that, but since you have inference, they will use it.

In 2023, when we first launched our AI role plays using GPT-4, back then, people were way more concerned about safety, right? And, you know, obviously the models now are much better at, like, refusals, and the line is sharper between what's appropriate and not.

But we did see a lot of our first users start to put in pretty questionable custom scenarios. Um- ... you probably guessed.

Yeah.

And, you know, uh, like this was something we expected, but I think seeing the logs in person is, like, very different.

Got it. Um-

Some shocking stuff in there.

Last couple questions. One on Andre. You talked to him when, in your machine learning journey. Um, he's also-

That was a long time ago, yeah

... he's also working on edtech now.

Yeah.

Uh, I don't know if you've ever, ever had conversations with him on-

No, I haven't

He's also interested in language learning, by the way, you know?

One thing that I think we didn't really realize early on or, like, fully internalize at least, was just, like, how deep the market is.

Say more.

It was so universal where we really struggled to do some of the basic startup stuff around define your, like-

ICP

... ideal customer profile-

Yeah

... and, and like, you know, segment your users because our users were everyone. Like, we, we had parents using it with their kids, we had really old people using it, we had people using it for work. So that was kind of, like, mind-boggling.

You still did customer segmentation or are you saying it doesn't matter?

I'm saying it was hard to do.

Yeah.

Like, we tried, and we have a sweet spot in Korea. It's, like, 25 to 45, more professional, more white collar, but it's very... Where it's like-

Yeah

... like, a very long tail on either side. Yeah, I think it, you know, it's a huge market, and I think it's a very special moment in time right now where it's obvious that a lot of the tech is here.

I think it's really good for humanity if we make a lot of progress here. So I'm really excited for his company, too.

We started asking about the Thiel Fellowship.

Yeah.

So maybe we can wrap with one of Thiel's favorite questions, which is, uh, what's something you believe in today that most people would not agree with you on?

I think that people, if you recall, expected the world to kind of explode when GPT-4 came out, and, you know, like, everything would change. And I think if you, like, go to another state outside of the Bay Area, probably even in California outside of the Bay Area, and then you ask somebody how much their life has materially changed, it's, like, pretty close to zero.

Real-world inertia is enormous. Obviously, AI is probably the most transformative technology we've ever built, but I think in a very real sense, the world hasn't changed that much either, and that's a really weird thing, right? So I think we need more builders, we need more people building applications.

It's weird to me that Speak is actually, like, not that many net new consumer AI-native applications at scale. Like, there should be way more. I would love for there to be way more. Consumer is hard.

Yeah. I'm intimidated, but like you know.

It was just like there was never any alternative for us.

Yeah.

Like I said before.

You didn't have a choice.

Yeah.

But also, you're very smart. But also, maybe you have some growth hack things that you can advise people on that, like, that people could, could learn. But yeah, I, I agree. I, I, think like, the general take actually is this is what we want, which is slow take-off, short timeline.

That's fair.

Right? The, this is the two by two that everyone always talks about in AI safety. You're seeing slow takeoff, and like, maybe don't complain. We, like, we, we have a heads-up because... Or, you know, Dario's right, and like, half of us lose our jobs in the next two years.

Yeah. It's a, it's, it's so hard to predict. Yeah. Sometimes I get AI anxiety.

Uh-huh.

And then I just-

You get anxiety?

Yeah.

Okay.

Then I just focus on our users.

That's a perfect place to wrap. Thank you so much for taking the time.

Yeah.

Thank you very much.

Thank you guys so much. This was great.