KnowBe4 — deferral + re-entry window (2026-07-23)

Founder forwarded a screenshot (iMessage, 10:56am ET) of an email from Liz (Elizabeth) Smith, Data Science Manager (KB4 side) to Sam (phData AE side). Founder's framing: "Kicking the can down the road."

What the email actually says

• KB4 is on an "extremely expedited timeline," targeting delivery end of next week (~2026-07-31).
• They are building it in-house: fusing their LLM unstructured risk summarization model with multi-modal (product → account state) XGBoost models + LLM SHAP summarization.
• They are "doing everything as fast as possible and relying heavily on CoCo" and she concedes "I'm sure that we are making some mistakes along the way."
• She herself highlighted the re-entry line: "we will definitely need to revisit this for some optimization/cost efficiency work" — once delivery lands and they have breathing room.
• Sign-off: "Hope to chat sometime in the future!"

Read

This is a timing objection, not a fit rejection, and the prospect wrote the re-entry ticket herself. The future engagement scope is pre-confessed: cleanup / optimization / cost-efficiency of a rushed LLM+XGBoost+SHAP build. A re-touch keyed to that highlighted sentence (cost-efficiency / LLM-ops review shaped offer) will land better than a generic check-in.

Re-entry plan

• Window: ~2026-08-11 (two weeks post their delivery target = "breathing room").
• Notion task queued (Owner Ray, due 2026-08-11): resurface to founder with a re-touch angle. Account ownership is Sam's; founder nudges.
• Related: [[2026-06-28-knowbe4-2024-loss-insider-read]] · [[2026-06-26-knowbe4-snowflake-workshop-pitch]] — the 6/26 workshop framing may be reusable as the optimization-phase artifact.