Anna: This section sets up Contract Negotiation Basics. Treat it as the frame for the decisions, handoffs, and evidence that appear in the next slides.
Greg: The practical question is simple: by the end, what should a junior IT professional be able to explain, check, or document in a real workplace?
Anna: Why negotiate carefully focuses attention on a concrete part of the work. Speaker A: We have all seen boilerplate vendor contracts. Why not just accept them?, Speaker B: 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, and Speaker A: So we press for clear uptime commitments, detailed service levels, and the ability to exit if things go south.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: 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; Speaker A: So we press for clear uptime commitments, detailed service levels, and the ability to exit if things go south; Speaker B: 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: Typical SLA terms focuses attention on a concrete part of the work. Speaker A: 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, Speaker B: Picture your ecommerce store offline for a full business day during peak season. That's more than an inconvenience—it's lost revenue, and Speaker A: Good SLAs also clarify incident notification and escalation paths.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: Picture your ecommerce store offline for a full business day during peak season. That's more than an inconvenience—it's lost revenue; Speaker A: Good SLAs also clarify incident notification and escalation paths; Speaker B: Plus, penalties or credits if the vendor misses targets. "Best effort" or "reasonable attempts" is code for "we'll try, maybe.".
Anna: Pricing models focuses attention on a concrete part of the work. Speaker A: Let's talk money. Vendors offer flat fees, per-user pricing, or pay-as-you-go models, Speaker B: The last one can be surprising. One startup projected $500 a month on AWS but got a $5,000 bill during a holiday rush, and Speaker A: Compare that with a fixed $2,000 a month hosting plan—expensive on quiet days, but stable during busy times.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: The last one can be surprising. One startup projected $500 a month on AWS but got a $5,000 bill during a holiday rush; Speaker A: Compare that with a fixed $2,000 a month hosting plan—expensive on quiet days, but stable during busy times; Speaker B: Ask about volume discounts, yearly increases, and onboarding fees.
Anna: Exit and renewal options focuses attention on a concrete part of the work. Speaker A: Ever heard of a company stuck in a contract for six months after service went downhill?, Speaker B: Unfortunately yes, because they needed 180 days' notice to terminate. Always read the exit clause, and Speaker A: Look for data portability promises too. When vendor X went bankrupt, company Y lost three months of data because extraction wasn't covered.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: Unfortunately yes, because they needed 180 days' notice to terminate. Always read the exit clause; Speaker A: Look for data portability promises too. When vendor X went bankrupt, company Y lost three months of data because extraction wasn't covered; Speaker B: Renewal terms deserve equal attention. Automatic price increases can sneak up on you if you don't have time to renegotiate.
Anna: Risk assessment frameworks focuses attention on a concrete part of the work. Speaker A: How do you know if a vendor is risky? Start by checking financial stability—are they profitable or bleeding cash?, Speaker B: Then examine security posture. When was their last penetration test and how quickly do they patch?, and Speaker A: Frameworks like NIST's vendor risk assessment or the SIG questionnaire provide structured questions.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: Then examine security posture. When was their last penetration test and how quickly do they patch?; Speaker A: Frameworks like NIST's vendor risk assessment or the SIG questionnaire provide structured questions; Speaker B: Score areas such as finance, security, and support history. If they fall below your threshold, reconsider.
Anna: Regulatory and legal considerations focuses attention on a concrete part of the work. Speaker A: When should lawyers join the negotiation?, Speaker B: Early—especially for industries like healthcare or finance, and Speaker A: Violating HIPAA can cost over $50,000 per incident, while ignoring PCI-DSS might halt your ability to process payments.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: Early—especially for industries like healthcare or finance; Speaker A: Violating HIPAA can cost over $50,000 per incident, while ignoring PCI-DSS might halt your ability to process payments; Speaker B: International deals complicate matters further. Data sovereignty laws may forbid storing customer data outside certain regions.
Anna: Vendor evaluation checklist focuses attention on a concrete part of the work. Speaker A: Before signing, what questions should we ask?, Speaker B: Start with references—call current customers and ask what went wrong and how issues were handled, and Speaker A: Verify security certifications such as SOC 2, then check financial health via credit ratings or public statements.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: Start with references—call current customers and ask what went wrong and how issues were handled; Speaker A: Verify security certifications such as SOC 2, then check financial health via credit ratings or public statements; Speaker B: 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: Red flags and hidden costs focuses attention on a concrete part of the work. Speaker A: What warning signs should make you think twice?, Speaker B: Watch for vague language like "industry-standard pricing" with no actual numbers. That's often sales talk for "expensive.", and Speaker A: 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: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: Watch for vague language like "industry-standard pricing" with no actual numbers. That's often sales talk for "expensive."; Speaker A: 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; Speaker B: 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: Post-contract relationship management focuses attention on a concrete part of the work. Speaker A: Negotiation doesn't end when the contract is signed, Speaker B: Schedule quarterly service reviews to discuss performance metrics and upcoming changes, and Speaker A: Include training and documentation requirements so your team isn't left guessing how to use the platform.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: Schedule quarterly service reviews to discuss performance metrics and upcoming changes; Speaker A: Include training and documentation requirements so your team isn't left guessing how to use the platform; Speaker B: Ongoing knowledge transfer keeps you independent rather than reliant on expensive vendor consultants.
Anna: Service delivery models focuses attention on a concrete part of the work. Speaker A: Not all services are delivered the same way. Are you outsourcing everything or sharing responsibilities?, Speaker B: You might use a hybrid model where some services stay in-house while others go to a managed provider, and Speaker A: 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: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: You might use a hybrid model where some services stay in-house while others go to a managed provider; Speaker A: 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?; Speaker B: Clear contracts specify responsibilities so you avoid finger-pointing later.
Anna: Integration requirements focuses attention on a concrete part of the work. Speaker A: Have you confirmed the vendor's system actually works with your existing tools?, Speaker B: Check API access, data exchange formats, and authentication methods, and Speaker A: A vendor might claim "it integrates with everything" only for you to learn that "everything" means their other paid products.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: Check API access, data exchange formats, and authentication methods; Speaker A: A vendor might claim "it integrates with everything" only for you to learn that "everything" means their other paid products; Speaker B: Clarify upfront whether you'll need custom development, middleware, or extra licenses.
Anna: Scalability and growth planning focuses attention on a concrete part of the work. Speaker A: What happens when your business triples in size?, Speaker B: Make sure the contract allows for scaling up—or down—without punitive fees, and Speaker A: Include options for additional capacity, more users, or even moving to a larger service tier.
Greg: In practice, ask who owns the work, what evidence proves it happened, and what handoff comes next. Use the supporting details as a checklist: Speaker B: Make sure the contract allows for scaling up—or down—without punitive fees; Speaker A: Include options for additional capacity, more users, or even moving to a larger service tier; Speaker B: I've seen companies caught off guard by data growth charges that skyrocketed after a successful marketing campaign.
Anna: The key takeaway is this: Speaker A: Negotiating a contract is about more than price, Speaker B: A well-crafted agreement covers uptime, pricing, exit strategies, and how the service will grow with you, and Speaker A: Use structured risk assessments and thorough checklists to evaluate vendors.
Greg: Use that takeaway to name the owner, evidence, and next action that should be visible after the work is done.