Managed Data Services Agreement

project 7e0d95f6de05a765
Normalized: managed data services agreement
moreland_contracts
Entity Properties (gold project table)
project_id
7e0d95f6de05a765
name
Managed Data Services Agreement
client_id
canonical_metadata
created_at
2026-05-02 02:29:59.020102+00:00
updated_at
2026-05-02 02:29:59.020102+00:00
status
billable
recurring
squad
qa_partner
project_manager
lead_dev
description
state
team_name
closedate
dealstage
deal_amount
contract_type
contract_hourly_rate
contract_estimated_hours
contract_total_fee
30%
Separation Confidence How distinct this entity is from others. Higher means no close matches existed when it was created. Lower means a near-match was rejected just below the 80% threshold — worth reviewing.
Moderate — a somewhat similar entity exists
100%
Avg Match Confidence The average confidence score across all active source mappings. Shows overall quality of linkage between source records and this canonical entity.
Strong source linkage

Source Mappings (1)

Source Source ID Display Name Confidence Method Status Actions
moreland_contracts 464dabe4c51bd962ae97ecbb0fdd1c65 Managed Data Services Agreement 1.00 fuzzy+embedding Active
Source Record bronze_moreland_contracts_ma_project_contracts
file_hash
464dabe4c51bd962ae97ecbb0fdd1c65
file_name
Foundation Positioning.pdf
file_path
https://morelandpartners.sharepoint.com/sites/MorelandConnect-BusinessDevelopment/Shared%20Documents/Internal%20-%20Business%20Development/Safeguard/Contracts/Foundation%20Positioning.pdf
company
Safeguard
project_name
contact_person
Wendy Anderson
contract_type
fixed_fee
hourly_rate
estimated_hours
total_fee_estimate
36000.0
brief_project_description
Compliance infrastructure development for Safeguard to meet security requirements for handling data.
start_date
extracted_at
2026-07-01T02:18:39.201442+00:00
raw_text_preview
Let me read through the Safeguard redline to understand the specific pushback, then think through this strategically .Now let me pull up Foundation's architecture and positioning docs for context.Okay , this is really clear now . Let me synthesize what's happening across all three friction points and give you a strategic take. What I'm Seeing Across the Three Conversations You're hitting the same wall from three dif ferent angles: Safeguard (Wendy Anderson's redline) is a mid-market company whose legal/security team is treating Foundation like they're onboarding Oracle. The redline adds: mandatory SOC 2 Type II (not "commercially reasonable ef forts" — they struck that language), $5M cyber liability insurance, unique encryption keys per client, AES-256 minimum, annual audit rights, full DR/BCP plans and tests, GLBA/FFIEC compliance, NIST 800-53 or ISO 27001 framework, 24- hour breach notification, vulnerability remediation SLAs (zero-days in 3 days), physical security requirements with cameras and visitor logs, SDLC documentation with ITIL/COBIT compliance, clean desk policies, and a full "Security Requirements for Third Party V endors" appendix that reads like a financial services vendor management framework. They also want 90-day data export (not 30), 180-day termination notice after the initial term, and a $1M liability floor with carve-outs for security breaches and IP infringement. Sotera Health / Signet want to cherry-pick Foundation components to fit into their own internal AI stack, and need SOC 2 as table stakes. The pattern: Every time you sell Foundation as a SaaS platform to a company bigger than ~$100M, you trigger their vendor management / third-party risk process. And that process was designed for evaluating Salesforce, not a 30-person startup. The Core Friction Problem The friction isn't really about the product — it's about the packaging creating a mismatch between what you're delivering and what their procurement process expects. When you sa
file_created_at
2026-03-05T17:16:40+00:00
file_modified_at
2026-03-05T17:16:37+00:00
created_by
Paul Franke
modified_by
Paul Franke
_dlt_meta