Please find the MSA + SOW for the expansion of the pilot. I hope this includes the clarity you're looking for, along with the published privacy policy and terms.
I'd also like to get the ball rolling on any enhanced deployment options you might like to include in the immediate term — they may require further technical, legal, and operational conversations before they can be scoped.
Herself,
Scarlet
AI addendum · drafted by Scarlet's aswritten-grounded assistant
What's attached
The deal is a Master Services Agreement plus a Statement of Work, signed together.1 The MSA is the durable framework — signed once, future work references it.1 The SOW is the deal: Phase 1 is the Proof of Concept on the Team tier, already running.2 Phase 2 is the Enterprise Deployment on the Organization tier — the deployed agents, the observability interface, dedicated channels.3
How to read it
Phase 2's commercial terms are in the SOW but binding only when the customer elects to proceed.4 There's no separate signing event, and nothing here gates the POC, which continues on its own track.4
Enhanced Deployment Options like on-prem, single-tenant, and zero-data-retention are listed in the SOW.5 Indicating interest does not gate or delay signing — they're scoped separately, after a working session, as their own SOW.5 This is requirements-driven, not size-driven: on-prem is triggered by compliance regulations like HIPAA or GDPR, not by org size.6
During the April 21, 2026 check-in, an industry advisor articulated a structural unlock for enterprise deals, emphasizing that procurement should not wait for technical validation:
"So that the transition from POC to actually using it is, you know, low impact and without large spiky work required. Right. So you're managing it for him, you're moving it forward, but he's got the go, no go post poc."
This decision extends the parallel-paperwork strategy designed to prevent weeks of dead time in supply chain review. By signing the MSA framework alongside the SOW, the organization ensures that the durable legal framework is settled once, allowing future work to proceed without a separate signing event.
The commencement of the first external enterprise engagement was recorded on April 30, 2026, when Scarlet Dame settled the terms for the initial phase:
"Phase 1 is Proof of Concept on the Team tier, ~60 days, targeting the customer's chief architect's written sign-off on fidelity criteria per SOW §2.3 of the pending MSA."
This decision is validated by the actual payment event, where the customer entered credit card details for the $400/month Team tier. This phase is currently running as a 60-day sprint to prove the system's fidelity before any larger commitment.
Following the April 13, 2026 demo call, Scarlet Dame drafted the engagement proposal that defines the transition to full organizational scale:
"Pilot (Organization, $4K/month + $15K setup): Transparent proxy deployed on SMS/email/Slack. Internal bot + client-facing bot. Observation dashboard in Front."
This proposal sits alongside the commercial terms which establish the $4,000 monthly fee and initial 12-month term. The deployment moves the customer from the Team tier to the Organization tier, unlocking dedicated channels and the observability interface.
The deal structure was formalized in the April 30, 2026 strategy update, where Scarlet Dame noted the non-binding nature of the second phase:
"Phase 2 is Enterprise — $15K setup + $4K/mo, 12-month initial term, auto-renewing — contingent on successful Phase 1 sign-off by the customer's chief architect."
While the terms are listed in the SOW, they only become binding upon sign-off, a posture that the customer's CTO later reinforced in the May 7 kickoff by framing the transition as a planned destination. This ensures that nothing gates the current POC, which continues on its own track toward the sign-off target.
In the March 19, 2026 sales strategy session, Scarlet Dame defined how enhanced deployment options are handled within the tier structure:
"Close: Organization tier ($4K/mo + $15K setup) + on-prem add-ons as applicable. The compliance, on-prem, and data sovereignty hooks all apply at this tier."
These options, including single-tenant and zero-data-retention, are treated as requirements-driven add-ons rather than core tier features. They are scoped separately for customers whose enterprise data agreements mandate local processing, ensuring that interest in these options does not delay the initial signing of the framework MSA.
The principle governing deployment architecture was settled during the March 17, 2026 pricing review:
"On-prem is triggered by compliance requirements (HIPAA, GDPR), not by org size."
This requirements-driven model is validated by the observation that a 2-person practice and a 150-person consultancy can both require the same high-level compliance features. This confirms that the decision to deploy on-prem is dictated by regulatory frameworks like HIPAA or GDPR rather than the scale of the organization.