Build · Create · Writing & Content

Build a Workflow Lock-In and Switching-Cost Register

The founder gets a structured lock-in register that documents, per top customer, the automations / integrations / team-workflows running through the product plus a switching-cost estimate and an integration-depth tier, surfacing where the product is embedded and where it needs to go deeper.

You receive: A JSON object: { customers: [{ customerId, name, automations: [string], integrationsDependedOn: [string], teamWorkflows: [string], integrationDepth: enum(surface|moderate|deep), switchingCostEstimate: enum(low|medium|high) }], depthCounts: { surface, moderate, deep }, surfaceCustomers: [customerId...] }

Part of Choose Business Model

What's verified: STUD verifies the register is complete and consistent: minimum customer count, each customer carrying a depth + switching-cost rating with at least one lock-in signal, 'deep' ratings backed by the required integration count, and the tallies/surface-list matching the data. STUD does NOT verify the switching-cost estimates are accurate, that the listed automations exist, or that the lock-in is real. It checks the audit's structural completeness, not the truth of the stickiness.

{
 "buyerParamKeys": [
  "requireAtLeastOneSignal",
  "requireDepthAndCostEach"
 ],
 "checkNames": [
  "format_parses",
  "cust_min",
  "unique_ids",
  "deep_justified",
  "depthcounts_consistency",
  "surface_list_consistency",
  "depth_cost_required",
  "signal_present"
 ],
 "constants": {},
 "deliverableLabel": "workflow_lockin_switching_cost_register",
 "documentKeys": [
  "customerId",
  "customers",
  "depthCounts",
  "integrationDepth",
  "integrationsDependedOn",
  "name",
  "surfaceCustomers",
  "switchingCostEstimate"
 ],
 "enumLiterals": [
  [
   "automations",
   "integrationsDependedOn",
   "teamWorkflows"
  ],
  [
   "low",
   "medium",
   "high"
  ],
  [
   "surface",
   "moderate",
   "deep"
  ],
  [
   "yes",
   "true",
   "y",
   "1"
  ]
 ],
 "submission": "a JSON document (submitted as a string), validated as data; every check below must pass",
 "tier": "doc-validator"
}