Ownership Model

EGI operates as part of a three-company structure. Each company has a distinct role, and clear ownership boundaries ensure that projects move smoothly from concept through long-term operation without gaps or duplicated effort.

The Three Companies

EGI (EGIntegrations) -- Build

EGI is the custom software and AI development arm. EGI is responsible for:

• Discovery, design, and architecture for new products and features
• Full-stack development and AI/ML engineering
• Quality assurance, testing, and performance optimization
• Launch execution and initial production monitoring
• Technical documentation for handoff

EGI owns a product from inception through successful launch and a defined stabilization period.

Mast -- Optimize

Mast focuses on systems efficiency and process optimization. Mast is responsible for:

• Evaluating and improving operational workflows across all three companies
• Identifying automation opportunities in client and internal processes
• Auditing system configurations for performance, cost, and reliability
• Defining and tracking operational KPIs
• Advising on tooling decisions and vendor selection

Mast operates as an advisory and optimization layer. Mast does not own products directly but influences how products and systems are built, deployed, and maintained.

Anchor MSP -- Operate

Anchor MSP is the managed services provider. Anchor is responsible for:

• Day-to-day infrastructure monitoring and incident response
• Ongoing maintenance, patching, and security updates
• Client helpdesk and first-line support
• SLA management and uptime reporting
• Routine operational tasks (backups, certificate renewals, scaling)

Anchor owns the operational lifecycle of a product after EGI completes the handoff.

Ownership by Lifecycle Phase

Phase	Primary Owner	Supporting Role	Key Handoff
Discovery	EGI	Mast (process input)	--
Design	EGI	Mast (efficiency review)	--
Build	EGI	--	--
Test	EGI	Anchor (environment support)	--
Launch	EGI	Anchor (monitoring setup)	--
Stabilization (first 30 days)	EGI	Anchor (shadow monitoring)	Anchor begins onboarding
Post-handoff operations	Anchor	EGI (app-level escalation)	Handoff complete
Optimization (ongoing)	Mast	EGI + Anchor (implementation)	--

Cross-Company Workflows

EGI to Anchor Handoff

The handoff from EGI to Anchor is the most critical cross-company transition. It follows a structured process to prevent knowledge gaps.

Handoff deliverables from EGI:

1. Runbook -- Step-by-step procedures for common operational tasks (restarts, scaling, log access, database maintenance)
2. Architecture diagram -- Current system topology including all services, databases, third-party integrations, and network boundaries
3. Monitoring configuration -- Dashboards, alert thresholds, and escalation rules already deployed and tested
4. Access credentials -- All service accounts, API keys, and infrastructure access documented in the shared secrets manager
5. Known issues log -- Any open bugs, technical debt, or workarounds that Anchor needs to be aware of
6. Support escalation matrix -- Clear definitions of what Anchor handles independently vs. what gets escalated back to EGI

Handoff process:

1. EGI completes all handoff deliverables and posts them to the project's documentation repository
2. EGI and Anchor hold a handoff walkthrough meeting (recorded) covering architecture, runbook, and known issues
3. Anchor shadows EGI operations for a minimum of 2 weeks during the stabilization period
4. Anchor assumes primary on-call responsibility; EGI remains secondary escalation
5. After 30 days with no critical escalations, the handoff is formally closed with a sign-off from both leads

For the full handoff process, see the Anchor Handoff documentation.

Mast Optimization Cycle

Mast engages with both EGI and Anchor on a recurring basis to identify improvements.

1. Quarterly audit: Mast reviews operational metrics, incident logs, and process documentation across all active projects
2. Recommendation report: Mast delivers a prioritized list of optimization opportunities with estimated effort and impact
3. Implementation: EGI or Anchor implements approved optimizations within their respective domains
4. Verification: Mast validates that implemented changes achieved the expected results

Cross-Company Escalation

When an issue crosses ownership boundaries, follow this path:

1. Anchor identifies an application-level issue that is beyond routine operations (e.g., a bug, a feature regression, or a required code change)
2. Anchor posts to the #cross-egi-anchor Slack channel with a structured escalation template: severity, impact, affected systems, and steps already taken
3. EGI acknowledges within 2 hours during business hours and assigns an owner
4. EGI and Anchor collaborate on resolution in the escalation thread
5. Once resolved, EGI updates the runbook if the fix changes any operational procedures

Ownership Disputes

If there is ambiguity about which company owns a particular responsibility:

1. Default to the Ownership by Lifecycle Phase table above
2. If still unclear, escalate to the monthly cross-company sync for resolution
3. Document the decision in this SOP to prevent future ambiguity

Accountability

Each company designates a point of contact for every active project. These contacts are responsible for:

• Representing their company in cross-company discussions for that project
• Ensuring their team meets SLA and handoff commitments
• Flagging risks or blockers early through the appropriate Slack channels

The project contact list is maintained in the project's SuiteDash portal and reviewed at each milestone.