What's the right way to navigate IT vs business stakeholders?

Question

Pulse RevOps · The Machine · Accepted Answer

IT is a **gatekeeper** (can kill, not approve); Business owns the outcome. Engage IT early with integration/security requirements, but let business stakeholders drive the business case. Separate conversations, aligned on facts.

## IT vs Business Stakeholders

**Role clarity:**
| Role | Authority | Motivation | Question Type |
|------|-----------|-----------|---------------|
| **Business** (COO/VP Ops) | Approves spend | Solves pain / drives outcome | "Will this move the needle?" |
| **IT** (VP Eng/CTO) | Gates technical fit | Minimizes risk / ops burden | "Can we support this?" |
| **Finance** (CFO) | Controls budget | ROI, TCO | "Does the math work?" |

**IT conversation (technical fit, not business case):**
1. Lead with constraints: "What are your API architecture limits? Data residency requirements? Support model expectations?"
2. Bring technical specs, not ROI: datasheets, integration docs, SLA guarantees
3. Ask IT to co-own the proof-of-concept timeline—they're not a blocker, they're a resource
4. **Security:** Front-load SOC 2, ISO 27001, or whatever compliance your customer requires

**Business conversation (outcome, not features):**
1. Sell the business impact: time saved, revenue captured, risk reduced
2. IT is mentioned as a resource: "Your team reviewed the architecture and flagged [X]; here's how we handle it"
3. Never say IT approved it—say "IT validated the technical fit"

**Common mistake:** AE pitches IT as the decider, or lets IT lead business conversations
- IT says "We're not sure about the vendor's uptime history" → Business gets scared
- Business asks "Can IT support this?" → IT says "We'd need 2 weeks to evaluate" → Deal stalls

**Sequencing:**
1. **Week 1:** Business stakeholder agrees on problem/outcome
2. **Week 2:** Loop in IT for technical fit (parallel, not sequential)
3. **Week 3:** Business + IT both present their concerns / solution to Finance
4. **Week 4:** Negotiate terms with all three aligned

**IT objections (how to handle):**
- "We need to vet the vendor" → Offer a 2-week proof-of-concept with your CSM embedded
- "We don't have bandwidth" → "Can your team dedicate [person] for 10 hours over 2 weeks?"
- "Security won't sign off" → Introduce your security officer directly; let them negotiate SOC 2 requirements

**Post-deal:** IT must own implementation, not just rubber-stamp it. A hand-off without IT buy-in kills onboarding and expansion.

```mermaid
flowchart LR
    A[Business: Problem Identified] --> B[IT: Technical Fit Review]
    A --> C[Finance: Budget Check]
    B --> D{All Three Aligned?}
    C --> D
    D -->|No| E[Resolve Gaps]
    E --> D
    D -->|Yes| F[Negotiation Phase]
    F --> G[IT Leads Implementation]
```

TAGS: stakeholder-navigation, it-gatekeeper, technical-fit, buying-committee, deal-structure

Role	Authority	Motivation	Question Type
Business (COO/VP Ops)	Approves spend	Solves pain / drives outcome	"Will this move the needle?"
IT (VP Eng/CTO)	Gates technical fit	Minimizes risk / ops burden	"Can we support this?"
Finance (CFO)	Controls budget	ROI, TCO	"Does the math work?"

What's the right way to navigate IT vs business stakeholders?

IT vs Business Stakeholders

What does the score mean?