What Working Problem Interviews Look Like (B2B SaaS)

Working B2B SaaS problem interviews look almost ordinary. There is no clever framework on display. There is one founder asking one operator to describe how their team gets work done, and the magic is that the founder learned something they did not expect.

It Starts Without the Product Frame

A good interview opens with the workflow, not the pain. "Walk me through the last time your team did X." Not "tell me about your biggest pain point." The first lets the operator describe their world. The second invites a curated complaint that may not match how they actually spend their time.

It Surfaces the Tool Stack

B2B operators almost always work across multiple tools. A good interview captures the actual stack as it appears in the story, not as a separate question. "We exported from Salesforce, dropped it in a sheet, the analyst added a column, then we re-imported into the campaign tool." That sentence is six tools and three handoffs. Each handoff is a potential product surface.

It Tracks the Handoff Pain

For B2B specifically, the highest-value pain often lives at handoffs - person to person, tool to tool, team to team. Working interviews slow down at these moments. "Tell me what happens when the analyst hands the file back." "Who validates that the import worked?" "What do you do when something goes wrong overnight?"

It Maps the Buyer-User Gap

B2B-specific. Late in the call, the working interview asks: "If your team wanted a tool for this, who would have to approve it?" The answer reveals the buyer. "What would they ask before approving?" Reveals the buyer's objections. "Have you tried to bring something like this in before?" Reveals the procurement history.

Founders who skip these questions ship products that users love and buyers reject.

It Surfaces the Internal Champion

B2B SaaS rarely sells without an internal champion. A working interview asks who, on this team, would push for a tool like this if they tried it and liked it. The champion is the person you actually need to win in your launch sequence.

It Captures Procurement Constraints

Data residency, security review, SOC 2, vendor consolidation pressure, existing-tool displacement politics. All of these surface naturally if you ask "what would the security team or finance team ask before approving this?" Founders who skip these questions discover the constraints late, after building.

It Ends With Specific Vocabulary

B2B operators have specific phrases. "Hand it off to ops." "Run the recon." "Push it to staging." "Write up the post-mortem." Capture the phrases. Your landing page should sound like an operator describing their week to a colleague, not a vendor describing their feature set.

What These Produce

By the end of fifteen well-run B2B interviews, you have: a workflow map, the tool stack, the handoff failures, the buyer-user gap, the internal champion profile, the procurement constraints, the vocabulary. That is the spec. Build around it.