Closed-lost & win-loss analysis

The problem

The closed-lost reason a rep types into the CRM is rarely the real one. The signal that explains a lost deal sits across support tickets, product usage, finance and call notes, and nobody has time to stitch it together for every deal.

Built from Rig's building blocks

Rig is not a fixed template. It is a set of building blocks, and this app is one way to assemble them. Take what you need, then shape the workflow around your own pain.

How to build it

1. 1

   Connect your deal data

   Point Rig at your CRM and the systems that hold the rest of the story, support, billing and product usage. Rig syncs them into one governed layer, no pipeline to build.

2. 2

   Model what a deal is

   In the context layer, join opportunities to their accounts, tickets, invoices and usage so Claude reasons over the full deal, not just the CRM record.

3. 3

   Score every lost deal

   Build a workflow that classifies each closed-lost deal against the real blockers (price, timing, champion, product gap) and writes the reason back.

4. 4

   Make it self-serve

   Publish a win/loss dashboard and let reps ask 'why did we lose Acme?' in Claude. Tune the blockers to your own sales motion, it is your workflow, not a fixed template.