How Work Scales | Goldmont Consulting Skip to content

How work scales

One decision spine. Four depths.

This page isn’t a menu. It explains how the work scales from a 2-minute Snapshot to deeper underwriting and a 90-day operating system install—depending on urgency and data access.

Same backbone at every depth: ranges, explicit assumptions, and proof checkpoints with owners—built to survive IC, lender, and operator scrutiny.

No discovery call required
Forwardable artifacts
Proof checkpoints + owners
Deterministic logic (Snapshot)
Decision Snapshot (≈2 minutes)

Determine the next step fast—then circulate a forwardable decision spine.

Router
When to use: You need an IC-safe next step before you spend weeks.
Output: PDF/shareable summary you can circulate internally.
  • Recommended next step + why (Deep Dive / Diagnostic / 90-Day)
  • Key assumptions + fragility (what breaks the case first)
  • Proof checkpoints (“evidence gates”) with owners + timelines
Note: The Snapshot is deterministic logic—no LLMs/agents. It routes you to the right depth and documents the “what must be true” spine.
Deep Dive Session

Collapse ambiguity with a working session—pressure-test the decision and lock the next proof steps.

Fast clarity
When to use: You need clarity now, but data access is partial or messy.
Format: Live working session + forwardable notes.
  • Live decision working session that collapses ambiguity fast
  • Decision map: what to prove next, by whom, by when
  • Follow-up notes you can forward (call + next actions)
Decision-Grade Diagnostic (≈2 weeks)

Convert assumptions into defendable ranges—evidence gates, owners, and an IC/lender-safe narrative.

Underwrite
When to use: You’re heading to IC or lender scrutiny and the memo must hold.
Output: Forwardable packet that survives thread-pulling.
  • Defensible ranges + assumptions ledger (IC / lender ready)
  • Risk priced and prioritized (not just “noted”)
  • Pass/fail proof checkpoints that decide proceed / pause / restructure
90-Day System Install

Translate diligence into execution—owners, cadence, governance, and a Day-100 operating rhythm.

Execute
When to use: The deal is real and you can’t afford post-close improvisation.
Output: Operating system installed (not a slide deck).
  • Owners + cadence + governance (operating rhythm installed)
  • Day-1 / Day-30 / Day-100 plan tied to value levers
  • KPI tree + baselines + weekly execution loop