AI Vision & Strategy

March 2026 Β· Confidential β€” Internal Use Only

The North Star

By the end of 2026, every egelloC employee will have an AI co-worker β€” plugged into a centralized egelloC brain β€” that empowers them to think bigger, move faster, and focus on the work that only humans can do.

We are not building AI to replace people. We are building AI to turn every person at egelloC into a supercharged version of themselves. The goal is simple: humans think, AI does.

Why This Matters Now

egelloC is at an inflection point. Our business is growing. Our teams are stretched. LLMs, autonomous agents, and workflow automation tools have matured enough to build real, production-grade intelligence into daily operations. But this only works if we are intentional about it. AI without direction creates noise, waste, and confusion. AI with a clear vision creates leverage.

The Co-Worker Model

At egelloC, we think about AI agents as co-workers β€” not assistants, not tools, not bots. A co-worker has a defined role, a clear scope of responsibility, and a way of working with the humans around them.

β€œWelcome to egelloC. This is Emerson. Emerson is your co-worker on the coaching team. Here is what Emerson can help you with. Here is how you work together.”

Current AI Agents

Cornelius

Chief of Staff & Tony's EA

Triage layer and orchestrator for the entire AI system. Routes requests, manages Mission Control, coordinates cross-agent workflows. Tony's direct AI partner with broad operational authority.

Emerson

Coaching & Fulfillment Expert

Built around the student journey and coaching process. Supports the coaching team with meeting prep, student context, knowledge retrieval, and workflow automation.

Jarvis

Product & Operations

Supports product development, QA, internal tooling, and operational workflows. Lives at the intersection of building and systematizing.

As the company grows, new agents emerge naturally. When an agent reaches its limits, it splits. When a new function is underserved, a new agent is born.

The egelloC Brain

Behind every AI agent sits a shared foundation: the egelloC Brain. A centralized knowledge and intelligence layer, hosted in the cloud, that gives every agent access to the collective memory, processes, and context of the company. It holds SOPs, institutional knowledge, playbooks, and decision frameworks. It is the connective tissue β€” not any single agent.

How It All Connects

Cloud VPSCentral hub. Hosts the egelloC Brain, SOP repository, and API key directory.
AI AgentsEach agent runs in its own environment. They connect to the VPS via Tailscale and SSH. Independent but share knowledge through the Brain.
Workflow EngineZapier for deterministic logic, OpenClaw for agent-driven tasks, custom integrations. Zapier handles if/then; agents handle thinking.
Mission ControlOperational dashboard for the entire AI system. Centralized view of all running SOPs, status, cost, and ownership.

Deciding What to Build β€” Five Principles

1

Repetition Is the Signal

If a task is done the same way, multiple times, by multiple people β€” it is a strong candidate. Sales calls, onboarding walkthroughs, meeting prep, check-in forms, chat responses β€” these are the veins of gold.

2

Data-Rich Means AI-Ready

If we already have a large volume of data for a process (call recordings, transcripts, chat logs, historical decisions), AI can learn from it immediately.

3

Internal Before External

AI that faces employees is low-risk and high-learning. AI that faces customers is high-risk and requires maturity. Build internal first, graduate to external when battle-tested.

4

New Capabilities Over Incremental Gains

Prefer building capabilities that don't exist yet over incrementally improving what already works β€” but only when those new capabilities involve repetitive, data-rich processes.

5

Fix Fulfillment First

Our sales engine works. Where the real optimization lives is in coaching, onboarding, and fulfillment. 2026 is our product year β€” the back end is the focus.

Guardrails & Operating Rules

Speed without guardrails creates chaos. These rules are non-negotiable.

πŸ’°

Cost Visibility

Every workflow must have its cost tracked independently. Separate API keys per workflow. Cron jobs default to Haiku. Sonnet requires team lead approval. Opus is leadership-approved only.

πŸ›‘

Human Approval Gates

Any AI interaction that reaches a customer, prospect, student, or parent must be reviewed and approved by a human before it is sent. AI drafts, humans approve. No exceptions.

πŸ”’

SOP Lock

Only the AI team can create, modify, or delete SOPs that drive AI workflows. Employees can use agents and request changes, but cannot alter underlying instructions.

⚠️

Safe to Fail

All AI team work is a testing ground. It is OK to break things. It is not OK to break things that touch customers. Internal experimentation encouraged; external deployment requires sign-off.

πŸ“‹

Logging Everything

Every command, every agent action, and every request should be logged. This creates the audit trail needed to debug, improve, and trust the system over time.

How the AI Team Operates

Development Team

Builds external-facing application. The product students, parents, coaches, and admins interact with. Follows standard product development with PRDs, QA, and feature-flagged deployments.

AI Team

Builds internal-facing intelligence. Agents, automations, and workflows. Lower experimentation bar, faster pace, higher tolerance for iteration. Over time, the two tracks converge.

What Success Looks Like

  • βœ“Coaches spend less time on prep and more time coaching.
  • βœ“CX team members resolve issues faster with AI-drafted responses.
  • βœ“Leadership has real-time visibility into operations without manual reporting.
  • βœ“New employees are productive faster because their AI co-worker accelerates onboarding.
  • βœ“Repetitive work steadily migrates from human effort to AI execution.

The Roadmap Mindset

The AI roadmap is not a fixed list of features. It is a living system driven by one simple rule: anytime something is done repetitively, it gets flagged as an opportunity. A continuous cycle:

  1. 1.Identify repetition or gaps in current operations.
  2. 2.Evaluate against the five principles.
  3. 3.Build a V1 internally. Keep it scrappy. Get it working.
  4. 4.Monitor cost, quality, and adoption.
  5. 5.Iterate, split, or sunset based on results.

First 30 Days β€” Month 1 Goal

Establish the Foundation

1

Connect all machines to the VPS via Tailscale + SSH β€” infrastructure prerequisite for everything.

2

Publish the centralized API key directory β€” one shared, secure directory organized by workflow.

3

Deliver Meeting Prep V1 β€” coaches receive a morning briefing with day's calls and Fathom context.

4

Audit and cost-track all cron jobs β€” documented, assigned cost-tracking keys, migrated to Haiku.

Every workflow you automate, every agent you improve, every SOP you create moves us closer to a future where this company runs with an intelligence layer that no competitor can easily replicate. Welcome to the team. Let's build something worth being proud of.