Build vs Buy
Configure defaults
Back to editor

Configure the defaults.

Set the canonical values every step starts at. The editor’s “Reset to saved defaults” button reverts working edits back to whatever you save here.

Atomic ladder
Name
Framing
L0
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L1
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L2
Name
Complexity
Description
Stop here
(top of ladder, no stop-here text)
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
Atomic ladder
Name
Framing
L0
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L1
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L2
Name
Complexity
Description
Stop here
(top of ladder, no stop-here text)
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
Atomic ladder
Name
Framing
L0
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L1
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L2
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L3
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L4
Name
Complexity
Description
Stop here
(top of ladder, no stop-here text)
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
Atomic ladder
Name
Framing
L0
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L1
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L2
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L3
Name
Complexity
Description
Stop here
(top of ladder, no stop-here text)
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
Atomic ladder
Name
Framing
L0
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L1
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L2
Name
Complexity
Description
Stop here
(top of ladder, no stop-here text)
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
Atomic ladder
Name
Framing
L0
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L1
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L2
Name
Complexity
Description
Stop here
(top of ladder, no stop-here text)
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
Atomic ladder
Name
Framing
L0
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L1
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L2
Name
Complexity
Description
Stop here
(top of ladder, no stop-here text)
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
Atomic ladder
Name
Framing
L0
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L1
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L2
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L3
Name
Complexity
Description
Stop here
(top of ladder, no stop-here text)
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
Atomic ladder
Name
Framing
L0
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L1
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L2
Name
Complexity
Description
Stop here
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
L3
Name
Complexity
Description
Stop here
(top of ladder, no stop-here text)
Build (wks)
to
Maintain (FTE share)
Engineering
ML
PM
Content Ops
Data Eng
Snapshot

Export the whole model. Hand it to Claude.

Export writes every step and ladder in full. It is a complete document, not a delta, so the file stays interpretable even after src/lib/capability-model.ts drifts. Hand the file to Claude and the values get baked into the source.

Fields changed vs code seed
0
Step edits
0
Ladder edits
0
File format reference
{
  "$schema": "bvb-model-snapshot/v3",
  "exportedAt": "2026-05-25T18:30:00.000Z",
  "blendedFteRateUsd": 175000,
  "ladders": [
    {
      "id": "<ladder-id>",
      "name": "...",
      "framing": "...",
      "steps": [
        {
          "id": "<atomic-step-id>",
          "name": "...",
          "description": "...",
          "giveUp": "..." | null,
          "complexity": "green" | "yellow" | "red" | null,
          "buildWeeksMin": 4 | null,
          "buildWeeksMax": 6 | null,
          "maintain": { "eng": 0.1, "ml": 0, "pm": 0, "contentOps": 0, "dataEng": 0 }
        }
      ]
    }
  ]
}
Changes here become the “defaults” the editor reverts to. They live in your browser’s localStorage and layer on top of the code-seeded values in src/lib/capability-model.ts.