Sell Into a Revenue Operations Tech Stack Review

A revenue operations leader often describes a stack review as a data problem. Begin with the work interrupted by bad information. A lead enters a queue without an owner. A customer success manager learns about an expansion after a report arrives. Finance receives a forecast whose stages mean different things to different teams. Each symptom points toward a different conversation. A product tour at this stage adds noise.

Ask for one recent event. “Where did someone first stop work and repair a record?” Leave space after asking. A complaint about a dashboard might lead toward reporting logic. An argument over lead ownership might point toward routing, field definitions, or a missing decision owner. Listen for the person doing repair, the record involved, and the action repeated. Those details shape a useful working session.

Consider a fictional software company with webinar registrations. A form sends registrations into a marketing system. A scoring rule routes selected records into a customer relationship system. Sales development receives alerts, yet account executives see blank industry values and return prospects to marketing. Marketing staff export a spreadsheet, add values from approved internal sources, then reload records. The operations leader calls this a stack problem. The seller should ask where industry enters, who owns field quality, who changed the scoring rule, and when a record belongs in sales.

Keep early discovery narrow. Request one recent record with personal details removed. Trace its path from entry through repair. Write each stop in ordinary language: registration arrives, scoring rule evaluates, record enters a sales queue, representative returns record, marketing repairs field. Beside every stop, note a system, a responsible person, and a decision. A small map exposes work hidden inside a large architecture diagram. The map also stops participants from debating every tool at once.

Data definitions deserve close attention. “Qualified lead,” “active account,” and “renewal opportunity” sound familiar, yet teams often attach different meanings. Ask who owns each definition, where staff read those words, and what event moves a record from one state into another. Ask one person to read a definition from a process document or system field help text. Then ask a colleague from another team how daily work follows those words. A gap between written language and routine behavior is evidence. Do not call such a gap poor adoption until the group examines whether the rule fits real work.

A buyer might ask which platform would clean everything up. Keep focus on the first broken workflow. Say, “I want to understand account ownership before we discuss approaches. Which record type creates the most repair work this month?” This wording gives the leader a choice among known problems without declaring a cause. If webinar records create repeated work, stay with webinar records. If forecast stages cause conflict, schedule a separate investigation rather than blending both topics.

Responsibility changes matter as much as data movement. A system sends a record, yet a person accepts, enriches, rejects, or reinterprets information. In the fictional company, marketing owns the webinar form, sales operations owns routing, and account executives decide whether a prospect belongs in an existing account. No one person sees every decision during ordinary work. Invite someone from each decision point to a short session. Skip observers without a direct action in the flow. The session needs a factual map and one agreed repair.

Prepare for concerns about change. An account executive might worry about slower response. A marketing lead might expect more rejected records. A data manager might remember an earlier cleanup effort with unresolved old values. Treat each concern as a test condition. Ask what observation would show whether a proposed adjustment reduces repair work or adds more work. The group might review ten webinar records across five business days. For every record, they would note field completion, assigned owner, and elapsed time before a sales response. Those observations relate to a specific handoff. They do not promise a companywide outcome.

Avoid “single source of truth” as a replacement for decisions. Ask whose value wins when systems disagree. Ask whether a correction needs to return to the original source. Ask who holds authority to change a field rule after a working session. “Operations” is too broad. Seek a named role, a decision route, and a check date. When the buyer lacks an answer, record an open question. A seller should not invent a governance model during discovery.

In a fictional practice situation, an operations leader says, “We use six tools, so our data is a mess.” The seller replies, “Which handoff creates the first repair after a webinar registration?” The leader says sales rejects records because account ownership arrives blank. The seller asks, “Where does ownership first become blank, and who updates the value today?” The leader names a routing rule maintained by sales operations. The seller requests a forty five minute session with marketing operations, sales operations, and an account executive who handles those records.

The seller prepares an invitation with a narrow purpose: trace one webinar registration from form submission through sales acceptance. The note asks each attendee for one recent example, existing field definitions, and a route diagram if one exists. No attendee needs to defend every tool. The account executive brings a returned record. Marketing operations brings form fields and scoring criteria. Sales operations brings routing logic and assignment rules. Those inputs give the group enough material to inspect one sequence.

At the session, start with the account executive’s record. Ask marketing operations to identify when industry became available. Ask sales operations to identify when ownership should have appeared. Ask the account executive why return to marketing felt safer than manual assignment. Write each answer beside the relevant point in the sequence. If participants disagree, record competing descriptions rather than forcing agreement. A disagreement often identifies an unstated rule needing an owner.

During coaching, review choices rather than product language. Did the seller select one workflow? Did the seller locate a person who repairs data? Did the seller separate a definition problem from a connection problem? Listen for assumptions such as “routing will solve this.” Ask what evidence supports each assumption. Strong discovery ends with work the buyer selected, not with an oversized promise.

Before leaving the fictional session, the seller reads back one action: sales operations will inspect the routing rule for the account executive’s record by Wednesday afternoon. Marketing operations will confirm the source for account ownership before noon on Wednesday. The seller schedules a Friday review of ten new registrations and opens the shared record map beside the first registration when both owners join.