Use Approval Friction as a Fintech Meeting Hypothesis

Approval friction is a useful reason to ask for a conversation, not a reason to announce a diagnosis. An invoice waits when a budget owner is away, a required document is absent, a delegate lacks access, or no person knows which exception path applies. From outside an organization, an SDR does not know which situation exists. Good outreach respects uncertainty and asks about a visible handoff.

Start with an observation related to the person’s work. A vendor asking for payment status, a manager following up on an expense, or an accounting team chasing missing support documents all point toward a process worth understanding. Do not treat one signal as proof of an AP problem. Say why you reached out and ask a question small enough for a busy person to answer. “When an invoice needs an exception, where does approval usually pause?” invites a process answer. “Are your approvals broken?” does not.

The word approval hides several separate events. A team needs to confirm a purchase, match a document, assign a cost owner, collect an approval, or resolve an exception. An invoice might wait before entry into an accounting process. Another might wait after entry because a reviewer needs more information. The same person might own both tasks, or separate teams might own them. An SDR earns a meeting by helping a prospect name which handoff deserves attention.

Build a short call plan before outreach. Identify the expected role, the reason for contact, one initial question, and one possible follow up question. Do not prepare a long product explanation. Your first job is to learn whether a relevant operational issue exists. If a prospect describes a delay, ask where the item waits and who handles the next step. If a prospect reports no concern, thank them and end politely. Pressure turns a reasonable question into an unwanted pitch.

Use language which leaves room for different answers. “Some finance teams see invoices wait when support documents arrive late. Others see a delay after documents arrive. Which pattern, if either, sounds familiar?” This is more useful than claiming every organization faces the same obstacle. The prospect might identify a document issue. They might point to a staffing change. They might say approvals move on time, while coding creates extra work. Each response gives a different direction for a later meeting.

Consider a fictional practice situation. North Row Studio is a marketing agency with project spending across several client teams. On Monday, an SDR speaks with Lee, an operations manager. Lee says a freelancer invoice took longer than expected, and a vendor followed up twice. The SDR does not say approval software would solve the problem. Instead, the SDR asks, “Where did the invoice wait before accounting entered the invoice?” Lee explains, “The project lead needed to confirm work completed, then a budget owner needed to review an amount above the normal project estimate.”

Those details matter. The first pause concerns work confirmation. The second concerns an exception. Neither detail proves a broader pattern, and neither tells an SDR who should buy anything. The SDR asks one further question: “When a budget owner is unavailable, does a documented substitute handle an exception, or does the invoice wait?” Lee says the team has a substitute in theory, but people often do not know where to send the request. Now the SDR has an observable handoff and a reason to ask for a focused conversation.

The meeting request should match what the prospect said. “You described an exception request waiting when an owner is out. Would a twenty minute session with the AP owner and whoever manages delegation help map where those requests go today?” This request does not promise an outcome. Nor does this assume Lee controls AP policy. A precise invitation makes attendance easier because each participant understands why their presence matters.

If a prospect says, “Send me information,” do not respond with a broad attachment and no next question. A better reply is, “I will send a short note. Before I do, when an invoice lacks support, who asks for missing details today?” The question separates a document problem from an approval problem. If the prospect answers, include their language in your follow up. If no answer arrives, send only what your normal process permits and leave the door open without inventing a pain point.

Keep clear notes after every conversation. Record the role, exact words used by the prospect, the point in the handoff, known participants, and uncertainty. Avoid labels such as “approval pain” when no one described a real delay. Write “Lee described a freelancer invoice waiting for project confirmation, then budget review above estimate.” This note tells the next rep what was heard and what still needs checking. This note also prevents a later call from repeating questions Lee already answered.

Separate a missing document from a delayed approval in every discussion. A missing document creates a request for information. A delayed approval means the required information is already present, yet no decision has happened. An exception is different again. An assigned owner needs to decide whether a request follows the usual path or needs separate attention. Asking which of these events occurred helps the SDR avoid promising a single solution for unrelated work.

Travel and delegation often reveal useful process details without asking for sensitive information. Ask, “When an approver is out, who knows a substitute exists?” or “Where does a requester look for an exception owner?” The answer might reveal an informal practice, a documented process, or no clear path. An SDR should not advise a prospect how to set approval authority. The appropriate internal owner decides policy. The SDR’s contribution is a clean description of the present handoff.

Expect resistance from people who protect their time. A finance leader says, “Our process is fine.” Accept the statement. Ask one final narrow question only if conversation remains open: “When a request falls outside normal limits, does your team have a visible route for review?” If the answer is no, offer a meeting. If the answer is yes, thank them for clarifying. A respectful exit preserves more trust than a forced objection response.

Use an internal review before scheduling a discovery meeting. Read the notes and ask whether a real process detail supports the meeting request. Check whether the chosen invitees match the stated handoff. An AP owner might need a project operations colleague, while a document issue might need a purchasing contact. Do not pack a meeting with people whose role was never mentioned. A smaller discussion makes ownership easier to see.

For practice, replay the fictional North Row Studio call. A colleague plays Lee and says, “Send me information.” Respond with a brief acknowledgment, then ask where a missing invoice document goes after accounting spots the gap. If Lee answers “the project lead,” write a follow up note for Wednesday which asks Lee whether the AP owner and project operations lead would join a twenty minute discussion about the exact current handoff.