{"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%3Amechanical-engineers-technical-specification-writing%3At-hsa%3Av1","links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Amechanical-engineers-technical-specification-writing%3At-hsa%3Av1","canonical":"https://api.sb/founding-hypotheses/fh%3Amechanical-engineers-technical-specification-writing%3At-hsa%3Av1","pool":"https://api.sb/v1/founding-hypotheses"},"foundingHypothesis":{"id":"fh:mechanical-engineers-technical-specification-writing: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/mechanical-engineers-technical-specification-writing","stableHash":"wcc:mechanical-engineers:technical-specification-writing:document:v1"},"problem":{"slotStatement":"The principal ships a 40-page component spec to the OEM's supplier and only discovers weeks later that a junior engineer (or an LLM draft) quietly inserted a GD&T callout, a material substitution, or a qualification-test reference that exceeded the contracted scope — binding the consultancy to design authority it never had, exposing it to 510(k) or airworthiness-certification liability, and forcing an expensive spec revision once the supplier has already cut tooling."},"approach":{"oneSentence":"A design-authority boundary engine that sits between the engineer's CAD/PLM drafting surface and the outgoing spec PDF, cross-checking every tolerance, material, and qualification-test callout against the signed statement-of-work scope and flagging any clause the consultancy is not contractually authorized to bind before the spec leaves the office, producing a verifiable authority-trace for the OEM's supplier-quality file."},"customer":{"icpShape":"Solo or two-principal mechanical design consultancies (targetCompanyType: company-type-solo-dental-practice-equivalent in ME consulting; 1–5 engineers) who author component/system technical specifications for regulated end-customers (FDA Class II device OEMs, DO-160/DO-254 avionics primes, ASME B&PV pressure-vessel buyers), where the buyer is the Principal Engineer / Owner who signs the services contract and the daily user is the staff Mechanical Design Engineer drafting the spec.","beachheadShape":"EarlyAdopterJTBD: solo mechanical consultants who subcontract to medical-device OEMs and get burned when a spec they authored accidentally commits the client to a tolerance, material callout, or qualification test the consultant had no authority to bind."},"archetype":"startup-archetypes.org.ai/AgenticWorkflow-Subscription","beachhead":"EarlyAdopterJTBD: solo mechanical consultants who subcontract to medical-device OEMs and get burned when a spec they authored accidentally commits the client to a tolerance, material callout, or qualification test the consultant had no authority to bind.","competitors":{"substitutes":[{"name":"Manual redline pass by the principal engineer against the SOW","category":"status-quo","uncopyabilityReason":""},{"name":"Excel-based clause-to-SOW traceability matrix maintained by the engineer","category":"manual-bridge","uncopyabilityReason":""},{"name":"Siemens Teamcenter Requirements Management (with Polarion)","category":"incumbent","uncopyabilityReason":"Teamcenter/Polarion is built around the OEM-side PLM deployment: it assumes the buyer owns the requirements baseline and the supplier writes against it. A 2-engineer consultancy cannot stand up a Teamcenter tenant, and Siemens' integration-depth moat (CAD ↔ BOM ↔ requirements) is also the thing that prevents them from shipping a lightweight outside-counsel authority-boundary checker in 6 months — it would cannibalize the enterprise seat model and require rebuilding the permissioning layer to recognize a contractor's SOW as the authority of record rather than the OEM's baseline."},{"name":"Jama Connect","category":"incumbent","uncopyabilityReason":"Jama's vertical-data-corpus advantage (decades of aerospace/medical requirement-decomposition templates) is locked to the requirements-engineering use case inside primes. It has no model of contractual authority boundaries — its ontology is traceability of requirements to verification, not traceability of clauses to signed scope. Retrofitting SOW-clause ingestion and design-authority attestation would require a new liability-posture (opining on what the consultancy is allowed to write), which Jama has explicitly avoided in its MSAs."},{"name":"GitHub Copilot / ChatGPT used ad-hoc for spec drafting","category":"AI-native horizontal","uncopyabilityReason":"Horizontal LLM assistants have a deployment-mode-mismatch: they ingest the draft spec but have no handle on the signed SOW PDF, the consultancy's E&O insurance rider, or the OEM's qualification-test catalog. Shipping an authority-boundary checker would require per-customer SOW ingestion plus a regulated-industry liability position (who is on the hook when the checker misses a clause), which OpenAI/GitHub structurally decline to underwrite."},{"name":"Ansys Granta MI (materials spec governance)","category":"incumbent","uncopyabilityReason":"Granta's moat is the curated materials-property corpus and its distribution channel through enterprise simulation licenses. That capital-intensity around materials data does not extend to contractual-scope checking — and their distribution channel (sold alongside Ansys simulation seats to F500 engineering orgs) cannot economically reach a 2-person consultancy at a price point the consultancy will pay."}]},"studioThesis":"T-HSA","killThreshold":{"K":11,"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":"Authority-boundary awareness (treats spec as free-text draft ↔ checks every clause against the signed SOW scope and E&O rider)","yAxis":"Deployment fit for sub-5-engineer consultancies (enterprise PLM seat with 6-month rollout ↔ desktop sidecar that reads the engineer's Word/PDF spec and the SOW folder on day one)","winningQuadrant":"Clause-level SOW-scope checking delivered as a desktop sidecar a solo ME consultancy installs in an afternoon, producing a per-clause authority trace the OEM's supplier-quality team can accept as review-ready evidence.","loservilleEscape":true,"loservilleQuadrant":"Teamcenter/Polarion and Jama Connect: enterprise PLM requirements suites with no model of contractual authority, sold on 6-month implementations the consultancy cannot afford and cannot self-host — so the consultancy falls back to a manual SOW redline the principal does at 11pm."}},"unmetRequirements":[],"pricingArchitecture":"single-price"},"actions":{},"options":{},"relationships":{"runtimeUnit":"https://api.sb/v1/runtime-units?startupRef=startup%3Afh%3Amechanical-engineers-technical-specification-writing%3At-hsa%3Av1","brand":"https://api.sb/v1/brands?startupId=startup%3Afh%3Amechanical-engineers-technical-specification-writing%3At-hsa%3Av1","listing":"https://api.services/listings?foundingHypothesisRef=fh%3Amechanical-engineers-technical-specification-writing%3At-hsa%3Av1","cell":"https://api.sb/v1/cells/work-contexts.org.ai/mechanical-engineers-technical-specification-writing","thesis":"https://api.sb/v1/theses/T-HSA"},"meta":{"level":"L0","scopes":[]},"user":{"requestId":"a0575aad1f690555","edgeLocation":"a0575aad1f690555","geo":{"country":"US"},"ua":{"browser":"Claude"}},"references":{"total":0,"limit":25,"page":1,"links":{"self":"https://api.sb/v1/founding-hypotheses/fh%3Amechanical-engineers-technical-specification-writing%3At-hsa%3Av1/references"},"items":[]}}