Run a Call With an Engineer and CFO in the Room

An engineer and a CFO bring different responsibilities into a sales call. An engineer often needs confidence about a technical path, present systems, or support for a workflow. A CFO often needs a clear reason for attention, a view of present effort, and an internal route for deciding on spend. Treating either concern as secondary loses both people.

Begin with an operating problem shared across roles. Choose language neither person needs to translate. A delayed incident investigation, a manual reporting routine, or a launch waiting on approval work gives technical and financial questions a common subject. Ask what happens now, who loses time, and what decision the group needs to make. Do not open with an architecture tour or a price discussion.

Set a simple purpose at the start. Say, “I would like to understand the incident review process first, then learn what evidence each of you needs before a next decision.” Ask whether either participant wants a different outcome. A short answer now prevents a surprise concern from taking over during final minutes. Write their answers where both people see them.

Invite the buyer closest to the workflow to describe one recent situation. For an incident investigation, ask when an alert arrived, who responded, where information lived, and when the team knew what happened. Do not ask an engineer to speak for finance or a CFO to describe technical work. Your role is to keep a shared picture visible while each participant supplies their own evidence.

After the example, ask the engineer, “What needs to work reliably within this sequence?” Let them name a condition in their own terms. They might focus on where records start, how teams review them, or who needs access. Follow with, “What would you inspect before supporting a further step?” Record their answer using their words. Avoid translating their concern into a product claim.

Then ask the CFO, “When you look at this same sequence, what would make attention or spend appropriate?” A CFO might focus on present burden, timing, ownership, or internal planning. Do not turn this into a promise about savings. Ask what information they use today when judging work like this. Their answer shows which evidence belongs in a later discussion and which assumptions need testing.

Bring both threads back to the shared problem. Say, “We have a technical question about source records and a financial question about time spent assembling them. Both connect to delay before leaders receive a clear incident view.” This is facilitation, not a claim about cause. Invite correction if either participant sees another connection.

Different questions deserve different pace. An engineer asking about architecture often needs time to explain a dependency. A CFO asking about cost often needs context before any number has meaning. Resist pressure to settle both in one reply. State which question you heard, ask one clarifying question, and name the evidence needed for an answer. This approach limits cross talk and respects each role.

Fictional practice situation: Elena, an account executive, meets Arun, an engineering director, and Dana, a CFO. Their fictional company reviews major service incidents after a delayed customer update. Arun says engineers collect notes from several places before a review. Dana asks how much staff time the present process consumes. Elena begins, “Let us trace one recent incident, then identify what each of you needs for a next decision.”

Arun describes an alert at 9:10 on a Tuesday. An engineer sees a customer report at 9:25. Team leads gather notes through the afternoon, then a manager requests a written explanation on Wednesday. Elena asks where notes start and who checks them before the manager review. Arun says notes live in separate tools and one lead compares them by hand. Elena records a technical question: review source information and access within one incident sequence.

Dana then asks whether staff time alone supports attention. Elena does not offer an invented estimate. She asks how Dana evaluates work delayed by incident follow up. Dana says she needs the engineering manager to describe how often the review blocks planned work, plus a view of whose time enters the process. Elena records a financial question: identify delayed work and the person who will assemble an honest description.

Elena checks alignment. “Arun needs a review of source information and access within one incident sequence. Dana needs a description of present effort and delayed work. Did I miss anything?” Arun adds a security lead should review access. Dana says the planning director should join only after the engineering manager describes present effort. These additions alter the next action. A broad product tour would address neither request.

Elena proposes a focused sequence. First, schedule a technical working session with Arun and the security lead. The invitation states one purpose: examine a fictional incident record, identify source information, and write access questions needing review. Second, ask the engineering manager for a short description of the present review routine for Dana. Schedule a joint meeting after both evidence requests have answers.

Meeting notes should make ownership obvious. Record the operating problem in one sentence. Under technical evidence, record the participant, source question, and planned review. Under financial evidence, record the person who will describe present work, the decision use for their information, and the due date they accepted. Do not label either area complete until a buyer confirms the evidence answers their question.

Watch for two common failures. First, a seller translates every question into product language. An engineer then lacks room to test a technical concern, and a CFO lacks a basis for judging timing. Second, a seller lets one role answer for another. An engineer might describe cost concerns, or a CFO might claim a technical review is easy. Return each question to its owner with a respectful prompt.

Use short summaries during the call. After a technical exchange, say, “The open technical point is source review before access discussion.” After a financial exchange, say, “The open business point is how incident follow up moves planned work.” A summary helps both people track movement without forcing agreement. If the group disagrees, name the disagreement and ask what evidence would narrow the issue.

Practice with two colleagues using a fictional situation. One plays an engineer who asks about source information. One plays a CFO who asks why planned work should move aside. Keep one operating problem on the page, ask each person for an evidence request, and resist answering either request yourself. End after each request has an owner and a date.

In Elena’s fictional call, Arun and the security lead accept Thursday at 10:00 for the record review. Dana asks for the engineering manager’s current work description by Monday afternoon. Elena opens separate invitations, places the fictional incident record request in Arun’s invitation, then asks the engineering manager to send Dana a plain description of one delayed planned task before Monday.