Company Operations

This section documents the operational standards, procedures, and organizational structure that govern how EGI (EGIntegrations) operates on a day-to-day basis. These standards apply to all team members and serve as the reference point for how we work.

Mission

EGI exists to build custom software and AI-powered solutions that solve real problems for real businesses. We focus on delivering high-quality, maintainable systems that can be operated and scaled beyond the initial engagement.

The Three-Company Model

EGI operates as part of a three-company ecosystem, each with a distinct role in the client lifecycle:

EGI (EGIntegrations) -- Build

EGI is the development arm. We design, architect, and build custom software solutions including:

• Full-stack web applications (primarily Next.js, React, Node.js)
• AI integrations and automation systems
• Data pipelines and analytics platforms
• Custom integrations between business systems
• Internal tools and operational software

EGI owns the project from discovery through development and initial deployment. Our deliverables include production-ready code, documentation, and handoff packages.

Mast -- Optimize

Mast focuses on systems efficiency and process optimization. Mast works with clients to:

• Audit existing business processes and identify inefficiencies
• Recommend and implement operational improvements
• Optimize workflows that EGI-built software supports
• Ensure technology solutions align with business operations
• Bridge the gap between what the software does and how the business uses it

Mast often engages before or alongside EGI to ensure the software we build addresses the right problems.

Anchor MSP -- Operate

Anchor MSP is the managed services arm. After EGI builds and delivers a system, Anchor takes over long-term operations:

• Ongoing system monitoring and maintenance
• Security patching and dependency updates
• User support and issue triage
• Infrastructure management (hosting, DNS, SSL)
• Performance monitoring and optimization

The handoff from EGI to Anchor is a critical transition point. EGI is responsible for delivering complete documentation (see Documenting Auth and Documentation Expectations) so Anchor can manage the system effectively.

How the Companies Interact

Client Need --> Mast (process audit) --> EGI (build solution) --> Anchor (operate and maintain)

Not every engagement follows this exact flow. Some clients come directly to EGI for development. Some Anchor-managed systems need EGI involvement for new features. The key principle is clear ownership at each stage:

Stage	Owner	Deliverable
Process audit and optimization	Mast	Process recommendations, requirements
Design and development	EGI	Production code, documentation, handoff package
Ongoing operations	Anchor	Monitoring, maintenance, support

Operational Standards

Communication

• Slack is the primary communication tool for internal discussions
• Email is used for external client communication and formal internal communication
• Video calls are used for complex discussions, client meetings, and pair programming sessions
• Response expectations: within 2 hours during business hours for direct messages; within 4 hours for channel messages

Project Management

• SuiteDash is the primary project management and client communication platform
• All client-facing projects are tracked in SuiteDash with clear milestones, tasks, and timelines
• Internal projects and operational tasks are also tracked to maintain visibility

Development Workflow

• All code lives in the EGI GitHub organization
• Feature branches and pull requests are required for all changes
• Code review is required before merging to main branches
• Deployments are managed through Vercel (for web applications) or project-specific CI/CD
• See the development standards section for detailed workflow documentation

Documentation

• Every project must have a README with setup instructions
• Architecture decisions are recorded as ADRs
• Auth systems are documented using the standard template for Anchor handoff
• SOPs are maintained in this Docusaurus site and updated as processes evolve

Security

• MFA is required on all services
• Named accounts only; no shared credentials
• Least-privilege access across all systems
• Quarterly access reviews conducted by the operations lead
• See the Auth & Access section for complete security standards

Section Contents

This section will expand to cover the following operational areas as documentation is developed:

• Communication standards and meeting cadence
• Client engagement lifecycle
• Project estimation and scoping process
• Quality assurance and testing standards
• Incident response procedures
• Vendor and tool evaluation process
• Business continuity and disaster recovery

Guiding Principles

1. Build for handoff: Everything EGI builds should be operable by someone who was not involved in building it. This means clear code, thorough documentation, and sensible architecture.

2. Automate the repetitive: If a process is manual and happens more than twice, it should be a candidate for automation. This applies to deployments, testing, provisioning, and reporting.

3. Communicate proactively: Do not wait for someone to ask for a status update. Share progress, blockers, and risks early and often.

4. Own your work: Every team member is responsible for the quality, documentation, and maintainability of their output. Code review is a shared responsibility, not a gatekeeping function.

5. Improve continuously: These SOPs are living documents. When you find something that is wrong, outdated, or missing, fix it or flag it. The team that uses the documentation is the team that maintains it.