SaaS contract negotiation workflow
From RFQ through legal review, pricing, and signature.
Every company that buys SaaS goes through vendor negotiations, but most teams handle it as a scattered email thread between procurement, legal, and budget. This template maps the flow: RFQ submission, proposal evaluation, feature demo, pricing negotiation, SLA review, legal review, and finally signature — with loops showing where negotiations stall.
The decision diamonds mark the high-friction points: does the vendor meet your requirements, is the pricing within budget, does legal sign off? Each "No" loops back to renegotiation, which is where calendar weeks get consumed. This template makes those loops visible so teams can parallelize: get a demo while legal reviews, negotiate pricing in parallel with SLA terms.
When to use this template
- Procurement playbook — document your company's vendor evaluation and approval process so every team negotiates consistently, hitting the same deadlines and SLA thresholds.
- Bottleneck analysis — if vendor deals take 3 months, trace this diagram: which loops are repeating? Are legal reviews blocking, or are price negotiations the bottleneck?
- Vendor management runbook — after a contract is signed, update this diagram to show the subscription activation step and the ongoing renewal or amendment process.
How to adapt it
Start with your company's actual process. Common extensions:
- Add a security audit step between demo approval and legal review (common for enterprise vendors, adds weeks).
- Insert a budget approval gate before vendor selection if procurement must get CFO sign-off above a threshold.
- Add a renewal notification loop at the end, triggered 90 days before contract expiry, to re-negotiate or cancel before auto-renewal traps you.
Visual edits regenerate clean Mermaid code, so you can document and evolve your team's procurement workflow without writing syntax.
Mermaid code
Copy it anywhere Mermaid is supported — GitHub, Notion, or your docs.
flowchart TD
A[Procurement creates RFQ] --> B[Send to vendors]
B --> C[Vendors submit proposals]
C --> D[Evaluate pricing & features]
D --> E{Meets requirements?}
E -->|No| F[Reject, loop to other vendors]
F --> C
E -->|Yes| G[Request demo & trial]
G --> H{Team approves?}
H -->|No| F
H -->|Yes| I[Negotiate contract terms]
I --> J{Pricing acceptable?}
J -->|No| K[Counter offer to vendor]
K --> I
J -->|Yes| L[Review SLA & support]
L --> M{SLA terms acceptable?}
M -->|No| K
M -->|Yes| N[Send to legal review]
N --> O{Legal approves?}
O -->|No| P[Flag concerns, vendor responds]
P --> N
O -->|Yes| Q[Prepare for signature]
Q --> R[Both parties sign]
R --> S[Update vendor registry]
S --> T[Activate subscription]
Frequently asked questions
- What is an RFQ and why do companies send them?
- An RFQ (Request for Quote) is a formal document describing what you need — features, performance, compliance, volume, support hours — and asking vendors to propose terms. RFQs protect buyers by forcing vendors to commit in writing, prevent scope creep during negotiations, and create an audit trail for compliance.
- Why does SaaS contract negotiation take so long?
- Because both sides have conflicting incentives. Vendors want higher pricing and looser SLAs; buyers want lower pricing and tighter guarantees. Neither side reads contracts the same way — your legal team has never seen this vendor's standard terms before, so legal review takes time. The loop — offer, counter-offer, review, flag — can take weeks.
- What should I look for in a SaaS contract?
- Pricing (total cost, minimum term, price increases, auto-renewal), data (ownership, residency, deletion upon termination), uptime (SLA percentage and credits), support (response times, severity levels), and exit (how to cancel, what happens to data). Negotiate the clauses that matter most to your business; skip the rest to move faster.
- How do I prevent bad contracts from getting signed?
- Use this diagram to enforce a gate at the legal review step — every vendor contract must pass legal before it reaches the vendor for signature. Empower legal to flag concerns without killing the deal, and give vendors a clear path to respond (amend terms or accept liability caps). Visual edits regenerate clean code so you can document your team's specific contract checklist and approval flow.