slug: twenty
provider: Twenty
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: Opportunities
  spec_file: twenty-opportunities-api-openapi.yml
  capability_id: BC-410.30
  capability_id_l1: BC-410
  capability_name: Opportunity & Pipeline Management
  confidence: 0.9
  evidence: POST /opportunities createOneOpportunity; Opportunity, OpportunityInput schemas with CurrencyMetadata
  reason: Create/read/update/delete of sales opportunities with amount metadata is plainly deal and pipeline
    lifecycle management in a CRM.
- tag: Companies
  spec_file: twenty-companies-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.8
  evidence: GET /companies findManyCompanies; 'REST endpoints for CRUD operations on all CRM records including
    companies, people, opportunities'
  reason: CRUD on company master records inside a CRM is customer master-data maintenance. Mapped to Customer
    Data Management; residual ambiguity is only whether it should sit at the broader CRM level.
- tag: People
  spec_file: twenty-people-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.8
  evidence: POST /people createOnePerson; Person schema with EmailsMetadata, PhonesMetadata, FullNameMetadata
  reason: Maintenance of contact/person records with emails, phones and names is customer/contact master
    data management within the CRM.