PromptBase
PromptBase SelectGet Select
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
Chat - (gpt-6.1-sol)
Token size
516
Example input
[CALL_TRANSCRIPT]: We run a small design agency. The buyer says projects are often re-scoped after kickoff and the team spends too much time on revisions. They want a clearer intake and approval gate before production. Next intake cycle is soon, but no exact date was given. [OFFER_AND_DELIVERY_MODEL]: Brand and web design delivered through a small agency team; work starts after an approved brief. [IDEAL_CUSTOMER_PROFILE]: Founder-led startups and small B2B companies that need brand or web design. [BUYING_CONTEXT_AND_ALTERNATIVES]: The current alternative is informal email feedback and ad hoc approvals. [DESIRED_NEXT_STEP]: Agree on a one-page brief and test the approval workflow on the next project.
Example output
## Executive brief The prospect runs a design agency and wants a more consistent way to scope projects before work begins. They described revisions and unclear ownership as the main source of margin pressure. The desired outcome is a reusable intake and approval process. The transcript confirms the pain and desired outcome, but budget, decision authority, timeline, and success metric were not discussed. ## Buyer language and desired outcome - Problem: projects are frequently re-scoped after kickoff. - Desired future state: a clear brief and approval gate before production. - Impact mentioned: unplanned revisions reduce margin. - Quote: “We lose time when the brief keeps changing.” ## Qualification signals | Signal | Evidence | Confidence | What to verify | |---|---|---|---| | Pain | Re-scoping causes revisions | High | Frequency and cost per project | | Urgency | Wants a process for the next intake cycle | Medium | Exact start date | | Authority | Not discussed | Low | Who approves process changes | | Budget | Not discussed | Low | Budget range and buying process | | Success criteria | Fewer revisions | Medium | Target reduction and measurement | ## Objections, risks, and proof required Risk: a new process may feel slower to creatives. Proof required: a short intake template and a pilot on one project. ## Recommended follow-up Subject: A lighter approval gate for the next project Thanks for explaining how changing briefs create extra revisions. I suggest we map the next intake into a one-page brief and approval step, then test it on one project. Would you be open to reviewing that workflow this week? ## Next-call plan 1. How often does scope change after kickoff? 2. Who owns final approval? 3. What must be in the brief before production? 4. What would count as a successful pilot? 5. When is the next project starting? ## Handoff checklist Sales: confirm authority, budget, and pilot timing. Delivery: draft the one-page brief and approval gate. Customer Success: schedule a pilot review. Open items: authority, budget, exact timeline, revision baseline, success metric.
GPT

Discovery Call Signal Extractor

Add to Cart
PromptBase Select
Get this prompt + 9 more with Select$14 your first month, then $19/mo$14 first month, then $19/mo
View Select
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
GPT-6.1-SOL
Tested icon
Guide icon
4 examples icon
Free credits icon
Turn a discovery-call transcript into a precise sales and delivery brief. Extract the buyer’s own language, business problem, urgency, decision process, objections, proof requirements, and next actions without inventing CRM facts. Built for consultants, agencies, recruiters, and B2B service teams that need better follow-up and cleaner qualification.
...more
Added 20 hours ago
Report
Browse Marketplace