Library › Sales AI › Revenue operations
Build a deal risk register in JSON using only allowed risk types
- For Revenue operations
- You practice Asking for a format you can use
- Time about 5 minutes
- Level Advanced
About this exercise
Convert the deal notes into one fenced JSON array with one object per deal, one object per line. Keys: deal (string), amount_k (number, no quotes), risk_type (one of legal, budget, champion, competitor, timing, using the first risk named in the note), owner (string). At most 6 non-empty lines inside the code block and at most 10 words outside it.
Common mistakes when you ask AI for this
- Quoting numbers. The AI writes "180" as a string. Try: Add: "amount_k is a number, no quotes."
- Using other risk types. The AI writes people or money from the old register. Try: Add: "Use only legal, budget, champion, competitor, timing."
- Picking the wrong risk. The AI chooses the most severe. Try: Add: "Use the first risk named in each note."
- Pretty-printed JSON. The AI spreads each object over many lines. Try: Add: "One object per line, at most 6 lines."
What a strong prompt includes
- Names the keys
- Fixes types
- Lists the allowed values
- Uses the first risk
- Limits lines
Related exercises
- Accept the buyer's counteroffer on three stated conditions (Sales AI · Sales and customer success)
- Adapt one ad image to 3 sizes with Midjourney (Image & Video AI · Marketing and content)
- Age open requisitions as of today and flag the old ones (Finance AI · FP&A and financial analysts)
- Announce a discount-approval process change in three bullets (Sales AI · Managers and team leads)
- Announce a new win in Slack without revealing the price (Sales AI · Sales and customer success)