Design Demo Build Plans

1. Reads the existing demo plan references, architecture diagrams and implementation plan artifacts.
2. Checks whether each reference actually has content. When a document turns out to be an empty placeholder, it asks the user where the missing material lives.
3. Writes a phased implementation plan covering the demo's scope. In one sample that scope included supplier management, a change lifecycle, a document repository, an Experience Cloud portal and reporting.
4. Answers fit questions along the way, such as whether a product suits the use case and whether the customer could build it themselves.
5. When asked to build, it works through the build phases. In one sample these were custom objects and fields, products, accounts, opportunities, quotes and orders. Flows, Apex classes, LWCs, approval processes, an Experience Cloud portal, reports and dashboards followed. The sample also included a demo reset script, a demo script, a UAT checklist and dry runs. That task is paused while it waits for the user to sign off on acceptance criteria, and its outcome counts nothing as built.

For the scripts that usually follow a build plan, see Document Demo Scripts.