Plan trade lead workflow for future brewery management app

[spizeck]

Context

Public trade inquiries are already durably persisted to Firestore and notification email is best effort. A richer workflow could eventually track states such as new, contacted, qualified, or closed and support internal notes/ownership.

Deep Dive Brewing plans to replace Ollie with a custom brewery management, inventory, and sales application after the Sea Saba booking platform is complete. That future application is the appropriate place to decide ownership of CRM-like trade/customer workflow rather than expanding this website into a second operational system.

Goal

Capture the desired trade-lead workflow and define the future integration/data-ownership boundary without implementing a competing CRM in this repository now.

Potential future concepts:

• lead status
• internal notes
• assignment/owner
• conversion from inquiry to trade customer/account
• history/audit trail
• handoff into customer/order workflows

Constraints

• Do not implement the workflow yet.
• The existing website trade inquiry must remain reliable and simple.
• Do not add inventory, sales, pricing, order-management, or CRM source-of-truth behavior to this website before the brewery management app architecture is defined.
• Preserve current privacy and security boundaries around trade lead data.

Acceptance criteria for future implementation

• Authoritative ownership of leads/customers is defined between the website and brewery management app.
• Lead lifecycle/status model is defined.
• Internal notes and assignment semantics are defined if actually needed.
• Inquiry-to-customer/account handoff is defined.
• Audit/history and permission requirements are defined.
• Existing website inquiries can be migrated/integrated without losing durable records.
• No duplicate operational source of truth is created.

Timing

Backlog / tabled. Revisit as part of the custom brewery management application design.