# Defensibility Test ## Which part of the layer is hard to copy? | Candidate moat | Strong if | Weak if | | --- | --- | --- | | Connectors | Deep, certified, hard to build | Built on an open standard | | Policy and audit data | Stored in vendor format, used for compliance | Customer can export it | | Workflow library | Grows with each customer | Written once by hand | | Routing data | Learns from outcomes | Static rules | | Local hosting | Needs licences and sites | A cloud region is enough | | Trust and references | Regulated customers refer others | No public reference | > [!important] Main finding > No single item is a moat on its own. The case rests on the combination, and on switching cost that grows with each workflow. ## Related - [[AI Deployment Layer MOC]] - [[Technical Moat Assessment Framework]] - [[AI era Defensibility]] - [[Switching Cost Design]]