Cavaridge Academy

--- title: Deal registration status: draft note: AI-generated first-pass transcript pending video production + SME review. --- Deal registration in Cavaridge™ is a partner-channel discipline. The goal is to reward the MSP that worked the opportunity first, prevent double-dipping, and keep the customer experience clean. The deal-registration engine in Cavaridge Operations enforces all three. ## The lifecycle A deal moves through these states: 1. **Submitted.** The MSP registers an opportunity for a named end customer. `deal_created` Pulse fires. 2. **Qualified.** The MSP attaches enough evidence (meeting notes, call recording, signed NDA) to demonstrate the opportunity is real. 3. **Registered.** The platform locks the customer to this MSP for the registered duration (default 30 days). `deal_registered` fires. 4. **Active.** The deal is moving — quotes are being drafted, demos scheduled. Pulse activity keeps the registration alive. 5. **Closed-won, closed-lost, or expired.** Final state. ## The 30-day rule A registered deal is protected for 30 days from `deal_registered`. During that window, no other MSP can register the same end customer. The window extends automatically every time the platform observes a documented progress event (a quote, a demo, a meeting note). If 30 days pass with no progress, the protection lifts. Other MSPs can register. This is intentional — protection is a privilege, not an entitlement. ## Edge cases worth knowing - **Two MSPs register simultaneously.** First-write-wins by Pulse timestamp. The losing MSP gets a notification with the timestamp delta. - **End customer pre-existing relationship.** If the customer is already a tenanted client of another MSP, registration is blocked with a clear message. - **Deal expired and a different MSP now closed it.** The closing MSP gets the registration credit. The original MSP can dispute via the partner manager, but the engine respects the documented timeline. ## Pulse events you'll see In the sandbox **cavalier-deal-reg-starter** seed, you have two partner records and one shared end customer. Try to register the customer from both partner accounts in succession. Watch: - `deal_created` from the first attempt. - `deal_registered` once the qualification evidence lands. - `partner_joined` if the partner account is new. - A clean rejection from the second attempt. ## What to tell your team Three rules: 1. **Register early.** The moment a real opportunity is real, register. Waiting is a tax. 2. **Document progress.** A quote, a meeting note, a follow-up email — each one extends your protection. Silence kills it. 3. **Pulse is the truth.** When timestamps disagree with memory, Pulse wins. Argue the process, not the timeline. ## Pulse + payouts Partner payouts trigger off `closed_won` Pulse events for registered deals. The percentage and timing are tier-dependent and live in `tenantConfig.partner_compensation`. Your partner manager owns those numbers; the engine just routes them. That's the system. Use it. The customers who notice you used it are the same ones who notice when you didn't — and they'll choose the team that's organized.

Deal registration

Knowledge check