{"api":{"name":"api.sb","description":"Business-as-Code surface for Startups.Studio","home":"https://api.sb","docs":"https://api.sb/docs","version":"1.0.0"},"$context":"https://api.sb/$context","$type":"FoundingHypothesis","$id":"https://api.sb/founding-hypotheses/fh%3Aproject-management-specialists-project-status-report%3At-low%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aproject-management-specialists-project-status-report%3At-low%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Aproject-management-specialists-project-status-report%3At-low%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:project-management-specialists-project-status-report: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/project-management-specialists-project-status-report","stableHash":"wcc:project-management-specialists:project-status-report:document:v1"},"problem":{"slotStatement":"Every Friday the PM specialist stitches together crew timesheets, Milsoft/Futura staking sheets, material-issue slips from the warehouse, and contractor pay-app emails into a board-ready status deck — and when RUS, FEMA, or the co-op's internal auditor later asks why a pole-mile slipped or why a change-order hit the loan budget, the underlying evidence (who approved the scope change, which crew-day it happened, which invoice it tied to) is scattered across shared drives and Outlook threads, producing audit findings the GM has to personally answer to the board."},"approach":{"oneSentence":"A construction-work-plan status engine that watches the co-op's staking, work-order, and AP systems across the week, certifies each reported pole-mile and dollar against the source crew-day and material issue, and hands the PM specialist a board-packet draft where every variance line carries a traceable record back to the approving foreman, engineer, or change-order."},"customer":{"icpShape":"Operations & Engineering leadership at member-owned electric cooperatives (CompanyType/company-type-member-owned-electric-cooperative) in the 40k–300k-meter range running capital construction and grid-hardening portfolios, where the buyer is the VP of Engineering & Operations (or COO) who signs the PM-tooling PO and the daily user is the Project Management Specialist / Staking Engineer assembling the weekly status report for the GM and the member-elected board.","beachheadShape":"EarlyMajorityWorkflow: G&T-affiliated distribution co-ops with active RUS/USDA loan-funded or FEMA/BRIC-reimbursed construction programs who must report weekly to a member board and a federal program officer."},"archetype":"startup-archetypes.org.ai/AIService-UsageMetered","beachhead":"EarlyMajorityWorkflow: G&T-affiliated distribution co-ops with active RUS/USDA loan-funded or FEMA/BRIC-reimbursed construction programs who must report weekly to a member board and a federal program officer.","competitors":{"substitutes":[{"name":"Network drive / SharePoint folder per construction work plan serving as the weekly-report evidence binder","category":"manual-bridge"},{"name":"Milsoft WorkSpace / Futura Stakeout (staking + work-order management)","category":"incumbent","uncopyabilityReason":"Integration depth: Milsoft and Futura own the staking-sheet and work-order data model but their reporting modules assume the staking engineer is the reporter; they have no AP/timesheet reconciliation layer and cannot ingest warehouse material-issue slips or contractor pay-apps without a multi-quarter schema extension to their co-op-specific data contracts."},{"name":"NISC iVUE Financials + Work Order Accounting","category":"incumbent","uncopyabilityReason":"Deployment-mode mismatch: NISC runs a shared multi-tenant co-op stack governed by the NISC member-cooperative board's release cadence; adding a weekly narrative-status engine that reconciles field-staking evidence to the GL would require an out-of-cycle core-system change that NISC's member-governed roadmap cannot ship in 6 months."},{"name":"Procore (construction PM platform)","category":"AI-native horizontal","uncopyabilityReason":"Vertical-data-corpus: Procore is trained on vertical/commercial-construction RFI/submittal workflows and has no model of pole-miles, RUS Form 219 loan-advance categories, FEMA Category-F reimbursement codes, or co-op staking-sheet conventions — repositioning for distribution-utility construction would require rebuilding its core object model."},{"name":"Smartsheet / Microsoft Project status templates maintained by the PM specialist","category":"status-quo"}]},"studioThesis":"T-LOW","killThreshold":{"K":11,"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":"Source-of-truth reconciliation (narrative pasted from memory ↔ each variance line traced to staking sheet + crew-day + material issue)","yAxis":"Vertical fit for RUS/FEMA-funded distribution co-op construction (generic construction PM ↔ pole-mile, Form 219, Category-F native)","winningQuadrant":"Every weekly-report variance line auto-reconciled to the co-op's staking/AP/timesheet source records, with a data model native to RUS loan-advance categories and FEMA disaster-reimbursement codes — defensible for the GM in front of the board and the RUS field rep.","loservilleEscape":true,"loservilleQuadrant":"Procore-style generic construction status templates filled in by hand from memory — no tie-back to Milsoft staking or NISC work-order accounting, and no concept of pole-miles or RUS categories, which is exactly where Procore and Smartsheet leave the PM specialist today."}},"unmetRequirements":[],"pricingArchitecture":"usage-meter"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Aproject-management-specialists-project-status-report%3At-low%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Aproject-management-specialists-project-status-report%3At-low%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Aproject-management-specialists-project-status-report%3At-low%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/project-management-specialists-project-status-report","thesis":"https://api.sb/v1/theses/T-LOW"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a0575ae82e6890ce","edgeLocation":"a0575ae82e6890ce","geo":{"country":"US"},"ua":{"browser":"Claude"}},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Aproject-management-specialists-project-status-report%3At-low%3Av1/references"},"items":[]}}