Project memory for remodeling teams
A remodel's decisions often live in a call, a text thread, and three different emails. A project-memory assistant built on the planned Provenience platform could help an authorized business administrator find those decisions together.
Bring in
Use the business's shared Site contact for conversations with the homeowner, designer, and subcontractors, and keep those people on the project's roster. A dedicated project contact is optional. Define categories such as finishes, fixtures, scope, and schedule. Catalog drawings and attachments as files. For SMS/MMS, qualifying images and short PDFs can be considered with the message; do not assume a drawing's contents have been extracted.
Ask
- What tile has the homeowner discussed for the primary bathroom?
- Where did the scope change come up?
- Which budget amounts were stated, and were they firm or tentative?
The useful result is a set of cited records the business administrator can inspect. During an active project, claims retain their recorded standing; a confirmed close-out sweep establishes later relationships. A client saying something new does not silently mark an older selection superseded.
Build around it
Use MCP with Claude or ChatGPT as the planned first query surface. A custom decision-history interface is an application idea, not a shipped template or a promise of an existing public application API.
Keep a person in the loop
The assistant should help find evidence before someone confirms a purchase or scope change. Phase 1 does not place orders, write back to job-management software, extract drawing contents, or provide a customer-facing portal.
Start with the project workflow and the capture capabilities.