{"api":{"name":"api.sb","description":"Business-as-Code surface for Startups.Studio","home":"https://api.sb","docs":"https://api.sb/docs","version":"1.0.0"},"$context":"https://api.sb/$context","$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acustomer-service-representatives-billing-dispute-resolution%3At-bu%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acustomer-service-representatives-billing-dispute-resolution%3At-bu%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Acustomer-service-representatives-billing-dispute-resolution%3At-bu%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:customer-service-representatives-billing-dispute-resolution:t-bu:v1","lens":"AIService","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":1,"C7_magicLensFit":1,"C4_competitorHonesty":1,"C6_crossSlotCoherence":1,"C1_customerSpecificity":1,"C2_problemFrictionRealism":1,"C9_killCriteriaAttestability":1,"C3_approachEngineCoverability":1,"C5_differentiationLoservilleEscape":1},"upperRightLoserville":true},"cellRef":{"id":"work-contexts.org.ai/customer-service-representatives-billing-dispute-resolution","stableHash":"wcc:customer-service-representatives:billing-dispute-resolution:voice:v1"},"problem":{"slotStatement":"When a member disputes a $480 bill, the Tier-1 CSR opens a ticket in iVUE, the meter-data analyst pulls AMI interval reads in MDM, the field tech logs a re-read in the truck tablet, and the billing clerk requests a rate-schedule check — by the time it lands back on the Tier-2 CSR three days later, half the context is missing, the member has called twice more, and the CSR re-investigates from scratch because nobody wrote down what was already ruled out."},"approach":{"oneSentence":"Dispute-ledger service that sits between the CIS ticket, the MDM interval-read pull, and the field re-read entry — every handoff appends a structured what-was-checked/what-was-ruled-out entry so the next CSR picks up a verifiable investigation trail instead of restarting, and the closeout letter to the member is generated from that trail."},"customer":{"icpShape":"Director of Member Services (economic buyer who signs the tooling PO) at a 40k–250k-meter member-owned electric cooperative (CompanyType/company-type-member-owned-electric-cooperative), where the buyer is the Director of Member Services and the daily user is the Tier-2 billing CSR handling escalated dispute tickets routed from the CIS (NISC iVUE or SEDC) queue.","beachheadShape":"EarlyAdopterJTBD: Touchstone Energy / NRECA-affiliated distribution co-ops in states with active PUC consumer-complaint dockets (e.g. NC, GA, TX, CO) where a high-bill-dispute backlog is a board-reported KPI."},"archetype":"startup-archetypes.org.ai/AIService-Subscription","beachhead":"EarlyAdopterJTBD: Touchstone Energy / NRECA-affiliated distribution co-ops in states with active PUC consumer-complaint dockets (e.g. NC, GA, TX, CO) where a high-bill-dispute backlog is a board-reported KPI.","competitors":{"substitutes":[{"name":"NISC iVUE Customer Care & Billing (native dispute/ticket module)","category":"incumbent","uncopyabilityReason":"NISC is a member-cooperative-owned CIS vendor whose release cadence is governed by its member-board roadmap and annual MIC conference — integration-depth barrier: iVUE's dispute module is a flat ticket-notes field bolted to the billing record, and re-architecting it into a structured multi-actor handoff ledger would require breaking the CIS↔MDM↔AMI data contract that 800+ co-ops depend on, which NISC will not do inside a 6-month window."},{"name":"SEDC (Southeastern Data Cooperative) UPN Billing + Service Orders","category":"incumbent","uncopyabilityReason":"Deployment-mode mismatch: SEDC's stack is predominantly on-prem AS/400-lineage deployments at individual co-ops with heavy per-site customization; shipping a cross-actor dispute workflow would require a SaaS control plane SEDC does not operate, and its revenue model is license + hosted, not workflow-outcome, so it has no commercial reason to route disputes through a reasoning layer it didn't sell."},{"name":"Salesforce Service Cloud (Energy & Utilities Cloud)","category":"AI-native horizontal","uncopyabilityReason":"Vertical-data-corpus barrier: Service Cloud's Einstein case-routing has no model of AMI interval data, rate-schedule riders (TOU, demand, irrigation), or NRECA/RUS reporting conventions. A co-op deploying it still has to hand-build the MDM connector, the rate-engine lookup, and the PUC complaint-letter template — the very corpus this engine is built around — and Salesforce's horizontal roadmap will not prioritize a 900-co-op TAM."},{"name":"Ironclad contract repository repurposed by AR/legal-ops","category":"manual-bridge"},{"name":"Shared Outlook mailbox + Excel dispute log + phone tag between CSR, meter analyst, and line crew","category":"informal"}]},"studioThesis":"T-BU","killThreshold":{"K":10,"M":50,"N":8,"rubricItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C7_magicLensFit","C8_lensFit","C9_killCriteriaAttestability"],"verdictPolicy":"all-load-bearing-pass-and-overall-ge-X","loadBearingItemSet":["C1_customerSpecificity","C2_problemFrictionRealism","C3_approachEngineCoverability","C4_competitorHonesty","C5_differentiationLoservilleEscape","C6_crossSlotCoherence","C9_killCriteriaAttestability"],"verdictPolicyVerbatim":"KILL unless every load-bearing rubric item passes per workbook AND overall pass-rate ≥ 8/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Handoff state model (free-text ticket notes ↔ structured what-was-checked/what-was-ruled-out ledger across CSR, meter analyst, field tech)","yAxis":"Co-op CIS/MDM integration depth (screen-scrape or CSV export ↔ native iVUE + MDM + AMI bidirectional writeback)","winningQuadrant":"Structured cross-actor dispute ledger with native iVUE/MDM/AMI writeback so the Tier-2 CSR inherits the prior two days of investigation and closes the ticket in one member callback","loservilleEscape":true,"loservilleQuadrant":"Free-text notes in iVUE's ticket module (or Salesforce Service Cloud cases) with CSV exports of meter reads pasted in — Tier-2 CSR re-pulls the AMI interval data and re-calls the field tech because the prior handoff state is unreadable, which is exactly the iVUE-native and SEDC-native failure mode today."}},"unmetRequirements":[],"pricingArchitecture":"tiered"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Acustomer-service-representatives-billing-dispute-resolution%3At-bu%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Acustomer-service-representatives-billing-dispute-resolution%3At-bu%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Acustomer-service-representatives-billing-dispute-resolution%3At-bu%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/customer-service-representatives-billing-dispute-resolution","thesis":"https://api.sb/v1/theses/T-BU"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a0575ad0dc2490ce","edgeLocation":"a0575ad0dc2490ce","geo":{"country":"US"},"ua":{"browser":"Claude"}},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acustomer-service-representatives-billing-dispute-resolution%3At-bu%3Av1/references"},"items":[]}}