slug: servicefusion provider: Service Fusion 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: 5 edges: - tag: Customers spec_file: servicefusion-customers-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.85 evidence: GET /customers listCustomers; POST /customers createCustomer; schemas Customer, CustomerInput, Address reason: CRUD over customer master records — customer data management within CRM. The vendor description also names "customer management" explicitly. - tag: Invoices spec_file: servicefusion-invoices-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.82 evidence: POST /invoices createInvoice; schemas Invoice, InvoiceInput, LineItem; vendor covers "invoicing, payments" reason: Customer invoice creation and retrieval is accounts receivable / customer invoicing. Not subscription billing — this is one-off job invoicing for contractors. - tag: Contacts spec_file: servicefusion-contacts-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.76 evidence: GET /customers/{id}/contacts listCustomerContacts "List a customer's contacts"; schemas Contact, Address reason: Maintaining contact records attached to customer master records is customer data management. Sub-capability choice is reasonably clear but the surface is thin (list/create only). - tag: Estimates spec_file: servicefusion-estimates-api-openapi.yml capability_id: BC-410.40 capability_id_l1: BC-410 capability_name: Quote & Configuration Management confidence: 0.74 evidence: POST /estimates createEstimate; schemas Estimate, LineItem; vendor covers "estimates" reason: Estimates with priced line items are quotes issued to prospective customers, matching Quote & Configuration Management. Some ambiguity vs. generic opportunity management, so not higher. - tag: Payments spec_file: servicefusion-payments-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.72 evidence: POST /payments "Record a payment"; schemas Payment, PaymentInput reason: Recording customer payments against invoices is cash application within accounts receivable. Thin surface and no explicit invoice linkage shown, so moderate confidence.