Feedback Session: Proposal Deliverable — Proper Hospitality Data & Analytics
Run ID: proposal-2026-02-proper-hospitality-data-analytics
Type: Proposal (sales deliverable) — final copy locked
Artifact: proposal-data-analytics-feb-2026.md
Date: February 2026
Prepared by: Robert Tseng
Audience: Payas Parab (Analytics Engineering), Mike (Chief of Staff)
What this is
Final proposal for Proper Hospitality Group: two workstreams (Lead Researcher + F&B Analytics) plus staff-augmented rate card. Lead Researcher is an Outlook-integrated AI tool (CC-based flow, dossier to thread, Salesforce/lead context). F&B Analytics is Toast → Snowflake pipelines, dbt, production tables, and basic dashboarding (Streamlit or Rill) with 1 DE + 1 DA. Pricing: WS1 18K (4 sprints); rate card 250/hr. Heuristics: low cost / high impact, hands-on keyboard for Payas. Uttam notes captured (agentmail.to, Exa, data vendors).
Why this matters
- Single source of truth for the pitch — Sales and delivery use one proposal; no version drift when we iterate with Proper.
- Reusable structure — Two workstreams + rate card + timeline is a pattern we can reuse for other hospitality or “one AE + many asks” leads.
- Learning from the deliverable — Storing it in vault with a feedback session entry means we can refer back to what we proposed, what we priced, and what we learned (e.g. Outlook not Slack, Toast + identity graph, lean tooling).
How this changes how you work
-
Before: “What did we propose to Proper? Where’s the latest version?”
-
After: Open proposal-data-analytics-feb-2026.md for the final proposal. This feedback session documents what it is and where it lives.
-
Before: Proposals lived in email or drive; no consistent place to log what we sent.
-
After: Proposals in
knowledge/sales/leads/{lead}/with a matching feedback session entry when we lock final copy—same pattern as offer updates (e.g. Edge-to-Activation) and deployment messages.
Where it lives
- Proposal (canonical): proposal-data-analytics-feb-2026.md
- Lead folder: proper — add meeting notes, follow-up, SOW when applicable.
- SOW framework (reference): sow-framework for templates and pricing logic if we convert to SOW.
What this enables
- Consistent handoff — Anyone can find the Proper proposal and see scope, pricing, and timeline in one place.
- Pattern reuse — Lead Researcher (Outlook + dossier) and F&B (Toast + dbt + lean dashboards) can be referenced for similar hospitality or “one AE, many streams” deals.
- Feedback loop alignment — Proposal deliverables get the same treatment as other “final copy” outputs: one canonical doc + one feedback session entry so we keep learning.