engagements

What problem does it solve?

This Skill helps you consistently create, update, and close client paid engagements in Shaw’s Notion-based Engagements database, so project history, delivery tracking, and wrap-up records stay accurate and aligned with Stripe and CRM.

Core Features & Use Cases

• Create Engagement Rows: Add a new Engagement (one row per won, invoiced project) with correct properties, body template, and relational linking to the client.
• Maintain Lifecycle Status: Transition Sold → Active → Delivered, with controlled handling for Refunds and On Hold, including the correct End Date and wrap prompts.
• Link Sessions and Calls: Append ABA Trainings and ABA Calls mention-pages into the right chronological sections, including reschedule updates.
• Fill Stripe Payment Details: Look up Stripe invoices, determine Paid Status, set Price, and write the correct Stripe link line into the engagement body (including proxy/void/replacement edge cases).
• Guard the Engagements vs CRM Boundary: Keep long-term relationship nurture and wrap-up 4Rs in the correct place (Clients (Nurture) after Delivered) to avoid data drift.

Quick Start

Ask the AI to create an Engagement for a client who just paid, then link the discovery call and prepare the engagement body so Stripe and session tracking can be filled in as delivery starts.