{"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","total":50,"limit":50,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses","first":"https://api.sb/v1/founding-hypotheses?limit=50","next":"https://api.sb/v1/founding-hypotheses?limit=50&cursor=fh%3Afinancial-managers-capex-approval-request%3At-ais-low-tech%3Av1"},"foundingHypotheses":[{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aaccountants-and-auditors-audit-workpaper-preparation%3At-ais-prem%3Av1","id":"fh:accountants-and-auditors-audit-workpaper-preparation:t-ais-prem:v1","lens":"AgenticWorkflow","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/accountants-and-auditors-audit-workpaper-preparation","stableHash":"wcc:accountants-and-auditors:audit-workpaper-preparation:document:v1"},"problem":{"slotStatement":"Between the senior associate who pulls the GL extract and the manager who signs off the workpaper, half the tickmarks, PBC-request context, and client email threads evaporate into a shared Slack channel — so the reviewer re-asks for evidence already provided, the client re-exports the same revenue subledger twice, and the engagement burns 8-14 hours per area re-establishing facts that were known three days ago."},"approach":{"oneSentence":"Engagement-letter-bound workpaper agent that watches the PBC inbox, the GL extract, and the reviewer's tickmark trail as a single running engagement state, and escalates a review-ready workpaper only when every assertion carries a named preparer, a named reviewer, and a pointer back to the client artifact it was drawn from."},"customer":{"icpShape":"Audit Partner (signs the engagement-tooling PO) at a US top-100 CPA firm in the company-type-vc-saas-startup-adjacent assurance segment (targetCompanyType: company-type-vc-saas-startup; firms auditing 50-400 VC-backed SaaS issuers annually, 80-600 audit staff), where the buyer is the Audit Partner / National Assurance Technology Leader and the daily user is the Senior Associate preparing SOC-1/GAAP workpapers","beachheadShape":"EarlyAdopterJTBD: interim-audit workpaper prep for Q3/Q4 SaaS-ARR and deferred-revenue testing at 2-partner-led engagement teams inside top-100 CPA firms"},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-RetainerEngagement","beachhead":"EarlyAdopterJTBD: interim-audit workpaper prep for Q3/Q4 SaaS-ARR and deferred-revenue testing at 2-partner-led engagement teams inside top-100 CPA firms","competitors":{"substitutes":[{"name":"Team inbox / Slack PBC channel","category":"informal"},{"name":"Excel tickmark workbooks shuttled over email","category":"manual-bridge"},{"name":"CaseWare Working Papers (Cloud + SmartSync)","category":"incumbent","uncopyabilityReason":"CaseWare's value lives in a 30-year corpus of firm-customized templates synced through a proprietary document-store; retrofitting an agentic state engine that reconciles live PBC email threads against GL deltas would require rebuilding the SmartSync deployment-mode (firm-hosted file server with offline sync) that every Big-4-adjacent firm has standardized on — deployment-mode mismatch."},{"name":"Thomson Reuters AdvanceFlow / Checkpoint Engage","category":"incumbent","uncopyabilityReason":"AdvanceFlow is anchored to Thomson's Checkpoint authoritative-content library and the UltraTax/GoSystem tax-seat integration; they cannot ship an engagement-state agent that reads arbitrary SaaS client artifacts (Stripe, NetSuite ARR schedules, Workday deferred-rev exports) without rebuilding the vertical-data-corpus licensing deals that fund Checkpoint — vertical-data-corpus lock-in."},{"name":"MindBridge Ai Auditor","category":"incumbent","uncopyabilityReason":"MindBridge is a GL-anomaly risk-scoring engine sold to the audit-analytics team, not the engagement team; its FINTRAC/PCAOB model-validation posture makes it liability-conservative about originating workpaper language, and expanding into preparer-reviewer handoff state would force it to assume preparer liability its E&O insurance does not cover — liability-posture barrier."},{"name":"AuditBoard (SOXHUB / OpsAudit)","category":"AI-native horizontal","uncopyabilityReason":"AuditBoard sells into the internal-audit and SOX-PMO buyer inside the issuer, not the external CPA firm; its distribution motion is issuer-side CAE relationships and it has no channel into the top-100 CPA-firm National Office that actually authorizes external-audit tooling spend — distribution-channel barrier."},{"name":"ChatGPT Enterprise used ad-hoc by senior associates","category":"AI-native horizontal","uncopyabilityReason":"Horizontal LLM chat has no integration into the firm's engagement-management system (CaseWare/AdvanceFlow) and no notion of engagement-letter scope, independence rules, or PCAOB workpaper-retention requirements; shipping those hooks would require integration-depth into firm-specific document repositories that OpenAI's product surface intentionally avoids — integration-depth barrier."}]},"studioThesis":"T-AIS-PREM","killThreshold":{"K":11,"M":75,"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 (stateless document drafter ↔ persistent engagement-state with preparer/reviewer identity + PBC lineage)","yAxis":"Authority boundary (back-office analytics suggestion ↔ engagement-letter-scoped workpaper originator covered under firm's quality-control system)","winningQuadrant":"persistent engagement-state agent operating inside the engagement-letter scope so each workpaper carries preparer, reviewer, and source-artifact lineage the National Office can sign off on","loservilleEscape":true,"loservilleQuadrant":"stateless LLM drafting loose memos outside the firm's QC system — the mode MindBridge and ChatGPT-Enterprise ad-hoc usage exhibit today, where associates re-key the same PBC context into every prompt and the reviewer has no way to verify which client artifact a number came from"}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aaccountants-and-auditors-audit-workpaper-preparation%3At-ais-prem%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aaccountants-and-auditors-audit-workpaper-preparation%3At-hsa%3Av1","id":"fh:accountants-and-auditors-audit-workpaper-preparation:t-hsa:v1","lens":"HeadlessSaaS","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/accountants-and-auditors-audit-workpaper-preparation","stableHash":"wcc:accountants-and-auditors:audit-workpaper-preparation:document:v1"},"problem":{"slotStatement":"On dental-practice engagements the in-charge senior routinely tick-marks and clears review notes on workpaper sections that AICPA independence and firm policy say only the engagement manager or partner may sign off — the authority boundary between preparer, reviewer, and approver is enforced only by Initials-in-a-box in the workpaper binder, so every peer review cycle surfaces out-of-role sign-offs that force the partner to re-perform and re-date entire sections, inflating close time by 3–6 weeks per engagement and triggering quality-control remediation."},"approach":{"oneSentence":"Engagement-letter-bound workpaper headless API that binds every tick-mark, review-note clear, and section sign-off to the signer's AICPA role and the firm's QC matrix, refuses writes that cross the preparer/reviewer/approver boundary, and hands the partner a verifiable sign-off trace the peer reviewer can replay section-by-section."},"customer":{"icpShape":"Audit Partner (economic buyer, signs the engagement-software PO) at a 40–150-person regional CPA firm serving solo dental practices (targetCompanyType: company-type-solo-dental-practice) as attest clients, where the buyer is the Audit Partner / Quality Review Partner and the daily user is the Senior Auditor / In-Charge preparing workpapers for dental PC reviews and compilations.","beachheadShape":"EarlyAdopterJTBD: regional CPA firms whose dental-practice attest book got flagged in their last peer review for workpaper sign-off authority gaps and who need a fix before next PCAOB/AICPA inspection cycle."},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-MoneyOnDelivery","beachhead":"EarlyAdopterJTBD: regional CPA firms whose dental-practice attest book got flagged in their last peer review for workpaper sign-off authority gaps and who need a fix before next PCAOB/AICPA inspection cycle.","competitors":{"substitutes":[{"name":"CaseWare Working Papers (with SmartSync)","category":"incumbent","uncopyabilityReason":"CaseWare's role model is a thick-client document-locking scheme built for large-firm deployments; adding engagement-letter-bound authority enforcement that actually refuses a senior's sign-off on partner-only sections would require rewriting the SmartSync replication protocol and the thirty-year-old desktop binder file format — an integration-depth barrier they cannot unwind in two quarters without breaking every existing firm template."},{"name":"Thomson Reuters AdvanceFlow / Checkpoint Engage","category":"incumbent","uncopyabilityReason":"AdvanceFlow is sold as a bundled SaaS tied to the Checkpoint content library and UltraTax workflow; its revenue model depends on firms standardizing on the Thomson stack end-to-end, so exposing a headless authority-boundary API that regional firms could embed into a best-of-breed binder would cannibalize the bundle — a distribution-channel barrier, not a tech gap."},{"name":"Wolters Kluwer CCH Axcess Engagement","category":"incumbent","uncopyabilityReason":"CCH Axcess is multi-tenant SaaS with a shared role taxonomy hard-coded at the tenant level; per-engagement-letter authority matrices that vary by client (dental PC vs. medical group vs. nonprofit) would require a capital-intensive re-architecture of their permissions service, which currently serves 100k+ tenants on a single schema."},{"name":"AuditBoard SOXHUB / OpsAudit","category":"AI-native horizontal","uncopyabilityReason":"AuditBoard's deployment mode targets internal-audit and SOX functions inside public-company issuers, not external CPA firms doing attest work on private dental PCs; its data model has no concept of an AICPA engagement letter or a peer-review-reviewable external sign-off chain — a deployment-mode-mismatch barrier that would require building a parallel product line for the external-attest market."},{"name":"Manual Excel tickmark sheets + PDF sign-off stamps shared over firm file server","category":"manual-bridge"},{"name":"Senior auditor emailing partner for verbal OK then initialing the box themselves","category":"informal"}]},"studioThesis":"T-HSA","killThreshold":{"K":11,"M":75,"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":"Authority-boundary enforcement (initials-in-a-box honor system ↔ engagement-letter-bound API that refuses out-of-role writes)","yAxis":"Deployment posture (monolithic SaaS binder with fixed role taxonomy ↔ headless API embeddable into the firm's existing CaseWare/Axcess binder)","winningQuadrant":"Headless API that refuses cross-boundary sign-offs per-engagement-letter and drops into the firm's existing binder tooling without ripping out CaseWare","loservilleEscape":true,"loservilleQuadrant":"Monolithic SaaS binder like AdvanceFlow where role enforcement is a checkbox field the senior can still tick on the partner's behalf, surfacing as peer-review findings every cycle"}},"unmetRequirements":[],"pricingArchitecture":"custom-quote","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aaccountants-and-auditors-audit-workpaper-preparation%3At-hsa%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aaccountants-and-auditors-financial-statement-review%3At-ais-prem%3Av1","id":"fh:accountants-and-auditors-financial-statement-review:t-ais-prem:v1","lens":"ManagedWorkflow","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"C7_magicLensFit":0,"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/accountants-and-auditors-financial-statement-review","stableHash":"wcc:accountants-and-auditors:financial-statement-review:document:v1"},"problem":{"slotStatement":"When the external auditor asks why the unbilled-revenue accrual swung $4M between Q2 and Q3, the staff accountant opens a shared Google Drive folder of 40 workpapers and cannot show who decided to reclassify the weather-normalization reserve or which rate-case exhibit drove it — the journal entry exists, the supporting memo exists, but the causal thread between them was never recorded, so Controller-level sign-off becomes a scramble of Slack archaeology two days before the FERC filing deadline."},"approach":{"oneSentence":"A close-binder workflow pinned to each utility's GL reconciliation and rate-case exhibits that captures every reclassification decision as a signed workpaper entry tying the journal line to the analyst, the rate-order citation, and the reviewing controller — so when the auditor asks 'why this accrual', the answer is one click, not a Slack search."},"customer":{"icpShape":"VP of Finance / Assistant Controller at an investor-owned public utility (CompanyType/company-type-public-utility, typically 500k–3M meters, FERC/PUC-regulated), where the buyer is the VP of Finance or Assistant Controller who owns the quarterly close and external-audit budget, and the daily user is the senior staff accountant running balance-sheet reconciliations and variance memos during the Day 5–Day 10 close window.","beachheadShape":"EarlyMajorityWorkflow: investor-owned electric and combined gas-and-electric utilities running Oracle EBS or SAP with a PwC/Deloitte external audit and an active PUC rate case, where the quarterly 10-Q review must tie to the FERC Form 1 roll-forward."},"archetype":"startup-archetypes.org.ai/ManagedWorkflow-RetainerEngagement","beachhead":"EarlyMajorityWorkflow: investor-owned electric and combined gas-and-electric utilities running Oracle EBS or SAP with a PwC/Deloitte external audit and an active PUC rate case, where the quarterly 10-Q review must tie to the FERC Form 1 roll-forward.","competitors":{"substitutes":[{"name":"Network drive / Google Drive folder per close","category":"informal"},{"name":"BlackLine Account Reconciliations + Journal Entry","category":"incumbent","uncopyabilityReason":"BlackLine's reconciliation workflow is built around matching balances and certifying completion, not around capturing the narrative causal chain that links a reclassification to a specific PUC rate-order exhibit; adding utility-specific rate-case evidence capture would require deep integration with FERC Form 1 roll-forward logic and PUC filing formats that sit outside BlackLine's horizontal cross-industry integration depth, which is its core distribution asset."},{"name":"Workiva Wdesk (close + SOX + regulatory reporting)","category":"incumbent","uncopyabilityReason":"Workiva's deployment posture is a document-assembly cloud optimized for SEC/10-Q filing round-tripping; its liability posture as the system of record for public filings means it cannot ship an opinionated decision-capture engine that takes authoritative positions on rate-case causality without materially changing its attestation exposure to subscribers, so it is structurally locked into being the document surface, not the decision log."},{"name":"Trintech Cadency","category":"incumbent","uncopyabilityReason":"Trintech's vertical-data-corpus advantage is in banking and insurance reconciliation templates; it lacks the utility-specific regulatory corpus (FERC USOA account structure, state PUC rate-order libraries, weather-normalization methodologies) required to auto-link a reclass to the rate-case exhibit that authorized it, and building that corpus would require a multi-year utility-analyst partnership outside its current go-to-market."},{"name":"Big 4 audit-support staff augmentation (Deloitte / PwC managed services)","category":"human alternative","uncopyabilityReason":"Deloitte's managed-services model carries independence-rule liability posture under PCAOB and SEC auditor-independence rules — they cannot simultaneously be the external auditor of record and the vendor operating the client's decision-capture system of record for the accounts being audited, which structurally blocks them from occupying the winning quadrant for any audit client they already serve."}]},"studioThesis":"T-AIS-PREM","killThreshold":{"K":8,"M":75,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Decision-capture granularity (balance-level sign-off only ↔ per-reclassification causal entry tying journal line to rate-order citation and named approver)","yAxis":"Utility-regulatory corpus depth (horizontal cross-industry templates ↔ FERC USOA + state PUC rate-order library pre-loaded)","winningQuadrant":"per-reclassification causal capture running on a pre-loaded FERC/PUC corpus, so every unbilled-revenue or weather-normalization swing carries its rate-case justification inline with the journal entry","loservilleEscape":true,"loservilleQuadrant":"balance-level sign-off on horizontal templates — BlackLine's close-certification model, which confirms the $4M swing was reviewed but cannot surface which PUC exhibit authorized the reclass, forcing Controllers into Slack archaeology during the auditor's PBC request"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aaccountants-and-auditors-financial-statement-review%3At-ais-prem%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aaccountants-and-auditors-financial-statement-review%3At-operations%3Av1","id":"fh:accountants-and-auditors-financial-statement-review:t-operations:v1","lens":"HeadlessSaaS","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/accountants-and-auditors-financial-statement-review","stableHash":"wcc:accountants-and-auditors:financial-statement-review:document:v1"},"problem":{"slotStatement":"A 12-entity NetSuite shop closes ~8,000 reconciling journal lines per month, hits a 6–9% exception rate on intercompany and accrual tie-outs, and each kicked-back item burns ~45 minutes of senior-accountant rework plus slips the close by a day — headcount can't grow linearly with acquisition-driven volume, so Day-5 close keeps sliding to Day-10."},"approach":{"oneSentence":"ERP-embedded reconciliation workflow that reconciles GL-to-subledger and intercompany ties inside NetSuite (with SAP and Dynamics 365 connectors), auto-clears matched lines against a client-tunable rules library, and escalates edge-case variances to a human-in-the-loop queue that hands the senior accountant a review-ready tie-out packet with primary-source citations — priced per transaction with an annual floor."},"customer":{"icpShape":"Shared-services finance operations at $50M–$500M NetSuite-standardized multi-entity companies (PE-backed roll-ups in professional services, SaaS, and light manufacturing) running a 6–20 person close team across 3–15 legal entities, where the buyer is the VP Controller or VP of Finance Operations (signs the annual contract out of the finance-transformation budget) and the daily user is the Senior Staff Accountant running monthly reconciliations and statement review.","beachheadShape":"EarlyMajorityWorkflow — PE-backed NetSuite multi-entity roll-ups in months 3–18 post-acquisition with intercompany reconciliation backlogs"},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-Subscription","beachhead":"EarlyMajorityWorkflow — PE-backed NetSuite multi-entity roll-ups in months 3–18 post-acquisition with intercompany reconciliation backlogs","competitors":{"substitutes":[{"name":"UiPath Finance Automation","category":"incumbent RPA"},{"name":"BlackLine Account Reconciliations","category":"incumbent close-software"},{"name":"NetSuite Account Reconciliation (Oracle native module)","category":"ERP-native automation"},{"name":"Genpact / Auxis finance BPO","category":"human alternative (outsourced BPO)"}]},"studioThesis":"T-OPERATIONS","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"ERP integration depth (external dashboard with CSV export ↔ native NetSuite SuiteApp writing cleared entries back into the subledger)","yAxis":"Exception-handling model (rule-only auto-clear that dumps all misses to a queue ↔ tiered human-in-loop review that returns a cited tie-out packet)","winningQuadrant":"Native SuiteApp that auto-clears inside NetSuite AND returns a human-reviewed, citation-linked packet for the 6–9% that don't match","loservilleEscape":true,"loservilleQuadrant":"UiPath screen-scrape bots that shuttle CSVs between NetSuite and Excel with no tiered review, dumping every unmatched line into an undifferentiated accountant queue"}},"unmetRequirements":[],"pricingArchitecture":"tiered","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aaccountants-and-auditors-financial-statement-review%3At-operations%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aaccountants-and-auditors-financial-statement-review%3At-professional%3Av1","id":"fh:accountants-and-auditors-financial-statement-review:t-professional:v1","lens":"AgenticWorkflow","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/accountants-and-auditors-financial-statement-review","stableHash":"wcc:accountants-and-auditors:financial-statement-review:document:v1"},"problem":{"slotStatement":"On financial-statement review engagements the partner must personally stand behind every tie-out, disclosure checklist item, and chart-of-accounts reclassification — one missed related-party disclosure or period-boundary accrual surfaced in peer review or a malpractice claim costs the partner weeks of remediation, a state-board inquiry, and a hard premium hit on the firm's professional-liability renewal."},"approach":{"oneSentence":"Engagement-letter-bound reconciliation service where a licensed CPA partner signs off on every tie-out, disclosure checklist, and journal-entry reclassification, delivered as a review-ready workpaper binder with primary-source citations back to the trial balance, billed on a $7K–$35K monthly retainer or partner-rate hourly."},"customer":{"icpShape":"Managing partners and audit/assurance practice leads at AICPA peer-reviewed CPA firms (regional firms with 20–150 professionals, $5M–$50M annual fee revenue) who personally sign engagement letters for SSARS review and compilation work — where the buyer is the Managing Partner / Assurance Practice Leader and the daily user is the senior accountant or engagement manager running the reconciliation file.","beachheadShape":"EarlyAdopterJTBD: regional CPA firms whose last AICPA peer review flagged documentation or disclosure deficiencies on SSARS-21 review engagements"},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-UsageMetered","beachhead":"EarlyAdopterJTBD: regional CPA firms whose last AICPA peer review flagged documentation or disclosure deficiencies on SSARS-21 review engagements","competitors":{"substitutes":[{"name":"Big-4 assurance outsourcing arms (Deloitte, PwC Managed Services)","category":"incumbent"},{"name":"Regional CPA boutiques offering white-label review support (e.g., Aprio, Armanino outsourced assurance)","category":"human alternative"},{"name":"Hiring another senior-associate CPA in-house","category":"build-vs-buy human alternative"},{"name":"Generic AI reconciliation SaaS (Trullion, FloQast AutoRec)","category":"AI-native horizontal"}]},"studioThesis":"T-PROFESSIONAL","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Partner signature density (unsigned SaaS output ↔ named-CPA-partner sign-off on every deliverable with PLI coverage)","yAxis":"Peer-review defensibility of the workpaper trail (loose export ↔ AICPA peer-review-ready binder with traceable citations to source documents)","winningQuadrant":"named-partner-signed deliverables backed by a peer-review-ready, citation-traceable workpaper binder the client firm can drop directly into their SSARS engagement file","loservilleEscape":true,"loservilleQuadrant":"Generic AI reconciliation SaaS (Trullion, FloQast AutoRec) that emits unsigned spreadsheet exports with no licensed reviewer and no peer-review-grade evidence trail — leaving the engagement partner personally exposed when the state board or peer reviewer asks who stood behind the number"}},"unmetRequirements":[],"pricingArchitecture":"custom-quote","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aaccountants-and-auditors-financial-statement-review%3At-professional%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aaccountants-and-auditors-tax-return-assembly%3At-hsa%3Av1","id":"fh:accountants-and-auditors-tax-return-assembly:t-hsa:v1","lens":"AgenticWorkflow","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/accountants-and-auditors-tax-return-assembly","stableHash":"wcc:accountants-and-auditors:tax-return-assembly:document:v1"},"problem":{"slotStatement":"Every filing season the tax team re-applies last year's state apportionment factors, Section 174 treatment, and multi-entity K-1 allocations from prior workpapers, only to discover during review — or worse, after a state notice lands — that a revenue-agent ruling or mid-year statute change silently invalidated the carry-forward logic, forcing schedule rework and exposing the DSO to amended-return penalties and audit findings."},"approach":{"oneSentence":"Engagement-letter-bound tax-assembly workflow that monitors each rule cited on a prior workpaper against the current IRS/state bulletin feed, flags schedules built on stale citations before partner review, and certifies every number on the return to a dated authority so the binder is review-ready for both internal sign-off and any downstream state examination."},"customer":{"icpShape":"Director of Tax at a PE-backed Dental Service Organization (company-type-pe-backed-dso) that rolls up 40-200 practice entities into consolidated 1120/1065 filings, where the buyer is the Director of Tax or VP Finance who signs the tooling PO and the daily user is the senior tax associate assembling the federal/state schedules and apportionment workpapers each season.","beachheadShape":"EarlyAdopterJTBD: PE-backed DSO tax directors running the first post-acquisition consolidated return cycle where prior-year workpapers were prepared by a patchwork of local CPAs under now-obsolete state rules."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-Subscription","beachhead":"EarlyAdopterJTBD: PE-backed DSO tax directors running the first post-acquisition consolidated return cycle where prior-year workpapers were prepared by a patchwork of local CPAs under now-obsolete state rules.","competitors":{"substitutes":[{"name":"CCH Axcess Tax (Wolters Kluwer)","category":"incumbent","uncopyabilityReason":"CCH Axcess is architected around form-fill compliance: its content team publishes form updates once per rule-promulgation cycle, but there is no per-workpaper citation graph linking a K-1 line to the specific Rev. Proc. or state TAM that justifies it. Retrofitting citation-level rule-drift detection would require rebuilding the input-worksheet engine that drives their per-return SKU revenue — a vertical-data-corpus barrier tied to 30 years of proprietary form content."},{"name":"Thomson Reuters GoSystem Tax RS","category":"incumbent","uncopyabilityReason":"GoSystem's value is deep integration with Checkpoint research and the Onvio workpaper suite, but that integration is advisory-only: Checkpoint tells a human researcher the rule changed, it does not reach into the filed-last-year return and invalidate dependent schedules. Closing that loop requires an integration-depth rewrite across three separately-licensed product lines owned by different Thomson BUs."},{"name":"Bloomberg Tax Provision / Workpapers","category":"incumbent","uncopyabilityReason":"Bloomberg's workpaper product is sold to F500 corporate tax departments with in-house provision analysts, not PE-backed roll-ups with 40+ entity apportionment. Its deployment-mode is a single-entity provision workbook; scaling to multi-entity DSO consolidation with state-by-state nexus drift would require a deployment-mode-mismatch rebuild plus a new distribution channel into mid-market PE portcos."},{"name":"Big-4 outsourced tax compliance (Deloitte/PwC tax managed services)","category":"human alternative","uncopyabilityReason":"Big-4 tax managed services carry state-licensure authority (signed 1120 by licensed CPA) that software cannot claim — but their liability-posture is the exact reason they cannot ship aggressive automated rule-drift detection: a false-positive flag that delays a filing creates malpractice exposure their partnership insurance will not underwrite."},{"name":"Prior-year Excel workpapers + shared OneDrive folder","category":"manual-bridge"},{"name":"Ironclad contract repository (for engagement letters and prior-year binders)","category":"informal"}]},"studioThesis":"T-HSA","killThreshold":{"K":10,"M":30,"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":"Rule-drift detection mode (annual content-team form update ↔ continuous per-citation bulletin monitoring against last-year's workpapers)","yAxis":"Multi-entity consolidation fit (single-entity provision workbook ↔ 40-200 entity PE-roll-up apportionment with per-state nexus tracking)","winningQuadrant":"continuous per-citation rule-drift monitoring wired into a 40-200 entity DSO consolidation, so a mid-year Rev. Proc. or state TAM automatically surfaces every downstream schedule that inherited the now-stale treatment before the partner signs the return","loservilleEscape":true,"loservilleQuadrant":"CCH Axcess/GoSystem-style annual form-content refresh bolted onto a single-entity workbook, which is how a DSO tax director discovers in September that 14 of 47 practice entities used a superseded apportionment factor — exactly the failure mode CCH's and Bloomberg's current workpaper products exhibit"}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aaccountants-and-auditors-tax-return-assembly%3At-hsa%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aadministrative-services-managers-facilities-contract-review%3At-hsa%3Av1","id":"fh:administrative-services-managers-facilities-contract-review:t-hsa:v1","lens":"ManagedWorkflow","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"C7_magicLensFit":0,"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/administrative-services-managers-facilities-contract-review","stableHash":"wcc:administrative-services-managers:facilities-contract-review:document:v1"},"problem":{"slotStatement":"Vendor contract review cycles drag from 3 days to 14 days because initial handoffs via email lack required SLA compliance metrics, forcing the contract manager into a 4-step rework loop to chase missing insurance certificates and pricing schedules before a review can even begin."},"approach":{"oneSentence":"A vendor-SLA evaluation pipeline that intercepts inbound supplier agreements at the edge, evaluates them against baseline facility requirements, and routes a review-ready compliance ledger to the contract manager only when the submission is complete."},"customer":{"icpShape":"VP of Operations at a 50-200 employee commercial real estate firm (company-type-bootstrap-agency) where the buyer is the VP of Operations and the daily user is the Facilities Contract Manager.","beachheadShape":"EarlyMajorityWorkflow: outsourced facilities administration teams managing high-volume vendor SLA renewals for mid-market property portfolios."},"archetype":"startup-archetypes.org.ai/ManagedWorkflow-MoneyOnDelivery","beachhead":"EarlyMajorityWorkflow: outsourced facilities administration teams managing high-volume vendor SLA renewals for mid-market property portfolios.","competitors":{"substitutes":[{"name":"shared-inbox and manual Slack routing","category":"informal"},{"name":"Ironclad","category":"incumbent","uncopyabilityReason":"Ironclad is anchored to a heavy integration-depth barrier — its ingestion layer relies on structured upstream ERP/CRM data mappings, meaning it cannot natively evaluate arbitrary facility SLA attachments at the inbox edge without a six-month professional services lift to rebuild its metadata parsers."},{"name":"Agiloft","category":"incumbent","uncopyabilityReason":"Agiloft suffers from a deployment-mode-mismatch — it acts as a centralized system-of-record requiring structured contract-record creation, which structurally prevents it from sitting inline as an unauthenticated pre-triage filter for messy external vendor emails without fundamentally breaking its tenant-isolation model."}]},"studioThesis":"T-HSA","killThreshold":{"K":10,"M":75,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Handoff interception (post-upload repository ↔ pre-triage inbox edge)","yAxis":"Cost shape (per-seat licensed ACV ↔ document-metered self-serve)","winningQuadrant":"Pre-triage inbox interception coupled with document-metered pricing that catches missing SLAs before the vendor review clock even starts.","loservilleEscape":true,"loservilleQuadrant":"Ironclad post-upload repository gated behind rigid per-seat licensing, where incomplete contracts sit idly until a user logs in only to trigger a manual rework loop for missing attachments."}},"unmetRequirements":[],"pricingArchitecture":"tiered","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aadministrative-services-managers-facilities-contract-review%3At-hsa%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aadministrative-services-managers-policy-manual-update%3At-td%3Av1","id":"fh:administrative-services-managers-policy-manual-update:t-td:v1","lens":"ManagedWorkflow","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/administrative-services-managers-policy-manual-update","stableHash":"wcc:administrative-services-managers:policy-manual-update:document:v1"},"problem":{"slotStatement":"When the board amends a policy (say Policy 210 on credit and collections), the Admin Services Manager edits the Word master on a shared drive, emails redlines to department heads, and manually re-issues binders — but three months later nobody can prove which version of Policy 210 was in force the night a disputed service disconnection happened, and the RUS auditor's provenance question sits unanswered for weeks."},"approach":{"oneSentence":"A board-resolution-linked policy register that ingests each approved motion from the board packet, redlines the affected manual sections against the prior in-force version, routes department-head acknowledgements with timestamps, and issues a dated, board-minute-cited manual edition that any auditor or member can trace back to the exact meeting that enacted it."},"customer":{"icpShape":"The General Manager / CEO at a member-owned electric cooperative (CompanyType/company-type-member-owned-electric-cooperative) in the 15k–150k meter band, where the buyer is the GM/CEO (who signs the software PO and answers to the elected board for RUS and NERC/FERC posture) and the daily user is the Administrative Services Manager or Corporate Secretary who maintains the Board Policy Manual and Section 7/Section 9 administrative policies.","beachheadShape":"EarlyMajorityWorkflow: Touchstone Energy / NRECA-affiliated distribution cooperatives with 20–60k meters that just completed an RUS Form 7 audit or a board-ordered policy refresh and have a standing Policy Committee cycle."},"archetype":"startup-archetypes.org.ai/ManagedWorkflow-MarketplaceClearing","beachhead":"EarlyMajorityWorkflow: Touchstone Energy / NRECA-affiliated distribution cooperatives with 20–60k meters that just completed an RUS Form 7 audit or a board-ordered policy refresh and have a standing Policy Committee cycle.","competitors":{"substitutes":[{"name":"Network drive / SharePoint folder holding the Word master and PDF binders","category":"manual-bridge","uncopyabilityReason":"A folder is not a product; it has no enactment chain, no in-force-on-date query, and no acknowledgement ledger — it is the pain, not a competitor."},{"name":"NISC iVUE Connect (policy and board-packet modules)","category":"incumbent","uncopyabilityReason":"NISC is a cooperative-owned CIS/accounting core whose roadmap is governed by a member ballot and multi-year release train; bolting a resolution-to-policy provenance engine onto iVUE requires touching the board-packet module, the document repository, and the member-portal notification layer simultaneously — integration depth across three regulated modules that NISC ships on an 18-month cadence, not six months."},{"name":"BoardDocs (Diligent Community) used for board packets and meeting minutes","category":"incumbent","uncopyabilityReason":"BoardDocs is a meeting-workflow product whose data model ends at the approved minute; it has no representation of an 'in-force manual section' or a department-head acknowledgement ledger, and its SOC2-scoped multi-tenant SaaS deployment cannot absorb a cooperative's on-prem Word/PDF manual corpus without a deployment-mode rebuild away from its K-12/municipal template library."},{"name":"PowerDMS (NEOGOV) policy management","category":"incumbent","uncopyabilityReason":"PowerDMS owns the law-enforcement and healthcare accreditation corpus (CALEA, DNV) and its distribution channel, pricing, and content library are tuned to those verticals; it lacks the NRECA/RUS policy taxonomy, the Section 7/Section 9 bylaw structure, and the Form 7 audit hooks, and rebuilding that vertical-data corpus and cooperative sales motion is a multi-year commitment against its core verticals."},{"name":"ChatGPT Enterprise used ad-hoc by the Admin Services Manager to summarize redlines","category":"AI-native horizontal","uncopyabilityReason":"A horizontal LLM has no liability posture for 'this is the policy that was in force on 2024-11-12' — it cannot be deposed, cannot sign an RUS auditor's attestation, and OpenAI's product shape deliberately avoids the regulated-record-of-authority liability that a cooperative's board minutes demand."}]},"studioThesis":"T-TD","killThreshold":{"K":11,"M":80,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Enactment linkage (free-text document store ↔ every manual section hard-linked to the board resolution and meeting minute that enacted it)","yAxis":"In-force-on-date query (latest-version-only ↔ point-in-time reconstruction of the full manual as of any historical date)","winningQuadrant":"Every policy section hard-linked to its enacting board motion, with point-in-time reconstruction so an auditor or member can pull 'the manual as it stood on 2024-11-12 at 19:00 CT'","loservilleEscape":true,"loservilleQuadrant":"Free-text Word masters on a SharePoint folder showing only the latest version — the exact failure mode BoardDocs and the shared-drive bridge exhibit when an RUS auditor asks which credit-and-collections policy governed a disputed November disconnection"}},"unmetRequirements":[],"pricingArchitecture":"tiered","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aadministrative-services-managers-policy-manual-update%3At-td%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aaudio-and-video-technicians-post-production-audio-mix%3At-ais-prem%3Av1","id":"fh:audio-and-video-technicians-post-production-audio-mix:t-ais-prem:v1","lens":"CoPilot","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/audio-and-video-technicians-post-production-audio-mix","stableHash":"wcc:audio-and-video-technicians:post-production-audio-mix:multimodal:v1"},"problem":{"slotStatement":"The mixer delivers a final executive or PUC-hearing master, but Comms, Legal, and the SVP sponsor are each endorsing their approval on a printed wet-signature routing sheet that walks the building for two to five days — meanwhile the mixer keeps pushing tweaked stems that nobody is authorized to bless, and half the time the file that ships to distribution is a version that was never actually signed off on the paper form."},"approach":{"oneSentence":"Session-bound mix sign-off that locks each stem-and-master revision to the named approvers (Comms, Legal, SVP Sponsor) with their scope of authority pre-encoded, routes the endorsement inside the DAW delivery handoff, and emits a verifiable output showing exactly which rendered WAV/MP3 hash every approver actually cleared — so distribution can only pull a master whose endorsements match the file being shipped."},"customer":{"icpShape":"Director of Corporate Communications / Media Production at a mid-to-large investor-owned or municipal public utility (company-type-public-utility, typically 500k–3M meter accounts) where the buyer who signs the PO is the Director of Corporate Communications and the daily user is the contracted post-production audio mixer/re-recording engineer handling executive town-halls, PUC-hearing testimony recaps, outage-response PSAs, and safety-training narration masters.","beachheadShape":"EarlyMajorityWorkflow: in-house and contracted post-production audio teams serving regulated-utility communications groups who must ship executive and regulatory-voiceover masters with endorsed sign-off before distribution."},"archetype":"startup-archetypes.org.ai/CoPilot-Subscription","beachhead":"EarlyMajorityWorkflow: in-house and contracted post-production audio teams serving regulated-utility communications groups who must ship executive and regulatory-voiceover masters with endorsed sign-off before distribution.","competitors":{"substitutes":[{"name":"Wet-signature paper routing sheet walked desk-to-desk","category":"informal","uncopyabilityReason":""},{"name":"Avid Pro Tools session notes + shared-drive 'FINAL_v7_approved' filename convention","category":"manual-bridge","uncopyabilityReason":""},{"name":"Frame.io (Adobe) review-and-approve for audio deliverables","category":"incumbent","uncopyabilityReason":"Frame.io's approval model is a generic creative-reviewer thumbs-up tied to a comment thread, not a scoped-authority endorsement bound to the specific rendered-file hash and the approver's delegated signing scope. Rebuilding a utility-grade authority-boundary model (Legal vs. Comms vs. SVP scopes, PUC-hearing evidentiary posture) would require re-architecting Frame.io's role/permission primitives, which are load-bearing for Adobe's prosumer creator pricing and cross-industry positioning — a deployment-mode-mismatch moat."},{"name":"DocuSign CLM routed around the WAV deliverable","category":"incumbent","uncopyabilityReason":"DocuSign's signature envelope sits outside the DAW delivery pipeline — it signs a PDF cover sheet, not the specific master render. Closing the gap requires deep integration into Pro Tools / Nuendo / Wwise session-export tooling and broadcast-delivery handoffs (AS-11, PAD, loudness-compliance metadata); that is an integration-depth moat DocuSign has never built because its revenue comes from horizontal contract workflows, not media-asset binding."},{"name":"Workiva for regulated-communications attestations","category":"AI-native horizontal","uncopyabilityReason":"Workiva owns the SEC/ESG document-assurance corpus and workflow, but it has no vertical-data-corpus for broadcast audio masters, loudness standards (ITU-R BS.1770, CALM Act), or DAW session artifacts. Extending into mix sign-off would require acquiring utility-comms and post-production audio reference data plus NLE/DAW integrations — a vertical-data-corpus barrier that is orthogonal to Workiva's filing-centric revenue base."}]},"studioThesis":"T-AIS-PREM","killThreshold":{"K":9,"M":40,"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":"Authority boundary of the approval (generic reviewer thumbs-up ↔ scoped signing authority bound to named Legal/Comms/SVP roles with delegated scope)","yAxis":"Artifact binding (approval attached to a comment thread or PDF cover sheet ↔ approval cryptographically bound to the exact rendered master WAV/MP3 hash that ships)","winningQuadrant":"Scoped-authority endorsements cryptographically bound to the exact master hash shipped to distribution, so an unauthorized or stale-version release is structurally impossible","loservilleEscape":true,"loservilleQuadrant":"Generic reviewer thumbs-up floating on a comment thread detached from the actual file — the failure mode Frame.io exhibits when the mixer re-renders 'FINAL_v7' after sign-off and distribution grabs the newer untagged file"}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aaudio-and-video-technicians-post-production-audio-mix%3At-ais-prem%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Abuyers-and-purchasing-agents-purchase-order-review%3At-td%3Av1","id":"fh:buyers-and-purchasing-agents-purchase-order-review:t-td:v1","lens":"ManagedWorkflow","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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/buyers-and-purchasing-agents-purchase-order-review","stableHash":"wcc:buyers-and-purchasing-agents:purchase-order-review:document:v1"},"problem":{"slotStatement":"Purchasing agents sit on a 200+ PO approval queue each week manually cross-checking line items against the requisition, the contract price list, and the vendor master for duplicate-PO and split-PO patterns — approvers rubber-stamp under deadline pressure, and the exceptions that slip through surface weeks later as invoice-match breaks or audit findings on the SOX three-way-match control."},"approach":{"oneSentence":"A PO-approval decision record that reconciles each line against the originating requisition, the active contract price book, and a 90-day duplicate/split-PO window inside the NetSuite approval screen, and writes a review-ready justification note — citing the requisition ID, contract clause, and duplicate-check result — to the PO audit trail before the approver clicks Approve."},"customer":{"icpShape":"Director of Procurement at US mid-market discrete manufacturers ($200M–$1B revenue) running NetSuite or Dynamics 365 F&O, where the buyer is the Director of Procurement (signs the tooling PO and owns the three-way-match SOX control) and the daily user is the Purchasing Agent clearing the PO approval queue","beachheadShape":"EarlyMajorityWorkflow: NetSuite-based discrete manufacturers with >500 POs/month and an active SOX three-way-match control"},"archetype":"startup-archetypes.org.ai/ManagedWorkflow-MoneyOnDelivery","beachhead":"EarlyMajorityWorkflow: NetSuite-based discrete manufacturers with >500 POs/month and an active SOX three-way-match control","competitors":{"substitutes":[{"name":"NetSuite native PO approval workflow with SuiteFlow rules","category":"incumbent"},{"name":"Coupa / Ivalua spend-control suite","category":"incumbent"},{"name":"AppZen / Oversight.ai autonomous AP/spend audit","category":"AI-native horizontal"},{"name":"Offshore BPO PO-review team (Genpact, WNS)","category":"human alternative"}]},"studioThesis":"T-TD","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence depth per line (approver sees a yes/no flag ↔ approver sees cited requisition line, contract clause, and duplicate-PO hit)","yAxis":"Where the review happens (separate spend-audit console reviewed weekly ↔ inline on the NetSuite PO approval screen before click-Approve)","winningQuadrant":"cited line-level evidence surfaced inline on the NetSuite PO approval screen, written to the PO audit trail as a review-ready justification note","loservilleEscape":true,"loservilleQuadrant":"AppZen-style post-hoc spend-audit console that flags exceptions weeks after the PO was approved, with no citation back to the requisition line or contract clause the approver needed at click-time"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Abuyers-and-purchasing-agents-purchase-order-review%3At-td%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Abuyers-and-purchasing-agents-rfq-package-preparation%3At-hsa%3Av1","id":"fh:buyers-and-purchasing-agents-rfq-package-preparation:t-hsa:v1","lens":"AgenticWorkflow","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/buyers-and-purchasing-agents-rfq-package-preparation","stableHash":"wcc:buyers-and-purchasing-agents:rfq-package-preparation:document:v1"},"problem":{"slotStatement":"When the board asks why Bidder B won over Bidder A on the 25 kVA pad-mount transformer RFQ, the purchasing agent cannot reconstruct which spec revision was sent to each vendor, which clarifications were issued mid-window, or which exceptions were accepted — the email thread, the SharePoint folder, and the tabulation spreadsheet disagree, and the RUS auditor flags the award package for missing evidence of equal-treatment."},"approach":{"oneSentence":"A co-op-procurement workflow engine that runs the full RFQ lifecycle — spec-packet assembly from RUS/NRECA templates, vendor distribution, clarification logging, bid tabulation, and award recommendation — while stitching every vendor-facing artifact, timestamp, and exception into a single traceable record the co-op attorney and RUS auditor can walk end-to-end without reopening Outlook."},"customer":{"icpShape":"Director of Power Supply & Contracts (budget holder and PO signer) at a 30k–150k-meter member-owned electric cooperative (CompanyType/company-type-member-owned-electric-cooperative), where the buyer is the Director of Power Supply & Contracts and the daily user is the Senior Buyer / Purchasing Agent running RFQs for transformers, conductor, poles, and construction services under RUS/USDA-funded work plans.","beachheadShape":"EarlyAdopterJTBD: G&T-affiliated distribution co-ops in the 30k–150k meter band running 80–200 RFQs/year against NRECA-standard specs and USDA-RUS Bulletin 1726/1728 material lists."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-Subscription","beachhead":"EarlyAdopterJTBD: G&T-affiliated distribution co-ops in the 30k–150k meter band running 80–200 RFQs/year against NRECA-standard specs and USDA-RUS Bulletin 1726/1728 material lists.","competitors":{"substitutes":[{"name":"Manual Outlook + SharePoint + Excel bid-tab workflow","category":"manual-bridge"},{"name":"Bonfire (Euna Solutions) public-sector e-sourcing","category":"incumbent","uncopyabilityReason":"Bonfire's deployment model is tuned to municipal/state public-bid statutes and its template library, approval chains, and vendor-portal UX are built around open-public-notice procurement — retrofitting RUS Bulletin 1726/1728 material lists, NRECA spec inheritance, and co-op board-approval workflow would require a vertical-data-corpus rebuild (co-op construction work plans, RUS equal-treatment evidence model) that its muni customer base will not fund."},{"name":"Power Advocate (sourcing suite for utilities)","category":"incumbent","uncopyabilityReason":"Power Advocate is distribution-channel-locked to IOUs and large G&Ts via six-figure enterprise contracts and named-account sellers; reaching a 60k-meter distribution co-op requires a self-serve / co-op-association distribution motion (NRECA, statewide associations, CFC financing tie-ins) that its direct-sales cost structure cannot support at co-op ACV."},{"name":"Coupa Sourcing / SAP Ariba","category":"incumbent","uncopyabilityReason":"Integration-depth barrier: Coupa/Ariba assume an underlying ERP (SAP, Oracle, Workday) with a corporate chart-of-accounts; co-ops run NISC iVUE or SEDC Daffron with RUS Uniform System of Accounts and construction-work-order (CWO/WO) coding. Building native iVUE/SEDC connectors plus RUS USoA mapping is a multi-year integration investment their mid-market-corporate roadmap will not prioritize."},{"name":"GPT-4 / Copilot used ad-hoc to draft bid tabs","category":"AI-native horizontal","uncopyabilityReason":"Liability-posture barrier: horizontal LLM vendors will not sign co-op-specific indemnification covering RUS equal-treatment findings or board-challenge exposure, and their consumer/enterprise licenses explicitly disclaim fitness for procurement-of-record use; the co-op attorney cannot accept an award package whose provenance chain ends at 'ChatGPT said so.'"}]},"studioThesis":"T-HSA","killThreshold":{"K":9,"M":60,"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":"Vertical fit to co-op procurement (generic RFQ tool ↔ RUS Bulletin 1726/1728 + NRECA spec library pre-baked, NISC/SEDC-aware)","yAxis":"Award-evidence reconstruction (auditor asks a question → staff digs through email for 3 days ↔ auditor asks a question → one click replays the full vendor-by-vendor timeline)","winningQuadrant":"RUS/NRECA-native workflow with one-click award-timeline replay bound to the tabulation and exceptions log","loservilleEscape":true,"loservilleQuadrant":"Generic e-sourcing (Bonfire) or manual Outlook+Excel where reconstructing who saw which spec revision takes days and still leaves RUS equal-treatment gaps unresolved"}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Abuyers-and-purchasing-agents-rfq-package-preparation%3At-hsa%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Abuyers-and-purchasing-agents-spend-analysis-report%3At-ais-low-tech%3Av1","id":"fh:buyers-and-purchasing-agents-spend-analysis-report:t-ais-low-tech:v1","lens":"HeadlessSaaS","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/buyers-and-purchasing-agents-spend-analysis-report","stableHash":"wcc:buyers-and-purchasing-agents:spend-analysis-report:document:v1"},"problem":{"slotStatement":"Every category spend-analysis report the startup ships today costs roughly $180–$400 in engineer + analyst time (3–6 hours stitching ERP extracts, UNSPSC/NAICS reclassification, supplier concentration math, and a sourcing-strategy narrative), and half of those hours are wasted re-doing the work when the jurisdiction boundary is wrong — a GPO-covered SKU gets priced as open-market, a state-contract line gets rolled into corporate spend, or a subsidiary's tax-jurisdiction rebate is missed — so the report lands on the purchasing agent's desk and gets kicked back for rework, forcing a wet-signature form to be re-routed for endorsement before the sourcing decision can move."},"approach":{"oneSentence":"Pay-per-report spend-analysis API: POST a CSV of GL+PO lines, get back a JSON category tree with UNSPSC codes, supplier-concentration stats, jurisdiction-tagged sourcing recommendations, and a per-line authority trace — $0.25 per spend line classified or $4 per full category report, free tier of 500 lines/month, paste an API key and run with no implementation call."},"customer":{"icpShape":"VP Engineering or Head of Data at a 40–200-person VC-backed SaaS startup (targetCompanyType: company-type-vc-saas-startup) that sells into procurement/sourcing teams and ships a spend-analysis or category-intelligence feature — where the buyer is the VP Engineering (signs the credit card / controls the dev-tools budget line) and the daily user is a senior backend or data engineer who'd rather curl an endpoint than book a demo.","beachheadShape":"EarlyAdopterJTBD: small VC-backed procurement/spend-intel SaaS startups whose own customers are buyers & purchasing agents, and who need a per-category spend-analysis & sourcing-strategy report generator they can embed under their own brand without building the classification + benchmark logic in-house."},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-UsageMetered","beachhead":"EarlyAdopterJTBD: small VC-backed procurement/spend-intel SaaS startups whose own customers are buyers & purchasing agents, and who need a per-category spend-analysis & sourcing-strategy report generator they can embed under their own brand without building the classification + benchmark logic in-house.","competitors":{"substitutes":[{"name":"The in-house Python + pandas script the data engineer already wrote","category":"informal","uncopyabilityReason":"Not a product — it is the DIY baseline, but it has no UNSPSC/NAICS crosswalk, no GPO/state-contract jurisdiction table, and no supplier-master dedupe, so it silently miscategorizes 15–30% of lines across contracting authorities."},{"name":"Wet-signature sourcing-approval form physically routed for endorsement","category":"manual-bridge"},{"name":"Coupa Spend Analysis (Spend 360)","category":"incumbent","uncopyabilityReason":"Deployment-mode mismatch: Coupa sells a full suite-license seat model with a 60–90 day implementation, SSO/SOC2 review, and taxonomy-workshop onboarding; it cannot re-ship as a $0.25/line paste-an-API-key endpoint without cannibalizing its seat-based contract floor and dismantling its Services org — the entire GTM is priced against implementation revenue."},{"name":"SAP Ariba Spend Analysis","category":"incumbent","uncopyabilityReason":"Integration depth: Ariba's classification engine is wired into the Ariba Network supplier graph and SAP MDG master-data, and its jurisdiction logic lives inside the SAP tax/contract modules. Exposing a clean per-event API that a 40-person startup could embed would require peeling classification out of a graph that is the reason CFOs buy Ariba in the first place."},{"name":"SpendHQ / GEP SMART spend analytics","category":"incumbent","uncopyabilityReason":"Vertical-data-corpus lock-in: SpendHQ and GEP's moat is their curated taxonomy + benchmark corpus collected under NDA from enterprise spend-cube engagements, licensed for use only inside their hosted UI. They cannot publish a per-call API against that corpus without violating the data-sharing terms that built it."},{"name":"ChatGPT / Claude with a pasted CSV","category":"AI-native horizontal","uncopyabilityReason":"Liability posture + vertical-data-corpus gap: a horizontal LLM has no authoritative UNSPSC↔NAICS crosswalk, no GPO/state-master contract registry, and no stable per-line trace — it will confidently cross jurisdictions and hallucinate supplier parents, and neither OpenAI nor Anthropic will attach the authority-boundary guarantee that a purchasing agent can defend to their controller."}]},"studioThesis":"T-AIS-LOW-TECH","killThreshold":{"K":11,"M":45,"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":"Per-report cost shape (seat-license + implementation fee ↔ pay-per-spend-line API, free tier, no minimum)","yAxis":"Jurisdiction-authority resolution (single flat category tree ↔ per-line GPO / state-master / corporate / subsidiary authority tag with reconcile trace)","winningQuadrant":"Pay-per-line API with per-line jurisdiction-authority tagging — a 40-person spend-intel startup pipes GL+PO lines in, gets back a category tree where every line carries the contracting-authority it falls under and why, and pays $0.25/line with no implementation call.","loservilleEscape":true,"loservilleQuadrant":"Seat-licensed suite (Coupa/Ariba/SpendHQ) with a single flat category tree and no jurisdiction-authority field — the documented failure mode where GPO-covered SKUs get priced as open-market and the report gets kicked back by the purchasing agent for rework."}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Abuyers-and-purchasing-agents-spend-analysis-report%3At-ais-low-tech%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Abuyers-and-purchasing-agents-supplier-contract-negotiation-brief%3At-low%3Av1","id":"fh:buyers-and-purchasing-agents-supplier-contract-negotiation-brief:t-low:v1","lens":"AgenticWorkflow","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/buyers-and-purchasing-agents-supplier-contract-negotiation-brief","stableHash":"wcc:buyers-and-purchasing-agents:supplier-contract-negotiation-brief:document:v1"},"problem":{"slotStatement":"When the co-op board or a RUS auditor asks why the negotiation brief locked in a given price band, liquidated-damages clause, or force-majeure carve-out, the procurement manager cannot reconstruct which supplier quote, prior-contract precedent, or board-meeting guidance drove each term — decisions arrive in the term sheet unattributed, and the co-op carries regulatory exposure into its next PUC rate case and cooperative-lender covenant review."},"approach":{"oneSentence":"After every supplier round, a negotiation-brief engine walks the co-op's prior executed contracts, quote emails, board-resolution minutes, and RUS bulletin precedents, then certifies each term sheet clause against the specific source that justified it so the CFO ships a brief the board and RUS examiner can trace line-by-line."},"customer":{"icpShape":"CFO or VP of Power Supply at a member-owned electric cooperative (CompanyType/company-type-member-owned-electric-cooperative) in the 80k–300k meter band negotiating wholesale power, transformer, and vegetation-management supplier contracts; the buyer is the CFO (signs the PO and owns the board-reporting line into the co-op board and state PUC) and the daily user is the Senior Power Supply Buyer or Procurement Manager who drafts the negotiation brief and term sheet.","beachheadShape":"EarlyMajorityWorkflow: Midwest and Southeast G&T-member distribution co-ops renegotiating 3–7 year wholesale power and transformer supply contracts under RUS/CFC financing covenants."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-Subscription","beachhead":"EarlyMajorityWorkflow: Midwest and Southeast G&T-member distribution co-ops renegotiating 3–7 year wholesale power and transformer supply contracts under RUS/CFC financing covenants.","competitors":{"substitutes":[{"name":"Manual Outlook + SharePoint + Cooperative-ERP (NISC iVUE / SEDC) search by the procurement manager","category":"manual-bridge","uncopyabilityReason":""},{"name":"Power Advocate (wholesale-energy sourcing and contract analytics suite used by utilities)","category":"incumbent","uncopyabilityReason":"Power Advocate's revenue model is built on IOU and large-public-power sourcing events where it owns the RFP workflow end-to-end; its data model assumes the buyer runs competitive auctions, which member-owned co-ops typically do NOT do (they negotiate bilaterally with their G&T and RUS-approved vendors). Re-plumbing the platform to cite RUS Bulletin 1724E precedents, G&T all-requirements contract carve-outs, and board-resolution minutes would require a vertical-data corpus (RUS/CFC/NRECA precedent library) Power Advocate has never licensed — a vertical-data-corpus barrier."},{"name":"Icertis Contract Intelligence","category":"incumbent","uncopyabilityReason":"Icertis is a deep-enterprise CLM deployed as a multi-tenant SaaS sold through 9–12 month Fortune-500 procurement cycles with six-figure implementations; a 120k-meter co-op CFO signing a $40k/year tool out of the G&A line cannot absorb that deployment-mode mismatch, and Icertis's go-to-market is structurally uninterested in sub-$5M ACV co-op deals — a deployment-mode-mismatch and distribution-channel barrier compounded."},{"name":"Ironclad AI Assist","category":"AI-native horizontal","uncopyabilityReason":"Ironclad's redline engine is trained on commercial SaaS, NDA, and MSA corpora; it has no integration depth against NISC iVUE, SEDC, or the RUS Form 7 filings that anchor a co-op's negotiation brief, and lacks the liability posture to certify a clause as RUS-compliant. Shipping that would require co-op-specific ERP connectors and a regulated-utility liability stance — an integration-depth barrier."},{"name":"NRECA Business & Technology Strategies shared-services contract templates and ad-hoc NRTC / CFC advisory","category":"human alternative","uncopyabilityReason":""}]},"studioThesis":"T-LOW","killThreshold":{"K":9,"M":65,"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":"Clause-to-source attribution depth (term sheet arrives as a flat Word doc ↔ every clause pinned to the specific prior contract, quote email, RUS bulletin, or board motion that justified it)","yAxis":"Co-op regulatory fit (generic CLM with no co-op / RUS awareness ↔ pre-loaded RUS Bulletin 1724E, CFC covenant, and G&T all-requirements precedent library)","winningQuadrant":"Every term sheet clause is attributed to a named RUS bulletin, G&T all-requirements precedent, or executed prior contract the CFO can hand to the board and the RUS field accountant without a follow-up email","loservilleEscape":true,"loservilleQuadrant":"Icertis-style flat redlines with no RUS/CFC precedent awareness and no per-clause attribution, leaving the procurement manager to rebuild the 'why' in Outlook the night before the board packet drops"}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Abuyers-and-purchasing-agents-supplier-contract-negotiation-brief%3At-low%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Achild-family-and-school-social-workers-case-assessment-report%3At-low%3Av1","id":"fh:child-family-and-school-social-workers-case-assessment-report:t-low:v1","lens":"HeadlessSaaS","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"C7_magicLensFit":0,"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/child-family-and-school-social-workers-case-assessment-report","stableHash":"wcc:child-family-and-school-social-workers:case-assessment-report:document:v1"},"problem":{"slotStatement":"After a home visit, caseworkers spend 3–5 hours retyping field notes, SDM risk-assessment scores, and collateral contacts into the SACWIS case record, and safety plans routinely get kicked back by supervisors and CFSR reviewers for missing decision rationale tying observed safety threats to the chosen in-home services."},"approach":{"oneSentence":"A safety-plan attestation workflow that reconciles home-visit field notes against the state's Structured Decision Making (SDM) rubric and emits a review-ready case assessment with every safety-threat finding linked back to the caseworker's primary observation, dropped directly into the SACWIS/CCWIS record."},"customer":{"icpShape":"County and state child welfare agencies (500–5,000 caseworkers) running CPS/DCF investigations on SACWIS/CCWIS systems, where the buyer is the Deputy Director of Child Welfare (or CCWIS Program Director) who owns the case-management tooling budget and the daily user is the frontline Child & Family Social Worker conducting home visits and drafting safety plans.","beachheadShape":"EarlyMajorityWorkflow: mid-sized county DCF/DSS agencies under active federal CFSR Round 4 corrective action plans where case-file documentation quality is a named finding"},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-MarketplaceClearing","beachhead":"EarlyMajorityWorkflow: mid-sized county DCF/DSS agencies under active federal CFSR Round 4 corrective action plans where case-file documentation quality is a named finding","competitors":{"substitutes":[{"name":"Binti (child welfare case management)","category":"incumbent"},{"name":"Northwoods Traverse / Compass case documentation","category":"incumbent"},{"name":"Casebook PBC","category":"adjacent vertical"},{"name":"Dictaphone + supervisor redlines in Word","category":"status-quo"}]},"studioThesis":"T-LOW","killThreshold":{"K":10,"M":45,"N":9,"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 ≥ 9/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence trace (narrative summary ↔ each SDM safety-threat finding cited to a timestamped field observation)","yAxis":"System-of-record embedding (sidecar note-taker exported as PDF ↔ writes structured fields directly into the state's SACWIS/CCWIS case record)","winningQuadrant":"Every SDM finding cited to a field observation AND written into the CCWIS case record so supervisors and CFSR reviewers can audit the decision chain in the system of record","loservilleEscape":true,"loservilleQuadrant":"Northwoods/Binti-style sidecar dictation that produces an unstructured narrative PDF with no cite-back to SDM rubric items, forcing supervisors to manually reconcile against the SACWIS record"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Achild-family-and-school-social-workers-case-assessment-report%3At-low%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Achild-family-and-school-social-workers-court-report-preparation%3At-bu%3Av1","id":"fh:child-family-and-school-social-workers-court-report-preparation:t-bu:v1","lens":"AIService","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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/child-family-and-school-social-workers-court-report-preparation","stableHash":"wcc:child-family-and-school-social-workers:court-report-preparation:document:v1"},"problem":{"slotStatement":"Social workers spend 8–14 hours per case stitching contact logs, CANS assessments, visitation notes, and service referrals from SACWIS into a court report that a judge, county counsel, and parent's attorney will cross-examine line-by-line — and any unsupported claim gets struck, delaying permanency hearings and triggering compliance findings."},"approach":{"oneSentence":"A court-report compilation workspace that pulls contact logs, CANS scores, and service referrals directly from the SACWIS case record, assembles each section against the jurisdiction's local rule rubric, and renders a review-ready report where every factual sentence links back to its primary-source case note for county counsel sign-off."},"customer":{"icpShape":"County-level child welfare agencies and nonprofit foster care providers (50–500 caseworkers) in U.S. jurisdictions with active juvenile dependency dockets, where the buyer is the Deputy Director of Child Welfare or Agency General Counsel and the daily user is the line Child & Family Social Worker preparing court reports","beachheadShape":"EarlyAdopterJTBD: county child welfare agencies under federal CFSR corrective action plans facing judicial findings of inadequate court reports"},"archetype":"startup-archetypes.org.ai/AIService-UsageMetered","beachhead":"EarlyAdopterJTBD: county child welfare agencies under federal CFSR corrective action plans facing judicial findings of inadequate court reports","competitors":{"substitutes":[{"name":"Manual Word + SACWIS copy-paste workflow","category":"status-quo"},{"name":"Binti / Northwoods Traverse case management narrative tools","category":"incumbent"},{"name":"CaseAide / Casetext CoCounsel used off-label by caseworkers","category":"AI-native horizontal"},{"name":"Contract paralegal report-writing services","category":"human alternative"}]},"studioThesis":"T-BU","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence trace (free-text narrative ↔ every claim hyperlinked to the originating SACWIS case-note ID and timestamp)","yAxis":"Jurisdictional rubric fit (generic dependency-report template ↔ encoded local court rules, e.g. WIC §366.21 California vs. Texas Chapter 263)","winningQuadrant":"Per-claim SACWIS citation trace bound to the specific juvenile court's local-rule rubric, so county counsel can defend every line at the hearing","loservilleEscape":true,"loservilleQuadrant":"Northwoods Traverse narrative drafts that produce generic dependency prose without per-sentence case-note citations or jurisdiction-specific rule checks, forcing workers to re-verify every paragraph manually"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Achild-family-and-school-social-workers-court-report-preparation%3At-bu%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Achild-family-and-school-social-workers-crisis-intervention-coordination%3At-ais-prem%3Av1","id":"fh:child-family-and-school-social-workers-crisis-intervention-coordination:t-ais-prem:v1","lens":"AgenticWorkflow","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/child-family-and-school-social-workers-crisis-intervention-coordination","stableHash":"wcc:child-family-and-school-social-workers:crisis-intervention-coordination:multimodal:v1"},"problem":{"slotStatement":"When a Tier-3 crisis breaks — a suicidal-ideation disclosure, a DCF hotline call, a mobile-crisis-team handoff — the social worker is working from a playbook whose policy citations (district board policy, state DCF statute, 504 timelines, MOU with local PD) have silently drifted out of sync since the quarterly committee review, so half the escalations trigger a rework loop: the intake was logged under last quarter's notification window, the wrong parent-consent form was sent, the MOU contact is stale, and the case has to be re-walked end-to-end before it will survive a Title-IX or DCF audit."},"approach":{"oneSentence":"After every crisis intake, a district-pinned coordination engine re-checks each escalation step against the current-effective board policy, state-statute, and MOU versions, flags any step executed against a superseded rule, and routes the social worker a review-ready remediation packet before the 24/72-hour notification clocks close."},"customer":{"icpShape":"District-level Student Services directors at K-12 public school districts (targetCompanyType: company-type-solo-dental-practice anchor; applied here as single-district/single-agency buyer unit of 15k-40k enrolled students) who own the Safe-Schools and crisis-response line items, where the buyer is the Director of Student Services (or Assistant Superintendent for Student Wellness) and the daily user is the school social worker coordinating Section-504, mandated-reporter, and mobile-crisis-team escalations.","beachheadShape":"EarlyAdopterJTBD: mid-size suburban K-12 districts under a fresh Safe-Schools or suicide-prevention board mandate whose crisis playbook was last revised after a post-pandemic policy shake-up and who have ≥1 FTE social worker but no dedicated crisis-coordination software."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-OutcomeBased","beachhead":"EarlyAdopterJTBD: mid-size suburban K-12 districts under a fresh Safe-Schools or suicide-prevention board mandate whose crisis playbook was last revised after a post-pandemic policy shake-up and who have ≥1 FTE social worker but no dedicated crisis-coordination software.","competitors":{"substitutes":[{"name":"Quarterly committee policy-review cycle","category":"informal","uncopyabilityReason":""},{"name":"PowerSchool Special Programs (formerly Enrich / SpecialServices Solutions)","category":"incumbent","uncopyabilityReason":"PowerSchool Special Programs is built as a compliance form-filler bonded to IEP/504 document templates and state-reporting exports; its data model treats board policy and inter-agency MOUs as static PDF attachments, not as versioned rule objects that can be diffed against a live case. Shipping rule-drift detection would require rebuilding the core workflow engine and renegotiating its state-SEA reporting certifications — a 2-3 year regulatory-licensure and integration-depth lift, not a 6-month feature."},{"name":"Frontline Education Special Ed & Interventions (Frontline Central)","category":"incumbent","uncopyabilityReason":"Frontline's suite is distributed through state-level DOE master contracts and HR/payroll bundles; its go-to-market and product surface is optimized for district HR and IEP-paperwork buyers, not the Student Services crisis-response budget line. Building a crisis-coordination wedge would cannibalize its HR-bundle pricing model and force a new distribution-channel motion into a different buyer, which its sales org is structurally not set up to run."},{"name":"Navigate360 Behavioral Threat Assessment / Suite","category":"incumbent","uncopyabilityReason":"Navigate360 is anchored in threat-assessment and emergency-ops (active-shooter, anonymous tip-line) content libraries curated by its clinical advisory board; it carries a liability posture where every workflow is a pre-approved protocol, which is incompatible with a per-district rule-drift engine that would need to accept arbitrary local board-policy and MOU text as the authority. Opening that authority boundary would expose its E&O insurance and clinical-endorsement moat."},{"name":"Generalist agentic assistants (ChatGPT Team / Copilot) used ad-hoc by social workers","category":"AI-native horizontal","uncopyabilityReason":"Horizontal LLM assistants have no deployment-mode path into a FERPA/HIPAA-hybrid student-record environment without a BAA and district-specific data-residency posture; they cannot ingest the live board-policy corpus, state DCF statute feed, and signed MOU registry as versioned authoritative sources, so they cannot close the rule-drift gap — they can only paraphrase whatever the social worker pastes in."}]},"studioThesis":"T-AIS-PREM","killThreshold":{"K":10,"M":80,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Rule-state freshness (static PDF policy attachments ↔ live-diffed versioned board-policy + statute + MOU graph per case)","yAxis":"Authority boundary (generic advisory suggestions ↔ district-pinned authoritative remediation against the exact policy version in force on the incident date)","winningQuadrant":"Live-diffed rule graph with district-pinned authoritative remediation — every escalation step is checked against the version-in-force for that incident date and superseded steps are auto-surfaced before the 24/72-hour clock closes","loservilleEscape":true,"loservilleQuadrant":"Static PDF policy attachments paired with generic advisory text — the failure mode PowerSchool Special Programs exhibits today, where last quarter's notification window is silently reused and the case has to be re-walked end-to-end to survive the DCF/Title-IX audit"}},"unmetRequirements":[],"pricingArchitecture":"tiered","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Achild-family-and-school-social-workers-crisis-intervention-coordination%3At-ais-prem%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Achild-family-and-school-social-workers-crisis-intervention-coordination%3At-hsa%3Av1","id":"fh:child-family-and-school-social-workers-crisis-intervention-coordination:t-hsa:v1","lens":"HeadlessSaaS","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"C7_magicLensFit":0,"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/child-family-and-school-social-workers-crisis-intervention-coordination","stableHash":"wcc:child-family-and-school-social-workers:crisis-intervention-coordination:multimodal:v1"},"problem":{"slotStatement":"After a multi-agency crisis call ends — school counselor, CPS intake worker, mobile crisis team, parent, and the DSO's on-site social worker all on the same bridge — the social worker has no single place where who-said-what, who-agreed-to-what-follow-up, and which mandated-reporter threshold was crossed actually lives; the handoff becomes screenshots of Teams chat, a Notes app transcript, and a post-hoc narrative typed into the EHR hours later, so when a safety-plan dispute surfaces two weeks later (parent complaint, CPS requesting the clinic's file, a school district subpoena) the provenance chain between the spoken decision and the documented decision is broken and the DSO loses the dispute by default."},"approach":{"oneSentence":"A crisis-call coordination workspace that joins the multi-party bridge at dial-in, transcribes and role-tags each participant (school, CPS, mobile crisis, guardian, clinician), captures every safety-plan decision and follow-up commitment against the clinician's intervention rubric, and closes out the call with a signed, verifiable handoff record routed to each agency's intake system and pinned to the EHR encounter."},"customer":{"icpShape":"Director of Behavioral Health Services at a PE-backed multi-site DSO (company-type-pe-backed-dso) whose clinics embed child/family social workers for school-referred crisis intake, where the buyer is the Director of Behavioral Health Services (signs the tooling PO and owns the cross-agency liability posture) and the daily user is the Licensed Clinical Social Worker running the crisis-intervention coordination calls with CPS, school counselors, and mobile crisis teams.","beachheadShape":"EarlyAdopterJTBD: 20-60 location PE-backed DSO groups that recently added a pediatric behavioral-health service line and are being asked by their school-district referral partners to produce an after-action handoff record within 24 hours of each crisis call."},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-Subscription","beachhead":"EarlyAdopterJTBD: 20-60 location PE-backed DSO groups that recently added a pediatric behavioral-health service line and are being asked by their school-district referral partners to produce an after-action handoff record within 24 hours of each crisis call.","competitors":{"substitutes":[{"name":"Screenshot archive of Teams/Zoom chat plus post-hoc EHR narrative","category":"informal"},{"name":"Epic Behavioral Health module (including Epic's Care Everywhere cross-agency share)","category":"incumbent","uncopyabilityReason":"Epic's data model is anchored to the covered-entity HIPAA boundary — CPS caseworkers and school counselors are not on Epic and cannot be provisioned as first-class participants without rebuilding the identity and consent layer. Epic's integration depth inside the DSO EHR is its moat but also its cage: shipping a neutral multi-agency bridge that treats CPS and a school district as equal tenants would cannibalize the Care Everywhere network-effect pricing that drives Epic's enterprise contracts."},{"name":"Netsmart myAvatar / CareManager (behavioral-health EHR with care-coordination add-on)","category":"incumbent","uncopyabilityReason":"Netsmart's crisis-workflow product is built around the state-contracted CCBHC and CMHC deployment mode — it ships as a licensed state-HHS appliance with per-state Medicaid billing logic baked in. It cannot pivot to a DSO-buyer SaaS that pulls CPS and school-district participants into a live-call workspace without a deployment-mode rebuild; its field engineers are organized around state HHS IT procurement, not commercial DSO IT."},{"name":"Julota / Collaborative Care Platform (cross-agency care-coordination network)","category":"incumbent","uncopyabilityReason":"Julota's value is a pre-negotiated data-sharing consortium with a specific county's 911, EMS, and CPS agencies — the uncopyable asset is the signed inter-agency MOUs per county, a distribution-channel moat that took years to build region by region. They cannot ship a turnkey record that a PE-backed DSO drops into any new market in 30 days without re-running the MOU process in each county."},{"name":"Read.ai / Otter.ai / Fireflies call-transcription bots","category":"AI-native horizontal","uncopyabilityReason":"Horizontal meeting-AI vendors carry no BAA posture calibrated to child-welfare data, no mandated-reporter escalation logic, and no liability framework for safety-plan commitments. Adding those would force them into a regulated-liability posture that their self-serve, paste-credit-card distribution model cannot absorb without collapsing unit economics."}]},"studioThesis":"T-HSA","killThreshold":{"K":10,"M":80,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Participant model (single-tenant clinician tool ↔ neutral multi-agency bridge where CPS, school, and mobile crisis are first-class participants with their own consent and retention rules)","yAxis":"Authority boundary over mandated-reporter escalation (advisory note-taking ↔ policy-bound escalation routing with timestamped handoff receipts to each named agency)","winningQuadrant":"Neutral multi-agency bridge with policy-bound escalation routing — the DSO clinician runs the call, but CPS and the school district receive structurally identical, signed handoff packets within minutes of call-end, and every reporter-threshold decision is timestamped against the clinician's rubric","loservilleEscape":true,"loservilleQuadrant":"Single-tenant advisory transcription — what Otter.ai and Fireflies deliver today: a clinician-only transcript with no agency-specific handoff, no mandated-reporter logic, and no cross-agency consent model, so the DSO still reconstructs the record by hand and still loses the two-week-later dispute"}},"unmetRequirements":[],"pricingArchitecture":"tiered","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Achild-family-and-school-social-workers-crisis-intervention-coordination%3At-hsa%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Achild-family-and-school-social-workers-home-visit-assessment%3At-td%3Av1","id":"fh:child-family-and-school-social-workers-home-visit-assessment:t-td:v1","lens":"AgenticWorkflow","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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/child-family-and-school-social-workers-home-visit-assessment","stableHash":"wcc:child-family-and-school-social-workers:home-visit-assessment:multimodal:v1"},"problem":{"slotStatement":"After a home visit, caseworkers spend 60–90 minutes retyping hand-scrawled safety-hazard notes, photos, and the state's structured safety-assessment checklist into SACWIS/CCWIS, and supervisors still bounce narratives back for missing rubric elements (sleeping arrangements, firearm storage, utilities) before the 24/48-hour contact deadline."},"approach":{"oneSentence":"A home-visit safety-assessment companion that captures voice dictation, room photos, and structured observations on a phone during the visit, scores them against the state's Structured Decision Making safety rubric, and emits a review-ready, citation-anchored assessment packet that drops directly into the SACWIS/CCWIS case record with each rubric factor linked to its supporting photo or utterance."},"customer":{"icpShape":"County and municipal Child Protective Services (CPS) agencies and private foster-care contract agencies with 40–400 caseworkers in the US, where the buyer is the CPS Deputy Director or IT/Practice Director (who signs the tooling PO under a Title IV-E or CAPTA grant line) and the daily user is the child-and-family social worker conducting the home visit.","beachheadShape":"EarlyMajorityWorkflow: mid-size county CPS agencies under active QA-review or consent-decree pressure on home-visit documentation timeliness"},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-Subscription","beachhead":"EarlyMajorityWorkflow: mid-size county CPS agencies under active QA-review or consent-decree pressure on home-visit documentation timeliness","competitors":{"substitutes":[{"name":"Binti and Northwoods Traverse/Compass","category":"incumbent"},{"name":"Paper safety checklists + dictation into MS Word, then manual SACWIS entry","category":"status-quo"},{"name":"Otter.ai / Microsoft Copilot generic transcription","category":"AI-native horizontal"},{"name":"Agency-hired clerical documentation specialists","category":"human alternative"}]},"studioThesis":"T-TD","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence trace per rubric factor (free-text narrative ↔ each SDM safety factor linked to a timestamped photo or utterance from the visit)","yAxis":"System-of-record embedding (exported PDF attached later ↔ writes structured fields directly into the state SACWIS/CCWIS contact record)","winningQuadrant":"Per-factor photo/utterance citations flowing straight into SACWIS/CCWIS structured fields so QA reviewers and courts can click from a rubric score to its source evidence","loservilleEscape":true,"loservilleQuadrant":"Otter/Copilot-style transcripts pasted into a Word doc with no rubric mapping, forcing the worker to re-key every SDM factor into SACWIS and leaving supervisors with unverifiable narrative claims"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Achild-family-and-school-social-workers-home-visit-assessment%3At-td%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Achild-family-and-school-social-workers-service-plan-documentation%3At-ais-prem%3Av1","id":"fh:child-family-and-school-social-workers-service-plan-documentation:t-ais-prem:v1","lens":"HeadlessSaaS","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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/child-family-and-school-social-workers-service-plan-documentation","stableHash":"wcc:child-family-and-school-social-workers:service-plan-documentation:document:v1"},"problem":{"slotStatement":"Social workers re-type client goals, objectives, and progress narratives across the service plan, weekly case notes, and treatment review forms in the EHR, and supervisors still find un-cited goal language and missing SMART-objective anchors during Medicaid and COA audits, triggering clawbacks and corrective-action plans."},"approach":{"oneSentence":"A service-plan binder that links every goal, objective, and progress note back to the specific assessment finding and session contact that justifies it, producing a review-ready record the supervisor signs off inside the existing EHR screen."},"customer":{"icpShape":"Mid-to-large non-profit child & family service agencies and school districts ($20M–$200M budget) operating Title IV-E / Medicaid-billable programs, where the buyer is the VP of Clinical Operations or Chief Compliance Officer who signs the EHR tooling PO, and the daily user is the MSW-level child/family/school social worker drafting service plans and progress notes.","beachheadShape":"EarlyAdopterJTBD: COA/CARF-accredited child & family agencies under active state QA review whose service-plan audit defect rate is threatening Medicaid reimbursement."},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-RetainerEngagement","beachhead":"EarlyAdopterJTBD: COA/CARF-accredited child & family agencies under active state QA review whose service-plan audit defect rate is threatening Medicaid reimbursement.","competitors":{"substitutes":[{"name":"Netsmart myEvolv / myAvatar service-plan module","category":"incumbent"},{"name":"Casebook PBC case-management suite","category":"incumbent"},{"name":"ChatGPT / Copilot used off-platform by caseworkers to draft narratives","category":"AI-native horizontal"},{"name":"Agency-employed QA reviewers who hand-check plans pre-audit","category":"human alternative"}]},"studioThesis":"T-AIS-PREM","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence trace (narrative pasted in as free text ↔ every goal/objective line linked to the assessment item and contact note that justifies it)","yAxis":"System-of-record embedding (external draft tool copy-pasted into EHR ↔ runs inside the Netsmart/Casebook service-plan screen with supervisor e-sign)","winningQuadrant":"Traceable goal-to-evidence links authored directly inside the EHR service-plan screen, with supervisor sign-off captured in the same record auditors pull","loservilleEscape":true,"loservilleQuadrant":"ChatGPT-drafted narrative pasted into myEvolv free-text fields with no link back to the assessment or contact note — exactly the failure mode Medicaid auditors flag as unsupported goal language in Casebook and myEvolv shops today"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Achild-family-and-school-social-workers-service-plan-documentation%3At-ais-prem%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Achild-family-and-school-social-workers-service-plan-documentation%3At-td%3Av1","id":"fh:child-family-and-school-social-workers-service-plan-documentation:t-td:v1","lens":"AgenticWorkflow","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/child-family-and-school-social-workers-service-plan-documentation","stableHash":"wcc:child-family-and-school-social-workers:service-plan-documentation:document:v1"},"problem":{"slotStatement":"Service plans and progress notes get written once and then silently fall out of jurisdiction when a case crosses from a school IEP context into a county CFSA or tribal ICWA context — the caseworker keeps authoring against the original framework, the supervisor catches the mismatch three weeks later at QA, and the plan has to be re-drafted, re-signed by the guardian, and re-submitted, blowing the 30/60/90-day review clock and pushing billable cycle time from days into weeks."},"approach":{"oneSentence":"Jurisdiction-aware service-plan authoring that continuously reconciles each open plan and progress note against the specific statutory framework in force for that client (IEP, IFSP, CFSA, ICWA, Medicaid 1915(i)), flags the exact clauses that drift when authority changes, and hands the supervisor a review-ready diff the guardian can re-sign before the review clock expires."},"customer":{"icpShape":"Series A–C VC-backed SaaS startups (company-type-vc-saas-startup, 80–400 FTE) that operate child, family, and school social-work programs under county or state Medicaid/Title IV-E contracts — where the buyer is the VP of Clinical Operations (or Chief Compliance Officer) who signs the tooling PO and owns audit exposure, and the daily user is the LCSW/LMSW case manager or school social worker drafting service plans and progress notes in the EHR/case-management system.","beachheadShape":"EarlyMajorityWorkflow: 10–40-caseworker clinical-ops teams at VC-backed behavioral-health SaaS operators running county contracts in 2–4 states where jurisdiction-specific service-plan rules (IEP/IFSP/CFSA/ICWA) collide on a single caseload."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-Subscription","beachhead":"EarlyMajorityWorkflow: 10–40-caseworker clinical-ops teams at VC-backed behavioral-health SaaS operators running county contracts in 2–4 states where jurisdiction-specific service-plan rules (IEP/IFSP/CFSA/ICWA) collide on a single caseload.","competitors":{"substitutes":[{"name":"Ironclad-style legal-ops contract repository repurposed for service agreements","category":"manual-bridge"},{"name":"Supervisor-maintained Google Sheet of 'which rules apply to which kid' cross-referenced against case notes at weekly staffing","category":"informal"},{"name":"Netsmart myEvolv / myAvatar (behavioral-health EHR with service-plan modules)","category":"incumbent","uncopyabilityReason":"Netsmart's service-plan templates are hard-bound to a per-state configuration package sold as professional services; adding live jurisdiction-reconciliation across IEP/CFSA/ICWA would require rebuilding their per-county implementation contracts and the revenue model that funds their 9-month deployment cycles (deployment-mode-mismatch + integration-depth)."},{"name":"Casebook PBC (child-welfare case management SaaS)","category":"incumbent","uncopyabilityReason":"Casebook's data model is scoped to a single jurisdiction's CFSR practice model per tenant instance; they lack the multi-framework legal corpus (tribal ICWA statutes, state IDEA regs, Medicaid 1915(i) waivers) and do not hold the licensed-clinician review posture needed to assert cross-jurisdiction plan validity (vertical-data-corpus)."},{"name":"PowerSchool Special Programs (IEP authoring for K-12)","category":"incumbent","uncopyabilityReason":"PowerSchool is sold through K-12 district procurement and is authorized to operate only inside the IDEA/FERPA perimeter; selling into county child-welfare or tribal social services requires a different licensure posture (BAA under 42 CFR Part 2, ICWA tribal data-sovereignty agreements) that their distribution channel is not set up to sign (regulatory-licensure + distribution-channel)."},{"name":"Horizontal AI scribe (Abridge / Nabla) dropped onto social-work notes","category":"AI-native horizontal","uncopyabilityReason":"Abridge/Nabla are trained and liability-priced for physician encounter transcription under clinician-of-record sign-off; accepting legal responsibility for a service plan's jurisdictional validity would expose them to non-medical statutory exposure (IDEA due-process, ICWA active-efforts) their malpractice carriers and SOC2 scope do not cover (liability-posture)."}]},"studioThesis":"T-TD","killThreshold":{"K":10,"M":60,"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":"Jurisdictional authority handling (single-framework template fill ↔ continuous multi-framework reconcile across IEP/CFSA/ICWA/1915(i) on every note)","yAxis":"Drift-detection cadence (quarterly supervisor QA audit ↔ per-save divergence check against the plan's governing statute)","winningQuadrant":"Continuous multi-framework reconcile with per-save divergence check — the plan is flagged the moment the child's legal context changes (school referral, tribal enrollment, kinship placement) and the specific clauses that now violate the controlling framework are surfaced before the next supervisor signature","loservilleEscape":true,"loservilleQuadrant":"Single-framework template fill audited quarterly — the failure mode Netsmart myEvolv and Casebook exhibit today, where a plan authored under a county CFSA template keeps accepting progress notes after an ICWA transfer and the jurisdiction-mismatch isn't caught until the 90-day review blows"}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Achild-family-and-school-social-workers-service-plan-documentation%3At-td%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acompliance-officers-audit-finding-response%3At-bu%3Av1","id":"fh:compliance-officers-audit-finding-response: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/compliance-officers-audit-finding-response","stableHash":"wcc:compliance-officers:audit-finding-response:document:v1"},"problem":{"slotStatement":"After every audit cycle, the compliance officer spends weeks reconciling findings whose control citations straddle FERC, state PUC, NERC-CIP, and internal-policy jurisdictions — and wet-signature response forms get physically routed to the wrong control owner because the finding's authority scope was never pinned, producing regulator-facing remediation commitments under the wrong regime and invisible regulatory exposure when a state examiner asks who actually owns the control."},"approach":{"oneSentence":"Authority-boundary resolution engine that, the moment a finding is logged, classifies each citation against a utility-specific jurisdiction graph (FERC vs state PUC vs NERC-CIP vs internal SOX-adjacent policy), binds the correct control owner and remediation regime to the finding, and produces a jurisdiction-scoped response packet the CAE can hand to the examiner without re-routing the paper form."},"customer":{"icpShape":"Chief Audit Executive or VP Internal Audit at a CompanyType/company-type-public-utility (investor-owned electric/gas/water utility, 500–5,000 employees, multi-state service territory under FERC + state PUC + NERC-CIP jurisdictions), where the buyer is the Chief Audit Executive (signs the GRC tooling PO with CFO co-sign) and the daily user is the Senior Compliance Officer or Audit Manager who drafts management responses and tracks remediation owners.","beachheadShape":"EarlyAdopterJTBD: multi-jurisdiction investor-owned utilities that failed a recent NERC-CIP or state-PUC audit cycle and have open findings crossing federal/state/internal-policy authority boundaries"},"archetype":"startup-archetypes.org.ai/AIService-Subscription","beachhead":"EarlyAdopterJTBD: multi-jurisdiction investor-owned utilities that failed a recent NERC-CIP or state-PUC audit cycle and have open findings crossing federal/state/internal-policy authority boundaries","competitors":{"substitutes":[{"name":"Wet-signature finding-response form physically routed for control-owner endorsement","category":"manual-bridge"},{"name":"Shared Excel finding-tracker with a 'Regulation' free-text column maintained by the audit coordinator","category":"informal"},{"name":"AuditBoard (CrossComply + OpsAudit modules)","category":"incumbent","uncopyabilityReason":"AuditBoard's data model treats 'framework' as a single-owner taxonomy tag chosen at finding-creation time; the utility-specific case where one finding spans FERC + state-PUC + NERC-CIP simultaneously would require rebuilding its control-library schema and its SOX-pedigree plan-audit integration, which is the exact contract surface that drives its Fortune-500 GRC revenue — integration-depth lock-in."},{"name":"Workiva Wdesk (Audit Management + Regulatory Reporting)","category":"incumbent","uncopyabilityReason":"Workiva's moat is the iXBRL/financial-reporting linked-document graph sold to CFO/SEC-reporting buyers; utility operational-audit findings with NERC-CIP evidence artifacts sit outside its corpus and its sales channel is financial-reporting procurement, not CAE/GRC procurement — distribution-channel mismatch prevents a 6-month pivot to jurisdiction-resolution for CIP."},{"name":"Archer (RSA Archer IT & Security Risk Management)","category":"incumbent","uncopyabilityReason":"Archer is a customer-configured policy platform deployed on-prem or in dedicated cloud; every jurisdiction-graph customization lives inside each utility's bespoke Archer instance, and RSA monetizes the professional-services hours to configure it — shipping a pre-baked FERC/PUC/CIP authority graph as product would cannibalize the SI services revenue that funds the platform (capital-intensity + services-model lock-in)."},{"name":"Fortress Information Security (NERC-CIP audit services)","category":"human alternative","uncopyabilityReason":"Fortress sells billable-hour CIP compliance consulting; their economic model depends on human analysts manually reading findings and assigning authority scope, and productizing jurisdiction resolution would collapse their utilization-based P&L — liability-posture plus services-revenue structure."}]},"studioThesis":"T-BU","killThreshold":{"K":11,"M":70,"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":"Authority-boundary handling (single free-text 'regulation' tag ↔ multi-jurisdiction graph that splits one finding across FERC + state PUC + NERC-CIP owners)","yAxis":"Utility regulatory corpus depth (generic GRC framework library ↔ pre-baked FERC Order 693 / NERC-CIP-013 / state-PUC docket taxonomy with control-owner mappings)","winningQuadrant":"Multi-jurisdiction authority graph pre-bound to a utility-specific FERC/PUC/NERC-CIP control-owner taxonomy, so a single finding auto-routes to the correct owner under each regime","loservilleEscape":true,"loservilleQuadrant":"Single-tag 'Regulation' column on a generic GRC framework library — where AuditBoard and Excel finding-trackers sit today, forcing the compliance officer to manually re-route the wet-signature form when the examiner questions which jurisdiction owns the control"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acompliance-officers-audit-finding-response%3At-bu%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acompliance-officers-policy-exception-review%3At-low%3Av1","id":"fh:compliance-officers-policy-exception-review:t-low:v1","lens":"AgenticWorkflow","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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/compliance-officers-policy-exception-review","stableHash":"wcc:compliance-officers:policy-exception-review:document:v1"},"problem":{"slotStatement":"Compliance officers spend 60-80% of each exception review re-typing the same context — policy clause cited, business justification, compensating controls, residual risk rating, approver chain — into a free-text memo that examiners later reject as inconsistent, unsourced, or missing the tie-back to the underlying policy section."},"approach":{"oneSentence":"A policy-exception workflow agent that reads the requesting team's ticket plus the cited policy section, assembles a review-ready risk-acceptance memo with every clause, compensating control, and approver signature traced back to its primary source, and routes it through the bank's existing GRC approval chain."},"customer":{"icpShape":"US regional banks ($10B-$50B in assets) regulated by OCC/FDIC, where the buyer is the Chief Compliance Officer (or Head of Enterprise Risk) who signs the GRC tooling PO and the daily user is the line Compliance Officer reviewing policy exception requests and risk acceptance memos.","beachheadShape":"EarlyMajorityWorkflow: second- and third-line compliance teams at $10B-$50B US regional banks who already run a quarterly exception backlog in Archer or ServiceNow GRC and are under MRA/MRIA pressure to tighten exception documentation."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-UsageMetered","beachhead":"EarlyMajorityWorkflow: second- and third-line compliance teams at $10B-$50B US regional banks who already run a quarterly exception backlog in Archer or ServiceNow GRC and are under MRA/MRIA pressure to tighten exception documentation.","competitors":{"substitutes":[{"name":"Archer Policy & Exception Management module","category":"incumbent"},{"name":"ServiceNow IRM with free-text exception form","category":"incumbent"},{"name":"Compliance analyst drafting the memo in Word with policy PDF open in a second window","category":"human alternative"},{"name":"ChatGPT Enterprise used ad-hoc by the compliance team to summarize the request","category":"AI-native horizontal"}]},"studioThesis":"T-LOW","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence trace on the memo (free-text justification ↔ every clause linked to the exact policy section and control ID)","yAxis":"Workflow placement (standalone drafting tool outside GRC ↔ runs inside the Archer/ServiceNow exception record and inherits its approval routing)","winningQuadrant":"clause-level citations to the policy of record, generated inside the existing GRC exception record so approvers sign the same object examiners later pull","loservilleEscape":true,"loservilleQuadrant":"ChatGPT Enterprise summaries pasted into a Word memo with no link back to the policy section and no presence in Archer's approval chain — exactly the failure mode examiners flag in MRA findings"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acompliance-officers-policy-exception-review%3At-low%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acompliance-officers-regulatory-gap-analysis%3At-ais-low-tech%3Av1","id":"fh:compliance-officers-regulatory-gap-analysis:t-ais-low-tech:v1","lens":"ManagedWorkflow","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"C7_magicLensFit":0,"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/compliance-officers-regulatory-gap-analysis","stableHash":"wcc:compliance-officers:regulatory-gap-analysis:document:v1"},"problem":{"slotStatement":"Every time a regulator pushes an amendment (NIST rev bump, HIPAA subpart edit, PCI-DSS errata), the on-call compliance dev eats 4-6 hours per framework hand-diffing the new text against their control library, and roughly 1 in 5 amendments still slips through undetected for a quarter — at a $95/hr loaded rate that's $400-600 of rework-loop labor per missed-amendment event, times ~30 amendment drops per year across their frameworks."},"approach":{"oneSentence":"Pay-per-diff regulatory-drift API: POST the framework name + your current control library, get back a JSON delta naming every amended clause, the exact control IDs that drift, and a traceable link to the source register — $0.25 per amendment-diff call, 50 free calls on signup, no contract, curl-and-go in under five minutes."},"customer":{"icpShape":"Senior compliance engineers and GRC platform devs at solo-to-small regulated SaaS shops (10-250 employees, targetCompanyType: company-type-solo-dental-practice-adjacent small regulated-software vendors), where the buyer who signs the credit-card charge is the Head of Engineering or Founding CTO and the daily user is the senior compliance-tooling dev or SRE wiring rule-ingest pipelines into their internal control library.","beachheadShape":"EarlyAdopterJTBD: solo/small regulated-SaaS teams who ship their own in-house rule-diff scripts against HIPAA/SOC2/PCI corpora and are tired of missing amendment deltas between quarterly regulator releases."},"archetype":"startup-archetypes.org.ai/ManagedWorkflow-MoneyOnDelivery","beachhead":"EarlyAdopterJTBD: solo/small regulated-SaaS teams who ship their own in-house rule-diff scripts against HIPAA/SOC2/PCI corpora and are tired of missing amendment deltas between quarterly regulator releases.","competitors":{"substitutes":[{"name":"In-house Python diff script hitting the Federal Register / NIST OSCAL feeds","category":"informal","uncopyabilityReason":""},{"name":"Manual Outlook + SharePoint search for the latest regulator bulletin PDF","category":"manual-bridge","uncopyabilityReason":""},{"name":"AuditBoard","category":"incumbent","uncopyabilityReason":"AuditBoard's revenue model is seat-licensed enterprise GRC suites sold through 4-6 month procurement cycles with SOC2 security review; shipping a $0.25-per-call credit-card API would cannibalize its $40k+ ACV floor and — more structurally — its deployment-mode is a multi-module UI workbench, not a developer API, so exposing a metered diff endpoint requires rebuilding the billing, entitlement, and rate-limit plane it doesn't own (deployment-mode-mismatch)."},{"name":"OneTrust","category":"incumbent","uncopyabilityReason":"OneTrust's moat is its regulator-relations data corpus (privacy authority mappings across 150+ jurisdictions) licensed under redistribution restrictions that prohibit exposing raw amendment deltas via a metered third-party API; its content-licensing contracts with regulator aggregators forbid the very usage pattern this approach sells (vertical-data-corpus lock-in)."},{"name":"Workiva","category":"incumbent","uncopyabilityReason":"Workiva is structurally a documents-and-workbooks collaboration platform integrated deep into SEC XBRL filing workflows — adding real-time amendment-diff requires integration depth into dozens of regulator feed parsers that its roadmap has deprioritized in favor of ESG and financial-reporting modules (integration-depth)."},{"name":"Hyperproof","category":"AI-native horizontal","uncopyabilityReason":"Hyperproof distributes via compliance-consultant channel partners who resell configured-framework bundles; a self-serve developer API undermines the partner margin structure its GTM depends on and it lacks the direct-to-developer marketing org to reach the SRE/compliance-dev persona (distribution-channel)."}]},"studioThesis":"T-AIS-LOW-TECH","killThreshold":{"K":8,"M":40,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Cost shape (seat-licensed enterprise ACV ↔ metered per-amendment-diff at $0.25/call)","yAxis":"Amendment-detection cadence (quarterly human review of regulator PDFs ↔ on-demand API call against live regulator register)","winningQuadrant":"Metered per-diff pricing with on-demand live-register detection — a dev hits the endpoint the morning after a NIST rev bump and gets the delta in under a second, billed at a quarter","loservilleEscape":true,"loservilleQuadrant":"Seat-licensed annual suite with quarterly human-reviewed bulletin PDFs — AuditBoard's documented failure mode where subscribers only learn about a HIPAA subpart edit when the Q3 regulatory-update deck lands in their GRC workspace, already two months stale"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acompliance-officers-regulatory-gap-analysis%3At-ais-low-tech%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acompliance-officers-training-completion-reporting%3At-ais-prem%3Av1","id":"fh:compliance-officers-training-completion-reporting:t-ais-prem:v1","lens":"ManagedWorkflow","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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/compliance-officers-training-completion-reporting","stableHash":"wcc:compliance-officers:training-completion-reporting:document:v1"},"problem":{"slotStatement":"Training Coordinators spend the two weeks before each FINRA exam window reconciling three incompatible exports (LMS completion CSVs, HRIS roster snapshots, and CE Council transcripts) by hand into a binder the CCO can sign, and every rep who changed branches mid-year shows up as a phantom lapse that takes hours of email archaeology to disprove."},"approach":{"oneSentence":"A training-completion close-binder that reconciles LMS, HRIS, and FINRA CE transcripts on a roster-effective-dated timeline, then certifies each rep's completion record against a CCO-signed rubric so every attested line item carries a review-ready citation back to its source event."},"customer":{"icpShape":"US-regulated broker-dealers and RIAs with 500-5,000 registered representatives where the buyer is the Chief Compliance Officer (signs the PO against the compliance tooling budget) and the daily user is the Compliance Training Coordinator assembling FINRA/SEC attestation packets","beachheadShape":"EarlyMajorityWorkflow: FINRA-member mid-size broker-dealers preparing annual Reg BI and Firm Element training completion filings"},"archetype":"startup-archetypes.org.ai/ManagedWorkflow-RetainerEngagement","beachhead":"EarlyMajorityWorkflow: FINRA-member mid-size broker-dealers preparing annual Reg BI and Firm Element training completion filings","competitors":{"substitutes":[{"name":"Cornerstone / SAI360 LMS completion reports","category":"incumbent"},{"name":"FINRA CE Online Council portal exports stitched in Excel by the Training Coordinator","category":"status-quo"},{"name":"ComplySci / RIA in a Box compliance suite add-ons","category":"adjacent vertical"},{"name":"Horizontal AI copilots (ChatGPT Enterprise, Hebbia) pointed at the LMS export","category":"AI-native horizontal"}]},"studioThesis":"T-AIS-PREM","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence trace per rep-line (bulk completion % ↔ per-rep citation back to LMS event-id, HRIS effective-date, and CE transcript hash)","yAxis":"Roster time-model (point-in-time snapshot ↔ effective-dated branch/registration history reconciled across the exam period)","winningQuadrant":"per-rep source-cited attestations reconciled against an effective-dated FINRA registration timeline, signable by the CCO without manual branch-transfer archaeology","loservilleEscape":true,"loservilleQuadrant":"Cornerstone/SAI360 dashboards that show an aggregate completion % on a point-in-time roster and silently list mid-year branch-transfers as lapses with no evidence trail"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acompliance-officers-training-completion-reporting%3At-ais-prem%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acomputer-and-information-systems-managers-it-risk-assessment%3At-hsa%3Av1","id":"fh:computer-and-information-systems-managers-it-risk-assessment:t-hsa:v1","lens":"AgenticWorkflow","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/computer-and-information-systems-managers-it-risk-assessment","stableHash":"wcc:computer-and-information-systems-managers:it-risk-assessment:document:v1"},"problem":{"slotStatement":"When the PUC auditor asks why a medium-likelihood SCADA vulnerability was accepted rather than mitigated in last cycle's treatment plan, the IT risk analyst cannot reconstruct who weighed which threat-model input against which compensating control — the decision sits in a Visio diagram, three Teams threads, and a retired engineer's head, and the audit finding lands as 'unattributed risk-acceptance decision' every cycle"},"approach":{"oneSentence":"A risk-register decision ledger that captures every accept/mitigate/transfer/avoid call on the NIST 800-30 register, binds each call to the threat source, asset criticality, and compensating-control evidence the analyst actually consulted, and produces a treatment-plan packet the PUC or NERC auditor can walk line-by-line as a traceable record"},"customer":{"icpShape":"Public utility IT organizations (CompanyType/company-type-public-utility) — electric, water, and gas utilities with 200k–2M meters subject to NERC-CIP, AWIA, or state PUC cybersecurity mandates — where the buyer is the VP of IT / CISO who signs the PO and the daily user is the IT Risk Analyst or GRC lead who runs the quarterly risk assessment and treatment-plan refresh","beachheadShape":"EarlyAdopterJTBD: mid-size investor-owned electric co-ops and municipal water utilities whose most recent NERC-CIP or state-PUC audit surfaced a finding on undocumented risk-acceptance rationale"},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-Subscription","beachhead":"EarlyAdopterJTBD: mid-size investor-owned electric co-ops and municipal water utilities whose most recent NERC-CIP or state-PUC audit surfaced a finding on undocumented risk-acceptance rationale","competitors":{"substitutes":[{"name":"Archer IT & Security Risk Management (RSA Archer)","category":"incumbent","uncopyabilityReason":"Archer's risk-register module is a form-driven workflow engine sold to Fortune-500 banks and large IOUs; its decision-capture is a free-text justification field with no linkage to the underlying threat-intel, asset-CMDB, or control-test evidence. Rebuilding that linkage as first-class decision ledger requires overhauling the core data model that its 15-year enterprise customer base depends on — a deployment-mode-mismatch and integration-depth barrier that blocks a 6-month pivot."},{"name":"AuditBoard CrossComply","category":"incumbent","uncopyabilityReason":"AuditBoard's distribution channel is SOX/internal-audit buyers at public companies; its sales motion, partner network, and content library are aimed at financial-reporting controls, not NERC-CIP-014 or AWIA sector-specific risk treatment. Retooling for utility-sector risk taxonomies and the PUC auditor walk-through artifact would require a separate distribution-channel build into utility CISO org charts they do not currently reach."},{"name":"ServiceNow IRM (Integrated Risk Management)","category":"incumbent","uncopyabilityReason":"ServiceNow IRM's liability-posture is that of a platform-of-record — it records what the customer's risk committee decides, but explicitly disclaims any role in the decision itself. Shipping an opinionated decision ledger that reconstructs analyst reasoning would expose ServiceNow to a liability-posture shift (being a participant in the risk-acceptance call) that is incompatible with its horizontal-platform go-to-market."},{"name":"Shared risk-register spreadsheet with a Word treatment plan emailed to the CISO","category":"manual-bridge"},{"name":"Tenable/Rapid7 vulnerability scanner report pasted into the annual risk memo","category":"informal"}]},"studioThesis":"T-HSA","killThreshold":{"K":9,"M":45,"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":"Decision-capture granularity (free-text justification field ↔ per-decision linkage to threat source, asset criticality, and control-test evidence)","yAxis":"Sector-regulatory fit (horizontal IRM taxonomy ↔ NERC-CIP / AWIA / state-PUC utility-sector pre-bake)","winningQuadrant":"Per-decision evidence linkage with NERC-CIP and AWIA utility pre-bake the PUC examiner can walk line-by-line","loservilleEscape":true,"loservilleQuadrant":"Free-text justification in a horizontal IRM taxonomy — Archer's and ServiceNow IRM's documented failure mode where the treatment-plan narrative cannot be reconstructed when the auditor asks 'why did you accept this risk?'"}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acomputer-and-information-systems-managers-it-risk-assessment%3At-hsa%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acomputer-and-information-systems-managers-it-risk-assessment%3At-low%3Av1","id":"fh:computer-and-information-systems-managers-it-risk-assessment:t-low:v1","lens":"HeadlessSaaS","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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/computer-and-information-systems-managers-it-risk-assessment","stableHash":"wcc:computer-and-information-systems-managers:it-risk-assessment:document:v1"},"problem":{"slotStatement":"IT risk analysts spend 3–5 weeks hand-copying control evidence from Jira, ServiceNow CMDB, Tenable, and vendor SIG questionnaires into a Word/Excel risk register, then defending every residual-risk rating line-by-line to examiners who demand a traceable record from finding to treatment owner to due date."},"approach":{"oneSentence":"A headless risk-register engine that continuously reconciles CMDB assets, vulnerability scans, and control-test results into an examiner-ready IT risk assessment and treatment plan, with every residual-risk score carrying a clickable traceable record back to its primary-source evidence."},"customer":{"icpShape":"US mid-market regional banks and credit unions ($2B–$20B assets) where the buyer is the CISO or VP of Information Security (signs the security-tooling PO) and the daily user is the IT Risk Analyst who authors the FFIEC/NIST-aligned risk assessment and treatment plan","beachheadShape":"EarlyAdopterJTBD: regional banks facing an imminent FFIEC CAT/NIST 800-53 exam cycle who need the next IT risk assessment and treatment plan delivered in under 6 weeks"},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-MoneyOnDelivery","beachhead":"EarlyAdopterJTBD: regional banks facing an imminent FFIEC CAT/NIST 800-53 exam cycle who need the next IT risk assessment and treatment plan delivered in under 6 weeks","competitors":{"substitutes":[{"name":"Archer IRM / ServiceNow IRM","category":"incumbent"},{"name":"LogicGate and Hyperproof GRC platforms","category":"adjacent vertical"},{"name":"Excel risk register maintained by the IT risk analyst with Big-4 advisory review","category":"status-quo"},{"name":"ChatGPT Enterprise used ad-hoc to draft risk narratives","category":"AI-native horizontal"}]},"studioThesis":"T-LOW","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence provenance (analyst-typed narrative ↔ each risk score cites the exact Tenable scan ID, CMDB CI, and control-test ticket)","yAxis":"Deployment posture (multi-tenant SaaS that cannot touch the core banking VPC ↔ headless service embedded behind the bank's firewall reading CMDB/SIEM directly)","winningQuadrant":"in-VPC headless engine where every residual-risk rating is click-through citable to the originating CMDB CI and scan finding — examiners accept the register without sampling","loservilleEscape":true,"loservilleQuadrant":"Archer/ServiceNow IRM multi-tenant SaaS where analysts still paste in narratives by hand and examiners must re-sample evidence because the risk ratings have no traceable link to source systems"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acomputer-and-information-systems-managers-it-risk-assessment%3At-low%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aconcierges-complaint-resolution-escalation%3At-bu%3Av1","id":"fh:concierges-complaint-resolution-escalation: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/concierges-complaint-resolution-escalation","stableHash":"wcc:concierges:complaint-resolution-escalation:voice:v1"},"problem":{"slotStatement":"When a PUC informal complaint lands, the Tier-2 concierge has to piece together the guest's call recordings, IVR transcripts, field-tech truck-roll notes, billing adjustments in CC&B, and the outage-management timestamps from four different systems — and when the 10-day PUC response goes out, roughly a third of the case files are missing the one IVR leg or field note that proves the utility actually did what it said, which the state consumer advocate flags as an adverse finding at the next rate case."},"approach":{"oneSentence":"A complaint-case-file service that, the moment a PUC-tagged or executive-escalation complaint is opened, pulls the CC&B billing trail, Genesys/NICE call legs, OMS outage windows, and field-tech Click/ServiceMax notes into a single chronological case record with each claim linked back to its source system log line, producing a review-ready packet the regulatory analyst can hand to the PUC without a 3-hour manual reconstruction."},"customer":{"icpShape":"Investor-owned or municipal public utilities (CompanyType/company-type-public-utility) with 200k–2M residential meters and an active state PUC docket, where the buyer is the VP of Customer Operations (or Director of Regulatory Compliance for co-signed purchases) and the daily user is the Tier-2 escalations concierge / complaint resolution analyst who handles PUC-tagged and executive-office complaints.","beachheadShape":"EarlyAdopterJTBD: regulated electric and gas utilities under a PUC consent decree or active rate case who must produce a per-complaint case file on 10-day PUC response windows and currently miss 15–30% of informal-complaint deadlines."},"archetype":"startup-archetypes.org.ai/AIService-Subscription","beachhead":"EarlyAdopterJTBD: regulated electric and gas utilities under a PUC consent decree or active rate case who must produce a per-complaint case file on 10-day PUC response windows and currently miss 15–30% of informal-complaint deadlines.","competitors":{"substitutes":[{"name":"Manual Outlook + SharePoint + CC&B tab-hopping reconstruction","category":"manual-bridge"},{"name":"Salesforce Service Cloud for Utilities (Energy & Utilities Cloud complaint console)","category":"incumbent","uncopyabilityReason":"Salesforce's E&U Cloud is an integration-depth problem for them: the complaint console is a case-object UI sitting on top of customer-supplied connectors, and the PUC-grade evidence assembly requires deep, utility-specific joins into Oracle CC&B meter-read history, OMS event logs, and Click/ServiceMax dispatch audit trails that Salesforce cannot own without rebuilding adapter IP they've explicitly left to SI partners — a 2-3 year reseller-contract re-negotiation, not a 6-month roadmap item."},{"name":"Oracle Utilities Customer Care & Billing (CC&B) with Customer Self Service add-on","category":"incumbent","uncopyabilityReason":"Oracle CC&B's deployment-mode mismatch is structural: it ships as a heavyweight on-prem/OCI billing system of record on a 12–18 month utility upgrade cadence gated by PUC change-control, so embedding a live complaint-evidence assembler that crosses into Genesys call recordings and non-Oracle OMS instances would require Oracle to exit its own billing-core scope and take liability for third-party call-center data — something its utility MSAs contractually disclaim."},{"name":"Verint / NICE CXone Quality Management for contact centers","category":"AI-native horizontal","uncopyabilityReason":"Verint/NICE are bounded by vertical-data-corpus: their speech analytics and QM are trained on contact-center interactions only and have no native model of a utility tariff, a PUC informal-complaint schema, or a CC&B billing adjustment — wiring those in means building a utility regulatory data model and a state-by-state PUC docket library they do not possess and cannot acquire from their telco/BPO customer base in under 18 months."},{"name":"J.D. Power / Escalation Management spreadsheets + homegrown Access DBs used by regulatory affairs teams","category":"informal"}]},"studioThesis":"T-BU","killThreshold":{"K":10,"M":70,"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":"Source-system reach for a single complaint (contact-center transcripts only ↔ full utility stack: CC&B billing + OMS outage + MWM field dispatch + IVR/ACD legs)","yAxis":"Time-to-packet for a PUC 10-day response (analyst hand-assembles over 3–5 hours ↔ draft case file ready within the first hour of ticket open)","winningQuadrant":"Full utility-stack reach with a sub-hour draft PUC case file the regulatory analyst only has to review-and-sign","loservilleEscape":true,"loservilleQuadrant":"Contact-center-transcript-only QM tools (Verint/NICE) that deliver a call summary hours later but leave the billing, outage, and field-dispatch reconstruction as manual analyst work — the documented failure mode where 25–30% of 10-day PUC responses go out missing the field-tech or OMS evidence leg"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aconcierges-complaint-resolution-escalation%3At-bu%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acounter-and-rental-clerks-inventory-discrepancy-resolution%3At-low%3Av1","id":"fh:counter-and-rental-clerks-inventory-discrepancy-resolution:t-low: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/counter-and-rental-clerks-inventory-discrepancy-resolution","stableHash":"wcc:counter-and-rental-clerks:inventory-discrepancy-resolution:voice:v1"},"problem":{"slotStatement":"When the cycle count disagrees with the ERP on-hand number for a reel of conductor or a pad-mount transformer, the counter clerk adjusts the book and moves on — and six months later during the PUC prudency review the auditor asks why 14 transformers were written down and nobody can reconstruct which work order, which truck, or which issue ticket caused the gap, so the utility eats the disallowance."},"approach":{"oneSentence":"Warehouse-counter discrepancy log that captures each adjustment at the moment the clerk posts it — pulling the open work order, the truck-assignment, the last cycle-count delta, and the issuing clerk's note into one frozen record the rate-case analyst can pull up unchanged months later when the PUC asks what happened to the 14 transformers."},"customer":{"icpShape":"Director of Meter-to-Cash Operations at a mid-sized public water/electric utility (CompanyType/company-type-public-utility, 80k–400k service connections, regulated by a state PUC), where the buyer is the Director of Meter-to-Cash Operations (signs the tooling PO against the annual rate-case OpEx budget) and the daily user is the Counter/Rental Clerk and the Inventory Control Analyst who handle meter, transformer, and service-truck stock at the warehouse counter.","beachheadShape":"EarlyAdopterJTBD: mid-sized investor-owned and municipal utilities whose last PUC prudency review flagged unexplained inventory write-offs on capital asset accounts"},"archetype":"startup-archetypes.org.ai/AIService-UsageMetered","beachhead":"EarlyAdopterJTBD: mid-sized investor-owned and municipal utilities whose last PUC prudency review flagged unexplained inventory write-offs on capital asset accounts","competitors":{"substitutes":[{"name":"Screenshot-archive folder of ERP inventory screens","category":"informal"},{"name":"Oracle Utilities Work and Asset Management (WAM) stock-adjustment module","category":"incumbent","uncopyabilityReason":"Oracle WAM's adjustment workflow is bound to its CIS/CC&B data model and deploys on multi-quarter Oracle Cloud Infrastructure upgrade cycles tied to utility IT steering committees; adding a counter-side evidence-capture layer that reaches into work-order, fleet-GPS, and cycle-count systems simultaneously would require reopening integration contracts with every utility's systems integrator — an integration-depth barrier Oracle cannot resolve in 6 months."},{"name":"IBM Maximo for Utilities inventory transactions","category":"incumbent","uncopyabilityReason":"Maximo's on-prem deployment posture at most utilities is air-gapped from the fleet-telematics and mobile-workforce-management clouds where the missing evidence actually lives; IBM's roadmap ships via customer-managed upgrades every 12–18 months, so a deployment-mode-mismatch prevents Maximo from streaming counter-clerk evidence into its adjustment record without a full hybrid-cloud re-architecture."},{"name":"SAP S/4HANA Utilities IS-U inventory postings","category":"incumbent","uncopyabilityReason":"SAP IS-U's stock posting is governed by the utility's SOX and FERC Form 1 controls already certified under the SAP audit-posture; introducing a new free-text clerk-evidence field into the posting path triggers re-certification of the entire regulated GL chain, a liability-posture barrier that makes a 6-month ship impossible for SAP's utility vertical team."},{"name":"Paper adjustment slips filed with the storeroom supervisor","category":"manual-bridge"}]},"studioThesis":"T-LOW","killThreshold":{"K":11,"M":55,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence-capture moment (reconstructed after month-end close ↔ frozen at the instant the clerk posts the adjustment at the counter)","yAxis":"Integration depth into utility-specific systems (generic inventory module ↔ natively joins WAM work-orders + fleet-GPS truck-assignments + cycle-count deltas)","winningQuadrant":"Frozen-at-post evidence capture that natively stitches the open work order, the issuing truck, and the cycle-count delta into the adjustment record the PUC auditor will eventually ask about","loservilleEscape":true,"loservilleQuadrant":"Post-hoc reconstruction from a generic stock-adjustment screen — the documented failure mode of Oracle WAM and SAP IS-U adjustments, where the clerk's reason-code dropdown is the only surviving artifact and the rate-case analyst has to reverse-engineer causality from timestamps six months later"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acounter-and-rental-clerks-inventory-discrepancy-resolution%3At-low%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acounter-and-rental-clerks-rental-agreement-walkthrough%3At-bu%3Av1","id":"fh:counter-and-rental-clerks-rental-agreement-walkthrough: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/counter-and-rental-clerks-rental-agreement-walkthrough","stableHash":"wcc:counter-and-rental-clerks:rental-agreement-walkthrough:voice:v1"},"problem":{"slotStatement":"When a customer disputes a damage charge or late fee three weeks after return, the counter clerk who walked them through the agreement is off-shift or gone, nobody recorded which specific clauses (fuel policy, insurance declination, return-by time) were actually read aloud and verbally accepted, and the signed PDF plus a shaky lot-camera clip cannot prove what the customer understood — so the ops manager eats the chargeback or writes off the deposit to avoid a chargeback-ratio hit."},"approach":{"oneSentence":"Counter-tablet walkthrough capture that records the clerk reading each material clause, timestamps the customer's verbal 'yes' against the exact clause ID, and assembles a clause-by-clause acceptance log the dispute team can pull up in 90 seconds when a chargeback lands."},"customer":{"icpShape":"Multi-location consumer equipment rental operators (party/event rental, construction tool rental, AV/staging rental) structured as company-type-vc-saas-startup-style rollups with 15-120 counter locations, where the buyer is the VP of Operations or Chief Risk Officer who signs the contract-management tooling PO and the daily user is the counter/rental clerk walking the customer through the rental agreement at pickup.","beachheadShape":"EarlyAdopterJTBD: PE-backed event & party rental rollups that have consolidated 8-30 independent yards under one brand and are now getting crushed by damage-waiver disputes and 'I never agreed to that' chargebacks at scale."},"archetype":"startup-archetypes.org.ai/AIService-Subscription","beachhead":"EarlyAdopterJTBD: PE-backed event & party rental rollups that have consolidated 8-30 independent yards under one brand and are now getting crushed by damage-waiver disputes and 'I never agreed to that' chargebacks at scale.","competitors":{"substitutes":[{"name":"Point-of-Rental Systems (POR)","category":"incumbent","uncopyabilityReason":"Point-of-Rental's product surface is a contract-generation and inventory ERP — its integration depth with the yard's pricing, availability, and tax modules is its moat, but that same architecture treats the customer walkthrough as an out-of-band signature event; adding clause-level verbal-acceptance capture means instrumenting the counter tablet with audio/prompt flow and re-architecting the contract object into an ordered clause-acceptance ledger, which breaks backward compatibility with every ERP-side report their 5,000+ yards depend on."},{"name":"Alert Rental / Solutions by Computer","category":"incumbent","uncopyabilityReason":"Alert is an on-prem/Citrix-hosted rental ERP whose distribution channel is dealer VARs selling to single-yard operators; their deployment-mode mismatch (thick-client Windows, VAR-gated upgrades) means any walkthrough-capture feature has to ship as a thick-client screen the VAR has to push, so they cannot match a web-tablet SaaS cadence for multi-location rollups even if they cloned the workflow."},{"name":"DocuSign + Zuora/Stripe dispute tooling","category":"AI-native horizontal","uncopyabilityReason":"DocuSign's liability posture is built around signature-block attestation, not clause-level comprehension capture — expanding into per-clause verbal acceptance would require them to take on a new evidentiary class (spoken acceptance of specific contract terms) that their E-SIGN Act compliance narrative and existing enterprise contracts explicitly carve out; their legal team will not let product ship a feature that re-opens what constitutes 'signed'."},{"name":"Manual Outlook + Drive + CRM evidence hunt by the AR/chargeback specialist","category":"manual-bridge"},{"name":"Lot-camera CCTV clip + signed PDF mailed to the card network","category":"informal"}]},"studioThesis":"T-BU","killThreshold":{"K":10,"M":45,"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":"Evidence granularity at dispute time (whole-contract PDF + signature ↔ per-clause timestamped acceptance log)","yAxis":"Counter-workflow friction (clerk adds 4+ min of separate logging ↔ capture happens inside the walkthrough the clerk already does)","winningQuadrant":"Per-clause timestamped acceptance log captured zero-friction inside the walkthrough the clerk is already performing at pickup","loservilleEscape":true,"loservilleQuadrant":"Whole-contract PDF with a signature block plus a separate 4-minute clerk checklist — Point-of-Rental's current flow, where the clerk signs the PDF in the ERP and then is supposed to tick a paper 'walkthrough completed' box that chargeback teams report is filled in <30% of the time."}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acounter-and-rental-clerks-rental-agreement-walkthrough%3At-bu%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acounter-and-rental-clerks-return-condition-assessment%3At-bu%3Av1","id":"fh:counter-and-rental-clerks-return-condition-assessment:t-bu:v1","lens":"CoPilot","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/counter-and-rental-clerks-return-condition-assessment","stableHash":"wcc:counter-and-rental-clerks:return-condition-assessment:voice:v1"},"problem":{"slotStatement":"When a clerk re-intakes returned rental equipment, they are still applying last quarter's damage-charge matrix and wear-and-tear thresholds — the tariff schedule and PUC-approved depreciation tables changed 6 weeks ago, counter training has not caught up, and every return assessed under the stale rule is a line item a rate intervenor or consumer-affairs auditor can pull to argue discriminatory billing."},"approach":{"oneSentence":"After every return, the clerk's tablet walks the gear against the CURRENT tariff-versioned condition rubric, flags each charge decision with the effective-dated rule that produced it, and escalates any assessment where the active rule diverges from what the clerk's muscle memory would have applied — producing a per-return traceable record the rate-case team can pull on demand."},"customer":{"icpShape":"VP of Customer Operations at a mid-to-large public utility (CompanyType/company-type-public-utility) that runs in-person equipment-rental and meter-loan counters — think 200k+ meter service territories where rental clerks check out and re-intake leak-detection gear, hotspot testers, bucket-truck attachments, and customer-loaned safety equipment; the buyer is the VP of Customer Operations (signs the PO, owns regulatory exposure to the PUC) and the daily user is the counter and rental clerk at the service center window.","beachheadShape":"EarlyAdopterJTBD: investor-owned and municipal utilities that have been cited or near-cited by a state PUC for inconsistent damage-charge assessments on returned customer equipment, where the ops VP needs a defensible per-return condition record before the next rate-case filing window."},"archetype":"startup-archetypes.org.ai/CoPilot-Subscription","beachhead":"EarlyAdopterJTBD: investor-owned and municipal utilities that have been cited or near-cited by a state PUC for inconsistent damage-charge assessments on returned customer equipment, where the ops VP needs a defensible per-return condition record before the next rate-case filing window.","competitors":{"substitutes":[{"name":"Clerk memory + laminated damage-charge sheet at the counter","category":"status-quo","uncopyabilityReason":""},{"name":"Ironclad-style contract repository used by legal-ops for storing the signed tariff amendments","category":"manual-bridge"},{"name":"SAP IS-U (Industry Solution for Utilities) Device Management module","category":"incumbent","uncopyabilityReason":"SAP IS-U's device-management flow is bound to a batch-ERP deployment posture with multi-year implementation cycles and a certified-partner customization channel; shipping a clerk-facing tablet experience that reconciles every return against a weekly-republished tariff rubric would require abandoning the batch posture and rebuilding the counter UX outside the partner-services revenue model (deployment-mode-mismatch)."},{"name":"Oracle Utilities Customer Care & Billing (CC&B) with Work & Asset Management","category":"incumbent","uncopyabilityReason":"Oracle CC&B's rating engine reads from a centrally-maintained rate schedule curated by utility IT on 90-day cadences; the integration depth required to capture which PUC filing and which effective date justified a specific damage-charge decision at the counter does not exist in the data model, and adding per-assessment rule provenance would require rewriting the rating-engine contract with every existing CC&B customer (integration-depth)."},{"name":"Itron Field Collection System + clerk-side FCS handhelds","category":"incumbent","uncopyabilityReason":"Itron's field hardware and firmware are certified for metrology accuracy under state weights-and-measures regimes; opening the handheld to run a dynamic tariff-rubric evaluator that could influence customer charges would pull the device into a new regulatory review for each state it operates in (regulatory-licensure)."},{"name":"Generic computer-vision damage-assessment AI (e.g. Ravin AI, Tractable) pitched horizontally into utilities","category":"AI-native horizontal","uncopyabilityReason":"These vendors have trained exclusively on auto-body and fleet-vehicle corpora and have no labeled library of utility-specific gear — leak-detection sondes, CT/PT clamps, arc-flash suits, bucket-truck liners — nor the ingested history of state-PUC-approved depreciation tables that govern charges; building that vertical data corpus would take multi-year partnerships with utilities that currently have no reason to share it (vertical-data-corpus)."}]},"studioThesis":"T-BU","killThreshold":{"K":9,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Rule-freshness cadence (rate schedule re-pinned annually at ERP-upgrade time ↔ tariff rubric re-pinned within hours of a PUC filing taking effect)","yAxis":"Authority boundary at the counter (advisory damage-charge suggestion the clerk can override silently ↔ rule-bound assessment that escalates any clerk-override to a supervisor queue with the divergent rule captured)","winningQuadrant":"Tariff rubric re-pinned within hours of each PUC effective date AND every clerk override captured against the specific effective-dated rule it diverged from — so the rate-case team can defend any single damage charge back to the filing that authorized it.","loservilleEscape":true,"loservilleQuadrant":"Annual-cadence rate tables with silent clerk overrides — where SAP IS-U customers today cannot tell a PUC auditor which version of the depreciation schedule was in force when a specific leak-detector return was charged, and clerks routinely apply last year's matrix from memory with no divergence trail."}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acounter-and-rental-clerks-return-condition-assessment%3At-bu%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acounter-and-rental-clerks-return-condition-assessment%3At-low%3Av1","id":"fh:counter-and-rental-clerks-return-condition-assessment:t-low:v1","lens":"AIService","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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/counter-and-rental-clerks-return-condition-assessment","stableHash":"wcc:counter-and-rental-clerks:return-condition-assessment:voice:v1"},"problem":{"slotStatement":"When customers return skid-steers, scissor lifts, and generators, return clerks must walk around the unit with a phone, judge 'fair wear' vs chargeable damage against a paper rubric, and photograph it — but disputes get charged back weeks later because the photo set is unlabeled, the clerk's condition call isn't defensible, and the branch loses the damage recovery the adjuster could have invoiced."},"approach":{"oneSentence":"A return-lane walkaround capture app that guides the clerk through a unit-specific damage rubric, pairs each photo to the rubric line it evidences, and closes out a review-ready condition packet posted straight into the rental ERP's return ticket."},"customer":{"icpShape":"Regional and national equipment rental chains (Sunbelt/United Rentals-scale franchisees and 20–200 branch independents in construction and event equipment rental, $50M–$500M revenue) where the buyer is the VP of Operations or Director of Fleet/Asset Management who owns damage-recovery P&L, and the daily user is the counter/rental return clerk at the branch.","beachheadShape":"EarlyAdopterJTBD: multi-branch construction-equipment rental chains with >$2M/yr in disputed damage write-offs and existing Wynne/Point-of-Rental ERP"},"archetype":"startup-archetypes.org.ai/AIService-UsageMetered","beachhead":"EarlyAdopterJTBD: multi-branch construction-equipment rental chains with >$2M/yr in disputed damage write-offs and existing Wynne/Point-of-Rental ERP","competitors":{"substitutes":[{"name":"Point-of-Rental / Wynne Rental Management return checklists + phone camera roll","category":"incumbent"},{"name":"Record360 (vehicle/equipment condition video capture)","category":"adjacent vertical"},{"name":"Branch clerk with paper damage-waiver form and clipboard","category":"status-quo"},{"name":"ChatGPT / generic multimodal LLM used ad-hoc by ops managers","category":"AI-native horizontal"}]},"studioThesis":"T-LOW","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence binding (loose photo album ↔ each photo pinned to a specific rubric line on a specific asset class)","yAxis":"ERP return-ticket embedding (standalone app the clerk opens separately ↔ packet auto-posted into the open Wynne/Point-of-Rental return ticket)","winningQuadrant":"per-rubric-line photo evidence auto-attached to the Wynne/POR return ticket before the customer drives off","loservilleEscape":true,"loservilleQuadrant":"Record360's time-stamped walkaround video sitting in a separate cloud portal that the A/R clerk has to hunt down weeks later when the customer disputes the damage charge"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acounter-and-rental-clerks-return-condition-assessment%3At-low%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acustomer-service-representatives-billing-dispute-resolution%3At-bu%3Av1","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","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acustomer-service-representatives-billing-dispute-resolution%3At-bu%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acustomer-service-representatives-billing-dispute-resolution%3At-td%3Av1","id":"fh:customer-service-representatives-billing-dispute-resolution:t-td:v1","lens":"CoPilot","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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":"Billing dispute reps spend 12–25 minutes per call pivoting between the CRM ticket, the billing system's charge detail, usage/metering logs, prior credit history, and promo-code tables to decide whether a disputed charge is valid, and the adjustment decisions they key in are rarely backed by a reviewable record that a QA auditor or state regulator can reconstruct after the fact."},"approach":{"oneSentence":"A dispute-resolution co-pilot that reconciles the disputed charge against billing-system CDRs, prior-cycle invoices, and promo/contract terms in the rep's existing agent desktop, then certifies a review-ready adjustment recommendation with line-item citations the rep can accept, edit, or escalate before posting the credit."},"customer":{"icpShape":"US-based mid-market telecom and ISP operators ($250M–$2B revenue) running Amdocs or CSG billing stacks, where the buyer is the VP of Customer Operations (or Director of Billing Ops) who controls the contact-center tooling budget and the daily user is the Tier-1/Tier-2 Billing Dispute Representative handling adjustment tickets","beachheadShape":"EarlyAdopterJTBD: regional cable/broadband carriers with >5% monthly billing-adjustment rates and active state PUC complaint exposure"},"archetype":"startup-archetypes.org.ai/CoPilot-Subscription","beachhead":"EarlyAdopterJTBD: regional cable/broadband carriers with >5% monthly billing-adjustment rates and active state PUC complaint exposure","competitors":{"substitutes":[{"name":"Amdocs CES / CSG Ascendon built-in dispute workflows","category":"incumbent"},{"name":"ASAPP and Cresta agent-assist copilots","category":"AI-native horizontal"},{"name":"Offshore BPO dispute-resolution teams (Teleperformance, Concentrix)","category":"human alternative"},{"name":"Rep-authored spreadsheet adjustment macros and tribal SOP docs","category":"status-quo"}]},"studioThesis":"T-TD","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Evidence trace on the credit decision (rep types free-form note ↔ every adjustment line cites the exact CDR, invoice line, and promo clause)","yAxis":"Embedding in the billing agent desktop (sidecar browser tab ↔ native overlay inside Amdocs/CSG adjustment screen with write-back to the ticket)","winningQuadrant":"Citation-backed adjustment recommendations rendered inside the Amdocs/CSG adjustment form with one-click write-back and a traceable record persisted to the ticket","loservilleEscape":true,"loservilleQuadrant":"Cresta/ASAPP-style sidecar chat that suggests talk-track language but leaves the rep to manually reconcile CDRs and key the adjustment without any citation trail — the pattern that leaves QA and PUC auditors unable to reconstruct why a credit was issued"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acustomer-service-representatives-billing-dispute-resolution%3At-td%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acustomer-service-representatives-complaint-escalation-handling%3At-td%3Av1","id":"fh:customer-service-representatives-complaint-escalation-handling:t-td:v1","lens":"CoPilot","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-complaint-escalation-handling","stableHash":"wcc:customer-service-representatives:complaint-escalation-handling:voice:v1"},"problem":{"slotStatement":"When a patient calls back furious about a crown, bill, or anesthesia consent and later disputes the charge with their card issuer, the office manager's free-text note in Dentrix and the shouted summary to the dentist are not enough to defend the chargeback — Visa/Mastercard reason-code 13.1/13.5 responses need a dated, signed escalation trail tying the complaint, the clinical note, the consent form, and the resolution offer together, and that trail simply does not exist, so the practice silently loses the $1,400 crown fee plus a $15-25 chargeback penalty every time."},"approach":{"oneSentence":"Sits inside the front-desk phone workflow as a complaint-intake co-pilot that listens to the patient call, pulls the matching Dentrix ledger line and consent PDF, and assembles a dated escalation packet the dentist can co-sign in two clicks — producing a review-ready dispute binder the practice can drop straight into the card-issuer's representment form."},"customer":{"icpShape":"Owner-operator dentists at solo dental practices (company-type-solo-dental-practice, 1-3 operatories, ~$800K-$1.5M annual collections) where the buyer is the Practice Owner/DDS who signs the software PO and the daily user is the front-desk Office Manager or lead CSR who fields the angry post-treatment call and logs the complaint in Dentrix/Eaglesoft.","beachheadShape":"EarlyAdopterJTBD: solo general-dentistry practices that have eaten ≥2 card-network chargebacks in the last 12 months on treatment-dispute grounds ('work not as described', 'unauthorized charge after anesthesia')."},"archetype":"startup-archetypes.org.ai/CoPilot-Subscription","beachhead":"EarlyAdopterJTBD: solo general-dentistry practices that have eaten ≥2 card-network chargebacks in the last 12 months on treatment-dispute grounds ('work not as described', 'unauthorized charge after anesthesia').","competitors":{"substitutes":[{"name":"Dedicated chargeback-dispute desk / outsourced recovery service","category":"informal","uncopyabilityReason":""},{"name":"Office manager writing free-text complaint notes in Dentrix","category":"manual-bridge","uncopyabilityReason":""},{"name":"Weave (dental practice communications platform)","category":"incumbent","uncopyabilityReason":"Weave's revenue model is built on being a horizontal front-desk phone/SMS platform across 30k+ practices; it deliberately stays generic across dental, vet, and optometry and has no clinical-ledger write-path into Dentrix/Eaglesoft consent objects. Shipping a dental-chargeback escalation binder would require a vertical-data-corpus investment (per-CDT-code dispute taxonomy, card-network reason-code mapping) that breaks its multi-vertical GTM."},{"name":"Dentrix Ascend / Henry Schein One practice-management suite","category":"incumbent","uncopyabilityReason":"Dentrix's integration-depth moat is also its cage: it owns the ledger but its release cadence is 2 major versions/year gated by Henry Schein distributor channel, and its liability posture as the clinical system of record means it cannot attach probabilistic call-transcript evidence to a patient chart without re-certifying the whole practice-management product against state dental-board record-keeping rules."},{"name":"Chargebacks911 / Midigator (horizontal chargeback-representment SaaS)","category":"AI-native horizontal","uncopyabilityReason":"Chargebacks911 is a distribution-channel play wired into Stripe, Shopify, and card-acquirer partnerships serving e-commerce merchants at scale; a $1.2M solo dental practice is below its minimum viable CAC and its evidence model assumes shipping-tracking + IP logs, not signed dental consent forms and CDT-coded clinical notes, so it cannot underwrite dental representment without a ground-up vertical-data-corpus build."}]},"studioThesis":"T-TD","killThreshold":{"K":9,"M":35,"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":"Evidence assembly trigger (post-hoc, after the chargeback letter arrives ↔ at-the-moment-of-complaint, while the patient is still on the phone)","yAxis":"Integration depth into the dental clinical record (bolt-on CRM notes ↔ native write into Dentrix/Eaglesoft ledger + consent PDF linkage)","winningQuadrant":"At-the-moment-of-complaint capture with native Dentrix/Eaglesoft ledger + consent linkage, so the dispute binder is already assembled 30-60 days before the card network's representment deadline","loservilleEscape":true,"loservilleQuadrant":"Post-hoc bolt-on note-taking — exactly where Weave's call recordings and the office manager's Dentrix free-text notes live today: the evidence is scattered across a call log, a sticky note, and a clinical chart, and has to be hand-reassembled under a 10-day representment clock (the documented failure mode that loses ~$1,400 + $25 per chargeback)."}},"unmetRequirements":[],"pricingArchitecture":"custom-quote","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acustomer-service-representatives-complaint-escalation-handling%3At-td%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acustomer-service-representatives-service-upgrade-consultation%3At-ais-low-tech%3Av1","id":"fh:customer-service-representatives-service-upgrade-consultation:t-ais-low-tech: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-service-upgrade-consultation","stableHash":"wcc:customer-service-representatives:service-upgrade-consultation:voice:v1"},"problem":{"slotStatement":"Every upgrade-consultation call the agency bills for ($1.80–$4.50 of rep-minutes plus a $0.40 QA sampling allocation) leaves a fragmented trail — the CRM note, the call recording, the order-system diff, and the rep's paraphrase of what the customer consented to all live in different systems, so when the end-client disputes a plan change or a regulator asks why the upsell was offered, the agency spends 12–25 minutes per contested call rebuilding the provenance chain by hand, and roughly 1 in 40 calls gets written off entirely because the chain can't be reassembled."},"approach":{"oneSentence":"A pay-per-call voice-side API plus 80-line CLI that, after each upgrade consultation, stitches the transcript turn, the plan-diff the rep keyed into the order system, and the customer's spoken consent into one signed JSON envelope the agency can hand back to its client — $0.12 per completed call, first 500 calls/month free, paste an API key and it runs against an existing Twilio or SIP recording stream with no integration project."},"customer":{"icpShape":"Founder-operators and technical leads at bootstrap digital agencies (company-type-bootstrap-agency, 10–60 staff) that white-label ISP/telco/SaaS upgrade-call handling for their clients — the buyer is the agency owner or COO who signs the credit card, and the daily user is the senior dev/SRE who wires the API into their existing Twilio/Asterisk voice stack. They sign up with a card, never schedule a sales call, and would otherwise write the Python script themselves.","beachheadShape":"EarlyAdopterJTBD: two-to-six-person dev squads inside bootstrap BPO/agency shops that resell outbound upgrade-consultation calling to regional ISPs, streaming services, and SMB telco resellers, and need a per-call record their end client can spot-check."},"archetype":"startup-archetypes.org.ai/AIService-MoneyOnDelivery","beachhead":"EarlyAdopterJTBD: two-to-six-person dev squads inside bootstrap BPO/agency shops that resell outbound upgrade-consultation calling to regional ISPs, streaming services, and SMB telco resellers, and need a per-call record their end client can spot-check.","competitors":{"substitutes":[{"name":"Homegrown Python script stitching Twilio recordings + Salesforce notes + Whisper transcripts","category":"manual-bridge","uncopyabilityReason":""},{"name":"Screenshot-archive folder (screen-grabs of the order-system diff filed per billing period)","category":"informal","uncopyabilityReason":""},{"name":"Salesforce Service Cloud Voice + Einstein Conversation Insights","category":"incumbent","uncopyabilityReason":"Service Cloud Voice is sold as a per-named-user seat license with a 20-seat floor and a mandatory Salesforce org; it cannot be delivered as a $0.12/call credit-card API because doing so would cannibalize its seat-based pricing AND would require decoupling from the Salesforce data model that its AppExchange distribution depends on — that is a distribution-channel moat pointed the wrong way for a pay-per-event wedge."},{"name":"NICE CXone with Enlighten AI for QA","category":"incumbent","uncopyabilityReason":"NICE CXone's QA-evidence product is locked to its own ACD/recording stack — to accept a third-party Twilio or SIP stream and emit a per-call signed envelope, NICE would have to rebuild the integration-depth assumption that its recording pipeline is the system of record, which is the exact integration moat its enterprise contracts are priced on."},{"name":"Observe.AI post-call QA","category":"AI-native horizontal","uncopyabilityReason":"Observe.AI ships as an annual-contract SaaS with a sales-assisted onboarding model and a supervisor-dashboard UX; its liability posture (it markets itself as coaching, explicitly NOT as a consent-of-record system) means it cannot sign and hand back a customer-consent envelope without taking on regulatory exposure its MSA currently disclaims, and rewriting the liability posture requires insurance and legal rework that outruns a 6-month window."}]},"studioThesis":"T-AIS-LOW-TECH","killThreshold":{"K":10,"M":45,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Cost shape (annual seat license + implementation SOW ↔ metered $/completed-call with credit-card signup)","yAxis":"Provenance-stitch latency per call (analyst rebuilds chain in 12–25 min after a dispute ↔ signed envelope emitted within 30s of call hangup)","winningQuadrant":"Metered per-call pricing with a sub-30-second signed envelope the agency can forward to its end client the same day the dispute lands","loservilleEscape":true,"loservilleQuadrant":"Seat-licensed QA suites (Salesforce Service Cloud Voice, NICE CXone) where the agency pays $90–$150/seat/month AND still burns 12–25 analyst-minutes per contested call reconstructing the provenance chain from four sources"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acustomer-service-representatives-service-upgrade-consultation%3At-ais-low-tech%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acustomer-service-representatives-service-upgrade-consultation%3At-ais-prem%3Av1","id":"fh:customer-service-representatives-service-upgrade-consultation:t-ais-prem: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-service-upgrade-consultation","stableHash":"wcc:customer-service-representatives:service-upgrade-consultation:voice:v1"},"problem":{"slotStatement":"Every quarter the practice updates membership tiers, per-procedure fees, or included-cleaning counts, but the CSR's upgrade-consultation script and quoting worksheet lag the amendment — so patients get quoted last-cycle pricing, the coordinator hand-rewrites the order, and the owner-dentist burns evening hours reworking mis-scoped upgrade tickets the next morning."},"approach":{"oneSentence":"Fee-schedule-bound upgrade consultation that listens to the live CSR call, reconciles the spoken plan tier and per-procedure quote against the currently-in-force amendment of the practice's membership schedule, and flags any drift before the order is committed — producing a per-call verifiable output the DDS-principal can spot-check in under a minute."},"customer":{"icpShape":"Solo and two-chair dental practices (company-type-solo-dental-practice) running voice-based service plan upgrade consultations for in-house membership/discount plans, where the buyer is the Practice Owner / DDS-Principal who signs the PMS and phone-stack contracts and the daily user is the front-desk Treatment Coordinator or CSR handling upgrade calls.","beachheadShape":"EarlyAdopterJTBD: solo DDS-owned practices running in-house dental membership plans (e.g. Kleer/DentalHQ-style) who personally review upgrade call outcomes and feel the fee-schedule drift pain first-hand."},"archetype":"startup-archetypes.org.ai/AIService-RetainerEngagement","beachhead":"EarlyAdopterJTBD: solo DDS-owned practices running in-house dental membership plans (e.g. Kleer/DentalHQ-style) who personally review upgrade call outcomes and feel the fee-schedule drift pain first-hand.","competitors":{"substitutes":[{"name":"Outside-counsel / plan-consultant quarterly update","category":"informal"},{"name":"Kleer / DentalHQ membership plan admin console","category":"incumbent","uncopyabilityReason":"Kleer and DentalHQ are vertical-data-corpus incumbents built around self-serve membership enrollment web flows; they have no voice-channel capture surface on the practice's phone system and no per-call reconciliation path. Shipping live CSR-call drift detection would require building a telephony/voice-capture stack orthogonal to their current web-portal product and re-negotiating their per-member SaaS pricing model."},{"name":"Weave (dental phone/communications platform)","category":"incumbent","uncopyabilityReason":"Weave owns the dental phone channel but its integration-depth into clinical fee schedules and membership-tier amendment history is shallow — it reads PMS appointment data, not the versioned fee-schedule ledger. To reconcile a quoted upgrade against the in-force amendment, Weave would need deep bi-directional writes into Dentrix/Eaglesoft/Open Dental fee tables, which its current PMS-read-only integration posture does not support."},{"name":"Dentrix / Open Dental built-in treatment-plan estimator","category":"incumbent","uncopyabilityReason":"Dentrix and Open Dental are deployment-mode-mismatched: they are on-prem or thick-client PMS installs whose fee-schedule editor is a manual human-driven form. They have no real-time voice surface and no amendment-versioning primitive — the current schedule simply overwrites the prior one, so even if they bolted on an AI, there is no historical in-force ledger to reconcile against."},{"name":"ChatGPT / generic LLM used ad-hoc by the coordinator","category":"AI-native horizontal","uncopyabilityReason":"Horizontal LLMs lack the liability-posture and vertical-data-corpus to be trusted on patient-facing price quotes: they cannot attest which amendment of the practice's fee schedule was in force on the call date, and the practice owner carries the professional-liability exposure if a mis-quote becomes a patient dispute. Closing that gap requires practice-specific fee-ledger ingestion and a signed per-call record, neither of which a general chat product can offer."}]},"studioThesis":"T-AIS-PREM","killThreshold":{"K":10,"M":45,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Fee-schedule amendment awareness (reads today's static price list ↔ reconciles quote against versioned in-force amendment on call-date)","yAxis":"Capture surface (post-hoc PMS note / manual re-entry ↔ live voice capture during the CSR upgrade call)","winningQuadrant":"Live-voice capture with amendment-version reconciliation — the CSR's spoken upgrade quote is checked against the fee schedule in force at call time, before the order commits","loservilleEscape":true,"loservilleQuadrant":"Static-price-list lookup reviewed post-hoc from PMS notes — Dentrix's built-in estimator and Kleer's admin console both sit here: the coordinator quotes from whatever price list was last manually edited, drift is only caught the next morning when the owner-DDS reworks the ticket"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acustomer-service-representatives-service-upgrade-consultation%3At-ais-prem%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Acustomer-service-representatives-service-upgrade-consultation%3At-bu%3Av1","id":"fh:customer-service-representatives-service-upgrade-consultation:t-bu:v1","lens":"CoPilot","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-service-upgrade-consultation","stableHash":"wcc:customer-service-representatives:service-upgrade-consultation:voice:v1"},"problem":{"slotStatement":"Inbound voice consultations for tier-upgrades stretch beyond 45 minutes because agents lack a real-time quoting tool, forcing them to burn expert time manually cross-referencing feature limits across internal wikis while the buyer waits on hold."},"approach":{"oneSentence":"Replace the manual wiki-searching and disjointed quoting during upgrade calls with a real-time voice copilot that evaluates feature usage mid-conversation and dispatches verifiable upgrade quotes directly into the billing engine before the conversation ends."},"customer":{"icpShape":"VP of RevOps at a 50-200 employee company-type-vc-saas-startup, where the buyer is the VP of RevOps and the daily user is the line-level CSM or Renewals Representative.","beachheadShape":"EarlyMajorityWorkflow: Series B/C B2B SaaS startups migrating from flat-rate to complex usage-based pricing models that require mid-call telemetry checks."},"archetype":"startup-archetypes.org.ai/CoPilot-Subscription","beachhead":"EarlyMajorityWorkflow: Series B/C B2B SaaS startups migrating from flat-rate to complex usage-based pricing models that require mid-call telemetry checks.","competitors":{"substitutes":[{"name":"Salesforce Service Cloud Voice","category":"incumbent","uncopyabilityReason":"Salesforce Service Cloud Voice is fundamentally bound to custom Apex triggers for downstream billing writes — deploying a lightweight, mid-call CPQ execution bridge without a heavy six-month SI implementation cycle is structurally impossible due to its integration-depth requirements."},{"name":"Zendesk Talk","category":"incumbent","uncopyabilityReason":"Zendesk Talk operates on an asynchronous ticket-generation paradigm; embedding real-time CPQ evaluations requires completely re-architecting their webRTC client to support synchronous streaming payloads over their legacy telephony stack, constituting a severe deployment-mode mismatch."},{"name":"Gong","category":"AI-native horizontal","uncopyabilityReason":"Gong’s entire risk model relies on maintaining a read-only, post-call conversational intelligence posture; they deliberately avoid the liability-posture required to execute live, real-time commercial transactions into external billing systems during live calls."},{"name":"Ironclad contract repository for legal-ops","category":"manual-bridge"}]},"studioThesis":"T-BU","killThreshold":{"K":10,"M":45,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Latency of action (post-call batch insight ↔ real-time in-call execution)","yAxis":"Write authority (read-only CRM sync ↔ bidirectional billing CPQ dispatch)","winningQuadrant":"real-time in-call execution with bidirectional CPQ dispatch directly to the billing ledger","loservilleEscape":true,"loservilleQuadrant":"Gong capturing the verbal \"yes\" to an upgrade via post-call insight, but leaving the agent to manually build the quote because it lacks bidirectional billing dispatch."}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Acustomer-service-representatives-service-upgrade-consultation%3At-bu%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aeditors-copy-editing-style-alignment%3At-dev-infra%3Av1","id":"fh:editors-copy-editing-style-alignment:t-dev-infra: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/editors-copy-editing-style-alignment","stableHash":"wcc:editors:copy-editing-style-alignment:pure-info:v1"},"problem":{"slotStatement":"Every docs PR sits in a style-approval queue waiting for the lone technical editor to hand-check terminology, voice, and Vale/house-rule exceptions against an out-of-date style guide — engineers ship features faster than the editor can sign off, so merges stall for 3–7 days, release notes miss the launch window, and engineers start bypassing the review by merging 'fix typo' PRs without endorsement."},"approach":{"oneSentence":"A house-style editorial gate that runs on every docs PR, redlines terminology and voice deviations against the living style guide, and hands the technical editor a pre-annotated diff with a signed review-ready record of which rules fired, which were overridden, and who cleared the merge — collapsing the endorsement step from days to minutes."},"customer":{"icpShape":"Head of Developer Relations or VP Engineering at a Series B–D VC-backed SaaS startup (CompanyType/company-type-vc-saas-startup, 150–600 employees) shipping a public docs portal, SDK reference, and technical blog — where the buyer is the VP Engineering (or Head of DevRel) who controls the docs-tooling budget and the daily user is the staff technical writer / copy editor running house-style passes on PR-gated MDX changes.","beachheadShape":"EarlyAdopterJTBD: single-writer DevRel teams at 200–500-person dev-tools SaaS startups where every docs PR blocks on a one-person style review queue."},"archetype":"startup-archetypes.org.ai/AIService-MoneyOnDelivery","beachhead":"EarlyAdopterJTBD: single-writer DevRel teams at 200–500-person dev-tools SaaS startups where every docs PR blocks on a one-person style review queue.","competitors":{"substitutes":[{"name":"Wet-signature style-review form routed in Slack/GitHub PR comments","category":"manual-bridge"},{"name":"Vale (open-source prose linter) wired into CI","category":"incumbent","uncopyabilityReason":"Vale is a rules-engine CLI maintained as an OSS project with no authoring UI, no reviewer hand-off workflow, and no notion of an endorsed merge record; shipping a reviewer-facing gated workflow with signed overrides would require building a commercial SaaS control plane, a hosted rules editor, and an identity/audit layer — none of which fit the project's volunteer-maintainer distribution model or single-binary deployment posture (deployment-mode-mismatch)."},{"name":"Acrolinx","category":"incumbent","uncopyabilityReason":"Acrolinx's revenue and integration depth is locked into large-enterprise Word/AEM/Oxygen author workflows with seat-priced terminology-governance contracts; re-targeting the Git/MDX/PR-diff surface where SaaS-startup DevRel teams actually work would cannibalize its enterprise author-seat pricing and require rebuilding its CMS-plugin integration catalog into a code-review integration (integration-depth)."},{"name":"Writer.com (enterprise Writer)","category":"AI-native horizontal","uncopyabilityReason":"Writer is a horizontal enterprise-content platform optimized for marketing/comms teams buying through a CMO; it lacks the developer-identity graph (GitHub App, CODEOWNERS, branch-protection hooks) and the MDX/RST/code-fenced-sample parsing a dev-docs gate needs, and its GTM channel is tuned to comms/legal procurement rather than the VP-Engineering budget line (distribution-channel)."},{"name":"Grammarly Business","category":"AI-native horizontal","uncopyabilityReason":"Grammarly's corpus and model are trained for generic business English and operate as a browser/IDE overlay on individual authors — it has no house-style DSL, no PR-diff review primitive, and no per-org terminology governance trained on the customer's docs monorepo; catching up would require a vertical-docs training corpus and a CI-native deployment mode neither of which its consumer-freemium funnel funds (vertical-data-corpus)."}]},"studioThesis":"T-DEV-INFRA","killThreshold":{"K":9,"M":40,"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":"Integration surface (author-side IDE/browser overlay ↔ PR-diff gate inside GitHub branch-protection)","yAxis":"Style-rule authority (generic English heuristics ↔ customer-owned house-style DSL with per-rule override ledger)","winningQuadrant":"PR-diff gate running the customer's own house-style DSL, producing a signed override ledger the technical editor endorses in-line","loservilleEscape":true,"loservilleQuadrant":"Author-side overlay firing generic English suggestions with no record of which rule fired or who cleared the merge — Grammarly Business's documented failure mode when a DevRel lead tries to enforce company-specific terminology across a 40-engineer docs monorepo."}},"unmetRequirements":[],"pricingArchitecture":"custom-quote","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aeditors-copy-editing-style-alignment%3At-dev-infra%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aeditors-manuscript-developmental-editing%3At-dev-infra%3Av1","id":"fh:editors-manuscript-developmental-editing:t-dev-infra:v1","lens":"AgenticWorkflow","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/editors-manuscript-developmental-editing","stableHash":"wcc:editors:manuscript-developmental-editing:pure-info:v1"},"problem":{"slotStatement":"Between rubric revisions the house structural guide drifts — an editor finishes a 90k-word manuscript using last quarter's 'three-act pacing' rules, the managing editor spot-checks the report against the current rubric, finds two or three rules were applied from a superseded version, and the entire developmental letter gets kicked back for a rework pass that costs 6-10 unbilled hours per manuscript and delays the author delivery by a week."},"approach":{"oneSentence":"A house-rubric versioning layer that pins every structural note an editor writes to the exact rubric revision in force on the read-date, flags any note whose underlying rule has since been superseded, and produces a developmental letter the managing editor can sign off on without rerunning the manuscript against the current guide."},"customer":{"icpShape":"Owner-operator or managing editor at a bootstrap developmental-editing agency (targetCompanyType: company-type-bootstrap-agency), typically a 4-20 person shop handling 30-80 manuscripts a year for indie authors and small-press imprints, where the buyer is the Agency Owner/Managing Editor who signs the tooling contract and the daily user is the lead developmental editor running chapter-by-chapter structural passes.","beachheadShape":"EarlyAdopterJTBD: bootstrap developmental-editing agencies whose house style guide and structural rubric have drifted across the last 2-3 revisions, causing editors to apply stale 'chapter-hook' or 'POV-consistency' rules that contradict the current client-facing rubric."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-UsageMetered","beachhead":"EarlyAdopterJTBD: bootstrap developmental-editing agencies whose house style guide and structural rubric have drifted across the last 2-3 revisions, causing editors to apply stale 'chapter-hook' or 'POV-consistency' rules that contradict the current client-facing rubric.","competitors":{"substitutes":[{"name":"AR specialist pattern — manual email/Drive/CRM evidence hunt","category":"manual-bridge","uncopyabilityReason":"Informal workflow, not a product; surfaced here per the bridges block but carries no uncopyability story."},{"name":"Editors working from a shared Google Doc rubric + Track Changes in Word","category":"informal"},{"name":"PerfectIt (with custom house style sheets)","category":"incumbent","uncopyabilityReason":"PerfectIt is built as a copy-edit consistency checker whose style-sheet model assumes flat, additive rule lists — its integration depth stops at the Word/Mac add-in surface and it has no versioned rubric graph or revision-diff primitive, so retrofitting rubric-version pinning would require rebuilding the style-sheet engine and the add-in's local-only deployment story (integration-depth barrier)."},{"name":"Sudowrite / AutoCrit (AI-native manuscript feedback)","category":"AI-native horizontal","uncopyabilityReason":"These tools are author-facing self-serve SaaS priced at $20-40/month consumer seats; serving a bootstrap agency's versioned house rubric requires a per-agency custom corpus and editor-audit workflow that collides with their consumer deployment mode and unit economics (deployment-mode-mismatch barrier)."},{"name":"Reedsy Editor + marketplace workflow","category":"incumbent","uncopyabilityReason":"Reedsy's distribution moat is the two-sided author↔freelancer marketplace; shipping a house-rubric version layer would cannibalize their neutral-platform positioning and require onboarding agency-level rubric data they have deliberately avoided collecting to keep the marketplace freelancer-led (distribution-channel barrier)."}]},"studioThesis":"T-DEV-INFRA","killThreshold":{"K":11,"M":35,"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":"Rule-state reconcile cadence (rubric frozen at project kickoff ↔ every note pinned to its rubric-revision-of-record with drift flagged on re-open)","yAxis":"Customization depth of the house guide (vendor-canned style presets ↔ agency-authored rubric DSL the managing editor edits directly)","winningQuadrant":"Agency-authored rubric DSL with per-note revision pinning and automatic drift flags when the guide changes mid-project","loservilleEscape":true,"loservilleQuadrant":"Vendor-canned style presets frozen at kickoff — the failure mode PerfectIt exhibits when a house 'POV-consistency' rule is revised mid-manuscript and prior notes silently go stale, forcing the managing editor's rework loop"}},"unmetRequirements":[],"pricingArchitecture":"custom-quote","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aeditors-manuscript-developmental-editing%3At-dev-infra%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afilm-and-video-editors-color-grade-session%3At-bu%3Av1","id":"fh:film-and-video-editors-color-grade-session:t-bu:v1","lens":"CoPilot","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/film-and-video-editors-color-grade-session","stableHash":"wcc:film-and-video-editors:color-grade-session:multimodal:v1"},"problem":{"slotStatement":"After every brand-guide refresh or FERC/PUC safety-messaging amendment, the colorist's saved look LUTs, node trees, and on-screen-legal-text overlays silently drift from the current approved standard — the editor grades from last quarter's show LUT, ships the storm-safety spot, and the co-op's comms VP later discovers the disclosure color, logo safe-area, or hazard-band treatment violated the amended guide, triggering an internal audit finding and a full regrade of weeks of delivered spots."},"approach":{"oneSentence":"Every color-grade session opens against a live, versioned brand-and-regulatory standards pack (show LUTs, logo safe-area, hazard-band chroma, legal-text legibility floors, current PUC/FERC disclosure amendments) that the session continuously diffs the project timeline against — flagging any node, LUT, or title that was authored under a superseded amendment and leaving a per-shot traceable record the comms VP can hand to internal audit."},"customer":{"icpShape":"Post-production and color-science leads at member-owned electric cooperatives (CompanyType/company-type-member-owned-electric-cooperative) running in-house broadcast/comms studios that produce member-facing safety videos, storm-response PSAs, and board-meeting recap reels — where the buyer is the VP of Member Communications (or Director of Corporate Communications) who signs the annual creative-tech budget and the daily user is the staff colorist/finishing editor driving DaVinci Resolve or Baselight sessions.","beachheadShape":"EarlyMajorityWorkflow: in-house comms studios at Touchstone/NRECA-aligned electric co-ops (150k–400k meters) that publish regulated-content videos monthly and have been dinged on brand-guide or safety-disclosure drift."},"archetype":"startup-archetypes.org.ai/CoPilot-Subscription","beachhead":"EarlyMajorityWorkflow: in-house comms studios at Touchstone/NRECA-aligned electric co-ops (150k–400k meters) that publish regulated-content videos monthly and have been dinged on brand-guide or safety-disclosure drift.","competitors":{"substitutes":[{"name":"Manual email + Google Drive + DaVinci Resolve project-notes search for the current brand guide","category":"manual-bridge","uncopyabilityReason":"Informal workflow — no product to out-build; this is the friction we displace."},{"name":"Colorfront Transkoder / On-Set Dailies with Frame.io review links","category":"incumbent","uncopyabilityReason":"Colorfront's business is high-end episodic/feature dailies with a seat-license + support-contract channel aimed at Netflix/Disney finishing houses; shipping a co-op-specific regulatory-amendment tracker would require a vertical-data-corpus (FERC/PUC/NRECA brand-pack ingestion pipeline) they have no relationship to license or maintain, and it is orthogonal to the codec-pipeline R&D that drives their roadmap."},{"name":"Blackmagic DaVinci Resolve Studio with Shared Project Server + built-in version history","category":"incumbent","uncopyabilityReason":"Blackmagic's deployment-mode is a perpetual-license creative tool sold into a horizontal colorist market; surfacing amendment-scoped divergence against an external regulatory standards pack requires an integration-depth (authoritative brand/regulatory feeds, per-node provenance API, audit export) that would fork their single-SKU product and contradict their all-things-to-all-editors positioning."},{"name":"IntelligentBank or Papersave BrandHub used by co-op marketing for brand-asset governance","category":"adjacent vertical","uncopyabilityReason":"BrandHub-class DAMs govern static asset approval (PDFs, logos, photos) via a librarian-review workflow; they have no hook into the colorist's node graph or LUT stack, and retrofitting one requires a liability-posture shift (attesting that a delivered video conformed to an amendment at grade-time) that their approval-ticket model was never underwritten for."},{"name":"Monday.com / Airtable brand-compliance checklist filled in by the producer post-delivery","category":"informal"}]},"studioThesis":"T-BU","killThreshold":{"K":10,"M":70,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Drift-detection cadence (post-delivery spot-check by producer ↔ continuous diff against live amendment feed during the grade session)","yAxis":"Regulatory-standards-pack fit (generic creative brand guide ↔ co-op-specific FERC/PUC/NRECA amendment corpus pre-bundled)","winningQuadrant":"Continuous in-session divergence detection against a co-op-specific regulatory standards pack, so the colorist sees 'this node was authored under the superseded Nov-2023 hazard-band spec' before render","loservilleEscape":true,"loservilleQuadrant":"Post-delivery producer checklist against a generic brand PDF — the pattern Monday.com/Airtable and Resolve's own version history currently exhibit, where missed amendments surface only when internal audit pulls the file months later"}},"unmetRequirements":[],"pricingArchitecture":"custom-quote","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afilm-and-video-editors-color-grade-session%3At-bu%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afilm-and-video-editors-vfx-comp-review%3At-low%3Av1","id":"fh:film-and-video-editors-vfx-comp-review:t-low:v1","lens":"CoPilot","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/film-and-video-editors-vfx-comp-review","stableHash":"wcc:film-and-video-editors:vfx-comp-review:multimodal:v1"},"problem":{"slotStatement":"When a showrunner rejects a hero shot at final-delivery review and asks 'why did this note from turnover v03 not get addressed,' the VFX Sup cannot reconstruct which client note was dispositioned, by whom, against which plate version, because approval state lives scattered across Frame.io comments, ShotGrid Notes, Zoom transcripts, and Slack DMs — leaving the studio exposed on overage invoices and vendor-package audits."},"approach":{"oneSentence":"Sitting behind ShotGrid and Frame.io, a shot-disposition ledger watches every comp iteration, client annotation, and supervisor decision, then certifies each approval with the plate-hash, note-author, and version lineage a producer can pull up during a delivery dispute."},"customer":{"icpShape":"Boutique VFX and post-production studios (company-type-solo-dental-practice class: owner-operator shops of 8-40 comp artists servicing episodic TV and streaming shows), where the buyer is the VFX Executive Producer or Head of Studio who signs the vendor MSA and the daily user is the VFX Supervisor / Lead Compositor driving dailies and client review sessions in Nuke and ShotGrid.","beachheadShape":"EarlyAdopterJTBD: boutique episodic-TV VFX shops delivering 40-120 shots per episode on SVOD schedules where client-side approval notes arrive via Frame.io, email, and Zoom recordings with no unified approval ledger."},"archetype":"startup-archetypes.org.ai/CoPilot-Subscription","beachhead":"EarlyAdopterJTBD: boutique episodic-TV VFX shops delivering 40-120 shots per episode on SVOD schedules where client-side approval notes arrive via Frame.io, email, and Zoom recordings with no unified approval ledger.","competitors":{"substitutes":[{"name":"Autodesk Flow (ShotGrid) Review + Notes","category":"incumbent","uncopyabilityReason":"ShotGrid's Notes and Review modules treat annotations as free-text records tied to a Version entity, not as dispositioned decisions with plate-hash lineage; shipping a genuine approval ledger would require Autodesk to re-architect the Version/Note schema that the entire ShotGrid customer base and all third-party pipeline tools (Shotgun Toolkit, tk-multi-publish2) depend on — integration-depth lock-in with their own ecosystem prevents a clean cut."},{"name":"Frame.io (Adobe) C2C + Review","category":"incumbent","uncopyabilityReason":"Frame.io's business is Camera-to-Cloud capture and web review for editorial, not VFX shot state reconciliation — it has no awareness of Nuke scripts, render passes, or plate versions, and Adobe's distribution-channel is Creative Cloud seat bundling to editors, not studio-bid VFX pipelines. Rebuilding a comp-aware approval lineage would cannibalize their editor-first positioning and require data-corpus access to VFX pipeline metadata they do not collect."},{"name":"ftrack Review","category":"incumbent","uncopyabilityReason":"ftrack is deployed as a multi-tenant SaaS review tool optimized for animation/VFX project tracking, but its approval records are statuses on Version entities, not cryptographically linked dispositions across plate+comp+note triplets. Shipping the winning quadrant requires on-prem-adjacent deployment inside the studio's Perforce/SAN perimeter — a deployment-mode mismatch with ftrack's cloud-only architecture."},{"name":"Per-show Google Drive / SMB share as approval binder","category":"manual-bridge"},{"name":"Producer emailing Zoom recording + PDF of Frame.io notes to client","category":"informal"}]},"studioThesis":"T-LOW","killThreshold":{"K":8,"M":65,"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":"Pipeline integration depth (web-review overlay only ↔ bound to Nuke scripts, plate hashes, and ShotGrid Versions)","yAxis":"Approval object model (free-text note on a Version ↔ dispositioned decision linking note-author + plate-hash + comp-iteration)","winningQuadrant":"Decisions bound to plate-hash + comp-iteration lineage, wired into the Nuke/ShotGrid pipeline the studio already runs, so any producer can answer 'which note, which version, who approved' in under 30 seconds during a delivery dispute","loservilleEscape":true,"loservilleQuadrant":"Frame.io-style free-text web annotations sitting on top of an MP4 proxy with no linkage to the underlying Nuke script or plate version — exactly where a showrunner's v03 note gets lost between turnovers"}},"unmetRequirements":[],"pricingArchitecture":"single-price","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afilm-and-video-editors-vfx-comp-review%3At-low%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afinancial-and-investment-analysts-earnings-call-model-update%3At-ais-prem%3Av1","id":"fh:financial-and-investment-analysts-earnings-call-model-update:t-ais-prem:v1","lens":"HeadlessSaaS","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"C7_magicLensFit":0,"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/financial-and-investment-analysts-earnings-call-model-update","stableHash":"wcc:financial-and-investment-analysts:earnings-call-model-update:multimodal:v1"},"problem":{"slotStatement":"During the 60-minute earnings call plus Q&A, the senior analyst is the single queue-serializer for reconciling guidance deltas, segment reclasses, and one-off charges against the working model — associates can transcribe but cannot judge which disclosures actually move the estimate, so the analyst burns the first-note window re-doing associate math instead of shaping the call back to clients."},"approach":{"oneSentence":"Earnings-call copilot that listens to the live audio, maps each management statement to the specific driver cell it would revise in the analyst's existing Excel model, and routes every proposed revision through the analyst's own published estimate rubric so the first-look note carries a line-by-line review-ready trail back to the timestamped call quote."},"customer":{"icpShape":"Sell-side equity research desks at boutique and mid-tier investment banks (CompanyType/company-type-solo-dental-practice archetype — a single senior covering analyst running a lean pod of 2-3 associates), where the buyer is the Director of Research (or Head of Equity Research) who controls the research-tech budget and the daily user is the covering Senior Equity Analyst updating the model during the live call.","beachheadShape":"EarlyAdopterJTBD: senior sell-side analysts covering 12-18 names in volatile sectors (semis, biotech, SaaS) who publish a first-look revision note within 45 minutes of the call hanging up."},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-OutcomeBased","beachhead":"EarlyAdopterJTBD: senior sell-side analysts covering 12-18 names in volatile sectors (semis, biotech, SaaS) who publish a first-look revision note within 45 minutes of the call hanging up.","competitors":{"substitutes":[{"name":"One senior analyst hand-updating the model during Q&A while an associate scribes","category":"informal","uncopyabilityReason":""},{"name":"The covering analyst as human queue-serializer for all judgment calls","category":"manual-bridge","uncopyabilityReason":""},{"name":"Visible Alpha / Street Account consensus feeds","category":"incumbent","uncopyabilityReason":"Visible Alpha's moat is contributor-consensus aggregation across the sell-side — its revenue model REQUIRES that each analyst still runs their own private model and uploads estimates; a product that revises the analyst's private model in-place during the call cannibalizes the very contribution flow Visible Alpha monetizes (distribution-channel barrier), and rebuilding around private-model embedding would require renegotiating contributor contracts across the whole sell-side."},{"name":"AlphaSense / Sentieo earnings-call transcript + summarization","category":"incumbent","uncopyabilityReason":"AlphaSense is architected as a cross-document search-and-summary index over a curated corpus (transcripts, filings, broker research); it has no integration depth into the analyst's proprietary Excel driver sheet and no write-path into model cells. Closing that gap requires a per-analyst model-ingestion and cell-mapping layer that is orthogonal to their search-index core — an integration-depth barrier that would force a second product line, not a feature."},{"name":"Bloomberg Terminal EQRV / ANR earnings tooling with BQuant scripting","category":"incumbent","uncopyabilityReason":"Bloomberg's leverage comes from the Terminal's walled distribution and its refusal to run customer-authored models outside BQuant's sandbox; a live-call revision copilot that modifies an analyst's off-Terminal Excel workbook is a deployment-mode mismatch with the Terminal's hosted-notebook posture, and Bloomberg's liability posture on data redistribution prevents it from writing into customer-owned spreadsheets that might later be sent to clients."},{"name":"Hebbia / generalist financial-LLM copilots","category":"AI-native horizontal","uncopyabilityReason":"Hebbia-class tools are horizontal document-QA engines trained on filings and transcripts broadly; they lack the vertical-data corpus of historical estimate-rubric mappings (which guidance phrasings actually moved which analyst's driver cells across prior quarters) that is required to propose a revision the analyst will accept without re-checking — a vertical-data-corpus barrier that compounds quarter-over-quarter per customer."}]},"studioThesis":"T-AIS-PREM","killThreshold":{"K":11,"M":80,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Write-path into the analyst's private model (read-only transcript summary ↔ cell-level revision proposals against the analyst's own Excel driver sheet)","yAxis":"Judgment qualification (generic LLM opinion on materiality ↔ revisions gated by the analyst's own published estimate rubric with per-line quote timestamps)","winningQuadrant":"Cell-level revision proposals written against the analyst's Excel model, each gated by that analyst's own rubric and carrying a timestamped call-quote trail the Director of Research can sign off before the first-look note goes out","loservilleEscape":true,"loservilleQuadrant":"Read-only transcript summarization with generic LLM materiality opinions — where AlphaSense drops a bulleted call summary into a side panel while the analyst still hand-keys every driver-cell change and guesses which comments crossed the rubric threshold"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afinancial-and-investment-analysts-earnings-call-model-update%3At-ais-prem%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afinancial-and-investment-analysts-earnings-call-model-update%3At-hsa%3Av1","id":"fh:financial-and-investment-analysts-earnings-call-model-update:t-hsa:v1","lens":"HeadlessSaaS","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"C7_magicLensFit":0,"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/financial-and-investment-analysts-earnings-call-model-update","stableHash":"wcc:financial-and-investment-analysts:earnings-call-model-update:multimodal:v1"},"problem":{"slotStatement":"During a utility earnings call the analyst nudges a dozen assumptions — authorized ROE, rate-case timing, capex escalator, weather-normalized load, FFO/debt — and by the time the flash note goes out at 4:30pm nobody can point to which sentence in the transcript, which slide in the deck, or which Q&A exchange actually drove each estimate change, so when the PM or compliance challenges the revision the next morning the analyst loses the dispute and the call is memory-holed into a shared drive folder."},"approach":{"oneSentence":"A rate-case-aware model-update copilot that watches the live earnings-call audio alongside the analyst's open DCF, proposes specific cell-level revisions to ROE, capex, and load assumptions, and binds each proposed change to the exact transcript timestamp, slide, and prior-period filing that justifies it so the flash note ships with a reviewer-ready trail back to primary utility disclosures."},"customer":{"icpShape":"Sell-side and buy-side equity research desks covering regulated electric and gas utilities (CompanyType/company-type-public-utility coverage universe), at $2B–$50B AUM asset managers and top-20 sell-side research shops, where the buyer is the Director of Research (or Head of Equity Research) who signs the data/tooling PO and the daily users are the utility-sector Senior Equity Analyst and their 1–2 associates maintaining the rate-base DCF model during earnings calls.","beachheadShape":"EarlyAdopterJTBD: utility-sector analysts who revise EPS/rate-base estimates live during the 60-minute earnings call window and must publish a same-day flash note defending each estimate change to PMs and compliance."},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-Subscription","beachhead":"EarlyAdopterJTBD: utility-sector analysts who revise EPS/rate-base estimates live during the 60-minute earnings call window and must publish a same-day flash note defending each estimate change to PMs and compliance.","competitors":{"substitutes":[{"name":"Shared network drive / Google Drive call binder","category":"manual-bridge","uncopyabilityReason":"Informal practice — no product to copy; it is the status quo the wedge replaces."},{"name":"Bloomberg Terminal (TRAN transcripts + MODL)","category":"incumbent","uncopyabilityReason":"Bloomberg's distribution-channel moat runs the other way here: its business is terminal-seat rent plus neutral data, so it structurally will not ship a tool that writes into the analyst's proprietary utility DCF and takes a position on ROE — doing so would expose Bloomberg to research-liability posture its data-vendor contracts explicitly disclaim, and rebuilding that liability shield inside 6 months is not feasible."},{"name":"AlphaSense / Sentieo (Tegus) earnings-call search","category":"incumbent","uncopyabilityReason":"Integration-depth barrier: AlphaSense is architected as a read-only search/summarization layer over transcripts and filings with no write-path into the analyst's Excel rate-base model. Adding bidirectional cell-level writes into per-firm proprietary DCF templates means reverse-engineering each desk's utility model conventions (FERC Form 1 line-items, decoupling mechanisms, storm-rider trackers) — a vertical-data-corpus lift they have not made and cannot compress into a 6-month roadmap."},{"name":"Visible Alpha / UBS Evidence Lab consensus tools","category":"incumbent","uncopyabilityReason":"Deployment-mode mismatch: Visible Alpha's value comes from normalizing line-items ACROSS contributing sell-side models into a consensus grid — it is intentionally a cross-firm aggregation layer, not an intra-call single-analyst workbench. Flipping to a live per-analyst assistant that edits one firm's proprietary model would collide with the contributor-anonymity contracts that underpin the consensus product."},{"name":"Generalist AI meeting-notetakers (Otter, Fireflies, Read.ai)","category":"AI-native horizontal","uncopyabilityReason":"Vertical-data-corpus gap: these tools transcribe and summarize generically but have no representation of a utility rate-base DCF, no mapping from phrases like 'constructive order in the Ohio rate case' to specific model cells, and no FERC/state-PUC docket corpus. Acquiring the utility-regulatory vocabulary and the per-desk model-template library is a multi-year data build, not a prompt tweak."}]},"studioThesis":"T-HSA","killThreshold":{"K":11,"M":80,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Model-write authority (read-only transcript search ↔ writes proposed cell-level edits into the analyst's live DCF)","yAxis":"Vertical regulatory fit (generic earnings-call NLP ↔ utility-specific: rate-case dockets, FERC Form 1 line-items, decoupling/tracker mechanics pre-baked)","winningQuadrant":"Writes cell-level edits into the utility analyst's open rate-base DCF with every proposed change anchored to the specific transcript moment, slide, and FERC/PUC filing that justifies it — inside the 60-minute call window.","loservilleEscape":true,"loservilleQuadrant":"Read-only generic transcript summarizer (Otter/Fireflies-style) that produces a bullet-list recap the analyst must manually retype into the DCF, losing the provenance link between each model nudge and the utterance that caused it."}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afinancial-and-investment-analysts-earnings-call-model-update%3At-hsa%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afinancial-and-investment-analysts-equity-research-note%3At-bu%3Av1","id":"fh:financial-and-investment-analysts-equity-research-note:t-bu:v1","lens":"HeadlessSaaS","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"C7_magicLensFit":0,"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/financial-and-investment-analysts-equity-research-note","stableHash":"wcc:financial-and-investment-analysts:equity-research-note:document:v1"},"problem":{"slotStatement":"Between the 10-Q drop and the note deadline, the analyst's segment build silently drifts against the latest SEC/FASB/IFRS amendment or the issuer's revised segment taxonomy — the rework loop hits when a portfolio manager spots a reclassified line item on the morning call and the whole estimate sheet has to be unwound and re-tied, usually after the note has already been published to clients."},"approach":{"oneSentence":"Engagement-letter-bound reconciliation that watches every filing, standard-setter release, and issuer 8-K against the analyst's live model, flags the exact cells whose basis has shifted since the last note, and certifies a per-note change-log the Director of Research can defend to compliance."},"customer":{"icpShape":"Sell-side equity research shops and boutique buy-side funds operating as solo-analyst coverage practices (CompanyType/company-type-solo-dental-practice pattern — single senior analyst covering 8-15 tickers) where the buyer is the Director of Research (signs the data/tooling PO out of the research budget) and the daily user is the sector-lead Equity Analyst maintaining the earnings model and note.","beachheadShape":"EarlyAdopterJTBD: solo-coverage sector analysts at sub-$2B AUM boutiques covering regulated sectors (utilities, banks, insurers) where rule-pack amendments between quarters routinely break prior-period comparability"},"archetype":"startup-archetypes.org.ai/HeadlessSaaS-MarketplaceClearing","beachhead":"EarlyAdopterJTBD: solo-coverage sector analysts at sub-$2B AUM boutiques covering regulated sectors (utilities, banks, insurers) where rule-pack amendments between quarters routinely break prior-period comparability","competitors":{"substitutes":[{"name":"Outside counsel / accounting-advisory quarterly rule-pack diff","category":"informal"},{"name":"Analyst-maintained Excel model plus FactSet/Bloomberg terminal copy-paste","category":"manual-bridge"},{"name":"Visible Alpha (consensus + model-hosting platform)","category":"incumbent","uncopyabilityReason":"Visible Alpha's business model is a contributed-estimates consensus network — its value to sell-side contributors is normalized line-item comparability ACROSS analysts, which structurally prevents it from flagging per-analyst drift against standard-setter amendments, because doing so would expose which contributors missed the amendment and destroy contribution rates. The barrier is distribution-channel: the contributor network IS the product."},{"name":"Bloomberg Terminal MODL / Research Management (RMS)","category":"incumbent","uncopyabilityReason":"Bloomberg's deployment mode is a fat-client terminal with read-only feeds into analyst spreadsheets; rule-pack reconciliation requires two-way write-back into the analyst's proprietary model schema, which Bloomberg has refused for 20 years because opening the terminal write-boundary would fragment its data-licensing contracts. The barrier is deployment-mode-mismatch."},{"name":"AlphaSense / Tegus Expert (AI research copilot)","category":"AI-native horizontal","uncopyabilityReason":"AlphaSense indexes public filings and transcripts as a retrieval layer, not a model-state engine — it has no representation of the analyst's actual earnings build, segment tree, or prior-period basis, so it cannot detect that a given line's basis has drifted. Building that would require integration-depth into each analyst's Excel model and an engagement-letter legal posture AlphaSense's self-serve SaaS contract explicitly disclaims."}]},"studioThesis":"T-BU","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Drift-detection surface (static filings search ↔ live reconciliation against the analyst's own model cells)","yAxis":"Authority boundary (advisory suggestion the analyst must re-verify ↔ Director-of-Research-signed change-log admissible to compliance review)","winningQuadrant":"Live model-cell reconciliation with a signed per-note change-log the Director of Research can hand to compliance without re-verification","loservilleEscape":true,"loservilleQuadrant":"Static filing-search suggestions the analyst must manually re-tie — where AlphaSense lives today: it surfaces that an amendment exists but cannot tell the analyst that row 47 of the segment build is the cell whose basis broke, leaving the rework loop fully on the analyst."}},"unmetRequirements":[],"pricingArchitecture":"custom-quote","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afinancial-and-investment-analysts-equity-research-note%3At-bu%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afinancial-and-investment-analysts-equity-research-note%3At-low%3Av1","id":"fh:financial-and-investment-analysts-equity-research-note:t-low:v1","lens":"AIService","type":"founding-hypothesis","click":{"rubricScores":{"C8_lensFit":0,"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/financial-and-investment-analysts-equity-research-note","stableHash":"wcc:financial-and-investment-analysts:equity-research-note:document:v1"},"problem":{"slotStatement":"After every PUC rate-order or 10-Q drop, the utilities analyst rebuilds the earnings model from PDF testimony and test-year tables into Excel, and the quiet-period clock forces a publish — so rate-base adjustments, allowed-ROE shifts, and regulatory-asset amortization deltas get silently written off into the estimate without a line-item trail back to the docket page, and when the note misses consensus the desk eats the dispute with portfolio managers who ask 'where did the 40bps come from' and nobody on the team can reconstruct it."},"approach":{"oneSentence":"Docket-to-model reconciliation that watches state PUC filings, 10-Qs, and FERC Form-1 dumps for a covered utility, re-derives each rate-base and ROE line against the analyst's published estimate, and escalates any divergence above a desk-set threshold with a line-level trace back to the testimony page — so the analyst can defend every bps of the EPS delta in the PM meeting."},"customer":{"icpShape":"Director of Equity Research (buyer who signs the PO) at a sell-side equity research desk or buy-side analyst shop covering company-type-public-utility names (regulated electrics, gas LDCs, water utilities), where the daily user is the sector analyst or associate publishing earnings-estimate updates and rate-case-driven notes — specifically the format: where the buyer is the Director of Research (or Head of Research Operations) and the daily user is the covering Equity Analyst / Associate.","beachheadShape":"EarlyMajorityWorkflow: sell-side utilities-sector research desks (10-40 analyst teams) publishing quarterly earnings-update notes on 15-60 regulated utility tickers under MiFID II unbundled research budgets"},"archetype":"startup-archetypes.org.ai/AIService-UsageMetered","beachhead":"EarlyMajorityWorkflow: sell-side utilities-sector research desks (10-40 analyst teams) publishing quarterly earnings-update notes on 15-60 regulated utility tickers under MiFID II unbundled research budgets","competitors":{"substitutes":[{"name":"Ironclad-style legal-ops contract repositories repurposed for docket storage","category":"manual-bridge","uncopyabilityReason":"Not a product category competition — it's the practice of dumping PUC PDFs into a lawyer-oriented repo that has no estimate-reconciliation workflow."},{"name":"Analyst-maintained Excel model + Bloomberg/FactSet + manual PUC PDF read","category":"informal"},{"name":"Visible Alpha (consensus estimate + model-line contribution platform)","category":"incumbent","uncopyabilityReason":"Visible Alpha's moat is its contributor-network of sell-side model line items — its revenue model depends on analysts uploading finished models, not on re-deriving lines from regulatory primary sources. Shipping a docket-grounded reconciliation engine would require a vertical-data-corpus (state-by-state PUC testimony, FERC Form-1 history, rate-case procedural calendars) they do not own and cannot licence without rebuilding their contributor contracts."},{"name":"AlphaSense (document search + summarization across filings and broker research)","category":"incumbent","uncopyabilityReason":"AlphaSense is an integration-depth mismatch: it indexes documents for retrieval and summarization but does not write back into the analyst's Excel estimate model or carry a line-level numeric reconciliation against a specific EPS build. Closing that gap requires deep Excel/model-DSL integration depth (range-level bindings into analyst-authored workbooks) that conflicts with their read-only search UX and would force a rebuild of their enterprise-search product surface."},{"name":"Bloomberg Terminal MODL / BI<GO> utility sector functions","category":"incumbent","uncopyabilityReason":"Bloomberg's distribution-channel moat (the $28k/seat terminal bundle) is also its constraint — sector-specific deterministic reconciliation tooling cannot be shipped as a narrow utilities-only add-on without cannibalizing the generalist-terminal value prop, and the terminal's closed deployment-mode (proprietary terminal runtime, no on-desk Excel agent) blocks the line-level model-write-back pattern this workflow requires."},{"name":"Hebbia / Rogo (AI-native horizontal analyst copilots)","category":"AI-native horizontal","uncopyabilityReason":"Horizontal analyst copilots face a vertical-data-corpus gap: they are trained/indexed on generic SEC filings and earnings transcripts, not on the 50-state patchwork of PUC docket formats, test-year conventions, and rate-case procedural schedules that drive utility EPS. Building that corpus and the state-by-state regulatory-accounting logic (CWIP, trackers, decoupling mechanisms) is a multi-year vertical buildout that breaks their horizontal positioning."}]},"studioThesis":"T-LOW","killThreshold":{"K":8,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Divergence detection cadence (analyst re-reads PDF at quarter-end ↔ continuous docket-watch with per-line delta alerts)","yAxis":"Integration depth into the analyst's estimate model (read-only summary sidebar ↔ round-trip writes into the published Excel/DSL model with line-level trace)","winningQuadrant":"Continuous PUC-docket watch that round-trips deltas into the analyst's actual earnings model with a per-line docket-page trace, so silent write-offs surface before publish","loservilleEscape":true,"loservilleQuadrant":"Quarter-end manual PDF re-read surfaced as a read-only chat summary — the failure mode AlphaSense and horizontal copilots like Hebbia exhibit today, where the analyst still hand-keys the delta into Excel and the docket citation never binds to the model line"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afinancial-and-investment-analysts-equity-research-note%3At-low%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afinancial-and-investment-analysts-sector-initiation-report%3At-ais-prem%3Av1","id":"fh:financial-and-investment-analysts-sector-initiation-report:t-ais-prem:v1","lens":"ManagedWorkflow","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/financial-and-investment-analysts-sector-initiation-report","stableHash":"wcc:financial-and-investment-analysts:sector-initiation-report:document:v1"},"problem":{"slotStatement":"Every sector initiation stalls on the same chokepoint: the one senior analyst who actually knows the sub-industry must personally vet the peer set, normalize the comparable-company adjustments, and sign off on the multiple framework — so junior analysts sit idle for days waiting for 30-minute reviews, and a 6-week initiation routinely stretches to 10 weeks because expert calendar time is the binding constraint, not drafting capacity."},"approach":{"oneSentence":"Sector-initiation workbench that captures the senior analyst's comp-selection and adjustment judgments once as a reusable rubric, then lets juniors investigate, normalize, and assemble the comparable-valuation section against that rubric — surfacing only the specific disagreements that require the expert's 10 minutes, with every peer-inclusion and adjustment decision carrying a review-ready justification back to the source filing."},"customer":{"icpShape":"Director of Equity Research (the budget-holder who signs the platform PO) at a mid-sized sell-side boutique or independent research shop (50-300 analysts) initiating coverage on a new sector, where the buyer is the Director of Research and the daily user is the junior sector analyst drafting the initiation report; firmographically anchored to CompanyType/company-type-pe-backed-dso-equivalent research shops under PE or partner ownership where coverage-launch velocity drives franchise economics.","beachheadShape":"EarlyAdopterJTBD: sell-side boutiques launching coverage on a net-new GICS sub-industry within the next 90 days, where the senior analyst is the single expert bottleneck for every comp-set decision."},"archetype":"startup-archetypes.org.ai/ManagedWorkflow-Subscription","beachhead":"EarlyAdopterJTBD: sell-side boutiques launching coverage on a net-new GICS sub-industry within the next 90 days, where the senior analyst is the single expert bottleneck for every comp-set decision.","competitors":{"substitutes":[{"name":"Manual senior-analyst review cycles in Excel + FactSet","category":"manual-bridge"},{"name":"FactSet Research Management Solutions (RMS) + Workstation","category":"incumbent","uncopyabilityReason":"FactSet's integration depth is its moat and its cage: RMS is architected around analyst-authored notes flowing into a closed publishing pipeline, and the comp-set logic is hand-curated inside the Workstation's canned screeners. Rebuilding the product around a captured-expert-rubric layer that juniors execute independently would require rewriting the authorship model the entire sell-side publishing workflow depends on — a 2-3 year integration-depth rebuild, not a 6-month feature."},{"name":"Bloomberg Terminal RV/EQS + BQuant","category":"incumbent","uncopyabilityReason":"Bloomberg's distribution-channel lock-in — $25k/seat/year bundled across trading, news, and chat — means the Terminal is sold horizontally to every desk; a sector-specific initiation workflow that captures one senior analyst's judgment cannot be surfaced without fragmenting the universal-terminal product narrative that drives 325k seat renewals. The channel economics actively prevent a vertical wedge."},{"name":"AlphaSense Enterprise Intelligence + Generative Search","category":"AI-native horizontal","uncopyabilityReason":"AlphaSense is positioned as a horizontal search-and-summarize layer over filings and transcripts; its liability-posture is explicitly 'assistive, analyst-verified,' and its contracts disclaim authoring decisions. Shipping a workbench where a captured rubric is the decision-making artifact (not the human) would require it to assume authorship liability for comp-set choices — a posture shift its E&O and customer contracts are structured to avoid."},{"name":"Visible Alpha / Canalyst consensus and model libraries","category":"adjacent vertical"}]},"studioThesis":"T-AIS-PREM","killThreshold":{"K":9,"M":40,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Expert-judgment capture (ad-hoc per-report review ↔ rubric persisted across the sector franchise)","yAxis":"Authority boundary (assistive search the analyst must re-verify ↔ rubric-bound decisions the junior can execute and the senior only adjudicates exceptions)","winningQuadrant":"Persisted sector rubric with rubric-bound junior execution — the senior analyst's comp-selection and adjustment logic is captured once and juniors ship initiation sections against it, with expert time reserved for flagged disagreements only","loservilleEscape":true,"loservilleQuadrant":"Ad-hoc review with assistive-only search — exactly AlphaSense's position today: every initiation re-starts the expert review loop from scratch because the tool refuses authorship and the rubric lives only in the senior analyst's head"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afinancial-and-investment-analysts-sector-initiation-report%3At-ais-prem%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afinancial-and-investment-analysts-sector-initiation-report%3At-hsa%3Av1","id":"fh:financial-and-investment-analysts-sector-initiation-report:t-hsa: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/financial-and-investment-analysts-sector-initiation-report","stableHash":"wcc:financial-and-investment-analysts:sector-initiation-report:document:v1"},"problem":{"slotStatement":"Every time a FERC Form 1 update, a state PUC rate order, or a revised allowed-ROE lands, the junior analyst has to chase the new rate-base and capex figures across the Excel comps tab, the DCF, the valuation football-field, and the initiation PDF — and the version that ships to institutional clients routinely cites a rate-base number that no longer matches the model footnote, which turns into a compliance callout from the supervisory analyst during the 15c2-11 pre-publication review."},"approach":{"oneSentence":"Sector-initiation reconciliation that pins every comp-set figure (rate base, allowed ROE, capex plan, authorized capital structure) to the specific FERC Form 1 line or PUC rate-order page it came from, re-runs the reconciliation on every filing update, and flags any number in the draft report whose underlying source has moved since the analyst last touched the cell — giving the supervisory analyst a review-ready diff before 15c2-11 sign-off."},"customer":{"icpShape":"Director of Equity Research (the budget-holder who signs the research-platform PO) at a sell-side boutique or regional broker-dealer covering regulated public utilities (targetCompanyType: company-type-public-utility), where the buyer is the Director of Equity Research and the daily user is the sector analyst drafting the initiation-of-coverage report.","beachheadShape":"EarlyAdopterJTBD: two-to-five-analyst utilities desks at regional sell-side shops launching initiation-of-coverage on IOUs coming off a rate case, where comp-set rate-base and allowed-ROE assumptions drift between the model, the deck, and the published PDF."},"archetype":"startup-archetypes.org.ai/AIService-UsageMetered","beachhead":"EarlyAdopterJTBD: two-to-five-analyst utilities desks at regional sell-side shops launching initiation-of-coverage on IOUs coming off a rate case, where comp-set rate-base and allowed-ROE assumptions drift between the model, the deck, and the published PDF.","competitors":{"substitutes":[{"name":"FactSet Research Management Solutions (RMS) + FactSet Utilities workstation","category":"incumbent","uncopyabilityReason":"FactSet's RMS note-authoring stack is built around analyst-edited Excel linked tables and a PDF publishing pipeline that treats the comp-set tab as the source of truth; to deliver per-figure reconciliation against FERC Form 1 and PUC rate-order pages they would have to rebuild the ingestion side of the product (they license financials from S&P CIQ, not directly from FERC/PUC filings) — that's an integration-depth rebuild across two vendor boundaries, not a feature ship."},{"name":"S&P Capital IQ Pro (Regulatory Research Associates module)","category":"incumbent","uncopyabilityReason":"RRA's value prop is human-curated summaries of state PUC dockets sold as a subscription research feed; their liability posture and editorial workflow require a human analyst to stand behind each datapoint, so they cannot expose page-anchored machine-reconciled figures to a customer's model without changing the indemnity terms of their research contract — a liability-posture barrier, not a tech gap."},{"name":"Bloomberg Terminal BI <GO> utilities function + DES rate-case screens","category":"incumbent","uncopyabilityReason":"Bloomberg's distribution is the Terminal seat; per-seat pricing and the closed Terminal runtime mean they cannot ship a reconciliation agent that writes back into an analyst's local Excel model and PDF draft without undermining the seat-licensing economics and opening the Terminal sandbox — a distribution-channel barrier tied to their ~$30k/seat model."},{"name":"Visible Alpha consensus estimates platform","category":"AI-native horizontal","uncopyabilityReason":"Visible Alpha is a consensus-aggregation network whose moat is the contributed-model corpus from ~180 sell-side shops; its deployment mode is a standardized KPI-tagging schema applied across sectors, which cannot accommodate utility-specific rate-base / authorized-ROE / test-year reconciliation without forking the schema and breaking cross-sector comparability — a deployment-mode-mismatch barrier."},{"name":"Junior-analyst-maintained 'Utilities Comps Master.xlsx' with manual FERC Form 1 copy-paste and a separate rate-case tracker tab","category":"manual-bridge"},{"name":"Outsourced research-support vendors (e.g. Evalueserve, Smartkarma associate pools) doing overnight comp-sheet refresh","category":"human alternative"}]},"studioThesis":"T-HSA","killThreshold":{"K":9,"M":40,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Source-of-truth binding (analyst retypes numbers from filings into Excel ↔ every figure in the draft is page-anchored to the specific FERC Form 1 line or PUC order page)","yAxis":"Drift-detection cadence (one-shot refresh at quarter-end ↔ continuous reconcile that flags stale figures the moment a new filing lands)","winningQuadrant":"Page-anchored per-figure binding with continuous reconcile — when Xcel files an amended Form 1 on a Tuesday, by Wednesday the initiation draft's rate-base footnote is flagged red with a diff against the cited page","loservilleEscape":true,"loservilleQuadrant":"Analyst-retyped numbers refreshed only at quarter-end — the FactSet/CIQ workflow where the comps tab is manually keyed off vendor-normalized financials and no one re-checks the initiation PDF against the underlying FERC filing until the next rate case"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afinancial-and-investment-analysts-sector-initiation-report%3At-hsa%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afinancial-managers-board-financial-presentation%3At-hsa%3Av1","id":"fh:financial-managers-board-financial-presentation:t-hsa:v1","lens":"CoPilot","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/financial-managers-board-financial-presentation","stableHash":"wcc:financial-managers:board-financial-presentation:multimodal:v1"},"problem":{"slotStatement":"Between board meetings the sponsor amends the EBITDA add-back policy, the covenant definition, or the same-practice cohort rule, and the FP&A manager rebuilds the board deck from a stale template that silently carries the prior quarter's rules — the CFO catches the drift during dry-run at T-48h and the team burns a weekend re-running the bridge, the cohort waterfall, and the management-adjustment memo."},"approach":{"oneSentence":"A board-binder engine that, on every deck refresh, diffs the current sponsor policy memo against the numbers baked into each slide, flags every figure whose underlying rule has shifted since the last board cycle, and ships the VP of Finance a review-ready change-log the operating partner can sign off on before the meeting."},"customer":{"icpShape":"VP of Finance at a PE-backed dental service organization (CompanyType/company-type-pe-backed-dso) with 40–120 supported practices and a quarterly board deck obligation to the sponsor's operating partner, where the buyer is the VP of Finance (signs the software PO and owns the month-end close budget) and the daily user is the FP&A Manager who actually builds the board book.","beachheadShape":"EarlyAdopterJTBD: PE-backed DSOs between Fund II and Fund III where the sponsor has tightened covenant reporting mid-year and the last three board cycles triggered restated EBITDA bridges."},"archetype":"startup-archetypes.org.ai/CoPilot-MarketplaceClearing","beachhead":"EarlyAdopterJTBD: PE-backed DSOs between Fund II and Fund III where the sponsor has tightened covenant reporting mid-year and the last three board cycles triggered restated EBITDA bridges.","competitors":{"substitutes":[{"name":"Manual Excel reconciliation of the prior quarter's board deck against the new sponsor policy memo","category":"manual-bridge"},{"name":"Vena Solutions (board reporting + FP&A)","category":"incumbent","uncopyabilityReason":"Vena's moat is its Excel-native modeling layer sold to the FP&A seat; detecting that a sponsor's add-back policy changed between cycles requires parsing the PE operating partner's side-letter memos and joining them to line-item provenance — a document-ingestion and NLP surface Vena has never shipped because its revenue model is priced per modeling seat, not per policy-diff event, and building it would require a second product org aimed at the sponsor rather than the portco."},{"name":"Planful (formerly Host Analytics) board reporting module","category":"incumbent","uncopyabilityReason":"Planful's integration depth is with NetSuite/Sage Intacct GL pulls and its board module assumes stable chart-of-accounts mappings quarter over quarter; the DSO-specific same-practice cohort logic (practice acquisition dates, de novo ramp curves, doctor-partner buyouts) lives outside the GL in practice-management systems like Dentrix and Open Dental that Planful has no native connectors for, and adding them would require a vertical PMS-integration team that their horizontal mid-market GTM does not fund."},{"name":"Big-4 / regional accounting advisory (Armanino, CohnReznick DSO practice)","category":"human alternative","uncopyabilityReason":"The advisory firms ARE the current substitute — they staff a senior manager for 2 weeks per quarter to rebuild the bridge by hand. Their liability posture (signed engagement letter, PCAOB-adjacent work-paper standards) means they cannot let a software product auto-publish the board exhibit under their letterhead without restructuring professional-liability insurance, so they will remain a $180k/year services line, not a product competitor."},{"name":"OneStream board reporting","category":"AI-native horizontal","uncopyabilityReason":"OneStream's deployment-mode is a unified CPM platform that requires a 6–9 month implementation and a dedicated admin; PE-backed DSOs refresh their sponsor reporting rules every 60–90 days and swap portcos in and out of roll-ups mid-year, which is a cadence OneStream's implementation-heavy deployment model structurally cannot match without abandoning its enterprise-CPM positioning."}]},"studioThesis":"T-HSA","killThreshold":{"K":11,"M":35,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Rule-change detection cadence (annual re-implementation ↔ diffed on every deck refresh)","yAxis":"Vertical fit for PE-backed DSOs (generic CPM chart-of-accounts ↔ native same-practice cohort + sponsor add-back memo parsing)","winningQuadrant":"Per-refresh policy-diff engine with native DSO cohort logic and sponsor memo parsing — the FP&A manager sees every figure whose rule shifted, the VP of Finance signs off, and the operating partner never finds drift during dry-run","loservilleEscape":true,"loservilleQuadrant":"Generic CPM template (Planful, OneStream) where chart-of-accounts mappings are locked at implementation and sponsor-memo changes propagate only when a consultant is re-engaged — the failure mode that produced the weekend-rebuild consequence this engine exists to kill"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afinancial-managers-board-financial-presentation%3At-hsa%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afinancial-managers-board-financial-presentation%3At-low%3Av1","id":"fh:financial-managers-board-financial-presentation:t-low:v1","lens":"AgenticWorkflow","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/financial-managers-board-financial-presentation","stableHash":"wcc:financial-managers:board-financial-presentation:multimodal:v1"},"problem":{"slotStatement":"The FP&A manager has no tool that can assemble the board financial packet — TIER margin walk, RUS Form 7 ratios, power-cost variance, deferred-revenue waterfall, capital-credits retirement schedule — so the week before every board meeting collapses into one analyst hand-stitching Excel exports from iVUE against last month's deck, and any director question at the table kicks a three-day re-pull that burns the controller's week."},"approach":{"oneSentence":"After every month-end close in NISC iVUE, an agentic packet-assembly workflow walks the co-op chart of accounts, rebuilds the TIER / DSC / equity-ratio schedules and the power-cost-adjustment variance, and hands the FP&A manager a board-ready deck where every figure carries a click-through lineage back to the GL journal and the RUS Form 7 line — so director questions at the table resolve in the room instead of triggering a three-day re-pull."},"customer":{"icpShape":"CFO at a 60k-200k-meter member-owned electric cooperative (CompanyType/company-type-member-owned-electric-cooperative), where the buyer is the CFO who signs the software PO under the CEO's delegated authority and the daily user is the Manager of Financial Planning & Analysis who assembles the monthly board packet for the elected member-director board.","beachheadShape":"EarlyMajorityWorkflow: Touchstone Energy / NRECA-affiliated distribution co-ops on NISC iVUE or SEDC whose nine-member elected boards meet monthly and whose FP&A team is one or two people."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-MoneyOnDelivery","beachhead":"EarlyMajorityWorkflow: Touchstone Energy / NRECA-affiliated distribution co-ops on NISC iVUE or SEDC whose nine-member elected boards meet monthly and whose FP&A team is one or two people.","competitors":{"substitutes":[{"name":"One credentialed FP&A analyst stitching Excel exports from NISC iVUE","category":"informal"},{"name":"Controller manually reconciling last month's board deck in PowerPoint","category":"manual-bridge"},{"name":"NISC iVUE Financials reporting module (Cooperative Financials + Report Writer)","category":"incumbent","uncopyabilityReason":"NISC is a member-owned cooperative itself serving ~860 utility members on a shared multi-tenant stack; shipping an agentic board-packet assembler means deep integration-depth rewrites across the iVUE GL, Service Suite, and MDM modules on a release cadence governed by a member-elected product board — the integration-depth barrier (and the governance cadence behind it) is why iVUE Report Writer has remained a static-template tool for a decade."},{"name":"SEDC UPN / financial reporting suite","category":"incumbent","uncopyabilityReason":"SEDC's deployment-mode is still predominantly on-premise IBM i / AS400-hosted at the co-op; a modern agentic workflow that browses the GL and rebuilds TIER schedules requires a SaaS control plane and LLM egress posture that the installed base's deployment-mode-mismatch (on-prem, no outbound internet from the finance VLAN) structurally blocks without a multi-year re-platforming."},{"name":"Workiva Wdesk (board & regulatory reporting)","category":"AI-native horizontal","uncopyabilityReason":"Workiva's distribution-channel is SEC-filer and Fortune-1000 finance orgs sold through a six-figure enterprise motion; the 800+ US distribution co-ops sit below its sales floor and none of its connectors speak the RUS Form 7 / CFC Key Ratio Trend Analysis / NISC iVUE vocabulary — the vertical-data-corpus for electric-co-op chart-of-accounts and TIER/DSC covenants simply isn't in its template library."}]},"studioThesis":"T-LOW","killThreshold":{"K":11,"M":35,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Source-system reach (static PDF template the analyst pastes into ↔ live agent that walks the iVUE GL and MDM on each refresh)","yAxis":"Co-op-specific financial vocabulary (generic GAAP P&L ↔ native RUS Form 7 + CFC KRTA + TIER/DSC/equity-ratio + power-cost-adjustment + capital-credits retirement)","winningQuadrant":"Live agent that walks iVUE and rebuilds the TIER/DSC/PCA/capital-credits schedules in the co-op's own covenant vocabulary, so a director's question about last month's power-cost variance resolves in the board room","loservilleEscape":true,"loservilleQuadrant":"Static PowerPoint template in generic GAAP vocabulary — the documented failure mode of the Report Writer + analyst-stitched-Excel workflow, where any off-script director question kicks a three-day controller re-pull"}},"unmetRequirements":[],"pricingArchitecture":"tiered","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afinancial-managers-board-financial-presentation%3At-low%3Av1"}},{"$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Afinancial-managers-capex-approval-request%3At-ais-low-tech%3Av1","id":"fh:financial-managers-capex-approval-request:t-ais-low-tech: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/financial-managers-capex-approval-request","stableHash":"wcc:financial-managers:capex-approval-request:document:v1"},"problem":{"slotStatement":"Every capex request >$5k currently gets routed as a wet-signature PDF or a Notion doc pinged around Slack — each approval cycle burns ~45 min of a senior engineer's and a finance lead's time ($55–90 of loaded labor per request) and, worse, routinely gets signed by someone outside the actual spending-authority matrix, forcing finance to unwind unauthorized commits at month-end close and adding 3–7 days of cycle-time inflation per deal."},"approach":{"oneSentence":"A pay-per-approval HTTP API + 40-line CLI that validates each capex request against your authority matrix, routes it to the correct signer, and returns a signed, review-ready JSON decision trace — free for the first 100 approvals/month, then $0.25 per approval with no seat fees, no minimum, and onboarding is literally `curl -H 'x-api-key: …' /v1/approvals`."},"customer":{"icpShape":"Series A–C VC-backed SaaS startups (company-type-vc-saas-startup, 30–200 headcount) where the buyer is the VP Engineering or Head of Finance who owns the corp-card and tooling budget, and the daily user is a senior platform engineer or FP&A-adjacent ops engineer wiring a capex/vendor-approval flow into Slack, Linear, or a homegrown admin console — someone who would rather paste an API key than schedule a sales call.","beachheadShape":"EarlyAdopterJTBD: founding platform engineers at 50–150-person VC-backed SaaS startups standing up their first real capex/vendor-spend approval workflow above the $5k signing threshold."},"archetype":"startup-archetypes.org.ai/AIService-UsageMetered","beachhead":"EarlyAdopterJTBD: founding platform engineers at 50–150-person VC-backed SaaS startups standing up their first real capex/vendor-spend approval workflow above the $5k signing threshold.","competitors":{"substitutes":[{"name":"Wet-signature PDF routed over email + Slack","category":"manual-bridge"},{"name":"The internal Python script the platform engineer would otherwise write against DocuSign + an auth-matrix YAML","category":"informal"},{"name":"Ramp Bill Pay approvals","category":"incumbent","uncopyabilityReason":"Ramp's approval engine is welded to its card/BillPay rails — approvals only exist for spend that lives inside Ramp's ledger. Extending it to arbitrary capex objects (contractor SOWs, infra commitments, data-vendor renewals not on a Ramp card) would require decoupling approvals from the card-issuance P&L that funds the product, a distribution-channel barrier they won't cross in 6 months."},{"name":"Workday Adaptive / Workday Spend Management approval workflows","category":"incumbent","uncopyabilityReason":"Workday's approval module requires a full Workday tenant, an implementation partner, and a 3–9 month deployment — a deployment-mode mismatch for a 60-person VC-backed SaaS shop that wants a credit-card self-serve API. Workday cannot ship a paste-API-key tier without gutting its SI channel economics."},{"name":"Pigment / Mosaic capex planning modules","category":"AI-native horizontal","uncopyabilityReason":"Pigment and Mosaic sell CFO-office planning suites with 6-figure ACVs and annual contracts; their integration-depth with GL/HRIS is their moat, but it is also their ceiling — they cannot expose a $0.25/approval metered API without cannibalizing seat-priced deals, and their product surface is a spreadsheet UI, not an HTTP contract a platform engineer embeds."}]},"studioThesis":"T-AIS-LOW-TECH","killThreshold":{"K":9,"M":30,"N":7,"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 ≥ 7/9 (CASCADE.md §4 Stage 9 commit threshold)."},"lifecycleState":"Active","differentiation":{"twoByTwo":{"xAxis":"Authority-boundary enforcement (human eyeballs trust the signer ↔ every request machine-checked against a declared spending-authority matrix before routing)","yAxis":"Setup friction and cost shape (annual seat license + implementation SOW ↔ paste API key, pay $0.25 per approval, no minimum)","winningQuadrant":"Machine-enforced authority-boundary checks exposed as a metered pay-per-approval API a platform engineer wires in during one afternoon","loservilleEscape":true,"loservilleQuadrant":"Workday Spend Management's 6-month SI-led rollout where signer authority is still defined in a Visio diagram and 'unauthorized-signer' is caught weeks later at month-end close by the controller"}},"unmetRequirements":[],"pricingArchitecture":"usage-meter","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Afinancial-managers-capex-approval-request%3At-ais-low-tech%3Av1"}}],"actions":{},"options":{},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a05757209b3624d3","edgeLocation":"a05757209b3624d3","geo":{"country":"US"},"ua":{"browser":"Claude"}},"relationships":{},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/references"},"items":[]}}