YC partner Pete Kumman interviews Octar founders on building an AI platform that fixes requirement misalignment in enterprise software implementations, from discovery to go-live.
Key Takeaways
- Enterprise software implementations often fail due to upstream requirement and design misalignment, not just technical configuration.
- Deep customer discovery (dozens of calls, iterating on written documents) was critical to finding the real problem.
- Early, focused launches can rapidly generate inbound demand in a short accelerator timeline.
- Customer-driven rewrites can be justified when feedback clearly signals the product direction is wrong.
What the video covers
- Octar is an AI platform for enterprise software implementations (e.g., ServiceNow, Salesforce, SAP), spanning discovery, design, configuration, and go-live.
- The founders' initial wedge was upstream: requirement and design misalignment, which causes many implementations to fail, overrun, or get extended.
- The idea came from a co-founder's friend at Deloitte working on a multi-year, hundreds-of-millions-dollar ERP transformation that relied on Word and Excel.
- The team conducted dozens of calls with services leaders, system integrators, and internal IT teams, iterating from config agents to requirements-to-configuration traceability.
- Their original plan was config agents per software vendor; feedback from practitioners shifted focus to upstream requirements and design problems.
- During YC, the founders worked in a focused, low-distraction setup near the office and launched early to drive inbound demand.
- The launch generated hundreds of demo bookings within days, which informed their go-to-market approach.
- They raised a seed round and reported significant customer feedback that shaped the platform.
- They performed a near-complete rewrite of their codebase in roughly six weeks, justified by customer survey feedback.
- A key industry insight is that large SAP and Salesforce implementations contain substantial custom code, and the implementation layer is the bottleneck.
Chapters
- 00:00Introduction and Company Overview
- 01:36Problem Discovery and Upstream Wedge
- 03:11Customer Research and Idea Validation
- 06:28YC Batch Experience and Focused Work
- 08:00Early Launch and Demo Pipeline
- 11:00Platform Rebuild and Customer Feedback
- 16:40Industry Insights on Custom Code and Implementation Bottlenecks
- 28:20Closing Reflections
Full Transcript — Download SRT & Markdown
Speaker A
[music] Hi, I'm Pete Kumman and I'm a partner at YC. I'm here today with the founders of Octar from the spring 25 batch.
Speaker A
Hi guys, welcome. Hey, thanks for having us. Uh, so to get us started, what is Octar?
Speaker A
Yeah, so Octar is an AI platform for software implementations. So when you think about a large enterprise uh and they're going through a bay transformation with a piece of software like a service now, a Salesforce, SAP, etc. There's a lot that goes into that
Speaker A
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
Speaker A
the way through the 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
Speaker A
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
Speaker A
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
Speaker A
implementations a lot of the times why they fail or they get extended or they go overrun is because of the misalignment in requirements in design in the very beginning of the implementation not even when it comes to the coding part. And so our wedge in
Speaker A
especially when we applied to YC was solving this piece this upstream piece and then it's pulled this more downstream into like configuration. So, one of the things that I remember standing out about your application was that you seemed really obsessed with
Speaker A
this problem. How did you discover this problem in the first place? 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
Speaker A
solve. And so, how we stumbled across this was I have a really close friend of mine um who works at Deote, which is a really large global system integrator.
Speaker A
And while he was at Deote, 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. [snorts] And every time I would catch up with him while he
Speaker A
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
Speaker A
GPT354 and it was like getting the traction within the enterprise of like actual usability.
Speaker A
And I just thought to myself hearing him talk about these super manual processes in 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
Speaker A
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, people that were system integrators, whether that be at a
Speaker 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 my buddy about. Very manual, very legacy in a very large industry all
Speaker A
while this new technology was on the horizon. And so we wanted to do something about it.
Speaker A
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?
Speaker A
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
Speaker A
started asking much more pointed questions. I would go from one call take what they said literally parid it and then say hey like this is what we're this is what I'm seeing. Like what do you think? And it became a lot more
Speaker A
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
Speaker A
was let me build configuration agents for X piece of software. So config agents for Service Now, config agents for SAP, config agents for Salesforce.
Speaker A
And that was the original idea for Octure. And I took that piece of paper back to the people I kept having these conversations with and I said like what do you think like and I I would I would
Speaker A
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 will like this would be
Speaker A
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 what do you mean?
Speaker A
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 and requirements in design before we even go
Speaker A
into the build and I'm like oh wow and so we iterated on that and uh took that piece of paper back to the 50 people 50ish people and they're like this is incredible right I had one person who worked at a firm
Speaker A
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 like okay like that's a problem worth solving and so that's when we as co-founders
Speaker A
came together built an MVP and you know got it in front of them and and then you applied to YC and you got in tell the story of the batch you had an unusual batch experience for us like I I remember texting you
Speaker A
about this when we were thinking about like housing and um you were really encouraging on getting somewhere near dog patch which makes sense right close to the YC office um but Sky being the fact that he's from the Bay Area. Like
Speaker A
luckily he had an apartment uh in Sunset which was 40 like 40 30 minutes from the office.
Speaker A
It was like really far away. Um but I actually think that like came to our advantage.
Speaker A
It was almost in some ways it was a good distance where we were I mean we were in the apartment all all day basically taking sales calls, building product. Um and it really allowed us to I think hyperfocus. And you guys just basically
Speaker A
went into hermit mode as I recall. Exactly. The only two places we would go would be the YC office and then this one deli called Georgees by the Zoo. And those would be our only two times we would leave the apartment. You know, we
Speaker A
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. And you
Speaker A
guys launched early in the you you took the advice and you launched early in the batch and I think you had a successful launch.
Speaker A
Yeah. Tell us about that. That that very pivotal launch. The advice is like launch early, right?
Speaker A
Launch fast. Um, and so for us, we we took that very literally and like we optimized all around like the launch because like for us when we think about like YC, it's a very short amount of time and you want to get a lot done and
Speaker A
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 that's not going to happen. And so it's like how do you drive as much inbound as
Speaker A
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
Speaker A
where we could post it 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.
Speaker A
So, we did the sign launch probably by the second or third week of YC, probably like second week. And we're like, okay, how do we make this as like different and notable as possible? And given that Sky is from the Bay, he has a beautiful
Speaker A
dog named Summer and we were like, let's just like have Summer in the photo. And so, it was us, the YC side, and then this like gorgeous like golden retriever. Yeah, like golden retriever. I think to the so
Speaker A
I this is a fun fact I used to like run a video editing business 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
Speaker A
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 on on the social media platform and then two also like eliciting some type of
Speaker A
emotion of like oh that's super cute or that's super super um like it makes makes me feel happy. Um, and there's I think maybe no better way to do that in a in a photo than having a a cute pet as
Speaker A
a member of the team as well. So, we called her the chief bark officer and everyone loved that. So, but like in all seriousness though, like like that photo alone almost got a million like that post almost got a million impressions on
Speaker A
LinkedIn. Third week of YC, second third, you know, and it like drove like literally within 3 days we had probably like 300 demos booked, like 200 300 demos booked.
Speaker A
Granted, like most of it was probably like not qualified and like, you know, not not relevant, but like it drove a ton of attention. uh and and and even like some of our like large enterprise contracts that we have today were
Speaker A
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
Speaker A
probably like at the exact halfway mark of of YC because we wanted to time it where we can keep feeling and reaping the benefits of the the dog post the summer post uh but then also still launch and get more and So that's where
Speaker A
we did the typical video. Here's the other thing. Because we had so many shots on goal from the first Yes.
Speaker A
launch. We were refining the pitch like every 30 minutes on these calls. Yeah. So So tell us about your your kind of mode of operation. You you had hundreds of of demos booked on the calendar. I think you were doing most or
Speaker A
all of the demos and then you two were were building product. What what was did you have a product at this point?
Speaker A
What were you demoing? I mean, you sat like across from me. So, I'll let you like talk about like what the demo experience was like, but it was like very like FTE like.
Speaker A
Yeah. I think 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
Speaker 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
Speaker A
where me and Sky were sitting across from Will, we could literally hear, you know, the feedback and the complaints or the push back from the calls that he was having and then that night we would just ship out like some kind of remediation
Speaker A
or or some kind of extension to our product that that would help address it.
Speaker A
So we were very very focused on okay, what could we do on the product side to help drive revenue as much as possible.
Speaker A
Yeah. It's basically you just built for the demos over and over and over again.
Speaker A
Yeah. Yes. And you launched again and I think you got you got a similar response. You you had a lot more not not a million. I think we got like 400 500k impressions which is still great. So yeah.
Speaker A
But you kept launching, you kept demoing. You kept building. Yes. How did the batch end for you guys?
Speaker A
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
Speaker A
us we also decided to make the move from SF to New York. But but tell us about like did you have customers? Did you have revenue? What was what did the product look like you know after hundreds of kind of demo
Speaker A
iterations? Yes. 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
Speaker A
they are asking for a feature like it's not like actually thinking like 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
Speaker A
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, like it was it was a mess.
Speaker A
We we took I think we like the talking to customers, you know, building with customers, building what people want, you know, very very literally. I think where like to Matt's point after a demo call or after an intro call we would
Speaker A
ship out you know three new features that um when surfaced back to them it's like wow this I this this nails it u but when when they you know came onto the platform for the first time yeah it was
Speaker A
it became very apparent that it was very hard to drive adoption because of you know if you think about like a larger onboarding it's it's just that learning curve to to understand what the platform can do with all these different features
Speaker A
was way too high. Just had hundreds of features that Exactly. Okay. Like you could imagine a a you know, if they wanted to create a solution design document and a business requirement document, we would have two two separate
Speaker A
features almost of, hey, you know, this is your BRD builder and this is your solution design document builder. When in reality, we just needed a a document builder with like a you know, a good agent harness that could, you know, be
Speaker A
malleable across the different outputs that they might want. So So where did that leave you? You moved to New York. You had you this point you had customers and revenue and you had a product that just sounds like
Speaker A
a monster. Yeah. Um what did you do? 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
Speaker A
sponsors who we have very fantastic relationships by the way. I think by because of how quickly would iterate on their feedback, it would also build a really tight relationship where they really trusted us in terms of, you know,
Speaker A
they're willing to work with us. 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 adoption within my business." Um so it did necessitate
Speaker A
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
Speaker A
to structure the product to really solve for a lot of the core pain points that may have been mentioned and that's kind of the framing where we where we went from there.
Speaker A
So you just rebuilt it from scratch basically. Yeah. Yes. [laughter] total rewrite of our code base at that point, which is which is really interesting because several years ago that would have been suicide.
Speaker A
Yeah. Yeah. You know, I think when I look back at optimizing, one of the biggest mistakes we made was to do a rewrite. It's possible to me in a way in a way it wasn't then. And and I guess like
Speaker A
looking back at the timeline, it sounds like that that decision to rewrite happened right around the time that I think Opus 45 came out if I rec like was it November of 2025. So you rewrote the whole thing.
Speaker A
Yeah. I remember when we ended YC like like the the like sendoff day or something like that.
Speaker A
Um I think was it Tom? It was Tom. Yeah, I remember sitting there and Tom Tom's giving a a talk about, you know, what not to do post batch. And number one on there was you're going to feel the urge to rewrite
Speaker A
your codebase because it's going to be messy, but no matter what, don't do it.
Speaker A
And that week, I remember on one side I was hearing, you know, the customers saying, "This is not working." And on other side, I was hearing Tom's voice, [laughter] do not rewrite the code today.
Speaker A
Um, but yeah, I know the outcomes were were tremendous for us, you know, once we came out the other side. So, so yeah.
Speaker A
So, how long did it take and and you know what what what gave you the evidence that this was the right decision? I I think it was around a month and a half all in all. Um maybe a bit closer to 2
Speaker A
months, but yeah, at the time it was very it was a very risky decision, right? And you know, it was it was um very volatile period of the company. We weren't really sure if coming out the other end, you know, whether it would
Speaker A
have been worth it. And obviously there was there was a lot of risk in uh in doing so with our existing customers. We would kind of have to put them on ice for this period. But yeah, I think
Speaker A
obviously in hindsight it was one of the most important and probably one of the best decisions that that we've made um in the lifetime of the company. Even in like the week that occurred right after releasing, you know, essentially the
Speaker A
second version of the product, we saw like all of our usage me metrics across the board just 5x 10x. It was it was ridiculous. And there was a lot of really really phenomenal feedback that we were getting from our customers.
Speaker A
Yeah. But I will say like Matt kind of like brushed past it, but like th those two months were like so scary because it was like we talked about like yeah we had a successful like you know YC
Speaker A
experience where we raised from Sequoia. Um we had a good amount of ARR and revenue coming out of YC. We had customers that seemingly loved us because of like the iteration speed and all of a sudden we were now in keep the
Speaker A
lights on mode with existing customer base doing an entire code rewrite of like 50 plus features cobbled together without like true understanding of like what would stick. We had data points but like it wasn't like concrete enough where like we had all of our customers
Speaker A
fill out a survey and they all said yes I would be happy if you did this thing.
Speaker A
like, "No, we didn't have that." Why do you think these customers have here 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
Speaker A
held out with you long enough for you to go and fix fix the problem. Why do you think they did that?
Speaker A
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
Speaker A
white glove support. We would meet them in some cases two, three times a week in those early stages where they would the feedback channels were like more than open, very very welcomed. Um, and they did see oftent times, you know, their
Speaker A
pain points 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,
Speaker A
mind-blowing in terms of uh they're not 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
Speaker A
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 into the vision into how
Speaker A
we wanted to adjust the platform. So yeah there was it was tremendous support from the from the customer base there. I I think the other piece there is um I think all of it kind of goes to show
Speaker A
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
Speaker A
are going to go to really really great lengths to to seek out any solution that kind of solves it. So yeah, even if at the time, you know, there were a ton of improvements that we needed to make from
Speaker A
a a product perspective, um it was a combination of that trust that the customers had in us as well as just their buy into the vision, their need for for the solution that we were we were going out to build that kind of
Speaker A
allowed them to, you know, stick with us during that that month and a half, two month.
Speaker A
It sounds like you guys did a really good job. First of all, you found a painoint that was real. Uh but you also became friends with your customers and like you just got really close with them and they trusted you.
Speaker A
It's the biggest piece. Like anecdotally um I I was telling you before this like I was in Indie um yesterday for like a like a it's like a it was like a customer conference kind of thing. And I met up with uh one of our customers
Speaker A
that we had signed on during YC. His name is 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 we just caught up
Speaker A
and obviously like a lot has progressed since 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.
Speaker A
There was one day where he was like in SF for for whatever reason and then Sky uh went to his hotel. Yeah.
Speaker A
His hotel lobby to like This is the week after we onboard him to 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 an SF. Would love to grab,
Speaker A
you know, a coffee. 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
Speaker A
is not know the right terminology here it should be this goes through everything there and end up it was originally supposed to be a 30-minute coffee chat was a 4hour discussion [laughter] so that weekend we re we did
Speaker A
a mini like reinface design during YC um and he's still yeah a customer today and I think a huge test is our first our first few customers um that we sold to are still customers um today. So and
Speaker A
they've been able to see the entire entire journey through. So just been a lot of talk lately about a SAS apocalypse, you know, and and that entire industry going away. What what are you seeing out there? Is there still
Speaker A
demand for these for these large platforms? 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 SAS platforms are having a shifted uh expectation in
Speaker A
terms of their mentality in the sense of like 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 customers and clients They're using AI,
Speaker A
so they see the power of AI in 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
Speaker A
wait 24 months for it to be imple 18 months for it to be implemented for me?
Speaker A
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
Speaker A
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 SAS vendors to fix this problem of like how do we drive quicker time to value for our customers and that largely
Speaker A
is reducing the implementation time 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
Speaker A
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.
Speaker A
Yeah. I also think it's interesting because for SAS SAS apocalypse, if you take if you take Salesforce, Service Now, SAP, these big enterprise software products and and vendors and you you can merge, you know, the trust and the like
Speaker A
enterprise grade all the all the different um yeah enterprise qualities of those products and you can merge it with quicker implementation timelines.
Speaker A
And from a for for those businesses, it should that demand for these core like enterprise softwares should not be decreasing and in fact it should just be increasing because you're marrying that trust with that speed from AI as well.
Speaker A
So yeah, I think that's one way that been thinking about it. So, so for somebody who's never worked at a big company that use Salesforce or who might assume that in the new world companies will just build their own SAP
Speaker A
or build their own Salesforce. Um, is that where's the misunderstanding there or is that a misunderstanding?
Speaker A
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
Speaker A
startup, right? Like vibe coding your CRM is fine because like you it's 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
Speaker 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 enterprisegrade, you are not
Speaker A
vibe coding that. And also, you don't want to 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 service now or a
Speaker A
workday or something like that. One thing I was surprised to learn 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, right?
Speaker A
Like 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
Speaker A
their position stronger. Yeah. Yeah. Exactly. I think it's very interesting. That's that's kind of 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
Speaker A
are are this scaled um the software needs to be so flexible um so configurable 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
Speaker A
primitives to be able to configure a piece of software around um so I I think like the analogy to to software engineering, right? Is if you need to use like a database or something, you're going to go and use Postgress. You're
Speaker A
not going to b 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
Speaker A
EHR system, they're going to 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
Speaker A
than kind of going around and and doing this entire thing from the ground up when they when they don't really have to. And then if that's the case, the question now it kind of comes to like this meta layer of development where
Speaker A
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.
Speaker A
All right, I think that's all you have time for. Uh I know you guys just closed the series A from Sequoia as well. Uh are you hiring?
Speaker A
Yeah. Yeah, we're we're hiring on all fronts uh with a with a big focus on the go to market side.
Speaker A
Cool. Thanks, guys. Thank you. [music]
Topics:enterprise AIsoftware implementationERP transformationrequirements traceabilitysystem integratorsY Combinatorstartup foundersSAPSalesforceServiceNow











