update-fundraising
Updates an existing fundraising record in the Carta CRM. Use this skill when the user says things like "update a fundraising", "edit fundraising", "update fundraising details", "change fundraising stage", "update fundraising fields", or "/update-fundraising". Accepts a fundraising ID or name (will search if no ID provided). Only the fields explicitly provided are changed — all other fields are left untouched.
What this skill does
## Overview
Partially update an existing fundraising. Only fields provided are modified — this is
a partial update, not a replacement. First resolve the fundraising ID, collect what to
change, then call the update tool.
## Step 1 — Resolve the fundraising ID
If the user provided a fundraising ID directly, use it and skip to Step 3.
If only a name or keyword was given, search first:
```
mcp__carta_crm__search_fundraising({ query: "<name>", limit: 10 })
```
If multiple fundraisings match, present the list and ask the user to confirm which one
to update (show name and ID for each).
## Step 2 — Collect what to update
Ask the user what they want to change:
- **name** — fundraising round name
- **stageId** — move to a different stage (call `get_fundraising_stages` to resolve name → ID)
- **fields** — custom field values keyed by field ID
If the user wants to update custom fields but isn't sure of field IDs, fetch the schema first:
```
mcp__carta_crm__get_fundraising_custom_fields()
```
**Important:** Only include fields that are explicitly being changed. Omit everything else.
## Step 3 — Update the fundraising
Call:
```
mcp__carta_crm__update_fundraising({
id: "<fundraising id>",
name: "<updated name>",
stageId: "<stage id>",
fields: {
"<field_id>": "<value>"
}
})
```
Omit any key that is not being updated.
## Step 4 — Report result
On success, respond with a summary of what changed:
> "Fundraising **{name}** updated (ID: `{id}`). Changed: [list of changed fields]"
On error, show the error message and suggest:
- Verify the fundraising ID is correct — run `/search-fundraisings` to find it
- Check that stage IDs are valid — run `get_fundraising_stages` to list options
- Check that custom field IDs are valid
## Updating multiple fundraisings
If the user wants to apply the same change to multiple fundraisings, repeat Steps 1 and 3–4
for each. Summarize at the end:
> "Updated N fundraisings: [list of names]"
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.