Leads & intake
What this covers
Section titled “What this covers”Long before there is a contract, there is a job in prospect — a property, an idea of what it should become, and a series of conversations that turn one into the other. That is real work, and it needs somewhere to live.
A lead is the record of that work before it is won. It holds the property, the people, the scope being discussed, and every meeting held along the way.
The rename to know first: a Legacy KI “Lead” is a KI Project Record. It is not a pre-sales stage that later converts into something else. The Project Record exists from the job walk onward and stays the same record through design, construction, and completion — see section 4.1.
Everything runs in Legacy KI
Section titled “Everything runs in Legacy KI”There is no Admin Portal on this instance, so intake, triage and the pipeline board are all Legacy KI screens.
A lead here carries the triage attributes — priority, likelihood, target dates, bid windows and the Lead Champion — and no design layer, because there is no design engagement to sell. There is no visioning, no questionnaire set, and no finish presentation.
Bidding is the sales motion
Section titled “Bidding is the sales motion”Invitations to Bid go out to subcontractors, their numbers come back, and bid tabulation compares them side by side to pick winners. Both are Legacy KI modules, and both are absent from Story’s instance.
When the work is won, the record carries its history forward rather than starting over.
What the client sees
Section titled “What the client sees”Nothing in KI. There is no Client Portal on this instance.
Related
Section titled “Related”- Part 3 — How a project runs — where intake sits in the project sequence
- Estimating and proposals — how the discussed scope gets priced