On-screen

Narration

Anna: Contract negotiation feels like a legal activity, and most of it isn't. It's an operational one.
Greg: The clauses that matter later are about uptime, escalation, what happens when things fail, and how you get your data back if you leave.
Anna: Those are questions the technical team can answer better than anyone, which is why you want to be in the room.
Greg: So we'll work through the terms that protect both sides, and the ones that only look like they do.

On-screen

Narration

Anna: We have all seen boilerplate vendor contracts. Why not just accept them?
Greg: Remember the Black Friday payment system outage we mentioned earlier? If you sign standard terms, you might find those "industry standard" uptime guarantees are worthless.
Anna: So we press for clear uptime commitments, detailed service levels, and the ability to exit if things go south.
Greg: Exactly. A well-negotiated contract tells the vendor how quickly they must respond, how they'll compensate you, and what recourse you have if service fails.
Anna: It also locks in pricing so you don't face huge renewal hikes.
Greg: Negotiation sounds tedious, but think of it as building a safety net before you walk the tightrope.

On-screen

Narration

Anna: Uptime numbers look impressive, but let's translate them into real impact. 99.9% uptime allows about 8.7 hours of downtime a year; 99.99% cuts that to under an hour.
Greg: Picture your ecommerce store offline for a full business day during peak season. That's more than an inconvenience—it's lost revenue.
Anna: Good SLAs also clarify incident notification and escalation paths.
Greg: Plus, penalties or credits if the vendor misses targets. "Best effort" or "reasonable attempts" is code for "we'll try, maybe."
Anna: Security and data handling should meet your compliance needs. If customer information leaks, you may face fines before the vendor even apologizes.
Greg: Strong SLAs keep daily operations running smoothly and give you leverage when they don't.

On-screen

Narration

Anna: Let's talk money. Vendors offer flat fees, per-user pricing, or pay-as-you-go models.
Greg: The last one can be surprising. One startup projected $500 a month on AWS but got a $5,000 bill during a holiday rush.
Anna: Compare that with a fixed $2,000 a month hosting plan—expensive on quiet days, but stable during busy times.
Greg: Ask about volume discounts, yearly increases, and onboarding fees.
Anna: And watch out for seemingly minor charges, like mandatory training or premium support.
Greg: It's like buying a cheap printer and discovering the ink costs a fortune. Do the math for best and worst-case scenarios so you know what you're signing up for.

On-screen

Narration

Anna: Ever heard of a company stuck in a contract for six months after service went downhill?
Greg: Unfortunately yes, because they needed 180 days' notice to terminate. Always read the exit clause.
Anna: Look for data portability promises too. When vendor X went bankrupt, company Y lost three months of data because extraction wasn't covered.
Greg: Renewal terms deserve equal attention. Automatic price increases can sneak up on you if you don't have time to renegotiate.
Anna: Treat the exit plan like a fire drill. You hope you never need it, but you'll be glad it's there in a crisis.
Greg: A clear renewal calendar and exit path keep you in control rather than locked in.

On-screen

Narration

Anna: How do you know if a vendor is risky? Start by checking financial stability—are they profitable or bleeding cash?
Greg: Then examine security posture. When was their last penetration test and how quickly do they patch?
Anna: Frameworks like NIST's vendor risk assessment or the SIG questionnaire provide structured questions.
Greg: Score areas such as finance, security, and support history. If they fall below your threshold, reconsider.
Anna: This process isn't just bureaucracy. Think of it as weather forecasting before a hike; you want to know if a storm is coming.
Greg: Document the results and revisit them annually. Circumstances change, and so should your risk profile.

On-screen

Narration

Anna: When should lawyers join the negotiation?
Greg: Early—especially for industries like healthcare or finance.
Anna: Violating HIPAA can cost over $50,000 per incident, while ignoring PCI-DSS might halt your ability to process payments.
Greg: International deals complicate matters further. Data sovereignty laws may forbid storing customer data outside certain regions.
Anna: Also consider time zones and jurisdiction in case of disputes. Which court will hear them?
Greg: Legal review clarifies intellectual property rights and liability caps so you don't pay for the vendor's mistakes. It might feel tedious, but skipping it could be expensive.

On-screen

Narration

Anna: Before signing, what questions should we ask?
Greg: Start with references—call current customers and ask what went wrong and how issues were handled.
Anna: Verify security certifications such as SOC 2, then check financial health via credit ratings or public statements.
Greg: Try the support line before signing to measure response time. If they ignore a prospective client, imagine their attitude once you're locked in.
Anna: Finally, map requirements from your RFP directly to contract terms so sales promises don't vanish.
Greg: This checklist prevents nasty surprises after the ink dries.
Anna: Some teams even create a weighted scoring rubric so every vendor is judged fairly.
Greg: A quick search for past legal disputes also helps reveal hidden issues.

On-screen

Narration

Anna: What warning signs should make you think twice?
Greg: Watch for vague language like "industry-standard pricing" with no actual numbers. That's often sales talk for "expensive."
Anna: Beware heavy reliance on proprietary tools that don't play nicely with others. If you can't move data or integrate systems, you're trapped.
Greg: Discounts that vanish after year one are another trap. I've seen a $50 per-user software fee jump to $100 once "promotional pricing" expired.
Anna: And check for unilateral change clauses where the vendor can update terms whenever they like.
Greg: If support levels are worse than what the sales team promised, push back. Otherwise you're locked into a bad deal.

On-screen

Narration

Anna: Negotiation doesn't end when the contract is signed.
Greg: Schedule quarterly service reviews to discuss performance metrics and upcoming changes.
Anna: Include training and documentation requirements so your team isn't left guessing how to use the platform.
Greg: Ongoing knowledge transfer keeps you independent rather than reliant on expensive vendor consultants.
Anna: Treat the relationship as a partnership, using SLA reports to justify renewals or call out issues early.
Greg: If problems pile up, escalate according to the contract and start planning that exit path.
Anna: Document lessons learned and update playbooks so mistakes do not repeat.
Greg: Celebrate successes too; recognising good performance builds trust.

On-screen

Narration

Anna: Not all services are delivered the same way. Are you outsourcing everything or sharing responsibilities?
Greg: You might use a hybrid model where some services stay in-house while others go to a managed provider.
Anna: Multi-vendor setups add complexity. If your CRM is hosted by one provider and your analytics by another, who takes the blame when integrations break?
Greg: Clear contracts specify responsibilities so you avoid finger-pointing later.
Anna: Matching the delivery model to your business needs ensures you get the right support without paying for unnecessary extras.
Greg: Consider how these models will evolve as the business scales.

On-screen

Narration

Anna: Have you confirmed the vendor's system actually works with your existing tools?
Greg: Check API access, data exchange formats, and authentication methods.
Anna: A vendor might claim "it integrates with everything" only for you to learn that "everything" means their other paid products.
Greg: Clarify upfront whether you'll need custom development, middleware, or extra licenses.
Anna: Poor integration can turn a simple project into a costly headache, especially if data needs to flow in real time.
Greg: Document these requirements in the contract so there's no dispute later.
Greg: Don't forget about data format quirks; mismatched CSV headers can derail a migration.
Anna: Add integration testing milestones so problems surface well before go-live.

On-screen

Narration

Anna: What happens when your business triples in size?
Greg: Make sure the contract allows for scaling up—or down—without punitive fees.
Anna: Include options for additional capacity, more users, or even moving to a larger service tier.
Greg: I've seen companies caught off guard by data growth charges that skyrocketed after a successful marketing campaign.
Anna: Also plan for shrinking usage if business slows; you shouldn't pay for unused capacity.
Greg: Scalability clauses protect you from outgrowing the vendor or wasting money when demand drops.
Anna: Build forecast models to estimate resource needs and confirm pricing scales sensibly.
Greg: Some vendors offer burst capacity on demand—handy during seasonal spikes.

On-screen

Narration

Anna: Negotiating a contract is about more than price.
Greg: A well-crafted agreement covers uptime, pricing, exit strategies, and how the service will grow with you.
Anna: Use structured risk assessments and thorough checklists to evaluate vendors.
Greg: Bring in legal expertise early, especially for international or regulated industries.
Anna: Keep the relationship healthy with regular reviews and training, and be ready to pivot if performance slides.
Greg: Good contracts form partnerships that survive growth, change, and the occasional curveball.
Anna: Remember the holiday outage scenario? Strong SLAs and careful integration planning could have prevented it.
Greg: Invest the time now for fewer sleepless nights later.