Blueprint Playbook for Tangoe

Who the Hell is Jordan Crawford?

Founder of Blueprint. I help companies stop sending emails nobody wants to read.

The problem with outbound isn't the message. It's the list. When you know WHO to target and WHY they need you right now, the message writes itself.

I built this system using government databases, public records, and 25 million job posts to find pain signals most companies miss. Predictable Revenue is dead. Data-driven intelligence is what works now.

The Old Way (What Everyone Does)

Your GTM team is buying lists from ZoomInfo, adding "personalization" like mentioning a LinkedIn post, then blasting generic messages about features. Here's what it actually looks like:

The Typical Tangoe SDR Email:

Subject: Optimize Your IT Spend Hi [First Name], I see your company is growing rapidly based on your recent LinkedIn post about expansion. At Tangoe, we help Fortune 500 companies gain visibility into their cloud, mobile, and telecom spending. Our platform has helped clients save millions through automated cost management. Would you be open to a 15-minute call to discuss how we can help you optimize your IT budget? Best regards, [SDR Name]

Why this fails: The prospect is an expert. They've seen this template 1,000 times. There's zero indication you understand their specific situation. Delete.

The New Way: Intelligence-Driven GTM

Blueprint flips the approach. Instead of interrupting prospects with pitches, you deliver insights so valuable they'd pay consulting fees to receive them.

1. Hard Data Over Soft Signals

Stop: "I see you're hiring compliance people" (job postings - everyone sees this)

Start: "Your 3 largest Verizon contracts expire March 15, 2025 - combined $840K annually. Verizon requires 90-day renewal notice for rate guarantees." (contract database with specific dates and amounts)

2. Mirror Situations, Don't Pitch Solutions

PQS (Pain-Qualified Segment): Reflect their exact situation with such specificity they think "how did you know?" Use contract data, spend patterns, renewal deadlines with specific amounts and dates.

PVP (Permissionless Value Proposition): Deliver immediate value they can use today - contract analysis already done, renewal calendars already built, savings opportunities already identified - whether they buy or not.

Tangoe Intelligence Plays

These messages demonstrate precise understanding of the prospect's current situation combined with immediate actionable value. Every play is ordered by quality score, with the strongest plays first.

PVP Public + Internal Strong (9.4/10)

S3 Storage Tier Migration Savings Plan

What's the play?

Analyze customer AWS S3 storage usage and provide specific migration plan showing $18K monthly savings by moving to Intelligent-Tiering. Include object-level analysis with ROI timeline.

Why this works

You're delivering a complete implementation plan with specific monthly savings. The object-level detail proves this is real analysis of their environment, not generic advice. They can evaluate and act immediately without a meeting.

Data Sources
  1. AWS Cost Explorer API - S3 storage tier usage and costs
  2. AWS S3 API - bucket configurations and object metadata

The message:

Subject: $18K monthly S3 savings - tier migration plan Your S3 costs could drop $18K monthly by moving 480TB to Intelligent-Tiering. I have the object-level analysis showing which buckets to migrate first and estimated ROI timeline. Want the migration plan?
DATA REQUIREMENT

This play requires AWS API access to analyze customer S3 bucket configurations and usage patterns.

Combined with public pricing data to calculate savings. This synthesis is unique to your platform's cloud visibility.
PVP Public + Internal Strong (9.4/10)

Verizon Rate Increase Avoidance Strategy

What's the play?

Alert customers to upcoming Verizon rate increases and provide complete avoidance strategy including renegotiation timeline, alternative carrier rates, and contract language.

Why this works

You're providing a specific strategy to avoid $84K annual cost increase with negotiation leverage. Alternative carrier rates give them concrete bargaining power. Complete action plan with contract language means they can act immediately.

Data Sources
  1. Internal customer contract database - line inventory and current rates
  2. Carrier rate change notifications
  3. Market pricing data from multiple carrier relationships

The message:

Subject: Your Verizon lines - rate increase avoidance plan Verizon's March 1 rate increase hits your 1,750 lines for $84K annually. I have the renegotiation timeline, alternative carrier rates, and contract language to avoid the increase. Want the avoidance plan?
DATA REQUIREMENT

This play requires customer line inventory, carrier rate data, and contract negotiation templates.

Combined with carrier rate change intelligence. This synthesis is unique to your telecom expense management platform.
PVP Public + Internal Strong (9.3/10)

Unallocated Cloud Spend Department Breakdown

What's the play?

Analyze customer AWS account to identify $340K in untagged resources and provide department-level breakdown by service type, region, and suspected owner based on deployment patterns.

Why this works

You're providing specific analysis of THEIR data, not generic industry stats. Department breakdown is exactly what they need for chargebacks. They can act on this immediately without a meeting to enforce cloud governance.

Data Sources
  1. AWS API - resource tags and metadata
  2. AWS Cost Explorer - spending by service and region

The message:

Subject: Your unallocated cloud spend by department Analyzed your AWS account - $340K in untagged resources across 12 departments. I have the breakdown by service type, region, and suspected owner based on deployment patterns. Want the department-level report?
DATA REQUIREMENT

This play requires AWS API access to customer accounts and ability to analyze resource metadata.

Combined with deployment pattern analysis. This synthesis enables accurate IT cost allocation.
PVP Public + Internal Strong (9.3/10)

International Roaming Plan Optimization

What's the play?

Analyze mobile invoice data to identify employees with excessive international roaming charges and provide employee-level plan mapping showing $15.6K quarterly savings.

Why this works

Employee-level detail means they can act immediately. $15.6K quarterly savings is significant. Specific plan recommendations are provided. Low-commitment ask makes it easy to engage.

Data Sources
  1. Internal mobile invoice data - roaming charges by user
  2. Carrier international plan pricing

The message:

Subject: 18K roaming waste - international plan mapping 47 employees cost you $18K in roaming charges last quarter. I have their names, destinations, and recommended international plans that would cost $2.4K quarterly. Want the employee-level plan mapping?
DATA REQUIREMENT

This play requires customer mobile invoice data and ability to map users to optimal plans.

Combined with carrier plan pricing. This synthesis delivers immediate cost reduction.
PVP Public + Internal Strong (9.3/10)

Non-Production Database Shutdown Schedule

What's the play?

Identify customer's non-production RDS databases running 24/7 and provide automated shutdown schedule with instance IDs, environments, and automation scripts for $22K monthly savings.

Why this works

Specific databases with automation solution provided. They can implement immediately without a meeting. $22K monthly savings is material. Includes technical implementation path.

Data Sources
  1. AWS RDS API - database instance usage patterns
  2. AWS Cost Explorer - RDS costs by instance

The message:

Subject: 22K monthly savings - RDS shutdown schedule Your 14 non-prod RDS databases could save $22K monthly with automated night/weekend shutdowns. I have the instance IDs, environments, and recommended automation scripts ready. Want the shutdown schedule?
DATA REQUIREMENT

This play requires AWS API access and ability to provide automation templates for customer implementation.

Combined with cost analysis. This synthesis delivers cost reduction with complete technical guidance.
PVP Public + Internal Strong (9.2/10)

Idle EC2 Instance Shutdown List

What's the play?

Analyze customer's EC2 instances to identify those idle 60+ days and provide shutdown candidate list with instance IDs, owners (based on tags), and last activity dates for $14K monthly savings.

Why this works

Completely actionable - specific instances with owners identified. They can review and act immediately without a meeting. $14K monthly savings is material. Low-commitment ask.

Data Sources
  1. AWS CloudWatch API - EC2 instance utilization metrics
  2. AWS EC2 API - instance tags and metadata

The message:

Subject: 14K monthly waste - idle instance shutdown list Found 18 EC2 instances idle 60+ days costing $14K monthly. I have the instance IDs, owners (based on tags), and last activity dates ready to review. Want the shutdown candidate list?
DATA REQUIREMENT

This play requires AWS API access to analyze instance utilization and tag metadata.

Combined with ownership identification. This synthesis enables immediate cost reduction.
PVP Public + Internal Strong (9.2/10)

Reserved Instance Renewal Strategy

What's the play?

Alert customers to expiring Reserved Instances and provide renewal plan with utilization analysis and optimal RI purchase recommendations for $45K annual savings.

Why this works

Specific savings with clear action path. Utilization analysis means this is real research, not generic. They can evaluate and purchase immediately. $45K annual savings is material.

Data Sources
  1. AWS API - Reserved Instance inventory and expiration dates
  2. AWS Cost Explorer - RI utilization analysis

The message:

Subject: 45K annual savings - RI renewal strategy Your 23 Reserved Instances expire April 2025 - renewal saves $45K vs on-demand. I have the instance types, utilization analysis, and optimal RI purchase recommendations. Want the renewal plan?
DATA REQUIREMENT

This play requires AWS API access to analyze RI utilization and provide purchase recommendations.

Combined with cost analysis. This synthesis prevents cost increase with specific purchasing strategy.
PVP Public + Internal Strong (9.1/10)

Q1 Telecom Renewal Calendar

What's the play?

Provide customers with complete Q1 2025 telecom renewal calendar including all 47 contracts, vendors, penalty trigger dates, current rates, and suggested negotiation timelines based on vendor patterns.

Why this works

Complete deliverable they can use immediately. Vendor negotiation patterns add value beyond just dates. Low-commitment ask. Helps them manage entire renewal season proactively.

Data Sources
  1. Internal contract database - renewal dates and penalty terms
  2. Historical vendor negotiation data

The message:

Subject: 47 renewals due Q1 - penalty dates by contract Pulled your Q1 2025 telecom renewals - 47 contracts, 23 with early notification penalties. I have the spreadsheet with penalty trigger dates, current rates, and vendor contacts. Want me to send it?
DATA REQUIREMENT

This play requires contract database with renewal dates and penalty terms from customer implementations.

Combined with vendor negotiation patterns. This synthesis enables proactive contract management.
PVP Public + Internal Strong (9.1/10)

Sprint T-Mobile Migration Checklist

What's the play?

Provide customers with complete Sprint to T-Mobile migration checklist including line-by-line current plans, T-Mobile equivalents, and cost impact analysis for the February 28 carrier mandate.

Why this works

Complete deliverable for mandatory migration. Line-by-line detail shows this is real work, not generic advice. Cost impact analysis helps them forecast budget. Low-commitment ask.

Data Sources
  1. Internal mobile inventory - Sprint plan codes
  2. T-Mobile plan mapping data

The message:

Subject: 340 Sprint lines - T-Mobile migration checklist Your 340 Sprint lines must migrate by February 28 - I built the migration checklist. Includes line-by-line current plans, T-Mobile equivalents, and cost impact analysis. Want the migration plan?
DATA REQUIREMENT

This play requires customer mobile inventory and T-Mobile plan mapping data.

Combined with carrier migration requirements. This synthesis simplifies mandatory migration.
PVP Public + Internal Strong (9.0/10)

Q1 Renewal Calendar with Vendor Patterns

What's the play?

Build complete Q1 2025 telecom renewal calendar with all 47 contracts, vendors, penalty trigger dates, and suggested negotiation timelines based on vendor negotiation patterns.

Why this works

Complete deliverable they can use immediately. Vendor negotiation patterns add value beyond just dates. Low-commitment ask. Helps them manage entire renewal season proactively.

Data Sources
  1. Internal contract database - renewal dates and penalty terms
  2. Historical vendor negotiation data

The message:

Subject: Q1 renewal calendar - vendors and penalty dates Built you a Q1 2025 telecom renewal calendar with all 47 contracts, vendors, and penalty trigger dates. Includes current rates and suggested negotiation timelines based on vendor patterns. Want me to send it?
DATA REQUIREMENT

This play requires customer contract database and historical vendor negotiation data.

Combined with negotiation insights. This synthesis enables proactive contract management.
PVP Public + Internal Strong (9.0/10)

Orphaned Load Balancer Cleanup List

What's the play?

Identify customer's Application Load Balancers with zero traffic for 45+ days and provide cleanup candidate list with ALB names, associated VPCs, and last activity dates for $8K monthly savings.

Why this works

Specific ALBs with technical details provided. They can review and act immediately. $8K monthly savings from simple cleanup. Low-commitment ask.

Data Sources
  1. AWS CloudWatch API - ALB traffic patterns
  2. AWS API - ALB configurations and VPC associations

The message:

Subject: 8K monthly waste - orphaned ALB list Found 7 Application Load Balancers with zero traffic for 45+ days costing $8K monthly. I have the ALB names, associated VPCs, and last activity dates ready. Want the cleanup candidate list?
DATA REQUIREMENT

This play requires AWS API access to ALB configurations and CloudWatch metrics.

Combined with traffic analysis. This synthesis identifies waste for immediate cleanup.
PVP Public + Internal Strong (8.9/10)

AT&T Contract Market Rate Comparison

What's the play?

Provide customers with market rate comparison for their AT&T contract renewal, showing their existing rate vs market average for their region to use in negotiations.

Why this works

Specific line count and rate comparison shows real research. Market rate context helps them evaluate renewal terms. They can use this in negotiations immediately. Low-commitment ask.

Data Sources
  1. Internal customer contract rates
  2. Aggregated market pricing data from multiple carrier relationships

The message:

Subject: Your AT&T renewal terms vs market rates Your AT&T contract renews January 12 - I pulled current market rates for 1,200 enterprise lines. Your existing rate is $30/line vs market average of $26/line in your region. Want the rate comparison?
DATA REQUIREMENT

This play requires customer contract rates and aggregated market pricing data from multiple carrier relationships.

This is proprietary data only you have - provides negotiation leverage with specific benchmarks.
PQS Public + Internal Strong (8.8/10)

International Roaming Overspending Alert

What's the play?

Analyze mobile invoice data to identify employees with excessive international roaming charges and alert customers to the $18K vs $2.4K opportunity.

Why this works

Specific employee count and overage amount shows real analysis. $18K vs $2.4K comparison is stark and actionable. Clear cost savings opportunity. Easy routing question.

Data Sources
  1. Internal mobile invoice data - roaming charges by user

The message:

Subject: International roaming - 47 employees overspending 47 employees triggered international roaming charges exceeding $200 last quarter. Total overage was $18K when international plans would cost $2.4K quarterly. Who manages your mobile plan optimization?
DATA REQUIREMENT

This play requires customer mobile invoice data and ability to identify roaming patterns by user.

Combined with carrier plan pricing. This synthesis identifies significant waste.
PQS Public + Internal Strong (8.7/10)

Verizon Rate Increase Impact Alert

What's the play?

Alert customers to upcoming Verizon rate increases and quantify the $84K annual impact across their line count, with specific deadline to renegotiate.

Why this works

Specific rate increase and line count shows research. $84K annual impact is material and quantified. February 1 deadline creates actionable urgency. Easy yes/no question.

Data Sources
  1. Internal customer carrier contract data
  2. Carrier rate change notifications

The message:

Subject: Verizon rate increase March 1 - 840K impact Verizon is implementing a $4/line rate increase effective March 1, 2025. Across your 1,750 Verizon lines, that's $84K annually unless you renegotiate before February 1. Is procurement aware of the increase deadline?
DATA REQUIREMENT

This play requires customer carrier contract data and carrier rate change notifications.

Combined with impact calculation. This synthesis creates urgency for renegotiation.
PQS Public + Internal Strong (8.7/10)

S3 Storage Tier Optimization Alert

What's the play?

Analyze customer AWS S3 storage growth and identify $18K monthly savings opportunity from optimizing storage tier usage.

Why this works

Specific storage numbers and growth rate shows real analysis. $18K monthly savings is significant and quantified. Storage tier recommendation is actionable. Easy routing question.

Data Sources
  1. AWS Cost Explorer API - S3 storage patterns and tier usage

The message:

Subject: Your S3 storage doubled to 480TB in 90 days Your AWS S3 storage went from 240TB to 480TB in the last 90 days. 73% of that growth is in Standard tier when Intelligent-Tiering could save $18K monthly. Who manages your cloud optimization reviews?
DATA REQUIREMENT

This play requires AWS Cost Explorer API access to analyze customer storage patterns and tier usage.

Combined with optimization recommendations. This synthesis identifies significant savings.
PQS Public + Internal Strong (8.6/10)

Untagged AWS Spend Alert

What's the play?

Analyze customer AWS spending to identify $340K in untagged resources making it impossible to allocate cloud costs back to departments accurately.

Why this works

Specific dollar amount and percentage shows they analyzed actual AWS account. The tagging gap is a legitimate visibility problem. Easy routing question. Directly relevant to budget allocation responsibilities.

Data Sources
  1. AWS billing data via API integration
  2. AWS resource tagging analysis

The message:

Subject: $340K in untagged AWS spend last quarter Your AWS bill grew $340K quarter-over-quarter, but 68% of new resources have no cost center tags. That makes it impossible to allocate cloud costs back to departments accurately. Who owns cloud tagging governance?
DATA REQUIREMENT

This play requires visibility into customer AWS billing data and resource tagging via API integration.

Combined with cost allocation analysis. This synthesis identifies governance gaps.
PQS Public + Internal Strong (8.6/10)

Reserved Instance Expiration Alert

What's the play?

Alert customers to expiring Reserved Instances worth $45K annually that will convert to 3x on-demand pricing without renewal.

Why this works

Specific RI count and expiration timing shows monitoring. $45K annual value and 3x cost increase is concerning. April 2025 gives reasonable planning time. Easy routing question.

Data Sources
  1. AWS API - Reserved Instance inventory and expiration dates

The message:

Subject: Reserved Instance expiring April 2025 - $45K risk You have 23 EC2 Reserved Instances expiring in April 2025 worth $45K annually. Without renewal, those instances convert to on-demand pricing at 3x the cost. Who manages your RI purchasing strategy?
DATA REQUIREMENT

This play requires AWS API access to customer Reserved Instance inventory and expiration dates.

Combined with pricing analysis. This synthesis prevents significant cost increase.
PQS Public + Internal Strong (8.6/10)

Non-Production Database Waste Alert

What's the play?

Identify customer RDS databases running continuously in non-production environments and quantify $22K monthly savings opportunity from night/weekend shutdowns.

Why this works

Specific database count and savings calculation shows analysis. Non-production callout makes this safe and actionable. $22K monthly is significant. Easy routing question.

Data Sources
  1. AWS RDS API - database instance usage patterns

The message:

Subject: Your RDS databases running 24/7 - $22K opportunity You have 14 RDS databases running continuously in non-production environments. Shutting them down nights/weekends could save $22K monthly with zero production impact. Who manages your database environment policies?
DATA REQUIREMENT

This play requires AWS RDS API access to analyze customer database instance usage patterns.

Combined with cost analysis. This synthesis identifies safe optimization opportunity.
PQS Public + Internal Strong (8.5/10)

Verizon Contract Renewal Deadline Alert

What's the play?

Alert customers to approaching Verizon contract renewal with specific dollar amount and 90-day notice requirement deadline.

Why this works

Specific vendor, date, and dollar amount shows detailed research. 90-day notice requirement is legitimate pressure point. Easy routing question. Time-sensitive and actionable.

Data Sources
  1. Internal contract database - vendor terms and renewal notification requirements

The message:

Subject: 3 Verizon contracts up March 15 - $840K Your 3 largest Verizon contracts expire March 15, 2025 - combined $840K annually. Verizon requires 90-day renewal notice for rate guarantees, which is December 15. Is finance already negotiating these?
DATA REQUIREMENT

This play requires customer contract database with vendor terms and renewal notification requirements.

Combined with deadline tracking. This synthesis creates actionable urgency.
PQS Public + Internal Strong (8.5/10)

Orphaned Load Balancer Waste Alert

What's the play?

Identify customer Application Load Balancers with zero traffic for 45+ days and quantify $8K monthly waste from decommissioned projects.

Why this works

Specific ALB count and traffic analysis shows real monitoring. $8K monthly waste from forgotten resources is believable. Decommissioned project explanation makes sense. Easy routing question.

Data Sources
  1. AWS CloudWatch API - ALB traffic patterns

The message:

Subject: Your Load Balancers serving zero traffic - $8K waste You have 7 Application Load Balancers with zero traffic for 45+ days. They're costing $8K monthly and appear to be from decommissioned projects. Who should review the ALB cleanup?
DATA REQUIREMENT

This play requires AWS CloudWatch API access to analyze ALB traffic patterns.

Combined with cost analysis. This synthesis identifies cleanup opportunity.
PQS Public + Internal Strong (8.4/10)

Q1 Telecom Renewal Penalty Alert

What's the play?

Alert customers to Q1 2025 telecom contract renewals with penalty clauses for late notification, creating urgency to engage procurement.

Why this works

Specific contract count and dollar amount shows real research. Penalty clause detail is legitimately concerning. Easy routing question. Actionable timeline pressure.

Data Sources
  1. Internal contract database - renewal dates and penalty terms

The message:

Subject: Your Q1 2025 telecom renewals - $2.3M at risk You have 47 telecom contracts renewing in Q1 2025 worth $2.3M annually. 23 of those contracts have penalty clauses for late renewal notifications (60-90 days prior). Is procurement already tracking these deadlines?
DATA REQUIREMENT

This play requires contract database with renewal dates and penalty terms from customer implementations.

Combined with deadline tracking. This synthesis creates urgency to avoid penalties.
PQS Public + Internal Strong (8.4/10)

Sprint T-Mobile Migration Deadline Alert

What's the play?

Alert customers to Sprint T-Mobile migration deadline with specific line count still on legacy plans and no migration plan filed.

Why this works

Specific line count and carrier deadline shows research. February 28 deadline creates legitimate urgency. Migration mandate is real industry issue. Easy routing question.

Data Sources
  1. Internal mobile inventory - Sprint plan identification

The message:

Subject: Sprint T-Mobile migration deadline February 28 Your legacy Sprint contracts must migrate to T-Mobile by February 28, 2025 per carrier mandate. You have 340 lines still on Sprint plans with no migration plan filed. Who's coordinating the T-Mobile transition?
DATA REQUIREMENT

This play requires customer mobile inventory and ability to identify legacy Sprint plan codes.

Combined with carrier mandate tracking. This synthesis creates urgency for mandatory migration.
PQS Public + Internal Strong (8.3/10)

AT&T Contract Renewal Deadline Missed

What's the play?

Alert customers to AT&T contract renewal with missed 75-day competitive quote deadline, creating urgency to engage procurement.

Why this works

Specific contract details and line count shows research. Missed deadline creates urgency and legitimate concern. Easy yes/no routing question. Actionable timeline pressure.

Data Sources
  1. Internal contract database - carrier terms and notification requirements

The message:

Subject: AT&T contract renews January 12 - no quote yet Your AT&T enterprise mobility contract renews January 12, 2025 - 1,200 lines, $432K annually. AT&T requires 75-day notice for competitive quotes, which passed on October 29. Has procurement already received renewal terms?
DATA REQUIREMENT

This play requires customer contract database with carrier terms and notification requirements.

Combined with deadline tracking. This synthesis creates urgency around missed opportunity.
PQS Public + Internal Strong (8.8/10)

Idle EC2 Instance Waste Alert

What's the play?

Identify customer EC2 instances running 60+ days with CPU utilization under 5% and quantify $14K monthly waste from orphaned dev/test environments.

Why this works

Specific instance count and utilization metric shows real analysis. $14K monthly waste is concrete and concerning. Orphaned dev/test explanation makes sense - common problem. Easy routing question.

Data Sources
  1. AWS CloudWatch API - EC2 utilization metrics

The message:

Subject: 18 EC2 instances idle for 60+ days - $14K waste You have 18 EC2 instances running 60+ days with CPU utilization under 5%. They're costing $14K monthly and appear to be orphaned dev/test environments. Who should own the shutdown review?
DATA REQUIREMENT

This play requires AWS CloudWatch API access to analyze customer EC2 utilization metrics.

Combined with cost analysis. This synthesis identifies significant waste.

What Changes

Old way: Spray generic messages about "visibility into IT spend" at job titles. Hope someone replies.

New way: Use contract data and cloud monitoring to find companies with specific renewal deadlines, penalty clauses, and waste patterns. Then mirror that situation back to them with evidence.

Why this works: When you lead with "Your 3 largest Verizon contracts expire March 15 - combined $840K annually, 90-day notice required by December 15" instead of "I see you manage telecom contracts," you're not another sales email. You're the person who did the homework.

The messages above aren't templates. They're examples of what happens when you combine real data sources (contract databases, AWS APIs, carrier rate data) with specific situations. Your team can replicate this using the data recipes in each play.

Data Sources Reference

Every play traces back to verifiable data. Here are the sources used in this playbook:

Source Key Fields Used For
Internal Contract Database renewal_dates, penalty_terms, vendor_names, contract_values Renewal deadline alerts, penalty tracking, negotiation timing
AWS Cost Explorer API spend_by_service, storage_patterns, RI_utilization, cost_trends Cloud cost optimization, storage tier analysis, RI renewal planning
AWS CloudWatch API EC2_utilization, RDS_usage_patterns, ALB_traffic_metrics Idle resource identification, usage optimization, waste detection
AWS EC2/RDS/S3 APIs resource_tags, instance_metadata, bucket_configurations Cost allocation, ownership identification, configuration analysis
Mobile Invoice Data roaming_charges_by_user, line_inventory, plan_codes Roaming optimization, Sprint migration tracking, plan optimization
Carrier Rate Change Notifications effective_dates, rate_increases, notification_deadlines Rate increase alerts, renegotiation timing, cost impact analysis
Market Pricing Data carrier_rates_by_region, enterprise_line_pricing, benchmark_data Contract negotiation leverage, market rate comparisons