diff --git a/docs/PRE-DEPLOY-PLAN.md b/docs/PRE-DEPLOY-PLAN.md
index b46ec4d6..55d1f5f7 100644
--- a/docs/PRE-DEPLOY-PLAN.md
+++ b/docs/PRE-DEPLOY-PLAN.md
@@ -148,12 +148,25 @@ Mechanical. Run last to minimize merge churn. ~2h.
 
 Dedicated commit. Email template URL builder, page-side fragment readers, Better Auth integration test. ~1h.
 
-### 2.9 Step 9 — Optional: NocoDB inspection + recommender simulator
+### 2.9 Step 9 — NocoDB inspection complete: simulator DEFERRED
 
-Pre-flight: use the NocoDB MCP to inspect what stage-advancement / win history exists in the legacy interest records.
+NocoDB `Interests` carries only the current `Sales Process Level`
+single-select + a handful of point-in-time event timestamps
+(`EOI Time Sent`, `Time LOI Sent`, `clientSignTime`,
+`developerSignTime`, `EOI_Completed_At`, `finalized_document_sent_at`)
+scattered as text fields. There is **no dedicated stage-change
+history table** — only the most recent stage value survives.
 
-- **If recoverable**: build the "simulate against history" admin tool that replays past wins through current recommender weights. ~half day.
-- **If not**: defer until production accumulates ~10+ wins. Update `BACKLOG.md` to reflect.
+The recommender simulator's tier-ladder + heat-score logic depends on
+"how long did this deal sit at each stage" and "which stage did past
+deals make it furthest to before falling through." Without an
+advancement timeline that's not recoverable: every imported interest
+collapses to one data point.
+
+**Decision (2026-05-14):** defer the simulator until production
+accumulates ~10+ won deals under the new pipeline — then the simulator
+can replay against real CRM history. The existing per-port heat-weight
+tuning UI in `/admin/berth-recommender` is sufficient for v1 launch.
 
 ---