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 howCHAPTERS
Jump to publisher timestampsChapter summaries
What Auctor is: an AI platform that preserves implementation context end-to-end
The founders define Auctor as an AI platform built to support large enterprise software implementations across the full lifecycle. They emphasize that implementations often fail not on pure technology, but on maintaining business context from discovery through go-live—even months later and after team turnover.
- •Auctor targets implementations for platforms like ServiceNow, Salesforce, and SAP
- •The hardest part is often aligning software work to business requirements and keeping that context through the project
- •The platform is meant to connect discovery, design, configuration, and go-live into one continuous thread
- •The initial entry point was not the "last mile" of configuration, but earlier stages where projects get derailed
Where the idea came from: seeing manual, legacy processes in massive ERP work
One founder explains the initial spark came from a close friend working at Deloitte on a large government ERP transformation. Hearing about expensive, multi-year projects running on Word and Excel—while LLMs were becoming more usable—pushed them to investigate the space seriously.
- •A founder’s friend at Deloitte described frustration with how implementation work was done
- •The contrast between project scale and manual tooling (Word/Excel) felt striking
- •Improving LLM capabilities made the opportunity feel newly actionable
- •This became the seed that led to structured customer discovery
Finding the real pain: dozens of calls to map workflows and pain points
After the initial spark, the founders ran extensive customer discovery across system integrators and internal IT teams. They describe starting with basic questions, then rapidly learning the industry’s language and iterating their understanding directly with prospects.
- •They spoke with dozens of services leaders across GSIs, boutiques, and internal IT teams
- •Early calls focused on understanding fundamentals; later calls became more tactical
- •They refined their thinking by repeating what they heard back to prospects to validate it
- •A consistent theme emerged: large, legacy workflows despite huge budgets
Pivoting the concept: from configuration agents to requirements/design traceability
The founders share that their first written concept was configuration agents for major enterprise software products. Prospects pushed back, saying configuration help wasn’t the root cause; the deeper issue was misalignment in requirements and design, and the lack of traceability from requirements to configuration.
- •Initial plan: build configuration agents for specific platforms
- •Feedback: the biggest pain often starts before build—at requirements and design alignment
- •They iterated the concept and re-validated it with roughly 50 people
- •A long-tenured industry leader highlighted the unmet need for requirements-to-design-to-config traceability
YC batch operating style: "hermit mode" to stay focused
The founders describe an unusually secluded YC experience, choosing distance and isolation to reduce distractions. Their days were dominated by sales calls and product building, with minimal time spent outside their apartment and the YC office.
- •They stayed far from the YC office but say it helped them focus
- •They spent most days in the apartment taking sales calls and building
- •They intentionally avoided distractions and comparisons to other teams
- •They left mainly for the YC office and a single deli
The dog photo that drove massive inbound and hundreds of demos
They explain how a YC sign photo featuring a golden retriever (Summer) became a viral “scroll stopper” on LinkedIn. The post generated enormous attention and led to hundreds of demos booked within days, including meaningful enterprise opportunities.
- •They launched very early and optimized heavily around generating inbound
- •They included Summer the dog in the YC sign photo and dubbed her “chief bark officer”
- •One founder linked the post’s success to virality mechanics: stopping scroll and eliciting emotion
- •They report nearly a million impressions and roughly 200–300 demos booked in days, many unqualified but some valuable
Building in a tight demo loop: shipping features nightly to address objections
With hundreds of demos, the team used a rapid feedback loop where sales calls directly shaped what was built next. Two founders built while another ran most demos, and they shipped fixes or additions quickly to remove friction and increase sales momentum.
- •They refined the pitch constantly due to high demo volume
- •Product feedback was heavily influenced by sales conversations rather than deep usage data
- •They listened to objections in real time and shipped responses the same night
- •Their focus was using product changes to drive revenue quickly
When building for demos backfires: the product becomes a Frankenstein
By the end of YC, the founders say the product had grown into a confusing set of one-off demo features. Customers had trouble adopting it because the learning curve was high and the platform lacked cohesive underlying structure.
- •They had customers and revenue, but the product was messy and reactionary
- •Shipping based on "gut reactions" from calls meant not always understanding root causes
- •The platform accumulated many separate builders/features for similar jobs
- •Adoption suffered because users couldn’t easily understand what the platform was for
The moment that triggered a reset: executive sponsors couldn’t drive adoption
A set of customer calls—particularly with executive sponsors—made the adoption issue unavoidable. Despite strong relationships, customers said they loved the vision but struggled to roll it out internally, prompting the team to step back and redesign from first principles.
- •Executive sponsors communicated clear adoption struggles inside their organizations
- •Strong relationships existed partly because the team had iterated quickly on feedback
- •They decided to consolidate learnings and rethink the product structure
- •They refocused on solving core pain points rather than accumulating features
Total rewrite: pausing customers, taking risk, and seeing usage jump 5–10x
They chose a full rewrite of the codebase, despite common startup advice to avoid it, and describe the period as volatile and scary. After release, they report usage metrics increased dramatically and customer feedback improved substantially.
- •They performed a total rewrite of the codebase
- •They estimate about 1.5–2 months to complete it
- •They had to effectively put existing customers “on ice” during the rebuild
- •After shipping the new version, they saw usage increase 5X–10X and received strong feedback
Why customers stayed: trust built through close, high-touch collaboration
Asked why customers tolerated the rebuild, the founders credit exceptionally tight customer relationships and fast iteration compared to typical enterprise software vendors. They also argue the underlying pain was severe enough that customers were willing to stick with an imperfect solution.
- •They provided white-glove onboarding and met with some customers multiple times per week
- •Customers were impressed by turning feedback into product changes quickly
- •They aligned executive sponsors on the vision and the planned product adjustments
- •They attribute retention to both trust and the “hair on fire” nature of the problem
A concrete customer story: a four-hour UI nitpick session and rapid redesign
One founder recounts meeting a customer they signed during YC who reviewed the product in extreme detail, turning a short coffee into a four-hour working session. The team made a mini interface redesign that weekend, and the customer remains on the platform today.
- •A customer in the Salesforce implementation space gave extensive, detailed feedback in person
- •The session covered nearly every page of the application and terminology details
- •They redesigned parts of the interface over a weekend during YC
- •Early customers remained customers through the company’s evolution
Why enterprise platforms still matter—and why AI may strengthen them
The conversation shifts to market context: despite “SaaSpocalypse” talk, the founders see ongoing demand for major enterprise platforms, with expectations changing due to AI. They argue enterprises won’t replace platforms like Salesforce/SAP by “vibe coding” equivalents, and that faster software creation on top of these systems could make them even more entrenched.
- •They see customers questioning long implementation timelines and large services costs in the AI era
- •They believe urgency is rising for faster time-to-value via shorter implementations
- •They argue enterprise platforms are too complex, battle-tested, and full of edge cases to be replaced by quickly built alternatives
- •They describe enterprises as buying secure, trusted primitives that get configured/customized—making implementation the bottleneck layer
Publisher timestamps
- 0:00AI for Enterprise Software Implementations
- 3:28Finding the Real Problem to Solve
- 6:46The Dog Photo That Booked Hundreds of Demos
- 10:13When Building for Demos Backfires
- 13:59The Rewrite That Increased Usage 5–10x
- 18:09Why Customers Stayed Through the Rebuild
- 22:17Why Enterprises Still Need Salesforce and SAP
- 26:21Building on Platforms, Not Replacing Them