@base <https://insights.euclid.vc/p/service-level-disagreement-ai-services-versus-software> .
@prefix schema: <https://schema.org/> .
@prefix owl: <https://www.w3.org/2002/07/owl#> .

<#article> a schema:Article ;
  schema:headline "Service-Level Disagreement"@en ;
  schema:name "Service-Level Disagreement"@en ;
  schema:alternativeHeadline "The VC debate on AI Services - and why they won't escape the gravity of software"@en ;
  schema:datePublished "2026-04-16" ;
  schema:inLanguage "en" ;
  schema:url <https://insights.euclid.vc/p/service-level-disagreement-ai-services-versus-software> ;
  schema:publisher <#the-verticalist> ;
  schema:author <#omar-el-ayat> ;
  schema:about
    <#ai-services>,
    <#services-as-a-wedge>,
    <#services-as-delivery-engine>,
    <#intelligence-arbitrage>,
    <#coordination-advantage>,
    <#automation-trap>,
    <#dispatcher-trap>,
    <#liability-ownership>,
    <#tam-illusion>,
    <#mirage-pmf>,
    <#venture-fundability>,
    <#service-level-diagnostic>,
    <#wedge-vs-delivery-misdiagnosis> ;
  schema:articleSection
    "The Case for AI Services"@en,
    "Comparing the two models"@en,
    "The Diagnostic: Three Questions"@en,
    "The Challenges with Services"@en,
    "The TAM Illusion"@en ;
  schema:abstract """The article argues that the current enthusiasm for AI-native services collapses two distinct business models into one category and therefore overstates their margins, TAM, and venture suitability."""@en ;
  schema:articleBody """Omar El-Ayat argues that investors discussing AI services often conflate two very different models: services-as-a-wedge and services-as-a-delivery-engine. The post accepts that selling outcomes instead of tools can unlock budgets and accelerate adoption, but argues that scope, addressable market, and venture fit are being overstated. In the wedge model, companies enter through outsourced intelligence work and hope rapid AI improvement turns low-margin services into software-like businesses before competitors commoditize them. In the delivery-engine model, software and services remain durably intertwined because coordination, compliance, liability, or physical-world handoffs do not disappear. The article proposes a three-question diagnostic around vendor position, liability ownership, and what happens when models get 10x better, then warns that many founders and investors are underestimating margin drag, operational fragility, and the difference between service revenue and software economics."""@en ;
  schema:hasPart
    <#part-case>,
    <#part-models>,
    <#part-diagnostic>,
    <#part-challenges>,
    <#part-tam> ;
  schema:mentions
    <#defined-terms>,
    <#argument-howto>,
    <#faq-1>, <#faq-2>, <#faq-3>, <#faq-4>, <#faq-5>,
    <#faq-6>, <#faq-7>, <#faq-8>, <#faq-9>, <#faq-10>,
    <#the-verticalist>,
    <#sequoia>,
    <#emergence>,
    <#coatue>,
    <#insurance-brokerage>,
    <#transactional-legal-work>,
    <#communication-compliance>,
    <#fund-administration> .

<#the-verticalist> a schema:Blog ;
  schema:name "The Verticalist"@en ;
  schema:url <https://insights.euclid.vc/> .

<#omar-el-ayat> a schema:Person ;
  schema:name "Omar El-Ayat"@en ;
  schema:affiliation <#euclid-ventures> .

<#euclid-ventures> a schema:Organization ;
  schema:name "Euclid Ventures"@en ;
  schema:url <https://euclid.vc/> .

<#sequoia> a schema:Organization ;
  schema:name "Sequoia Capital"@en ;
  schema:url <https://www.sequoiacap.com/> .

<#emergence> a schema:Organization ;
  schema:name "Emergence"@en ;
  schema:url <https://www.emcap.com/> .

<#coatue> a schema:Organization ;
  schema:name "Coatue"@en ;
  schema:url <https://www.coatue.com/> .

<#insurance-brokerage> a schema:DefinedTerm ;
  schema:name "Insurance brokerage"@en ;
  schema:description """The article’s example of a strong services-as-a-wedge category: outsourced, intelligence-heavy, fragmented, and already bought from external vendors."""@en .

<#transactional-legal-work> a schema:DefinedTerm ;
  schema:name "Transactional legal work"@en ;
  schema:description """The article’s second wedge example: standardized tasks like NDAs and routine filings that companies already outsource to outside counsel."""@en .

<#communication-compliance> a schema:DefinedTerm ;
  schema:name "Communication compliance"@en ;
  schema:description """A delivery-engine example in which the outcome requires not just analysis but filing, audit readiness, and ongoing regulatory ownership."""@en .

<#fund-administration> a schema:DefinedTerm ;
  schema:name "Fund administration"@en ;
  schema:description """A delivery-engine example where auditable books, LP reporting, and system-of-record responsibilities keep human coordination in the loop."""@en .

<#ai-services> a schema:DefinedTerm ;
  schema:name "AI-native services"@en ;
  schema:description """The broad category under debate: companies that sell outcomes or labor replacement rather than software seats alone, using AI to automate some share of delivery."""@en .

<#services-as-a-wedge> a schema:DefinedTerm ;
  schema:name "Services-as-a-Wedge"@en ;
  schema:description """The model where startups enter through outsourced work, build trust and data, and aim to automate away the service layer before intelligence work commoditizes."""@en .

<#services-as-delivery-engine> a schema:DefinedTerm ;
  schema:name "Services-as-Delivery-Engine"@en ;
  schema:description """The model where software alone cannot deliver the complete outcome, so service remains a permanent last-mile capability around coordination, compliance, or liability."""@en .

<#intelligence-arbitrage> a schema:DefinedTerm ;
  schema:name "Intelligence arbitrage"@en ;
  schema:description """The wedge model’s core bet that rapidly improving AI will turn outsourced intelligence work into something that scales with software-like economics."""@en .

<#coordination-advantage> a schema:DefinedTerm ;
  schema:name "Coordination advantage"@en ;
  schema:description """The delivery-engine model’s leverage point: AI improves the product, but the moat comes from owning messy last-mile coordination and compliance."""@en .

<#automation-trap> a schema:DefinedTerm ;
  schema:name "Automation trap"@en ;
  schema:description """The risk that humans turn out to be difficult to automate away, so gross-margin expansion never materializes as hoped."""@en .

<#dispatcher-trap> a schema:DefinedTerm ;
  schema:name "Dispatcher trap"@en ;
  schema:description """The commoditization risk that competitors and incumbents gain access to similar models, eroding differentiated economics in wedge businesses."""@en .

<#liability-ownership> a schema:DefinedTerm ;
  schema:name "Liability ownership"@en ;
  schema:description """The article’s second diagnostic question: whether the company merely performs work or actually owns the outcome and its associated risk profile."""@en .

<#tam-illusion> a schema:DefinedTerm ;
  schema:name "TAM illusion"@en ;
  schema:description """The article’s critique that counting all labor spend as addressable market overstates what AI services can realistically capture or fund at software multiples."""@en .

<#mirage-pmf> a schema:DefinedTerm ;
  schema:name "Mirage PMF"@en ;
  schema:description """The concept borrowed from Emergence to describe strong revenue and retention that can mask weak true automation and poor long-run unit economics."""@en .

<#venture-fundability> a schema:DefinedTerm ;
  schema:name "Venture fundability constraint"@en ;
  schema:description """The article’s concern that service-heavy businesses may not satisfy later-stage expectations for software-like growth and software-like margins simultaneously."""@en .

<#service-level-diagnostic> a schema:DefinedTerm ;
  schema:name "Three-question diagnostic"@en ;
  schema:description """The article’s framework for deciding whether a company is truly a wedge business or a delivery-engine business."""@en .

<#wedge-vs-delivery-misdiagnosis> a schema:DefinedTerm ;
  schema:name "Wedge-versus-delivery misdiagnosis"@en ;
  schema:description """The article’s warning that founders often mistake a temporary service wedge for a durable service-layer moat, or vice versa, and damage the business accordingly."""@en .

<#defined-terms> a schema:DefinedTermSet ;
  schema:name "Defined terms for Service-Level Disagreement"@en ;
  schema:hasPart
    <#ai-services>,
    <#services-as-a-wedge>,
    <#services-as-delivery-engine>,
    <#intelligence-arbitrage>,
    <#coordination-advantage>,
    <#automation-trap>,
    <#dispatcher-trap>,
    <#liability-ownership>,
    <#tam-illusion>,
    <#mirage-pmf>,
    <#venture-fundability>,
    <#service-level-diagnostic>,
    <#wedge-vs-delivery-misdiagnosis> ;
  schema:isPartOf <#article> .

<#part-case> a schema:WebPageElement ;
  schema:name "The case for AI services"@en ;
  schema:position 1 ;
  schema:about <#ai-services> ;
  schema:text """The article acknowledges the appeal of selling outcomes instead of tools, especially where labor budgets are larger than IT budgets and AI can remove workflow bottlenecks."""@en .

<#part-models> a schema:WebPageElement ;
  schema:name "Comparing the two models"@en ;
  schema:position 2 ;
  schema:about <#services-as-a-wedge>, <#services-as-delivery-engine>, <#intelligence-arbitrage>, <#coordination-advantage> ;
  schema:text """The core distinction is between wedge businesses trying to automate away service over time and delivery-engine businesses where service remains structurally necessary."""@en .

<#part-diagnostic> a schema:WebPageElement ;
  schema:name "The diagnostic: three questions"@en ;
  schema:position 3 ;
  schema:about <#service-level-diagnostic>, <#liability-ownership> ;
  schema:text """The article asks whether the company is an external vendor or embedded partner, who owns the outcome, and what happens if the model gets 10x better."""@en .

<#part-challenges> a schema:WebPageElement ;
  schema:name "The challenges with services"@en ;
  schema:position 4 ;
  schema:about <#automation-trap>, <#dispatcher-trap>, <#mirage-pmf>, <#venture-fundability> ;
  schema:text """The piece warns that many tech-enabled services show early traction by trading margin for growth, only to discover that automation is too slow, too hard, or too commoditized."""@en .

<#part-tam> a schema:WebPageElement ;
  schema:name "The TAM illusion"@en ;
  schema:position 5 ;
  schema:about <#tam-illusion> ;
  schema:text """The article argues that treating all labor spend as serviceable market exaggerates realistic capture potential and ignores the economic gravity that pulls service businesses back toward software expectations."""@en .

<#argument-howto> a schema:HowTo ;
  schema:name "How the article evaluates AI services business models"@en ;
  schema:about <#services-as-a-wedge>, <#services-as-delivery-engine> ;
  schema:isPartOf <#article> ;
  schema:step <#step-1>, <#step-2>, <#step-3>, <#step-4> ;
  schema:description """The post first accepts the AI-services thesis, then separates two service archetypes, applies a diagnostic, and finally critiques the margin and TAM assumptions behind the hype."""@en .

<#step-1> a schema:HowToStep ;
  schema:name "Acknowledge the appeal of outcome-selling"@en ;
  schema:position 1 ;
  schema:text "The article begins by recognizing that selling work rather than tools can unlock budgets and wedge into software-resistant markets."@en ;
  schema:isPartOf <#argument-howto> .

<#step-2> a schema:HowToStep ;
  schema:name "Separate wedge from delivery-engine models"@en ;
  schema:position 2 ;
  schema:text "It then splits AI services into two fundamentally different categories with different margin, hiring, GTM, and defensibility properties."@en ;
  schema:isPartOf <#argument-howto> .

<#step-3> a schema:HowToStep ;
  schema:name "Run the three-question diagnostic"@en ;
  schema:position 3 ;
  schema:text "Founders are told to diagnose vendor position, liability ownership, and what happens when the model gets 10x better."@en ;
  schema:isPartOf <#argument-howto> .

<#step-4> a schema:HowToStep ;
  schema:name "Pressure-test margins and TAM"@en ;
  schema:position 4 ;
  schema:text "The final move is to challenge assumptions about gross-margin expansion, venture scalability, and whether all labor budgets are truly capturable."@en ;
  schema:isPartOf <#argument-howto> .

<#faq-1> a schema:Question ;
  schema:name "What is the article’s main disagreement with the AI services thesis?"@en ;
  schema:text "What is the article’s main disagreement with the AI services thesis?"@en ;
  schema:acceptedAnswer <#faq-1-answer> ;
  schema:isPartOf <#article> .
<#faq-1-answer> a schema:Answer ;
  schema:text "It argues that investors are collapsing two different service models into one category and therefore overstating their margins, TAM, and venture suitability."@en ;
  schema:isPartOf <#article> .

<#faq-2> a schema:Question ;
  schema:name "What is Services-as-a-Wedge?"@en ;
  schema:text "What is Services-as-a-Wedge?"@en ;
  schema:acceptedAnswer <#faq-2-answer> ;
  schema:isPartOf <#article> .
<#faq-2-answer> a schema:Answer ;
  schema:text "It is the model where a startup enters by performing outsourced work and hopes to automate the service layer into a software-like business over time."@en ;
  schema:isPartOf <#article> .

<#faq-3> a schema:Question ;
  schema:name "What is Services-as-Delivery-Engine?"@en ;
  schema:text "What is Services-as-Delivery-Engine?"@en ;
  schema:acceptedAnswer <#faq-3-answer> ;
  schema:isPartOf <#article> .
<#faq-3-answer> a schema:Answer ;
  schema:text "It is the model where service remains essential because coordination, compliance, liability, or physical-world handoff still owns the outcome."@en ;
  schema:isPartOf <#article> .

<#faq-4> a schema:Question ;
  schema:name "What is intelligence arbitrage?"@en ;
  schema:text "What is intelligence arbitrage?"@en ;
  schema:acceptedAnswer <#faq-4-answer> ;
  schema:isPartOf <#article> .
<#faq-4-answer> a schema:Answer ;
  schema:text "It is the wedge model’s bet that rapidly improving AI will turn low-margin intelligence services into software-like businesses before the market commoditizes."@en ;
  schema:isPartOf <#article> .

<#faq-5> a schema:Question ;
  schema:name "What is coordination advantage?"@en ;
  schema:text "What is coordination advantage?"@en ;
  schema:acceptedAnswer <#faq-5-answer> ;
  schema:isPartOf <#article> .
<#faq-5-answer> a schema:Answer ;
  schema:text "It is the delivery-engine model’s advantage when AI improves the product but the durable moat remains in ownership of messy last-mile coordination and compliance."@en ;
  schema:isPartOf <#article> .

<#faq-6> a schema:Question ;
  schema:name "What are the three diagnostic questions?"@en ;
  schema:text "What are the three diagnostic questions?"@en ;
  schema:acceptedAnswer <#faq-6-answer> ;
  schema:isPartOf <#article> .
<#faq-6-answer> a schema:Answer ;
  schema:text "The article asks whether you are an external vendor or embedded partner, who owns the outcome, and what happens when the model gets 10x better."@en ;
  schema:isPartOf <#article> .

<#faq-7> a schema:Question ;
  schema:name "Why does liability ownership matter?"@en ;
  schema:text "Why does liability ownership matter?"@en ;
  schema:acceptedAnswer <#faq-7-answer> ;
  schema:isPartOf <#article> .
<#faq-7-answer> a schema:Answer ;
  schema:text "Because in delivery-layer businesses, owning liability can create switching costs and pricing power that function more like insurance than ordinary feature competition."@en ;
  schema:isPartOf <#article> .

<#faq-8> a schema:Question ;
  schema:name "What is the automation trap?"@en ;
  schema:text "What is the automation trap?"@en ;
  schema:acceptedAnswer <#faq-8-answer> ;
  schema:isPartOf <#article> .
<#faq-8-answer> a schema:Answer ;
  schema:text "It is the risk that people prove much harder to automate away than expected, so margin expansion never arrives."@en ;
  schema:isPartOf <#article> .

<#faq-9> a schema:Question ;
  schema:name "What does the article mean by the TAM illusion?"@en ;
  schema:text "What does the article mean by the TAM illusion?"@en ;
  schema:acceptedAnswer <#faq-9-answer> ;
  schema:isPartOf <#article> .
<#faq-9-answer> a schema:Answer ;
  schema:text "It means counting all labor spend as addressable market can wildly overstate what an AI services company can actually capture or sustain at software-like economics."@en ;
  schema:isPartOf <#article> .

<#faq-10> a schema:Question ;
  schema:name "What is the worst strategic mistake according to the article?"@en ;
  schema:text "What is the worst strategic mistake according to the article?"@en ;
  schema:acceptedAnswer <#faq-10-answer> ;
  schema:isPartOf <#article> .
<#faq-10-answer> a schema:Answer ;
  schema:text "Misdiagnosing which model you are in: treating a wedge as if it had a durable service moat or stripping out the service layer that actually makes a delivery-engine business defensible."@en ;
  schema:isPartOf <#article> .