Blueprint Playbook for Navitas Life Sciences

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 Navitas Life Sciences SDR Email:

Subject: Streamline your clinical research operations Hi [Name], I see your company is conducting clinical trials. Navitas Life Sciences helps life sciences companies manage complex research data and regulatory compliance. Our platform automates workflows, ensures FDA compliance, and provides audit trail management for multi-site operations. Would love to show you how we've helped pharma companies reduce submission time by 30%. Available for a quick call next week? Best, [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 Seattle facility received FDA Warning Letter WL-320214-24 on November 14th for data integrity violations" (government database with record number)

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 government data with dates, record numbers, facility addresses.

PVP (Permissionless Value Proposition): Deliver immediate value they can use today - analysis already done, deadlines already pulled, patterns already identified - whether they buy or not.

Navitas Life Sciences Best Plays: Delivering Immediate Value

These messages provide actionable intelligence before asking for anything. The prospect can use this value today whether they respond or not. Ordered by quality score.

PVP Public Data Strong (9.4/10)

Systemic CAPA Plan for Repeat Data Integrity Violations

What's the play?

Target drug manufacturers with 2+ warning letters for the same violation category within 24 months. Offer a root cause analysis showing systemic gaps across all citations with unified CAPA recommendations.

Why this works

Repeat violations trigger FDA consent decree discussions. The recipient needs a systemic response that addresses all citations holistically, not individual CAPAs. You're delivering the exact analysis their FDA response requires.

Data Sources
  1. FDA Warning Letters Database - recipient_company, violation_type, violation_date
  2. Drug Establishments Database (DECRS) - establishment_name, facility_address
  3. FDA Inspection Results (Form 483) - inspection_findings, 483_observations

The message:

Subject: Your systemic CAPA plan for 3 data integrity violations I reviewed all 3 of your data integrity citations (Jan 2023 Form 483, June 2023 Warning Letter, November 2024 Warning Letter) and mapped the systemic root causes. You've got 2 recurring procedural gaps and 1 training deficiency showing up in all three citations - these need a unified CAPA. Want the root cause analysis with recommended systemic corrections?
PQS Public Data Strong (9.3/10)

Third ALCOA+ Violation Since 2023

What's the play?

Target manufacturers with 3+ FDA citations for ALCOA+ data integrity failures within 24 months. Mirror the escalation pattern with exact dates and violation history.

Why this works

Three violations in 24 months triggers FDA's consent decree protocol. You're documenting a serious compliance trajectory the recipient urgently needs to address before enforcement escalates further.

Data Sources
  1. FDA Warning Letters Database - recipient_company, violation_type, violation_date
  2. Drug Establishments Database (DECRS) - establishment_name, facility_address
  3. FDA Inspection Results (Form 483) - inspection_date, inspection_findings

The message:

Subject: Seattle facility's third ALCOA+ violation since 2023 Your Seattle site has received 3 FDA citations for ALCOA+ data integrity failures since January 2023 (Form 483 Jan 2023, Warning Letter June 2023, Warning Letter November 2024). The FDA's escalation protocol moves to consent decree discussions after 3 violations in 24 months. Who's owning the systemic CAPA across all three citations?
PVP Public Data Strong (9.2/10)

21 CFR Part 11 Violation Mapping

What's the play?

Map all data integrity citations to specific 21 CFR Part 11 subsections being violated. Show systemic compliance gaps with regulatory language and required fixes.

Why this works

The recipient needs a defensible FDA response that addresses regulatory requirements precisely. You're delivering technical regulatory mapping that strengthens their CAPA documentation.

Data Sources
  1. FDA Warning Letters Database - recipient_company, violation_type, violation_date
  2. 21 CFR Part 11 (Electronic Records) - regulatory subsections

The message:

Subject: Your 3 data integrity violations mapped to 21 CFR Part 11 I mapped all 3 of your data integrity citations to specific 21 CFR Part 11 subsections you're violating. You've got 4 subsections cited across all 3 violations - these are your systemic compliance gaps. Want the mapping with the specific regulatory language and required fixes?
PQS Public Data Strong (9.1/10)

Second Data Integrity Warning Letter in 18 Months

What's the play?

Target manufacturers with 2+ warning letters for data integrity violations within 18 months. Mirror the repeat violation pattern with exact dates and facility location.

Why this works

Repeat violations in the same category trigger consent decree consideration. You're naming a crisis-level situation that requires immediate coordinated CAPA response across both citations.

Data Sources
  1. FDA Warning Letters Database - recipient_company, violation_type, violation_date
  2. Drug Establishments Database (DECRS) - establishment_name, facility_address

The message:

Subject: Your second data integrity warning letter in 18 months The FDA issued you a warning letter on November 14th 2024 for data integrity violations at your Seattle facility - your second in 18 months. Repeat violations in the same category trigger consent decree consideration and potential production halts. Is someone coordinating the CAPA response across both letters?
PVP Public + Internal Strong (9.0/10)

Satellite Site Compliance Risk Ranking

What's the play?

Analyze compliance variance across all trial sites and rank them by FDA inspection risk. Deliver site-specific risk analysis prioritizing the highest-risk locations.

Why this works

The recipient needs to allocate limited compliance resources smartly. You're delivering prioritized risk analysis that helps them focus on sites most likely to receive FDA findings.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, locations, enrollment_status
  2. Internal Customer Data - site-level compliance variance, deviation rates, audit trail completeness

The message:

Subject: Your 3 highest-risk satellite sites for FDA inspection I analyzed compliance variance across your 7 NCT04567890 sites and ranked them by FDA inspection risk. Your Phoenix, Atlanta, and Denver sites have the highest deviation rates and audit trail gaps - they'd be my focus if I were the FDA. Want the risk analysis with specific findings for each site?
DATA REQUIREMENT

This play requires compliance variance data across trial sites showing deviation rates, audit trail completeness, and protocol adherence by location.

Combined with public ClinicalTrials.gov data to identify multi-site programs. This synthesis is unique to your platform.
PQS Public + Internal Strong (9.0/10)

Aseptic Processing Validation Expiring During Inspection Window

What's the play?

Target manufacturers whose aseptic processing validation is expiring during their FDA routine inspection window. Mirror the coinciding timing urgency.

Why this works

Expired validation during FDA inspection is catastrophic. You're surfacing a timing collision the recipient may not have connected, creating immediate urgency to schedule revalidation.

Data Sources
  1. Drug Establishments Database (DECRS) - establishment_name, facility_address, establishment_type
  2. FDA Inspection Results Database - last_inspection_date, inspection_type
  3. Internal Customer Data - validation records, equipment registration, revalidation schedules

The message:

Subject: Your Cambridge aseptic processing validation expires March 2025 Your FEI 3004567890 aseptic processing validation was completed March 2022 and has a 3-year revalidation requirement. That puts your revalidation due March 2025 - exactly when you're in the FDA inspection window. Is your revalidation study scheduled yet?
DATA REQUIREMENT

This play requires validation records showing equipment type, validation completion dates, and revalidation schedules.

Combined with public FDA facility and inspection data to identify timing collision. This synthesis requires internal validation tracking.
PVP Public + Internal Strong (8.9/10)

Statistical Analysis Plan Review Against FDA Rejections

What's the play?

Review the sponsor's statistical analysis plan against FDA's recent Phase 3 application rejections in their therapeutic area. Identify analysis approaches that triggered FDA questions.

Why this works

The recipient can avoid costly submission rejection by fixing SAP issues before submission. You're delivering comparative analysis against real FDA feedback that prevents future problems.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, study_type, condition
  2. Internal Customer Data - statistical analysis plans, FDA Complete Response Letter patterns, rejection analysis by therapeutic area

The message:

Subject: Your IND 145392 statistical analysis plan review I reviewed your statistical analysis plan for IND 145392 against FDA's recent Phase 3 application rejections in your therapeutic area. There are 3 analysis approaches in your SAP that triggered FDA questions in 67% of recent rejections. Want me to send you the comparison with specific FDA feedback from those rejections?
DATA REQUIREMENT

This play requires database of FDA Complete Response Letters and rejection patterns by therapeutic area, with analysis approach categorization.

Combined with public clinical trial data to identify sponsors. This FDA feedback synthesis is unique to regulatory data platform expertise.
PQS Public + Internal Strong (8.9/10)

Stability Data Gap Blocking Phase 3 Submission

What's the play?

Target Phase 2 sponsors whose stability data doesn't meet FDA guidance requirements for Phase 3 applications in their therapeutic area. Mirror the timeline impact.

Why this works

Stability data gaps are submission blockers that add months to timeline. You're surfacing a critical requirement the recipient may have missed, preventing a major delay.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, study_type, condition, last_updated
  2. Internal Customer Data - Phase 2 protocol data, stability study protocols, FDA guidance documents by therapeutic area

The message:

Subject: IND 145392 needs 3 additional stability timepoints Your Phase 2 used 6-month stability data but FDA guidance for Phase 3 applications in your therapeutic area requires 12-month stability. You need 3 additional timepoints before submission - that's 6 more months from your February data lock. Is your stability study already running the extended protocol?
DATA REQUIREMENT

This play requires knowledge of Phase 2 protocol stability requirements and FDA therapeutic area guidance documents for Phase 3 applications.

Combined with public clinical trial data. Requires regulatory expertise in therapeutic-specific stability requirements.
PVP Public + Internal Strong (8.8/10)

Satellite Site Training Gap Analysis

What's the play?

Compare training records across all trial sites and identify specific GCP modules missing at sites with protocol deviations. Deliver training completion timelines.

Why this works

You're connecting training gaps to observed deviations, giving the recipient a clear fix path. The specificity of identifying exact modules makes this immediately actionable.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, locations, enrollment_status
  2. Internal Customer Data - training management system records, GCP module completion by site, protocol deviation data

The message:

Subject: Your satellite site training gap analysis for NCT04567890 I compared training records across your 7 trial sites and found Phoenix, Atlanta, and Denver are missing 2 specific GCP modules that Boston completed. Those 2 modules cover the exact protocol requirements where you're seeing deviations. Want the training gap analysis with completion timelines?
DATA REQUIREMENT

This play requires training management system data showing GCP module completion by site and investigator, plus protocol deviation tracking.

Combined with public trial data to identify multi-site sponsors. This training-deviation correlation requires internal platform data.
PQS Public Data Strong (8.8/10)

CAPA Response Due in 15 Working Days

What's the play?

Target manufacturers whose FDA warning letter CAPA response deadline is approaching (15 working days from issuance). Mirror the exact deadline with time elapsed.

Why this works

The timeline calculation creates immediate urgency. With a repeat violation pattern, missing this deadline escalates FDA enforcement. This is time-sensitive and actionable.

Data Sources
  1. FDA Warning Letters Database - recipient_company, violation_type, violation_date

The message:

Subject: Seattle CAPA response due February 13th 2025 Your November 14th 2024 warning letter requires CAPA response within 15 working days - that's February 13th 2025. You're now at 8 weeks since issuance with a repeat data integrity violation pattern. Is your CAPA response submitted yet?
PVP Public + Internal Strong (8.8/10)

Phase Transition Timeline Bottleneck Analysis

What's the play?

Map the sponsor's Phase 2-to-3 submission timeline with all FDA milestones and internal dependencies. Identify critical path bottlenecks causing 6-8 week delays.

Why this works

You're delivering analysis the recipient needs but hasn't done yet. The specific bottleneck identification and delay quantification makes this immediately valuable for timeline recovery.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, enrollment_status, last_updated
  2. Internal Customer Data - aggregated Phase 2-to-3 transition timelines, submission preparation workflows, typical bottleneck patterns

The message:

Subject: Your Phase 2-to-3 submission timeline mapped I mapped your IND 145392 data lock (Feb 15) through Phase 3 submission with every FDA milestone and internal dependency. You've got 4 critical path bottlenecks that could delay your Q2 2025 target by 6-8 weeks. Want me to send you the timeline with the specific bottlenecks?
DATA REQUIREMENT

This play requires aggregated Phase transition timeline data from customer workflows showing typical bottlenecks and milestone durations.

Combined with public protocol data to model recipient's specific timeline. This benchmarking requires internal customer workflow data.
PQS Public + Internal Strong (8.7/10)

EDC Login Activity Gap Correlates to Protocol Deviations

What's the play?

Target sponsors whose satellite site investigators show low EDC login frequency compared to lead sites, correlating with higher protocol deviation rates.

Why this works

You're surfacing operational intelligence the recipient didn't connect. The login activity correlation to deviations suggests supervision issues, creating actionable insight.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, locations, enrollment_status
  2. Internal Customer Data - EDC audit logs showing site investigator login frequency, protocol deviation reporting by site

The message:

Subject: Your NCT04567890 Phoenix site EDC login activity shows gap Phoenix site investigators logged into your EDC system only 12 times in Q4 2024 compared to 47 logins at Boston. That activity gap correlates with your 3 protocol deviations and suggests supervision issues. Is anyone reviewing Phoenix's PI engagement level?
DATA REQUIREMENT

This play requires EDC audit log data showing investigator login frequency by site and user, plus deviation reporting by location.

Combined with public clinical trial data to identify multi-site sponsors. This EDC activity analysis requires internal platform access.
PVP Public + Internal Strong (8.7/10)

Inspection Readiness Checklist for Sterile Manufacturing

What's the play?

Build facility-specific inspection prep checklist based on the 12 most common sterile manufacturing citations from 2024 FDA inspections. Include SOPs, records, and equipment logs FDA typically requests.

Why this works

You're delivering practical preparation help customized to their facility type. The "first 2 hours" detail shows you understand FDA inspection procedure, building credibility.

Data Sources
  1. Drug Establishments Database (DECRS) - establishment_name, facility_address, establishment_type
  2. FDA Inspection Results (Form 483) - inspection_findings, 483_observations by facility type
  3. Internal Expertise - pattern analysis of common sterile manufacturing citations, inspection procedure knowledge

The message:

Subject: Your Cambridge facility inspection readiness checklist I built an inspection prep checklist for your Cambridge facility (FEI 3004567890) based on the 12 most common sterile manufacturing citations from 2024 FDA inspections. It includes the specific SOPs, records, and equipment logs the FDA typically requests in the first 2 hours. Want me to send you the checklist?
DATA REQUIREMENT

This play requires internal expertise analyzing FDA Form 483 patterns by facility type to identify common citations and typical inspection document requests.

Combined with public inspection and facility data. This pattern analysis requires regulatory consulting expertise.
PQS Public + Internal Strong (8.7/10)

IND Data Lock to Phase 3 Submission in 31 Days

What's the play?

Target Phase 2 sponsors whose data lock date leaves only 31 days to complete statistical analysis, CSR writing, and Phase 3 application before their stated Q2 target.

Why this works

You know their exact data lock date from protocol amendments. The 31-day calculation makes timeline pressure concrete and immediate. This hits hard because it's THEIR specific problem.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, enrollment_status, last_updated
  2. Internal Knowledge - protocol amendments in FDA database, client milestone tracking, typical Phase transition timelines

The message:

Subject: IND 145392 data lock scheduled for February 15th Your Phase 2 data lock is February 15th according to your protocol amendment filed November 2024. That gives you 31 days to complete statistical analysis, write the CSR, and submit the Phase 3 application before your stated Q2 target. Who's coordinating the submission package?
DATA REQUIREMENT

This play assumes access to protocol amendments in FDA database combined with internal tracking of client milestones and typical submission timelines.

Combined with public clinical trial data. Requires monitoring of protocol amendments and regulatory milestone tracking.
PVP Public + Internal Strong (8.6/10)

Protocol Deviation Root Cause Analysis

What's the play?

Analyze all protocol deviations at satellite sites and trace them to specific procedural gaps. Compare to lead sites with zero deviations to identify training program differences.

Why this works

The root cause finding is immediately actionable. The comparison to the lead site helps the recipient see the gap clearly and understand what needs fixing.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, locations, enrollment_status
  2. Internal Customer Data - trial deviation reporting by site, training program documentation, procedural gap analysis

The message:

Subject: Phoenix site protocol deviation root cause analysis I analyzed all 3 protocol deviations at your Phoenix site for NCT04567890 and traced them to 2 specific procedural gaps. Both gaps are in your satellite site training program - not present at your Boston lead site which had zero deviations. Want the analysis with recommended training fixes?
DATA REQUIREMENT

This play requires trial deviation reporting combined with training program documentation to identify procedural gaps by site.

Combined with public trial data to identify sponsors. This root cause analysis requires internal deviation tracking and training program access.
PQS Public + Internal Strong (8.6/10)

Site-Level Protocol Deviation Variance Pattern

What's the play?

Target sponsors whose satellite sites show protocol deviation clustering while lead sites have zero deviations. Mirror the variance pattern with specific site names and deviation counts.

Why this works

The variance insight is valuable - the recipient may not have compared sites this way. FDA scrutiny during pre-approval inspections makes this urgent and actionable.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, locations, enrollment_status
  2. Internal Customer Data - site-level compliance variance, protocol deviation tracking by location

The message:

Subject: Your Phoenix site has 3 protocol deviations vs 0 in Boston NCT04567890 shows your Phoenix site logged 3 protocol deviations in Q4 2024 while your Boston lead site had zero. That variance pattern triggers enhanced FDA scrutiny during pre-approval inspections. Is anyone reviewing Phoenix's deviation root causes?
DATA REQUIREMENT

This play assumes access to ClinicalTrials.gov site-level reporting combined with internal analysis of compliance patterns across trial networks.

Combined with public trial data. This site-level variance analysis requires internal compliance tracking systems.
PQS Public Data Strong (8.5/10)

Manufacturing Facility in Routine Inspection Window

What's the play?

Target sterile drug manufacturers whose last FDA inspection was 34+ months ago, putting them in the Q1-Q2 2025 routine inspection window. Mirror the timing with FEI number and last inspection date.

Why this works

The specific FEI number and 34-month calculation shows research. The Q1-Q2 window prediction is valuable and creates immediate pressure to prepare now.

Data Sources
  1. Drug Establishments Database (DECRS) - establishment_name, facility_address, establishment_type
  2. FDA Inspection Results Database - last_inspection_date, inspection_type

The message:

Subject: Your FEI 3004567890 last inspected March 2022 Your Cambridge facility (FEI 3004567890) was last inspected March 2022 - that's 34 months ago. FDA targets routine inspections every 24-36 months for sterile drug manufacturers, putting you in the Q1-Q2 2025 window. Is someone preparing the inspection readiness documentation?
PQS Public Data Strong (8.4/10)

Sterile Manufacturing Facility 6 Months Overdue for Inspection

What's the play?

Target sterile injectable manufacturers that haven't had an FDA inspection since March 2022, making them 6 months overdue based on typical 28-month intervals.

Why this works

Specific facility and product type shows understanding of their operations. The "overdue" framing creates appropriate urgency about immediate inspection prep.

Data Sources
  1. Drug Establishments Database (DECRS) - establishment_name, facility_address, drugs_manufactured, establishment_type
  2. FDA Inspection Results Database - last_inspection_date, inspection_type

The message:

Subject: Cambridge facility due for sterile manufacturing inspection Your Cambridge site manufactures sterile injectables and hasn't had an FDA inspection since March 2022. The FDA's ORA inspection scheduling shows your facility type averaging 28-month intervals - you're 6 months overdue. Who's leading your current inspection prep?
PQS Public + Internal Strong (8.4/10)

Phase 2-to-3 Transition Timeline at Risk

What's the play?

Target Phase 2 sponsors with Phase 3 planned for Q2 2025. Calculate timeline risk using FDA's median review time and their completion target.

Why this works

Extremely specific - you know their exact IND number and timeline. The 74-day FDA stat provides context but the insight is about THEIR timeline risk. This is a real risk they need to address.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, enrollment_status, last_updated
  2. Internal Knowledge - client Phase transition timelines, submission planning, FDA review time benchmarks

The message:

Subject: Your IND 145392 Phase 2-to-3 transition in March Your IND 145392 shows Phase 2 completion targeted for March 2025 with Phase 3 planned for Q2. The FDA's median review time for Phase 3 applications is 74 days - that puts you at risk of missing your Q2 window. Is someone mapping the data package timeline?
DATA REQUIREMENT

This play assumes access to ClinicalTrials.gov data combined with internal knowledge of client Phase transition timelines and submission planning.

Combined with public trial data. Requires tracking of client milestone planning and FDA review time benchmarks.
PQS Public + Internal Strong (8.3/10)

Satellite Sites Missing EDC Audit Trails

What's the play?

Target sponsors whose satellite sites had incomplete EDC audit trails for data corrections in Q4 2024. Mirror the incomplete audit documentation issue with FDA Form 483 context.

Why this works

Specific to their trial and exact problem sites. The incomplete audit trail issue is a real compliance risk that could save them from a warning letter.

Data Sources
  1. ClinicalTrials.gov - sponsor_organization, trial_phase, locations, enrollment_status
  2. Internal Customer Data - EDC system audit logs showing data correction trails, site-level audit trail completeness

The message:

Subject: 4 satellite sites missing EDC audit trails in Q4 Your NCT04567890 trial shows 4 of 7 satellite sites had incomplete EDC audit trails for data corrections in Q4 2024. The FDA cited incomplete audit documentation in 23% of Form 483s issued in 2024 - it's their third most common finding. Who's responsible for satellite site data quality oversight?
DATA REQUIREMENT

This play assumes access to trial site reporting data combined with internal audit of EDC system logs showing audit trail completeness.

Combined with public clinical trial data. Requires EDC audit log analysis and site-level quality tracking.

What Changes

Old way: Spray generic messages at job titles. Hope someone replies.

New way: Use public data to find companies in specific painful situations. Then mirror that situation back to them with evidence.

Why this works: When you lead with "Your Seattle facility received FDA Warning Letter WL-320214-24 on November 14th for data integrity violations" instead of "I see you're hiring for compliance roles," 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 with specific situations. Your team can replicate this using the data recipes in each play.

Data Sources Reference

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

Source Key Fields Used For
ClinicalTrials.gov sponsor_organization, trial_phase, study_type, condition, intervention, locations, enrollment_status, last_updated Clinical Trial Sponsors, Phase Transition targeting, Multi-site trials
Drug Establishments Database (DECRS) establishment_name, facility_address, establishment_type, drugs_listed, registration_status, last_inspection_date FDA-Registered Drug Manufacturers, Manufacturing Facilities, CMOs
NIH RePort institution_name, grant_title, funding_amount, fiscal_year, research_area, principal_investigator, award_date NIH-Funded Clinical Research Centers, Academic Medical Centers
FDA Warning Letters Database recipient_company, violation_type, facility_type, violation_date, regulatory_area Manufacturers with compliance violations, Repeat violation patterns
FDA Inspection Results Database establishment_name, inspection_date, inspection_type, inspection_findings, 483_observations, warning_letter_issued Facilities approaching inspection window, Compliance risk assessment
USPTO Patent Database patent_assignee, filing_date, approval_date, technology_area, inventors, claims Product developers, Innovation velocity tracking