Prompt Details
Model
Chat - (gpt-5.6)
Token size
602
Example input
[PRODUCT OR SERVICE AND SALES CONTEXT]: a $2,800 per month managed cybersecurity service for small and medium businesses including 24/7 monitoring endpoint protection and incident response sold through a 2-call process to business owners and IT managers
[TARGET PROSPECT AND THEIR SITUATION]: business owners and IT managers at companies with 20-150 employees who know cybersecurity is important but feel overwhelmed by technical complexity and have been exposed to fear-based messaging from multiple vendors
[SALES PROCESS AND BIGGEST CHALLENGE]: 2-call discovery and solution presentation process with the biggest challenge being prospects agree the risk is real but hesitate at the price point and often say let me think about it before going completely silent
Example output
Below is a complete, consultative sales system tailored to your $2,800/month managed cybersecurity service. The central strategy is to avoid selling fear and technical complexity. Instead, sell clarity, appropriate protection, reduced operational risk, and a clear decision framework.
1. SALES STRATEGY AND FRAMEWORK
Recommended methodology: Consultative SPIN + Challenger + Mutual Action Plan
Use three complementary approaches:
SPIN Selling for discovery
Situation → understand the environment.
Problem → uncover vulnerabilities and uncertainty.
Implication → quantify the business consequences.
Need-payoff → help the prospect articulate the value of solving the problem.
Challenger principles for positioning Your prospects have already heard plenty of cybersecurity fear messaging. Differentiate by teaching them something useful rather than increasing anxiety.
Core insight:
> "The goal isn't to buy the most cybersecurity possible. It's to make sure the level of protection matches the level of business risk."
Mutual Action Plan for closing The "let me think about it" followed by silence problem usually begins before the close. Call 1 and Call 2 should establish a clear decision process, stakeholders, timeline, and next step before a proposal is presented.
---
Buyer journey mapping
Stage Prospect mindset Sales objective
Unaware/Reactive "We're probably okay." Create awareness without fear
Problem-aware "Cybersecurity is complicated." Simplify the decision
Solution-aware "What type of protection do we need?" Establish your framework
Vendor evaluation "Why you, and why $2,800/month?" Differentiate on outcomes
Decision "Is this worth doing now?" Resolve financial and commitment risk
Post-sale "Did we make the right decision?" Reinforce value and confidence
---
Core value proposition
Use this positioning:
> "We help growing businesses with 20 to 150 employees get enterprise-grade cybersecurity management without needing to become cybersecurity experts or build an expensive internal security team. We continuously monitor, protect, and respond so you have a clear level of protection against the risks that matter to your business."
Shorter version:
> "We turn cybersecurity from something you have to constantly worry about into something professionally managed."
---
Competitive differentiation approach
Do not say:
> "We're better than other cybersecurity providers."
Instead:
> "There are plenty of companies that can sell security tools. The more important question is who is continuously accountable for making sure those tools are actually protecting your business."
Position against three alternatives:
Alternative 1: Do nothing or remain reactive
> "The issue with reactive security is that the first time you discover whether your protection was sufficient may be during an incident."
Alternative 2: Buy multiple tools
> "More tools don't automatically create more security. Someone still needs to monitor them, interpret what they're detecting, and respond when something requires action."
Alternative 3: Hire internally
> "For most companies your size, building 24/7 security coverage internally can be disproportionately expensive compared with using a specialized managed team."
---
Sales cycle optimization strategy
Your biggest issue is likely not the closing technique.
It is decision ambiguity.
By the end of Call 1, you should know:
1. Why they are considering cybersecurity now.
2. What happens if they don't improve their protection.
3. Who makes the decision.
4. What financial criteria they use.
5. What alternatives they are considering.
6. When they want a decision made.
7. What must be true for them to move forward.
Before Call 2, establish:
> "If the solution we show you addresses the concerns we discuss today, are you comfortable using our next conversation to make a decision on whether moving forward makes sense?"
This does not force a purchase. It prevents Call 2 from becoming an information-gathering session with no decision process.
---
KPIs
Track:
Discovery
Discovery-to-presentation rate
Percentage of calls with identified decision process
Percentage with quantified business impact
Percentage with confirmed decision timeline
Presentation
Presentation-to-close rate
Objection rate by category
"Think about it" rate
Proposal acceptance rate
Follow-up
Response rate
Days from presentation to decision
Ghosting rate
Closed-lost reason
A critical KPI:
> Percentage of prospects who leave Call 2 without a scheduled decision conversation.
Your target should be close to zero.
---
2. DISCOVERY CALL SCRIPT
Opening and rapport — approximately 5 minutes
Call opener
> "Hi [Name], thanks for taking the time today. I'm looking forward to learning more about your business and understanding how you're currently thinking about cybersecurity."
> "My goal isn't to overwhelm you with technical information or try to convince you that you need every security product available. I want to understand your environment, where you feel confident, where you have uncertainty, and whether there's actually a gap that makes sense for us to help with."
---
Permission-based agenda
> "I was thinking we could spend the first part learning about your business and current environment, then talk about how you're currently handling cybersecurity and what concerns you have. If it looks like there's a meaningful fit, I'll explain how we could potentially help and we can decide whether a second conversation makes sense."
> "Does that work for you?"
Then ask:
> "And is there anything specific you want to make sure we cover today?"
---
Rapport questions
1. "How has the business been growing recently?"
2. "What are the biggest technology or operational priorities for the company this year?"
3. "How did cybersecurity become something you wanted to look at right now?"
The third question is especially important because it reveals the buying trigger.
---
Discovery and qualification — approximately 20 minutes
A. Situation questions
1. "Can you give me a quick picture of the business—approximately how many employees and devices are you responsible for?"
2. "How is your IT environment currently managed?"
3. "Who is responsible for cybersecurity today?"
4. "What security tools or protections do you currently have in place?"
5. "When there is a potential security issue, how does your team currently identify and respond to it?"
Avoid interrogating. Use follow-ups:
> "Tell me more about that."
> "How confident are you in that process?"
> "How often does that actually get reviewed?"
---
B. Problem identification questions
1. "What parts of cybersecurity feel most uncertain or difficult for your team right now?"
2. "Are there areas where you know you have protection but aren't completely sure how well it's actually being monitored?"
3. "How confident are you that a serious threat would be detected quickly?"
4. "What would happen if your internal IT person or external provider was unavailable when a security incident occurred?"
5. "Have you ever had a situation where something happened and you weren't sure whether it was a genuine security threat?"
Then summarize:
> "It sounds like you have some protections in place, but the bigger question isn't whether you have tools. It's whether someone is continuously watching, validating, and responding when something happens. Is that fair?"
---
C. Implication questions
These questions create urgency through business consequences—not fear.
1. "If a serious incident disrupted operations for several days, what would the impact be on the business?"
2. "What would an incident potentially mean for your customers or your reputation?"
3. "If sensitive information were compromised, who would need to become involved internally?"
4. "What does it cost the business today when leadership or IT has to spend time worrying about issues outside their core responsibilities?"
Then:
> "I'm not asking these questions to create a worst-case scenario. I'm trying to understand the level of risk so that we can determine whether the investment in additional protection is actually justified."
---
D. Need-payoff questions
1. "If you had a team monitoring your environment around the clock and responding to legitimate threats, what would that change for your team?"
2. "How valuable would it be to have a clear answer to the question, 'Are we adequately protected for a company our size?'"
3. "Would having a defined incident response process give you more confidence than relying on people figuring things out when something happens?"
4. "If cybersecurity became something professionally managed rather than something you periodically worried about, where would that free up your IT team or leadership?"
---
Budget and authority qualification
Decision-maker question
> "When companies like yours make a decision about a service like this, who else besides you normally needs to be involved?"
Follow with:
> "Who ultimately has the authority to approve the investment?"
Budget question
Do not ask:
> "What's your budget?"
Instead:
> "I want to be respectful of your time. Services in this category can vary significantly depending on the level of coverage. How are you thinking about the financial investment required to address this?"
If they resist:
> "That's completely fair. Another way to approach it is: if you found a solution you believed was genuinely appropriate for the business, what would you use to determine whether the monthly investment was justified?"
Then establish price context before Call 2:
> "Based on what you've shared, our managed service is typically around $2,800 per month. Before we go further, does that sound like a range that could potentially make sense if the service addressed the issues we've discussed?"
This prevents the price surprise on Call 2.
---
Next step and close — approximately 5 minutes
Summary and pain reflection
> "Let me make sure I've understood everything correctly."
> "You currently have [CURRENT SITUATION]. The main concerns are [CONCERN 1], [CONCERN 2], and [CONCERN 3]."
> "The biggest uncertainty isn't necessarily whether you have security tools. It's whether your current level of monitoring and response is sufficient if a genuine incident occurs."
> "And ideally, you'd like [DESIRED OUTCOME]. Did I capture that accurately?"
---
Solution teaser
> "Based on what you've described, I believe there may be a fit. Rather than giving you a generic cybersecurity presentation, the next conversation would focus specifically on how we would address the gaps and concerns you've identified."
---
Scenario 1: Strong fit
> "I suggest we schedule a solution session where I'll walk you through the specific protection model, what monitoring and response would look like, and the investment."
> "At the end, we can decide together whether it makes sense to move forward. Fair?"
---
Scenario 2: Additional stakeholder needed
> "Because [STAKEHOLDER] will be involved in the decision, I'd recommend including them in the next conversation so we're not asking you to translate technical or business details afterward."
> "Would it make sense to schedule the solution session when they can join?"
---
Scenario 3: Prospect needs time
> "That makes sense. Before we schedule anything, what information or confidence would you need before feeling ready to evaluate a solution?"
Then:
> "Let's make the next conversation specifically about answering those questions rather than giving you a generic presentation."
---
3. DEMO AND PRESENTATION SCRIPT
Opening framework — approximately 3 minutes
Agenda confirmation
> "Thanks for joining again. Based on our last conversation, I want to make sure today's discussion stays focused on what matters to you."
> "I suggest we do three things: first, briefly recap what we learned; second, show you how our service addresses those specific concerns; and third, discuss whether the investment and timing make sense."
> "If it looks like a fit, we can discuss moving forward. If it doesn't, we should be comfortable saying that too. Does that agenda work?"
---
Expectation setting
> "You mentioned previously that cybersecurity can feel complicated and that you've heard a lot of fear-based messaging."
> "My goal today is the opposite. I want you to leave with a clear understanding of what protection you need, what you don't necessarily need, and whether we're the right partner."
---
Presentation body
Problem acknowledgment
> "Last time, you told me that [PAIN]."
> "The challenge isn't simply buying more security. The challenge is having the right level of protection and knowing that someone is accountable for monitoring and responding."
---
Solution walkthrough
Use this sequence:
1. Protect
> "First, we focus on reducing the likelihood that a threat can successfully compromise the environment."
2. Monitor
> "Second, we continuously monitor for activity that requires attention rather than relying on someone manually checking systems."
3. Respond
> "Third, when something requires action, our team follows an established response process rather than leaving your business to figure it out during a stressful situation."
4. Communicate
> "You also have visibility into what's happening, so cybersecurity doesn't become a black box."
---
Feature-to-benefit translation
Feature Do not say only Translate to
24/7 monitoring "We monitor 24/7." "Potential threats don't have to wait until your IT team is working."
Endpoint protection "We deploy endpoint software." "Every managed device has an additional layer of protection."
Incident response "We provide incident response." "You have a defined response capability when an incident requires action."
Managed security team "You get access to experts." "You don't have to hire and manage a full internal security operation."
Continuous oversight "We manage your environment." "You have ongoing accountability instead of periodically wondering whether your protection is still adequate."
---
ROI and value calculation
Do not promise a precise financial ROI unless you can substantiate it.
Use a risk-and-cost framework:
> "Let's look at the investment in business terms."
> "$2,800 per month is $33,600 annually."
Then:
> "The question isn't whether we can predict exactly what an incident would cost. The question is whether reducing the likelihood and potential impact of a serious security incident is worth $33,600 annually to this business."
Explore:
Downtime costs
IT response costs
Recovery costs
Leadership distraction
Customer impact
Potential lost revenue
Script:
> "If a significant incident caused [X] days of disruption, involved your IT team and external specialists, and distracted leadership, would the potential cost and disruption be materially greater than the annual investment?"
Let them answer.
---
Case study story — approximately 2 minutes
Use a real, anonymized, or clearly hypothetical example.
> "Let me give you an example of the type of situation this service is designed for."
> "A business similar in size to yours had basic security tools, but no one was continuously monitoring the environment. A suspicious activity pattern occurred outside normal working hours."
> "Because the activity was identified and investigated quickly, the response process could begin before the situation developed into a larger operational disruption."
> "The important lesson wasn't that a single security tool saved the company. It was that detection alone wasn't enough. There needed to be monitoring, human investigation, and a response process."
Then:
> "That's the difference we're trying to provide: not simply more technology, but managed accountability."
---
Closing the demo — approximately 7 minutes
Check-in and objection surfacing
Ask:
> "Based on everything we've discussed, what feels most compelling to you?"
Then:
> "And where do you still have questions or reservations?"
Pause.
Then ask the critical question:
> "What would prevent you from feeling comfortable moving forward?"
---
Next-step proposal
If positive:
> "Based on what you've told me, I believe this addresses the gaps you were concerned about."
> "The investment is $2,800 per month."
> "Does moving forward feel like the right decision?"
Then remain silent.
---
Timeline and urgency
Avoid artificial urgency.
> "I'm not going to tell you that you need to be afraid or manufacture a deadline."
> "But I do think there is a legitimate question: now that you've identified the gap, what is your preferred timeline for addressing it?"
If they say "later":
> "What specifically would need to happen between now and then for this to become a priority?"
---
4. OBJECTION HANDLING LIBRARY
1. "It's too expensive."
Acknowledge
> "I understand. $2,800 per month is a meaningful investment."
Clarify
> "When you say expensive, are you comparing it with another option, or are you unsure whether the value justifies the investment?"
Reframe
> "That distinction matters. We shouldn't expect you to invest simply because cybersecurity is important. The question is whether the level of risk and responsibility we've identified justifies professional management."
Confirm
> "Does that address the concern, or is there another financial issue we should discuss?"
Advance
> "If the investment made sense financially, would you be comfortable moving forward?"
---
2. "Let me think about it."
> "Absolutely. Usually when someone says they want to think about it, they're thinking about something specific."
> "What are the main things you want to think through?"
Then:
> "Let's talk through those now so I don't leave you with unanswered questions."
---
3. "We already have an IT provider."
> "That makes sense. I'm not assuming they aren't doing a good job."
> "How are they currently handling continuous security monitoring and incident response?"
Then:
> "If they're covering those areas effectively, we may not be necessary. If there are gaps, we can determine whether we complement their capabilities."
---
4. "We already have security software."
> "That's good. Having tools is an important foundation."
> "Who is responsible for continuously monitoring alerts and responding when something suspicious happens?"
Reframe:
> "The difference isn't necessarily tools versus no tools. It's whether those tools are being actively managed."
---
5. "We're too small to be a target."
> "I understand why you would think that."
> "When you say 'target,' do you mean you believe an attacker would specifically choose your company?"
Reframe:
> "Many security incidents are opportunistic rather than personally targeted. The more useful question is whether your systems could be affected if an automated or broad attack encountered them."
---
6. "We've never had an incident."
> "That's good, and hopefully that continues."
> "How do you currently determine whether you've never experienced an incident versus whether an incident simply wasn't detected?"
Pause.
> "I'm not suggesting you have a hidden problem. I'm asking how confident you are in your visibility."
---
7. "We need to compare other vendors."
> "You absolutely should compare options."
> "What criteria will you use to make the comparison?"
Help define:
Coverage
Monitoring
Response
Accountability
Communication
Cost
Then:
> "Would it be helpful if I gave you a comparison framework so you can evaluate providers consistently?"
---
8. "I need approval."
> "Of course. Who needs to approve it?"
Then:
> "What do you think their biggest questions will be?"
Prepare together.
---
9. "Send me information."
> "Happy to. To make sure I send something useful, what information are you hoping will help you make a decision?"
Then:
> "Would it make sense to schedule 15 minutes after you've reviewed it so we can discuss your questions?"
---
10. "The timing isn't right."
> "I understand. What specifically is making the timing difficult?"
Determine:
Cash flow
Competing priorities
Staffing
Contract timing
Then:
> "When do you expect those conditions to change?"
---
11. "We can't afford it right now."
> "I appreciate your honesty."
> "Is the issue that the service isn't valuable enough to justify the investment, or is it purely a cash-flow and budget timing issue?"
Those require different solutions.
---
12. "We need to discuss internally."
> "That makes sense."
> "What do you expect the internal discussion to focus on?"
Then:
> "Would it help if we included everyone who needs to evaluate it in one conversation?"
---
13. "I'm worried about changing providers."
> "That's completely reasonable. Changing something connected to your IT environment creates concern."
> "What specifically feels risky about the transition?"
Then explain your actual onboarding process rather than making generic assurances.
---
14. "How do I know we really need this?"
> "That's probably the most important question."
> "Based on what you've shared, which risks concern you most—and which ones don't?"
Then:
> "If we concluded your existing protection is sufficient, I would rather tell you that than sell you something unnecessary."
This builds trust.
---
15. "I'll get back to you."
> "That's fine. Before we leave it open-ended, when do you realistically expect to have a decision?"
If they give a date:
> "Would it be useful to put a brief follow-up on the calendar now?"
If they won't:
> "That's okay. Is there something unresolved that makes committing to a timeline difficult?"
---
5. CLOSING SCRIPT COLLECTION
1. Assumptive close
> "Based on what we've discussed, the next step would be to begin onboarding and schedule the implementation process. Would you prefer to start [OPTION A] or [OPTION B]?"
Use only after clear buying signals.
---
2. Alternative-choice close
> "There are really two reasonable paths: continue with the current approach and accept the existing level of uncertainty, or move forward with managed monitoring and response."
> "Which approach feels more appropriate for the business?"
---
3. Summary close
> "You came into this conversation because [TRIGGER]."
> "You told me the biggest concerns were [PAIN 1] and [PAIN 2]."
> "We've shown how the service addresses those concerns."
> "Given everything we've discussed, does moving forward make sense?"
---
4. Ethical urgency close
> "I don't believe in creating artificial deadlines."
> "But now that you've identified a gap between your current protection and the level of confidence you want, what is the reason for delaying?"
Then:
> "If there's a legitimate reason, let's discuss it. If there isn't, we should probably make a clear decision rather than leaving the issue unresolved."
---
5. Trial close and commitment ladder
Trial close
> "On a scale from 1 to 10, how confident are you that this is the right solution?"
If they say 7:
> "What would need to happen to move from a 7 to a 9?"
Commitment ladder
1. "Does the problem need to be addressed?"
2. "Do you agree that continuous monitoring is valuable?"
3. "Does our approach address the gaps you identified?"
4. "Is the investment potentially reasonable?"
5. "What would prevent us from moving forward?"
---
6. FOLLOW-UP AND NURTURE SCRIPTS
Post-discovery follow-up email
Hi [Name],
Thank you again for taking the time to speak with me today.
My understanding of your current situation is that:
- You currently have [CURRENT PROTECTION].
- The main areas of concern are [CONCERN 1], [CONCERN 2], and [CONCERN 3].
- The biggest goal is to create greater confidence that potential threats are being continuously monitored and appropriately addressed.
Based on our conversation, I believe our managed cybersecurity service may be able to help by providing 24/7 monitoring, endpoint protection, and incident response without requiring your team to build and manage those capabilities internally.
As discussed, the investment is approximately $2,800 per month.
For our next conversation, I'll focus specifically on how the service would address the priorities you identified rather than giving you a generic technical presentation.
Looking forward to speaking on [DATE].
Best,
[Your Name]
---
Proposal follow-up sequence
Email 1 — immediately after presentation
Hi [Name],
Thank you for the conversation today.
The main priorities we discussed were:
- [PRIORITY 1]
- [PRIORITY 2]
- [PRIORITY 3]
Our proposed approach is designed to address those areas through continuous monitoring, endpoint protection, and incident response for an investment of $2,800 per month.
The most important question is not simply whether cybersecurity matters—we both agree that it does—but whether this level of managed protection is the right investment for your business at this stage.
You mentioned that you wanted to [DECISION PROCESS/NEXT STEP]. Let's reconnect on [DATE] to discuss your decision and answer any remaining questions.
Best,
[Your Name]Email 2 — 3 to 5 days later
Hi [Name],
I wanted to follow up on our conversation.
Usually, when companies reach this stage, the remaining question tends to fall into one of three areas:
1. Whether the current approach is sufficient
2. Whether our service provides enough additional value
3. Whether the timing and investment make sense
Which of those is most relevant to your situation right now?
If there's something else, I'm equally happy to discuss that directly.
Best,
[Your Name]Email 3 — decision-oriented
Hi [Name],
I wanted to close the loop on our discussions.
Based on what you've shared, I believe we could help address the cybersecurity concerns you identified. At the same time, I don't want to keep following up if the timing or investment isn't right.
Would you prefer to:
1. Move forward with the next step
2. Revisit the discussion at a later date
3. Close this out for now
Any of those answers is completely fine—I would simply appreciate knowing where things stand.
Best,
[Your Name]
---
Ghosted prospect re-engagement
Script 1: Direct
> "Hi [Name], I haven't heard back, so I wanted to check whether cybersecurity is still a priority or whether something changed internally."
Script 2: Insight-based
> "Hi [Name], I've been thinking about our previous conversation. You mentioned that the biggest challenge wasn't understanding that cybersecurity mattered—it was knowing how much protection was actually appropriate. Has your thinking on that changed since we spoke?"
Script 3: Close-the-file
> "Hi [Name], I'll assume the timing isn't right and close the loop on my side for now. If cybersecurity becomes a priority again, feel free to reach out."
---
Voicemail scripts
1. Post-discovery
> "Hi [Name], this is [Name] from [Company]. I wanted to thank you for our conversation and follow up on the priorities you shared around [ISSUE]. I'll send you a brief email as well. I look forward to our next conversation."
2. After proposal
> "Hi [Name], this is [Name]. I'm following up on our discussion about your cybersecurity priorities and the proposed managed service. No need to call back if email is easier—I mainly wanted to see what questions have come up as you've considered the decision."
3. No response
> "Hi [Name], this is [Name]. I've tried reaching you a couple of times, so I wanted to leave one final message rather than continue following up unnecessarily. If the timing isn't right, that's completely fine. If there's still something you'd like to discuss, I'm happy to help."
4. Scheduled decision call reminder
> "Hi [Name], this is [Name]. Just a quick reminder about our scheduled conversation on [DATE/TIME]. My goal is simply to answer any remaining questions and help you make a clear decision either way."
---
LinkedIn follow-up messages
1. After discovery
> Hi [Name], great speaking with you today. I appreciated learning more about how you're currently thinking about cybersecurity. Looking forward to continuing the conversation.
2. Value follow-up
> Hi [Name], one thought from our conversation stayed with me: the biggest challenge for many businesses isn't a lack of security tools—it's knowing whether someone is actively monitoring and responding when those tools detect something. Thought that might be useful as you evaluate your options.
3. Re-engagement
> Hi [Name], just wanted to reconnect. We previously discussed [TOPIC], and I wasn't sure whether it's still a priority for you. No pressure either way—just thought I'd check in.
---
The most important change to your current sales process
Your highest-leverage improvement is this:
Do not end Call 2 with "What do you think?" and wait for the prospect to decide later.
Instead, establish the decision process on Call 1 and use Call 2 to answer the question:
> "Based on everything we've learned, is this a problem worth solving with us now?"
When a prospect says, "Let me think about it," don't treat it as the end of the conversation. Treat it as a signal that an unresolved concern still exists.
Your job is not to pressure them into removing that concern. Your job is to identify it clearly enough that both of you can make an informed decision.
By purchasing this prompt, you agree to our terms of service
GPT-5.6
An AI-powered sales script meta prompt designed to help salespeople and business owners create complete, high-converting sales scripts — covering discovery calls, demo presentations, objection handling, closing techniques, follow-up scripts, and voicemail frameworks for any B2B or B2C sales situation.
...more
Added over 1 month ago
