Prospect Into Cash Visibility With Respectful Questions

Cash visibility means different things inside different finance teams. One leader might mean a daily decision about payment timing. Another might mean preparation for a weekly discussion. A third might mean locating information spread across several places. An SDR who treats every mention of cash visibility as an urgent problem starts from an assumption rather than a prospect’s words. A better opening uses a modest hypothesis and invites correction.

Start with language connected to an observable workflow. A prospect who says, “Our finance group checks several systems before Monday’s meeting,” has described a process, not a buying signal. An SDR might respond, “Which decision depends on those checks before Monday?” This question respects existing work. The answer might reveal a useful discovery topic, or perhaps leaders already receive what they need. Either response gives more value than a broad claim about better forecasting or financial outcomes.

Consider a fictional distributor named Northfield Supply. Its controller, Priya, opens bank portals each morning and receives a report from operations before an internal review. The sales development representative hears only one detail during an initial call: Priya spends time gathering information. Instead of saying, “We solve cash visibility,” the representative asks, “When you gather those sources, what decision waits until the review is ready?” Priya answers, “Our team uses the review to decide which supplier questions need attention first.” This answer gives the conversation a real subject: information flow before a defined meeting.

Good prospecting separates current process from presumed dissatisfaction. Ask how often leaders review cash position. Ask who joins those reviews. Ask what information arrives late, if any. Ask where a team needs to combine information by hand. Each question earns a place because a prospect has mentioned a related workflow. Avoid turning an answer into a verdict. “We use bank portals and a spreadsheet” does not prove confusion, poor accuracy, or a financial risk. Ask what purpose each source serves before proposing another conversation.

Words matter in this area. “Visibility” sounds familiar, yet different teams use the word differently. One person might refer to balances. Another might refer to expected receipts. Someone else might mean a manager’s ability to see a prepared internal report. An SDR needs no lecture on finance terminology. Ask, “When you say visibility, what do you need to see for your next decision?” The prospect supplies the definition. Repeat back a short version and check your understanding. “You are looking for the information used during the supplier review, correct?”

Respect a stated treasury process. When a prospect says, “We already have a treasury process,” do not challenge the statement or rush into a comparison. Respond with curiosity. “Which decisions does your process support today?” A finance leader might say, “Daily balances are covered, but a weekly operating review takes preparation.” Or the response might be, “Our team is comfortable with both.” In the first case, the SDR has permission to ask about preparation. In the second, no pressure belongs in the call. Thank the prospect and leave room for a future conversation only if a relevant change arises.

Use a narrow call objective. The aim of a first exchange is not proof of need. The aim is a clear answer about whether a workflow deserves discovery. A useful internal note might read: “Fictional example. Controller combines bank portal information with an operations report before a Monday supplier review. Asked which decision depends on review. Prospect described prioritizing supplier questions. No claims about results.” Notes written this way preserve prospect language and stop the next person from inventing pain points.

The difference between a useful question and a leading question often appears in the final words. “How much time do you lose compiling reports?” assumes loss. “What happens between the first source and the Monday review?” invites an accurate description. “Would a single view improve your forecast?” assumes both a desired feature and an outcome. “Which source does the team check first, and why?” invites context. An SDR should listen for decision timing, participants, source handoffs, and unanswered questions. Those details support a disciplined next step.

Priya might describe a complication. Operations sends a revised report late Monday morning, after she has completed her first review. The SDR should not label this a system failure. Instead, ask, “When the revised report arrives, who needs to know before the meeting?” Priya might say she updates one manager and carries the revision into the discussion. Now the SDR understands a handoff and a timing issue. The SDR still does not know whether a product discussion fits. Further discovery needs the prospect’s interest and appropriate participants.

Direct invitations work best after a prospect names a specific workflow worth examining. “You described combining bank information and an operations report before a weekly supplier review. Would a short discovery conversation with the people involved help map those handoffs?” This invitation states only what the prospect shared. Do not promise a better cash position, faster decisions, improved accuracy, or financial performance. Those claims reach beyond an SDR conversation and beyond information gathered so far.

Practice against common pressure. In a fictional role play, a manager tells the SDR, “Push for a meeting. Every finance team needs better visibility.” The SDR should resist universal language. The prospect says, “We already have a treasury process.” The SDR replies, “Understood. Which decisions does your current process support, and is there any review where information arrives later than your team wants?” If the prospect names none, the SDR closes the topic politely. If the prospect names a weekly handoff, the SDR asks who owns each source and whether a focused conversation would be useful.

Prepare before each call with one workflow based question, one follow up question, and one respectful exit. For Northfield Supply, the first question is, “Which decision waits for the Monday review?” The follow up is, “Who brings each source into the Monday review?” The exit is, “Thanks for explaining your process. I will leave this here unless you want a focused conversation about those handoffs.” During the fictional call, Priya says operations owns the late report. The SDR writes “operations report, Monday review, supplier questions” in the account note and asks whether Priya wants to invite her operations counterpart to a 20 minute mapping conversation.