What should be included in a good project scope?

A good scope should define the site, assistant, public brain, categories, Q&A, image context, public files, private brain if needed, reporting, update responsibilities, timelines, approval process and ongoing support.

The clearer the scope, the less chance of confusion later. Pricing and scope should be framed as a commercial discussion rather than a fixed public promise, because needs and delivery pathways vary. In other words, the goal is to give the client a controlled first AI layer instead of leaving the whole topic vague and undefined. In the SupplyOnly.com model, the point is to make this useful rather than decorative: connect the answer to approved business facts, public Q&A, image context and the Own The Conversation fulfilment pathway. That gives a referrer or client a clearer reason to act without pretending that AI visibility is magic or guaranteed.