A framework is a map, not a script
A cold-call framework gives you enough structure to open clearly, learn whether the problem is relevant, and ask for a sensible next step. It should not force every prospect through the same speech.
The examples below are starting points. Replace every placeholder with claims you can substantiate, adapt the language to your market, and measure results against your own baseline.
Framework 1: relevant observation
Use this when you have a specific, credible reason for contacting the person.
Structure
- Identify yourself and ask for a brief moment.
- State the observation that made the call relevant.
- Connect it to a problem you understand.
- Ask whether the problem is worth discussing.
Example
“Hi Sarah, this is Marcus at BuildFlow. I saw that your team is expanding its logistics product line. We work with operations teams that need to coordinate more vendors as they launch. Is that something your team is dealing with, or am I off base?”
The value of this opening comes from the observation, not from pretending you know the prospect’s internal situation. A good next question lets them correct your assumption.
Framework 2: problem hypothesis
Use this when you understand a role or industry but do not have company-specific information.
Structure
- Explain why this role is relevant to your work.
- Offer one problem as a hypothesis.
- Ask whether it matches their experience.
- Explore before introducing your solution.
Example
“Hi David, this is Jessica at CloudPath. I speak with compliance teams that are trying to reduce manual audit work. Is that a priority for you this quarter, or is your process already where you need it to be?”
This is deliberately easy to reject. If the hypothesis is wrong, acknowledge it and move on. If it is partly right, ask how the problem shows up before pitching.
Framework 3: genuine referral
Use this only when someone actually suggested the introduction and you have permission to name them.
Structure
- Identify yourself.
- Name the referrer and the reason they suggested contact.
- Confirm the context rather than assuming it.
- Ask for the next appropriate conversation.
Example
“Hi Marcus, Elena from LogicFlow. Michael Brennan suggested I contact you because you are reviewing reporting infrastructure. Is that project still active? If it is, I can explain where we may fit and you can decide whether a longer conversation makes sense.”
The referral establishes relevance; it does not give permission to overstate the relationship or skip discovery.
Questions that improve any opening
- “Am I off base?” gives the prospect a low-friction way to correct you.
- “How are you handling that today?” moves from hypothesis to current state.
- “What would have to change for this to become a priority?” clarifies timing.
- “Who else is affected by that?” helps map the problem without forcing a meeting.
- “Would a separate conversation be useful?” creates a clear next step.
Follow up without inventing a formula
There is no universal sequence that fits every market. Decide in advance how many attempts are appropriate for your audience, vary the time and channel, and make each message add context rather than merely repeat “checking in.” Respect opt-outs and any rules that apply to commercial outreach.
Track at least:
- attempts;
- conversations reached;
- relevant problems confirmed;
- next steps accepted; and
- reasons people decline.
Compare one opening with another over enough calls to learn from your own environment. Do not copy a benchmark from a different product, region, or buyer and treat it as a promise.
Use Cinder with a framework
Cinder can support a framework without forcing you to read it word for word. On-Demand analysis is available on every plan for user-triggered help. Starter and Pro add Continuous Coaching, and Pro adds Script Assist for following an adaptive script during the call.
No Cinder participant bot joins the call. You remain responsible for any notice and consent required for transcription or coaching. See how live coaching works or download Cinder.