By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
YC Root AccessBuilding the AI Platform for Enterprise Software Implementations
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
Great conversations run long. Their best ideas don't have to.
uListen is free on iPhone, iPad, Android, Chrome, and Claude.
See howTranscript
30 min read · 5,746 words- 0:00 – 3:28
AI for Enterprise Software Implementations
- PKPete Koomen
[upbeat music] Hi, I'm Pete Koomen, and I'm a partner at YC. I'm here today with the founders of Auctor from the Spring '25 batch. Hi, guys. Welcome.
- AFAuctor founders
Hey. Hey. Thanks for having us.
- PKPete Koomen
Uh, so to get us started, what is Auctor?
- AFAuctor founders
Yeah. So Auctor is an AI platform for software implementations. So when you think about a large enterprise, uh, and they're going through a big transformation with a piece of software, like a ServiceNow, a Salesforce, SAP, et cetera, there's a lot that goes into that. And many times, the hardest part of these large-scale software implementations isn't necessarily just the technology piece. It's also being able to connect it to what the business needs, the requirements, and maintaining that context from initial conversations all the way through to go live. Could be, like, months down the line, right? Um, so for us, as a platform, we're able to connect it across that entire life cycle, so even when people leave after a project is done, you maintain it. So really spanning from initial discovery all the way through design, configuration, and go live. I'd even say, like, it's not necessarily even just, like, the last mile. In fact, like, our original wedge into the problem was, like, upstream of the last mile. Like, if you think about the last mile as doing, like, the build or the configuration, that's not where we started. Where we started was we had identified this wedge into this big problem space that in these implementations, a lot of the times why they fail or they get extended or they go overrun is because of the misalignment in requirements and design in the very beginning of the implementation, not even when it comes to the coding part. And so our wedge in, especially when we applied to YC, was solving this piece, this upstream piece, and then it's pulled us more downstream into, like, configuration.
- PKPete Koomen
So one of the things that I remember standing out about your application was that you seemed really obsessed with this problem. How did you discover this problem in the first place?
- AFAuctor founders
For all of us, we're just, like, super curious and have always, like, loved building. I think that was something that probably resonated a lot. Um, and always looking for, like, problems to solve. And so how we stumbled across this was I have a really close friend of mine, um, who works at Deloitte-
- PKPete Koomen
Mm-hmm
- AFAuctor founders
... which is a really large global system integrator.
- PKPete Koomen
Mm-hmm.
- AFAuctor founders
And while he was at Deloitte, he was staffed on this large-scale ERP transformation for one of the, the 50 states, and it was, like, a multi-year project, million-- I mean, hundreds of millions of dollars. And every time I would catch up with him while he was staffed on this project, he expressed a lot of discontent, uh, in terms of just, like, a lot of the internal processes and how he saw work being done. And this is also when the models were getting quite good. It was, like, GPT-3.5, 4, and it was, like, getting the traction within the enterprise of, like, actual usability. And I just thought to myself, hearing him talk about these super manual processes and this really large-scale transformation that was millions of dollars, and they were using, like, Word and Excel sheets. And I'm like, "There's no way." And so that's, that was, like, the seed of the idea and what introduced us to this problem space. And then basically, over two months, all I did was I talked to dozens and dozens of services leaders.
- PKPete Koomen
Hmm.
- AFAuctor founders
People that were system integrators, whether that be at a boutique shop or a GSI or even internal IT teams, and I got an understanding of the workflow and the pain points, and it kept coming back to what I was talking with my, with my buddy about. Very manual, very legacy, in a very large industry, all while this new technology was on the horizon. And so we wanted
- 3:28 – 6:46
Finding the Real Problem to Solve
- AFAuctor founders
to do something about it.
- PKPete Koomen
So you did a whole bunch of these calls. What did you end up with at the end of it? Like, what was the idea?
- AFAuctor founders
Yeah, yeah. The first, like, 20 calls was just, like, asking dumb questions. Like, like, the most basic questions on, like, the industry itself. After, like, the 20 or 30th conversation, like, I started speaking the same language as them. I started asking much more pointed questions. I would go from one call, take what they said, literally parrot it, and then say, "Hey, like, this is what we're s- this is what I'm seeing. Like, what do you think?" And it became a lot more tactical. And more or less around, like, the 30th conversation, on a piece of paper, I wrote down what I believed these models could solve from the pain I kept hearing over and over again. And at first, what was on that piece of paper was, "Let me build configuration agents for X piece of software." So config agents for ServiceNow, config agents for SAP, config agents for Salesforce. And that was the original idea for Auctor. And I took that piece of paper back to the people I kept having these conversations with, and I said, like, "Pete, what do you think?" Like, and I would, I would, I would pull up my screen, share my screen. It would be a Google Doc, and it would be, like, in writing, and they would- we would iterate on it. And what they said was, like... like, "Well, like, this would be helpful for, for, for helping streamline these software implementations. No doubt about it. But, like, this doesn't solve the root cause of a lot of my pain and suffering." I'm like, "Well, what do you mean? Like, like, config is, is such a big piece of it." And they said, to what I was saying in the beginning, like, "A lot of the pain comes from the misalignment in requirements and design before we even go into the build."
- PKPete Koomen
Hmm.
- AFAuctor founders
And I'm like, "Oh, wow." And so we iterated on that and, uh, took that piece of paper back to the 50 people, 50-ish people, and they were like, "This is incredible." Right? I had one person who worked at a firm where they were like, "I've been in the industry for 30 years, and no one's been able to solve this problem of, like, traceability between requirements through design into configuration."
- PKPete Koomen
Hmm.
- AFAuctor founders
I'm like, "Okay, like, that's a problem worth solving." And so that's when we as co-founders came together, built an MVP, and, you know, got it in front of them and-
- PKPete Koomen
And then you applied to YC and you got in. Tell the story of the batch. You had an unusual batch experience.
- AFAuctor founders
For us, like, I, I remember texting you about this when we were thinking about, like, housing and, um, you were really encouraging on getting somewhere near Dogpatch, uh, which makes sense, right? Close to the YC office. Um, but Sky being f- the fact that he's from the Bay Area, like, luckily he had an apartment, uh, in Sunset, which was, uh- 40, like 40, 30 minutes from the office. [laughs] It was, like, really far away. Um, but I actually think that, like- Came to our advantage
- AFAuctor founders
It was almost, i- in some ways, it was a good distance where we were, I mean, we were in the apartment all [laughs] all day, basically, taking sales calls, building product, um, and it really allowed us to, I think, hyper-focus.
- PKPete Koomen
Yeah, you guys just basically went into hermit mode-
- AFAuctor founders
Yeah
- PKPete Koomen
... as, as I recall.
- AFAuctor founders
Exactly. Exactly.
- AFAuctor founders
We were under a-
- AFAuctor founders
The, the only two places we would go would be the YC office, and then this one deli called George's by the Zoo, and those would be our [laughs] only two times we would leave the apartment. You know, we, we were very focused on our, on our goals. There was, like, very little distractions. We weren't thinking about what others may be doing, and I think it helped us really just hone down and, and progress as quickly as we could.
- 6:46 – 10:13
The Dog Photo That Booked Hundreds of Demos
- PKPete Koomen
And you guys launched early in the... You f- you, you took the advice and you launched early in the batch.
- AFAuctor founders
Yeah.
- PKPete Koomen
And I think you had a successful launch.
- AFAuctor founders
Yeah.
- PKPete Koomen
Tell us about that.
- AFAuctor founders
That, that very pivotal launch. The advice is, like, launch early, right? Launch fast. Um, and so for us, we, we took that very literally, and, like, we optimized all around, like, the launch. 'Cause, like, for us, when we think about, like, YC, it's a very short amount of time, and you wanna get a lot done. And so even when it comes to, like, sales, like, setting up a whole, like, sales motion over the course of two months, like, codifying it and doing all, like, th- that, that's not gonna happen. And so it's like, how do you drive as much inbound as humanly possible for this problem that you're solving as a small YC company? Hard problem. And so, like, when it came to the launch, uh, we, we viewed it in two different aspects. We had the YC, infamous YC sign launch that we could do, where we could post it.
- AFAuctor founders
Mm-hmm.
- AFAuctor founders
And then there's, like, the more official launch that we would do with YC, where we do the video, and YC would post it. So we did the sign launch probably by the second or third week of YC, m- probably, like, second week. And we were like, "Okay, how do we make this as, like, different and notable as possible?" And given that Sky's from the Bay, he has a beautiful dog-
- AFAuctor founders
[laughs] Summer
- AFAuctor founders
... uh, named Summer.
- AFAuctor founders
Yeah.
- AFAuctor founders
And we were like, "Let's just, like, have Summer in the photo."
- AFAuctor founders
Yeah.
- AFAuctor founders
And so it was us, the YC sign, and then this, like, gorgeous, like, golden retriever.
- AFAuctor founders
Golden retriever, yeah.
- AFAuctor founders
Yeah, like, golden retriever.
- AFAuctor founders
I, I think, too, that, so I... This is a fun fact. I used to, like, run a video editing business-
- AFAuctor founders
Yeah. [laughs]
- AFAuctor founders
... in, in high school, and so I learned a lot about, you know, virality, I guess. And I think that the two main things that usually elicit, you know, posts to do very well is, one, I think it's a little bit of, like, a scroll stopper, of like, oh, like, do a double take [laughs] on, on the social media platform. And then two, also, like, eliciting some type of emotion of like-
- AFAuctor founders
Yes
- AFAuctor founders
... oh, that's super cute, or that's super, super, um, like it makes, makes me feel happy. Um, and there's, [laughs] I think, maybe no better way to do that in a, in a photo than having a, a cute pet [laughs] as a member of the team as well, so.
- AFAuctor founders
We called her the chief bark officer.
- AFAuctor founders
[laughs]
- AFAuctor founders
And everyone loved that. So but, like, in all seriousness, though, like, like, that photo alone almost got a milli- like, that post almost got a million-
- AFAuctor founders
Yeah
- AFAuctor founders
... impressions-
- AFAuctor founders
Hmm
- AFAuctor founders
... on LinkedIn.
- AFAuctor founders
Hmm.
- AFAuctor founders
Third week of YC, uh, second, third, uh, you know. And it, like, drove s- uh, like, literally within three days, we had probably, like, 300 demos booked, or like 200, 300 demos booked. Granted, like, most of it was probably, like, not qualified or, like, you know, not, not relevant, but, like, it drove a ton of attention. Uh, and, and e- and even, like, some of our, like, large enterprise contracts that we have today were because they somehow saw that post, and it got on their feed, and they just read the problem statement and were like, "Wow, this is interesting," right? So that was the first, first launch, to your question. And then the second launch came, you know, probably, like, the, at the exact halfway mark of, of YC, 'cause we wanted to time it-
- 10:13 – 13:59
When Building for Demos Backfires
- PKPete Koomen
Yeah, so, so tell us about your, your kind of mode of operation. You, you had hundreds of, of demos booked on the calendar.
- AFAuctor founders
Yeah.
- PKPete Koomen
I think you were doing most or all of the demos, and then-
- AFAuctor founders
Yeah
- PKPete Koomen
... you two were, were building product. What, what was... Did you have a product at this point?
- AFAuctor founders
[laughs] Yeah.
- PKPete Koomen
Where, where, where were you demoing?
- AFAuctor founders
I mean, you sat, like, across from me, so I'll let you, like, talk about, like-
- AFAuctor founders
[laughs]
- AFAuctor founders
... what the demo experience was like. But it was, like, very, like, FDE-like. [laughs]
- AFAuctor founders
Yeah, I think, I, I think it's very interesting when we're, you know, when you're kind of at that stage of company and, um, there's not a lot of customers really to be listening from at that point. You know, we, we only had a handful that were on the platform. Um, so it was very, very heavily skewed, um, towards feedback that we were hearing from the sales side. And yeah, the, the way that we would operate in, in our product loop, it was extremely scrappy, where me and Sky were sitting across from Will. We could literally hear, you know, the feedback and the complaints or, or the pushback from the calls that he was having, and then that night we would just ship out, like, some kind of remediation or, or some kind of extension to our product that, that would help address it. So we were very, very focused on, okay, what can we do on the product side to help drive revenue as much as possible?
- AFAuctor founders
Yeah.
- PKPete Koomen
So basically you just built for the demos over and over and over again.
- AFAuctor founders
100%.
- AFAuctor founders
Exactly.
- AFAuctor founders
Yeah.
- AFAuctor founders
Yeah.
- PKPete Koomen
Yes. And you launched again, and I think you got, you got a, a similar response.
- AFAuctor founders
Yeah.
- PKPete Koomen
You got, you had a lot more demos.
- AFAuctor founders
Not, not, not a million. I think we got, like, 400, 500K impressions, which is still great. So yeah, it was-
- PKPete Koomen
But you kept launching. You kept demoing. You kept building.
- AFAuctor founders
Yes.
- PKPete Koomen
How did the batch end for you guys?
- AFAuctor founders
From, like, a YC company going through YC objective standpoint, I think it ended well. Like, we, we were able to raise a seed round that we were happy about from a firm that we were excited about. It set us up on the right foot, and, like, for us, we also decided to make the move from SF to New York.
- PKPete Koomen
But, but tell us about, like, did you have customers? Did you have revenue?
- AFAuctor founders
Oh, yeah.
- PKPete Koomen
What was the, what did the product look like, you know, after hundreds of kind of demo iterations?
- AFAuctor founders
Yes.
- AFAuctor founders
So we had customers. Uh, I don't know how many customers. The product was a Frankenstein of demo features, because when you're shipping at that speed based on just pure- Gut reactions from a sales call. Like you're not root causing why they are asking for a feature. Like th- it's not like actually thinking like a, a like product. It's, it's more just like reactionary. And so by the end of YC, we had sold this vision and like these one-off features that they thought like w- would sell well, but like the, the customers that bought into that didn't necessarily know that's what they needed or whether or not it wasn't what they needed. And so like from a product standpoint-
- 13:59 – 18:09
The Rewrite That Increased Usage 5–10x
- PKPete Koomen
So, so where did that leave you? You, you moved to New York. You had, you, at this point you had customers and revenue, and you had a product that just sounds like-
- AFAuctor founders
[chuckles]
- PKPete Koomen
... a monster.
- AFAuctor founders
Frankenstein.
- PKPete Koomen
Yeah. Um, what did you do?
- AFAuctor founders
Well, there was one very pivotal week, I would say, where we had a certain series of customer calls that lined up, um, I think looking back now, very fortunately of, um, basically a lot of our executive sponsors who we have very fantastic relationships by the way. I think by, because of how quickly we would iterate on their feedback, it would also build a really tight relationship where they really trusted us in terms of, you know, they're willing to work with us.
- PKPete Koomen
Mm-hmm.
- AFAuctor founders
But they basically came to us this week and said, "Hey, you know, we love you guys. We love the vision, but I'm struggling to, to drive [chuckles] adoption within my business." Um, so it did necessitate what we ended up, um, you know, a, a big shift where we decided to really take a step back, take all of our learnings across, across these conversations with customers, and from first principle was think about, you know, how we would want to structure the product to really solve for a lot of the core pain points that-
- PKPete Koomen
Mm
- AFAuctor founders
... may have been mentioned, and that's kind of the framing where we, where we went from there.
- PKPete Koomen
So you just rebuilt it from scratch, basically?
- AFAuctor founders
Yeah.
- AFAuctor founders
Yes. [laughs]
- AFAuctor founders
Total rewrite of, of our code base at that point.
- PKPete Koomen
Which is, which is really interesting because, like several years ago, that would've been suicide.
- AFAuctor founders
Yeah.
- AFAuctor founders
Yeah.
- PKPete Koomen
You know, I think when I look back at Optimizely, one of the biggest mistakes we made was to do a rewrite. It's possible today-
- AFAuctor founders
[laughs]
- PKPete Koomen
... in a way, in a way it wasn't then. And, and I guess like looking back at the timeline, it sounds like that, that decision to rewrite happened right around the time that I think Opus 4.5 came out, if I re- like was it November of 2025? So you rewrote the whole thing.
- AFAuctor founders
Yeah. I remember when we ended YC, like, like the, the like sendoff day or something like that.
- AFAuctor founders
Mm-hmm.
- AFAuctor founders
Um, I think, was it Tom?
- AFAuctor founders
It was Tom, yeah. I remember sitting there-
- AFAuctor founders
[laughs]
- AFAuctor founders
... and Tom, Tom's giving a, a talk about-
- AFAuctor founders
Yeah
- AFAuctor founders
... you know, what not to do post-batch, and number one on there was, "You're gonna feel the urge to rewrite your code base because it's gonna be messy, but no matter what, don't do it." And that week I remember on one side I, I was hearing, you know, the customers saying, "This is not working," and on the other side I was hearing Tom's voice-
- PKPete Koomen
[laughs]
- AFAuctor founders
... of like, "Do not rewrite the code base." [laughs] Um, but yeah, no, the outcomes were, were tremendous for us, you know, once we came out the other side, so.
- 18:09 – 22:17
Why Customers Stayed Through the Rebuild
- AFAuctor founders
we didn't have that.
- PKPete Koomen
Why do you think these customers of yours stuck with you through this, this rebuild? It, it just sounds like you gave them a product that basically didn't work from their perspective, and they held out with you long enough for you to go and fix, fix the problem. W- why do you think they did that?
- AFAuctor founders
I, I think, I think a lot of it was- We, so we, we had an extremely tight relationship with our customers where, um, you know, we, we would onboard onto the platform. It would be a very, you know, white glove support. We would meet them s- in some cases two, three times a week. And it was early stages where they would... The feedback channels were, like, more than open, very, very welcomed. Um, and they did see oftentimes, you know, their pain point that they mentioned to us maybe on a more surface level, and they would see how we would be able to turn that into something tangible on a product. And yeah, for them, I think that was, one, a little bit, you know, mind-blowing in terms of, uh, they're not... They're, they're used to working with these very clunky, large enterprise softwares that iteration speeds are super slow. So I think that helped foster a lot of that trust. And then, yeah, I think that, that foundation allowed us to be able to feel like we had an opportunity to make this change where, um... And we did talk to all of our, you know, executive sponsors of, of our different customers, and they were, like, bought in, in, into the vision into how we wanted to adjust the platform.
- AFAuctor founders
Mm.
- AFAuctor founders
So yeah, there was, it was tremendous support from, from the customer base there.
- AFAuctor founders
Uh, I, I think the other piece there is, um, I think all of it kinda goes to show that, you know, what we were solving for and the vision that we had as a company was truly a, a really deep pain for these people. Um, as YC says, you know, it's, if, if it's a hair on fire problem, people are gonna go to really, really great lengths to, to seek out any solution that kinda solves it. So yeah, e- even if at the time, you know, there were a ton of improvements that we needed to make from a, a product perspective, um, it, it was a combination of that trust that the customers had in us, as well as just their buy-in to the vision, their need for, for the solution that we're, we're going out to build, that kind of allowed them to, you know, stick with us during that, that month and a half, two-month period.
- PKPete Koomen
And it sounds like you guys did a really good job. First of all, you found a pain point that was real. Uh, but you also became friends with your customers.
- AFAuctor founders
Yes.
- PKPete Koomen
Like, you just got really close with them-
- AFAuctor founders
[laughs]
- PKPete Koomen
... and they trusted you.
- AFAuctor founders
It's the biggest piece.
- PKPete Koomen
Yeah.
- AFAuctor founders
Like, a- anecdotally, um, I, I was telling you before this, like, I was in Indy, um, yesterday for, like, a, a, like a... It's like a, it was like a customer conference kinda thing, and I met up with, uh, one of our customers that we had signed on during YC. His name's Joshua. Um, and he has been in the Salesforce space for years. Many, many years. Uh, and he's just an absolute expert at, like, Salesforce implementations. And w- we just caught up, and obviously, like, a- a lot has progressed since v- when he signed on in YC. But, like, for YC, when we were, when we had signed him on, he had so much feedback on the platform.
- PKPete Koomen
Yeah.
- AFAuctor founders
There was one day where he was, like, in SF for, for whatever reason.
- PKPete Koomen
Even-
- AFAuctor founders
And then Sky, uh, went to-
- AFAuctor founders
His hotel.
- AFAuctor founders
Yeah.
- AFAuctor founders
His hotel room.
- AFAuctor founders
His hotel lobby to, like-
- AFAuctor founders
This is the week after we onboard him onto the platform, and he was very eager to get his hands on the platform. One weekend, yeah, he does, he, he messages me, "Hey, I'm in SF. Would love to grab, you know, a coffee."
- AFAuctor founders
Yeah.
- AFAuctor founders
Um, "I'm, I'm staying here." So I go to meet him, and, um, he has his laptop, and he essentially goes through every single page in our application, and nitpicks to the detail of, "Oh, this hint text in this form, this is not, you know, the right terminology here. It should be this." Goes through everything there, and the, it was really supposed to be a 30-minute coffee chat. Was a four-hour discussion. [laughs]
- AFAuctor founders
[laughs]
- AFAuctor founders
So that weekend we re- we did a mini, like, re-interface design.
- AFAuctor founders
This is during YC.
- PKPete Koomen
Yeah.
- AFAuctor founders
During YC.
- 22:17 – 26:21
Why Enterprises Still Need Salesforce and SAP
- AFAuctor founders
so.
- PKPete Koomen
Just been a lot of talk lately about a SaaSpocalypse, you know, and, and that in- entire industry going away. What, what are you seeing out there? Is there still demand for these, for these large platforms?
- AFAuctor founders
Yeah. There's still demand, like, for sure, but, like, the customers and the clients of these one implementations, but also the customers of these large enterprise SaaS platforms, are having a shifted, uh, expectation in terms of their mentality, in the sense of, like, it, it's more so like they're questioning the status quo of what they've been doing the last, like, 20, 30 years, where, like, they are now, like these c- customers and clients, they're using AI. So they see the power of AI-
- PKPete Koomen
Mm
- AFAuctor founders
... and, like, these LLMs in terms of being able to just be more efficient. And so now they're questioning, "Hey, I'm paying, like, $10 million for this piece of software. Why do I have to wait 24 months for it to be impl- 18 months for it to be implemented for me, and then I pay, like, even more than I'm paying for the software for services?" So, like, it's, it's like they're just kind of waking up to, like, this fact of what they've believed to be true this whole time, but now they're questioning it because of the, like, because of AI. And so I think, like, with that, it's driving urgency for both the SaaS vendors to fix this problem of, like, how do we drive quicker time to value for our customers? And that lar- largely is reducing the implementation time-
- PKPete Koomen
Mm
- AFAuctor founders
... and being able to get them to speed faster, right? With the value. And then for system integrators, for services businesses, for IT teams, their whole urgency now is, like, how do we be more efficient to make the implementation faster, right? So I think that's, that's, that, at least that's how we're seeing that affect us, uh, in terms of our market.
- AFAuctor founders
Yeah. I, I also think it's interesting 'cause for SaaS, S- SaaSpocalypse, if you take, if you take Salesforce, ServiceNow, SAP, these big enterprise software products and, and, and vendors, and you, you can merge, you know, the trust and the, like, enterprise grade, all the, all the different, um, yeah, enterprise qualities of those products, and you can merge it with quicker implementation timelines. Then from a, for, for, for those businesses- It should, that demand for these core like enterprise softwares should not be decreasing. In, in fact, it should just be increasing 'cause you're marrying that trust with that speed from AI as well. So yeah, I think that's one way that I've been thinking about it.
- PKPete Koomen
So, so for somebody who's never worked at a big company that used Salesforce or who might assume that in the new world, companies will just build their own SAP or, or build their own Salesforce, um, is that-- where's the misunderstanding there, or is that a misunderstanding?
- AFAuctor founders
I think people underestimate like how complex and heavy these like enterprise softwares are. Like, I mean, they're doing constant acquisitions. They're-- They've been around for a long time and have ultimately become very, very ingrained into like the Fortune 2000. For like a startup, right, like vibe coding your CRM is fine because like you-- it's v-very limited requirements on what you need that CRM to do. When you're thinking about vibe coding a CRM or something like a Salesforce, which is not just a CRM anymore, right? Like, there's so much to it, um, for like a Fortune 500 company, like the reliability, the, the, like the edge cases, the permissioning, like all of the things that make a piece of software enterprise-grade, you are not vibe coding that, and also you don't wanna maintain that, right? And so like I think that's the discrepancy between like this concept of being able to just like vibe code software and then ultimately production-grade enterprise software such as a ServiceNow or a Workday or something
- 26:21 – 28:40
Building on Platforms, Not Replacing Them
- AFAuctor founders
like that.
- PKPete Koomen
Well, one thing I was surprised to learn wh-when I first started looking into this was that in most cases, these big implementations of SAP and Salesforce contain a lot of custom code.
- AFAuctor founders
Mm-hmm.
- PKPete Koomen
Right? Like in, in many cases, maybe more custom code than there is sort of application code, uh, in the first place. Uh, and so it occurs to me that the ability to write software super quickly and easily on top of these platforms might actually make their position stronger.
- AFAuctor founders
Yeah.
- AFAuctor founders
Yeah, exactly. I, I think it's very interesting. That's, that's kinda the way that I see it, where, um, a lot of these platforms when, when you get to, you know, the needs of enterprises that are, are, are this scaled, um, the software needs to be so flexible, um, so configurable and, and malleable that essentially when, you know, these large enterprises, they're buying SAP or Salesforce or whatever it is, they're really more so just buying like primitives to be able to-
- AFAuctor founders
Hmm
- AFAuctor founders
... configure a piece of software around. Um, so I think like the analogy to, to software engineering, right, is if you need to use like a database or something, you're gonna go and use Postgres. You're not gonna vibe code like your, your own database from, from the ground up. And it's, it's a similar kind of thing for these large softwares where, yeah, if you need, um, you know, if a hospital needs an EHR system, they're gonna go and use Epic and kind of configure it based off of their needs, um, using those primitives that, to Will's point, you know, they have the trust, the security. They know that, that they're battle-tested, rather than kind of going around and, and doing this entire thing from the ground up when they-
- AFAuctor founders
Yeah
- AFAuctor founders
... when they don't really have to. And then if that's the case, the question now, it kinda comes to like this meta layer of development where you're not developing code, you're developing on top of these components and primitives of the core software, and that bottleneck goes to essentially the layer that we're sitting at, which is the implementation.
- PKPete Koomen
All right. I think that's all we have time for. Uh, I know you guys just closed a Series A from Sequoia as well. Uh, are you hiring?
- AFAuctor founders
Yeah. Yeah. We're, we're hiring on all fronts, uh, with a, with a big focus on the go-to-market side.
- PKPete Koomen
Cool. Thanks, guys.
- AFAuctor founders
Thank you.
- AFAuctor founders
Appreciate it. [upbeat music]
Episode duration: 28:41
In the uListen app, the transcript lights up word by word as you listen. Get uListen
Transcript of episode FmvRhxq2oHE