SFDC Update

---
name: clay-sf-update
description: >
  Generate a Salesforce opportunity field update for Solange from a call transcript or meeting notes.
  Use this skill whenever Solange asks to update Salesforce, log a call, write next steps for a deal,
  or produce a post-call SFDC note. Triggers include update Salesforce, log this call, write up next
  steps, SFDC update, update the opp, or any request to document a meeting with a prospect or customer
  for CRM purposes.
---

# Clay Salesforce Opportunity Update

Produces a structured, CRM-ready field update from a call transcript or meeting notes.

## Ground Rules

- Always refer to Solange as **"Solange"** (never "you" or "I")
- Use **M/D** date format (e.g., 4/7, not April 7th)
- If info is missing, write **"Not mentioned"** — never guess
- Correct **"Sixth Sense" / "6th Sense"** → **6Sense**
- The **entire Salesforce Update line is hard-capped at 255 characters** (from the date prefix through U, R, and NS combined) — count carefully before finalizing
- Keep U, R, NS tight and skimmable — write for a CRO who has 5 seconds

## Output Format

Produce all six sections below, in this exact order:

---

### Salesforce Update:
`[M/D] SL — U: <update> | R: <risk> | NS: <next steps>`

**Character rules — the entire line above must be ≤255 characters total:**
- U (Update): What happened on the call — key decisions, proposals, stage changes
- R (Risk): What could stall or kill the deal
- NS (Next Steps): Concrete actions + owners
- Because the whole line shares a single 255-char SFDC field, keep U and R tight to leave room for NS

---

### Clay Use Cases (customer wants):
1) One sentence per use case — what the customer explicitly wants to do with Clay
2) One sentence per use case
3) One sentence per use case
*(Add more if needed, delete unused lines)*

---

### Need for Clay
1) **Why Any Solution:** <pain / problem / gap that exists regardless of Clay>
2) **Why Clay:** <why Clay specifically fits>
3) **Why Now:** <urgency / trigger / forcing function / timeline>

---

### Tech Stack (mentioned on call):
- Tool — 2-3 words on what it's used for
- Tool — 2-3 words on what it's used for
*(List only tools explicitly named on the call)*

---

### ROI metrics for using Clay:
<Quantified outcomes, benchmarks, or proof points mentioned. If none, write "Not mentioned.">

---

## Tips

- Pull the most recent Granola call first, then supplement with Gmail/Slack if needed
- Lead the U field with the date and Solange's initials: `4/7 SL —`
- For NS, abbreviate aggressively: "w/" not "with", "&" not "and", acct not account
- If multiple next steps, chain with semicolons: `NS: Hayden to send analysis; SL to send pricing calc; schedule ref call`
- Verify the full Salesforce Update line character count before returning — it must be ≤255 total