ChatGPT Plugin

Derail the Pitch™ Copilot

Know if you can win the pitch

Brand: Joel Pilger

Category: Pending
Primary Subcategory: Pending

Integration details

Description

Derail the Pitch Copilot helps creative studio founders find out whether they're the favorite or just filler before spending weeks on a competitive pitch. It counts red flags and green lights, and helps founders reshape the opportunity or walk away. Signed-in Forum members get full coaching that uses their studio's Centerfile. Without signing in, it runs in a limited diagnostic mode. A Forum AI Copilot by Joel Pilger.

Integration type: Plugin
Verification status: Not applicable
Platform: ChatGPT
Category: Pending
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Joel Pilger
Access: Account required
First tracked: 2026-11-13
Tool count: 40
Market: US

AgentDiscoChatGPT Plugin Discovery Score

ChatGPT organic discovery is live

Not discoverable in ChatGPT yet

ChatGPT now suggests Plugins on its own when they match a user's request, but not every Plugin is being surfaced yet.We haven’t seen Derail the Pitch™ Copilot suggested yet. Sign up and we’ll track it, and your Discoverability Score will appear here once ChatGPT starts surfacing it.

ChatGPT recommends Airtable when a user asks it to update a CRM. — ChatGPT surfaces Airtable because it matches the user's request.

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Derail the Pitch™ Copilot has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

40 tools agents can invoke

Attach one or more existing pipeline entries (leads) to a lead room Joel Pilger API POST /api/v1/lead-rooms/{id}/pipeline-entries.
Session details (Clerk id + local user when resolved) Joel Pilger API GET /api/v1/auth/me.
Create a new Centerfile (Centerfile Copilot sync) Called by the Centerfile Copilot GPT after the user confirms a draft. `content` is a free-form JSON object whose keys are v3.0 section names. Sales Scout stores it opaquely. Joel Pilger API POST /api/v1/me/centerfiles.
Create a new lead (pipeline entry) Structured write. Scout MUST confirm the payload with the user before calling. Resolve `ownedByUserId` via GET /pipeline/assignable-users. Enum values are case-sensitive. Joel Pilger API POST /api/v1/pipeline.
Create a lead room (with initial pipeline entries and optional linked chats) Joel Pilger API POST /api/v1/lead-rooms.
Add a checklist task to a lead room Joel Pilger API POST /api/v1/lead-rooms/{id}/tasks.
Log a GPT chat (ChatGPT URL) against a lead room Joel Pilger API POST /api/v1/lead-rooms/{id}/linked-chats.
Check the user's CRM connection status (call before other crm_* tools) Returns the active CRM connection (or null when the user has not connected a CRM). If null or status is not CONNECTED, tell the user to connect their CRM in Sales Scout → Settings → CRM Integrations, and do not call other crm_* tools. Joel Pilger API GET /api/v1/crm/connection.
Create a note in the CRM (preview + confirm first) Joel Pilger API POST /api/v1/crm/notes.
Create a CRM record with full fields (preview + confirm first) Never name-only when more context exists. Resolve companyId, primaryContactId, pipelineId, stageId, ownerId first. Pass full CrmWriteFields. Optional note+task on the same create. Preview exact JSON, one yes, then call. Joel Pilger API POST /api/v1/crm/records.
Create up to 10 CRM records in one call (one preview, one confirm) Bulk create (max 10). Preview items[] once, one yes, then call once. Resolve/create companies first so people include companyId. Partial success — do not retry ok indexes. Joel Pilger API POST /api/v1/crm/records/batch.
Create a task in the CRM (preview + confirm first) Joel Pilger API POST /api/v1/crm/tasks.
List activities on a CRM record Joel Pilger API GET /api/v1/crm/records/{entityType}/{id}/activities.
List notes on a CRM record Joel Pilger API GET /api/v1/crm/records/{entityType}/{id}/notes.
Retrieve a single CRM record (company, person, lead, opportunity) Joel Pilger API GET /api/v1/crm/records/{entityType}/{id}.
List tasks on a CRM record Joel Pilger API GET /api/v1/crm/records/{entityType}/{id}/tasks.
List CRM pipelines and their stages Joel Pilger API GET /api/v1/crm/pipelines.
List CRM pipeline stages (optionally filtered by pipelineId) Joel Pilger API GET /api/v1/crm/stages.
List CRM users (resolve ownerId for creates/updates) Returns CRM users so you can set fields.ownerId by name/email. Always resolve owner before creating an opportunity or assigning a person. Joel Pilger API GET /api/v1/crm/users.
Search CRM companies Joel Pilger API GET /api/v1/crm/companies.
Search CRM leads (may be unsupported by some providers → 400) Joel Pilger API GET /api/v1/crm/leads.
Search CRM opportunities (deals) Joel Pilger API GET /api/v1/crm/opportunities.
Search CRM people (contacts) Joel Pilger API GET /api/v1/crm/people.
Update allowed fields on a CRM record (additive; preview + confirm first) Canonical CrmWriteFields only. Opportunity: stageId, pipelineId, monetaryValue, status, closeDate, ownerId. Person: title, email, phone, companyId, linkedinUrl, details. Preview exact fields; one yes/no before calling. Joel Pilger API PATCH /api/v1/crm/records/{entityType}/{id}.
Get full Centerfile (identity payload for Scout) Joel Pilger API GET /api/v1/me/centerfiles/{id}.
Get full lead room detail Joel Pilger API GET /api/v1/lead-rooms/{id}.
Get one pipeline entry (lead) Joel Pilger API GET /api/v1/pipeline/{id}.
List users who can own a pipeline entry (for resolving ownedByUserId) Always call this before POST /pipeline or before PATCHing `ownedByUserId`. Match on name/email and echo the chosen user to the human — never invent a userId. Joel Pilger API GET /api/v1/pipeline/assignable-users.
List Centerfiles for the user Joel Pilger API GET /api/v1/me/centerfiles.
List lead rooms for the user Joel Pilger API GET /api/v1/lead-rooms.
List GPTs assigned to the user (metadata, URLs) Joel Pilger API GET /api/v1/me/gpts.
List pipeline entries (leads) for the authenticated user Joel Pilger API GET /api/v1/pipeline.
Update a Centerfile (rename and/or replace content) Called by the Centerfile Copilot GPT to push refinements. `content` is replace-all — read the current Centerfile first, merge edits client-side, then PATCH the full object. `name` is renamable on its own. Joel Pilger API PATCH /api/v1/me/centerfiles/{id}.
Rename / re-describe a lead room Joel Pilger API PATCH /api/v1/lead-rooms/{id}.
Replace lead-room notes (append client-side first if you want to keep history) Joel Pilger API PATCH /api/v1/lead-rooms/{id}/notes.
Update a task (rename, complete/uncomplete, reorder) Joel Pilger API PATCH /api/v1/lead-rooms/{id}/tasks/{taskId}.
Update a logged GPT chat entry Joel Pilger API PATCH /api/v1/lead-rooms/{id}/linked-chats/{chatId}.
Update a lead (structured write — exact enums) Joel Pilger API PATCH /api/v1/pipeline/{id}.
Mark a Centerfile as the user's default Joel Pilger API PATCH /api/v1/me/centerfiles/{id}/set-default.
Verify access — invoke on session start and sign-in requests Call first each session and when user asks to sign in or check access. HTTP 401 renders ChatGPT's Sign In button; prose without this call does not. Returns 200 only for ACTIVE provisioned users. Joel Pilger API GET /api/v1/integrations/whoami.

FAQs