Statement of Work · June 10, 2026

Phase 1 — AI Connectivity Orchestration Platform

The written, signed companion to the Phase 1 proposal walkthrough. The walkthrough shows what we're building and why; this document fixes the boundary — exactly what's included, what isn't, who does what, the schedule, and the price.

Vendor

LlamAssist

Client

Point5 Managed Services LLC

Version

v0.1 · indicative, pending final confirmation

Governing agreement

Master Services Agreement (MSA)

01Engagement summary

Point5 sits as the hinge between enterprise customers and a fragmented carrier landscape — and its scaling ceiling is the manual, multiplying communication that surrounds every quote and order.

Phase 1 attacks the highest-ROI, lowest-risk part of that first — the "Sell" stage — by delivering reliable, fast AI-assisted quoting and making the data Point5 already holds in Salesforce genuinely usable, while keeping a human on every decision.

This is a build-and-operate engagement: LlamAssist builds the platform and then hosts, runs, and continuously services it, so the capability stays off Point5's headcount. Phase 1 is the entry point to a phased roadmap (Sell → Deliver → Support); later phases are scoped under their own SOWs.

02Approach & principles

03Phase 1 scope — what's included

The following are the committed Phase 1 deliverables. Anything not listed here is, by definition, out of Phase 1 (Section 4) and handled as a change order (Section 12).

04Explicitly not in Phase 1

To prevent scope creep, the following are out of Phase 1 and will be scoped under later SOWs or as change orders.

• ✕SOC 2 certification — the platform is built with SOC 2 in mind; certification itself is deferred.
• ✕Advanced disaster-recovery & high-availability hardening — geo-distributed async backups, log-truncation, and full DR protocols. Baseline backups are included in Phase 1 foundations (Section 3.7); the broader HA/DR build is a later phase.
• ✕Mobile application.
• ✕Full-scale voice — only the light POC in Section 3.6 is included.
• ✕The full dashboard suite, including MACD tracking (moves/adds/changes/disconnects) — a later phase.
• ✕Service-delivery automation — touchless carrier-email ingestion, intent-based triage, status-update generation, automatic circuit-ID assignment, jeopardy alerts (Phase 2 "Deliver").
• ✕NOC orchestration & alert correlation, SLA monitoring, automated carrier credit claims (Phase 3 "Support").
• ✕Customer portal modernization and customer self-serve quoting (later phase).
• ✕Customer-facing MCP (Model Context Protocol) server — letting enterprise clients connect their own LLMs directly to Point5 data (e.g. invoices, ticket status). Noted as a Phase 1 candidate and consciously deferred to a later phase.
• ✕Salesforce Agentforce adoption — paused; LlamAssist provides the AI layer.
• ✕The network / heat-map view shown in the walkthrough — illustrative of later phases, not a Phase 1 deliverable.

The walkthrough may preview later-phase capabilities for context; nothing outside Section 3 is committed in this SOW.

05Deliverables

1. The Phase 1 platform deployed and running in LlamAssist's managed production environment (per Section 3).
2. Source code in a Point5-owned GitHub repository, transferred from the first commit (Section 11).
3. Development/staging and production environments configured on LlamAssist's managed GCP.
4. A brief operations & handoff reference for the delivered capability.
5. Architecture & technical documentation for the delivered platform, maintained to M&A-diligence standard.
6. The Phase 1 acceptance checklist signed off (Section 6).

06Acceptance criteria

Phase 1 is accepted when:

1. Reps can produce both a budgetary and a firm quote for the 2–3 named priority carriers, validated against source pricing, with the 40% margin floor enforced and below-floor deals routed for approval.
2. For the budgetary (cached) quote surface, the first result card returns in ~1 second and the composed set in ~3 seconds under normal load; live firm-pricing results stream in behind an interactive status indicator.
3. The role-based Salesforce experience layer surfaces the agreed views on Point5's live data.
4. The churn and account-health dashboards are live on Point5 data.
5. Adoption instrumentation is capturing usage.
6. The light voice POC is demonstrable.
7. The platform is running in production with development/staging retained.

Acceptance criteria are finalized and signed at SOW execution. Criteria that depend on Point5-side data (e.g., calibration against historical close rates) are conditional on the prerequisites in Sections 9–10 landing.

07Timeline

Target Phase 1 delivery: end of August 2026. Timelines include deliberate buffer.

08Investment

Indicative figures below; final monthly figures confirmed at production go-live. Commercial terms owned by LlamAssist (Eric Thiel).

8.1 · One-time build (R&D)

8.2 · Managed platform & services — monthly

Two always-on environments, billed as clear line items. Each tier includes LLM tokens, GCP hosting, storage, and ongoing servicing — LlamAssist absorbs the token complexity so Point5 gets a flat, predictable spend.

8.3 · Payment schedule (proposed — to be confirmed by LlamAssist)

• Build: staged across signing / mid-point milestone / delivery & acceptance.
• Monthly platform fees begin at each environment's go-live.

09What we need from Point5

A build-with-you engagement. To hold the schedule, Point5 provides:

• Salesforce access (read, and write where required) and access to the relevant dashboards.
• Availability of the right people for working sessions through the build.
• Review and feedback at each milestone.
• Carrier portal details for the carriers being automated.
• A point of contact for unblocking access within one business day.

10Schedule dependencies & risks

Our build speed is not the primary schedule risk. A few items outside LlamAssist's control move the date more than our effort does; we flag them up front.

If any dependency slips, LlamAssist flags it immediately rather than silently pushing delivery.

11Ownership & intellectual property

• Day-1 IP transfer. All Phase 1 code lives in a Point5-owned GitHub repository from the first commit.
• Hosted, not locked in. The platform runs in LlamAssist's managed cloud (GCP), so Point5 carries none of the IT, security, and compliance overhead — yet because Point5 owns the code and IP outright, it can be ported off LlamAssist infrastructure at any time.
• Domain ownership for any project domains is transferred to Point5.
• All Phase 1 work product belongs to Point5 on delivery, designed to be a clean asset for any future due diligence.

12Change management (scope-creep control)

• The committed scope is Section 3 only. Items in Section 4, or any new request, are out of scope for this SOW.
• Any addition or change is handled via a written change order, scoped and priced separately, and signed by both parties before work begins.
• Later phases (Deliver, Support, and beyond) are each scoped under their own SOW after the prior phase ships.

13Assumptions

• Salesforce remains the system of record; no migration off Salesforce is in scope.
• Point5 provides timely access and feedback per Section 9.
• Carrier automation coverage in Phase 1 is the 2–3 named priority carriers; broader coverage accrues over time and in later phases.
• Monthly figures assume baseline usage; materially higher token/storage usage may adjust the monthly tier (discussed transparently, never as a surprise).

14Approvals

This SOW is issued under and governed by the MSA between LlamAssist and Point5 Managed Services LLC. On execution, the committed scope in Section 3 is fixed and changes flow through Section 12.