A
Agent
A software process that executes a defined task on a schedule or in response to an event, without requiring a human to initiate or complete each instance. In the BLM OS, agents are the execution layer. They run within each operational layer and report exceptions and completions to Prime.
Agent Layer
The tier of the BLM OS architecture that sits between the Fusion Grid (data) and Prime (governance). All seven operational layers run their specialist agents within this tier. The agent layer is what moves work forward without waiting for the operator.
Approval Gate
A configured checkpoint where an agent pauses and routes a decision to the operator before continuing. Approval gates are set by the operator for high-value or high-risk actions: payments above a threshold, outreach messages, content before it publishes. They surface in Prime's approval queue.
B
BLM OS
Business Lifecycle Management Operating System. The integrated seven-layer agent system built by Echo 1 Labs for owner-led businesses. The OS covers go-to-market, revenue operations, marketing, finance, document intelligence, market intelligence, and governance in a single coordinated architecture.
Broadcast
The marketing layer of the BLM OS. Broadcast runs content brief generation, drafting across channels, scheduling, and performance monitoring. The operator approves briefs and drafts; execution runs on the schedule they configure. Connected to Prime for briefing and exception reporting.
Business Lifecycle Management
A category of business infrastructure that covers the full operational lifecycle of a business through an integrated agent layer, supervised by a governance layer. Echo 1 Labs is the defining company in this category.
C
Confidence Threshold
A configurable minimum confidence score below which an agent will not act autonomously and will instead escalate to the exception queue. Confidence thresholds let the operator define how much uncertainty is acceptable before a human decision is required.
CRM Hygiene
The ongoing maintenance of accurate and current data within a customer relationship management system. In the RevOps layer, CRM hygiene is handled automatically through stage-gate automation and field updates based on activity signals, rather than requiring manual cleanup.
E
Engine
The go-to-market layer of the BLM OS. Engine handles ICP prospecting, contact enrichment, outreach sequencing, meeting scheduling, and pipeline velocity monitoring. The operator configures the ICP and approves messaging; outreach executes on schedule regardless of the operator's daily bandwidth.
Event-Triggered Agent
An agent that activates when a specific condition occurs (an invoice arriving, a deal entering a new stage, a document being uploaded) rather than on a fixed schedule. Event-triggered agents reduce latency between a business event and the appropriate response.
Exception Queue
The list of items that agents have escalated because they fall outside configured parameters. The operator reviews the exception queue through Prime and makes decisions on each item. Exceptions are the primary surface where the operator's attention is directed.
F
Founding Cohort
The first group of businesses onboarded to the BLM OS. Founding Cohort members receive founding-cohort pricing, priority access to new layers as they ship, and direct input into the product development process. Access is application-based.
Fusion Grid
The data integration and normalization layer of the BLM OS. The Fusion Grid connects to the business's existing tools (CRM, QuickBooks, project management, communication platforms) and normalizes their data into a consistent schema that all seven agent layers can operate against without custom translation logic per source.
G
Governance Layer
The supervision tier of the BLM OS, implemented by Prime. The governance layer compiles activity from all seven operational layers, surfaces exceptions and approvals, and maintains the structured record of what agents have done and what decisions the operator has made. It is how humans stay in control when agents are running operations.
I
ICP
Ideal Customer Profile. A defined description of the company type, revenue band, headcount range, industry, role, and problem that an outreach program is designed to reach. In the BLM OS, the ICP is the configuration input for the Engine layer's prospecting and enrichment agents.
L
Ledger
The finance operations layer of the BLM OS. Ledger handles daily general ledger reconciliation, accounts payable routing and approval, cash flow monitoring and projection, and expense categorization. Native integration with QuickBooks. Available now.
O
Operator
In the BLM OS model, the operator is the human in the supervision role, the owner or the designated point of authority. The operator configures the agents, reviews exceptions, approves high-value actions, and reads the daily briefing. They do not run execution; they supervise it.
Owner-Led Business
A company where the owner or founder retains active operational authority, making or approving key decisions across revenue, finance, and operations. The BLM OS is built specifically for this profile: $5M to $100M revenue, 50 to 200 employees, no dedicated RevOps or marketing operations team.
P
Pipeline Velocity
The rate at which deals move through the sales pipeline from initial contact to close. The RevOps layer's Pipeline Velocity Monitor tracks stalls and flags deals that are not moving at the expected rate, so the operator can re-engage before opportunities go cold.
Prime
The governance layer of the BLM OS. Prime compiles a daily briefing from all seven operational layers, manages the exception queue and approval gates, and maintains a structured record of agent activity and operator decisions. It is the primary interface between the operator and everything the system is doing on their behalf.
R
RevOps
The revenue operations layer of the BLM OS. RevOps handles lead qualification scoring, deal intelligence and stall detection, rolling pipeline forecasting, revenue reconciliation against accounting records, and CRM data hygiene. It delivers the operational discipline of a full RevOps team without the headcount.
S
Scheduled Agent
An agent that runs on a fixed cadence (daily, weekly, or at a configured interval) regardless of whether a specific event triggered it. GL reconciliation, content brief generation, and pipeline forecasting are examples of tasks that run on schedule rather than on event.
Signal
The market intelligence layer of the BLM OS. Signal is designed for PE-backed businesses and capital allocators who need business intelligence in a transaction context. It is not self-serve; access requires application and individual review. No pricing is publicly listed.
Supervision Model
The operating principle underlying the BLM OS: agents run execution, operators supervise it. The supervision model defines which decisions require human judgment and which can be handled autonomously. It is implemented through approval gates, confidence thresholds, and the Prime exception queue.
T
Titan
The document intelligence layer of the BLM OS. Titan classifies incoming documents by type, extracts structured data from them, parses contract terms and obligations, and matches invoices against purchase orders. It processes documents on arrival rather than when someone has time to review them.