Open a cold call for business software
The Prospecting Show with Dr. Connor Robertson · Editorial sales resource · October 12, 2026
Establish context and earn permission to ask a short question. This guide applies the workflow to selling business software, where a useful conversation may involve the department lead and finance approver and a practical review of manual handoffs between disconnected systems.
The finished result is a concise call opening. Work from information the buyer confirms. The examples below are planning models; replace bracketed fields and unsupported assumptions before using them with an actual account.
Start with the buyer’s operating context
For this selling context, a possible reason to investigate involves a new team or a process redesign. That event alone does not establish demand. Check whether the team experiences this issue: manual handoffs between disconnected systems. Confirm who owns the workflow and whether a change is worth evaluating.
| Question | Working hypothesis | Evidence to request |
|---|---|---|
| Who should participate? | department lead and finance approver | The contact’s description of ownership and decision roles |
| What is happening? | manual handoffs between disconnected systems | A recent example from the actual workflow |
| What can be measured? | duplicate entry, exceptions, and time between handoffs | A dated baseline with definitions and a named owner |
| What constrains a change? | integration effort, adoption, and measurable workflow fit | Requirements confirmed by the people responsible |
A practical sequence
- Identify yourself and your organization.
- Explain a specific reason for the call.
- Check whether the person can spare a moment.
- Ask one relevant diagnostic question and listen before continuing.
Apply these steps to the same account rather than changing the hypothesis halfway through the exercise. If new evidence contradicts your starting assumption, update the record and reconsider the next action. The objective is a useful decision, not a completed form.
Worked example: open a cold call
Illustrative example, not a report of a client result.
“Hi [Name], this is [Rep] with [Organization]. I’m calling about business software. Is this a workable moment for one question? When your team reviews manual handoffs between disconnected systems, who usually owns that discussion?” Pause and respond to the answer rather than reading the rest of a script.
Use a concrete artifact
A useful supporting resource in this context is a diagram of the current handoff. It should help the department lead and finance approver assess the current situation without forcing them through a generic sales presentation. Keep the scope narrow enough that the buyer can correct it.
For example, connect the artifact to duplicate entry, exceptions, and time between handoffs. Identify which inputs came from the buyer, which are public observations, and which remain assumptions. Do not request private operational records before the buyer has agreed an appropriate purpose and handling process.
Build the working record
Complete this worksheet during preparation, then revise it after the conversation. An unknown is a useful finding when it is recorded honestly.
| Field | What to write |
|---|---|
| Account and owner | [Account] · [Rep] · [Review date] |
| Confirmed problem | The buyer’s description of manual handoffs between disconnected systems, or “not confirmed” |
| Baseline | Available evidence for duplicate entry, exceptions, and time between handoffs, with source and date |
| Deliverable | a concise call opening, including scope and the person who reviews it |
| Open questions | Unconfirmed assumptions, required participants, and unresolved constraints |
| Next decision | Advance, gather evidence, revisit by request, or close the record |
Evaluate the result
Track relevant conversations divided by connected calls. Define the numerator, denominator, and review window before comparing results. Use comparable accounts and channels; otherwise an apparent improvement may simply reflect a different list or buying context.
For business software, pair the workflow measure with the quality of evidence about manual handoffs between disconnected systems. A reply or meeting is useful only if it helps establish relevance. Record declined and unsuitable opportunities so the team can improve targeting as well as messaging.
A common failure to avoid
A clever opener cannot compensate for poor targeting. Respect a refusal and record the outcome accurately.
In this context, the practical consequence is spending time on a demo using one real workflow rather than a generic feature tour before the buyer has confirmed a reason to do it. Revisit integration effort, adoption, and measurable workflow fit early enough to discover a genuine mismatch.
When to move forward
Proceed when the prospect agrees to discuss the issue or directs you to a more appropriate contact. A sensible next step may be a demo using one real workflow rather than a generic feature tour, but only when it follows from the evidence. If the buyer cannot identify a relevant problem or owner, close or reclassify the record instead of manufacturing urgency.
Continue the workflow
- Leave a useful voicemail
- Write a relevant first email
- Open a cold call across selling contexts
- Business software sales guides
For the wider collection, visit the prospecting and sales library. Learn about the host on the Dr. Connor Robertson profile or explore the published podcast interviews.