Each agent owns a function. Together they run the business.

The CEO agent doesn't run a function — it runs the fleet. Every morning, after the other eleven agents complete their reports, the CEO agent reads all of them, identifies the patterns across functions, and produces a single daily briefing with one recommended action.

This is the agent you actually talk to most days. The other eleven do the work; the CEO surfaces what you need to know without making you read eleven separate reports. A pipeline issue from CRO, a cash flow alert from CFO, and a churn signal from CCO all get connected into one narrative — “here's what's actually going on in the business, and here's what to do.”

The CEO agent also handles cross-functional decisions. If CRO wants to discount a deal but CFO is flagging cash-flow risk, the CEO weighs both and makes the call. If CMO proposes a campaign that CHRO knows the team can't support, the CEO catches the conflict before it ships.

The COO agent runs operational logistics. It routes inbound leads to the right place, manages workflow transitions across the business, monitors operational metrics, and flags when something is breaking before it becomes urgent.

When a lead comes in, the COO classifies it (inbound demo, support inquiry, partnership, recruiting) and routes it to the right next step automatically. When a deal moves stages, the COO triggers the downstream workflow — proposal generation, contract send, kickoff scheduling — without anyone manually updating the CRM.

The COO also watches the seams between functions. Sales handed something to Customer Success and CS hasn't acted on it? COO flags it. A new hire is starting next week and IT hasn't provisioned access yet? COO flags it. The work that falls through cracks in normal operations is exactly what the COO catches.

The CFO agent connects to your accounting system and produces the financial work most mid-market businesses can't justify a full-time CFO for. Cash forecasting that updates weekly. Runway analysis that adjusts to actual revenue and spend, not a static spreadsheet. Variance tracking against budget. Scenario modeling — “if we close this deal, what does cash look like in 90 days; if we don't, what changes.”

It also does the boring-but-critical work — flagging when expenses drift, when AR ages past terms, when a recurring revenue stream stops recurring. The kind of work that quietly compounds into financial trouble when nobody's watching the numbers daily.

When the CEO agent asks for financial input on a cross-functional decision, the CFO is who responds. CRO wants to extend payment terms? CFO models the cash-flow impact and gives a yes/no with conditions.

The CRO agent reads your CRM and your communication threads to know what's actually happening in revenue, not what the CRM says is happening. Deals stale for two weeks? Flagged. A prospect went quiet after a discovery call? Flagged. A customer started replying to invoices instead of paying them? CRO catches that before it becomes churn.

It also handles deal prioritization actively. Not all pipeline is equal — the CRO knows which deals are moving, which are stuck, which are being qualified out by silence rather than rejection. Each morning it produces a prioritized list of what to chase today, in what order, with what message.

For closed deals, the CRO tracks attribution — what message converted, which channel produced the lead, what discovery question opened the door. The signal compounds over months into actual sales intelligence rather than gut feel.

The CMO agent runs the marketing function — content creation, campaign management, performance monitoring. It drafts blog posts, email sequences, social copy, and outreach messages calibrated to your business voice. It runs the publishing schedule and watches what converts.

This is the agent most likely to be running active workflows on your behalf — drafting Monday's blog post on Friday, scheduling the social distribution for the following week, A/B testing two subject lines on the next email send. The CRO sees the conversion data; the CMO uses that data to ship the next version.

It also watches your competitors and your category — what messaging is landing in your space, what positioning gaps exist, where the conversation is moving. Mid-market businesses rarely have time to read industry coverage; the CMO summarizes what matters weekly.

The CSO agent watches the world outside your business. Competitor moves, market signals, regulatory changes, technology shifts that affect your category, M&A activity, public commentary on your industry. It produces a weekly digest of what changed and what it means for you specifically — not a generic “here's what happened in tech this week.”

The “what it means for you specifically” piece matters. Every business owner subscribes to industry newsletters and most of them go unread because the signal-to-noise ratio is bad. The CSO filters relentlessly to your specific business — your industry, your size, your geography, your competitive set — and surfaces only what changes a decision you're about to make.

It also handles strategic question scoping. When you say “should we expand into the X segment,” the CSO researches the market sizing, the competitive landscape, the customer-acquisition economics, and produces a memo. Not a recommendation — context. The decision is yours.

The CCO is the agent that makes Forgehelm different from every other AI executive platform. Eleven of the twelve agents do the work of running a business. The CCO works on the leader running it.

It watches how you make decisions over time. The patterns you fall into when stressed. The biases you have around hiring, around firing, around when to push and when to fold. The blind spots that show up in your interactions with the team. The growth edges you've been avoiding.

It's not a therapist and it doesn't pretend to be. It's an executive coach with full context on your business — the kind of coaching CEOs at $500M companies pay $300/hour for from human coaches who've worked with hundreds of leaders. The CCO has the same context, persistent memory across years, and can reflect patterns back when you ask.

You won't talk to the CCO every day. But when you're about to make a decision that pattern-matches to a previous decision that didn't go well, the CCO reminds you. When the team starts showing signs of burnout, the CCO surfaces it before anyone resigns. When you've been avoiding a conversation for three weeks, the CCO names it.

This is also the agent that catches churn risk earliest. Customer disengagement signals in communication, in support patterns, in usage data — the CCO reads what the CRO doesn't see and flags it before the renewal conversation goes sideways.

The CHRO agent monitors team health continuously — engagement signals in communication, performance trends, attendance patterns, sentiment in messages. It catches the early signals of burnout, disengagement, or flight risk before they become resignations or performance problems.

It also handles the hiring funnel. Job descriptions drafted, applicants scored against criteria, interview scheduling coordinated, candidate communication kept warm during slow stretches. For mid-market businesses without a dedicated recruiter, the CHRO is functionally that role.

For existing team members, the CHRO tracks performance reviews, growth conversations, and compensation benchmarking. It surfaces when someone's been at the same comp for too long, when a high performer is at flight risk, when a new hire is showing signs of being underwater.

The CHRO works closely with the CCO — the CCO reflects patterns to the leader, the CHRO acts on them with the team.

The CLO agent monitors the legal and compliance dimensions of the business — contracts in flight, regulatory changes affecting your industry, risk surfaces in operations. It's not your lawyer, but it works with your lawyer (or in their absence) to surface what matters before it becomes a problem.

For contracts: it reads incoming agreements, flags non-standard terms, suggests negotiation positions, tracks renewal dates, and watches for contract obligations the business is at risk of missing. For mid-market businesses without in-house counsel, this is the agent that catches the auto-renewal you forgot about and the indemnity clause that wasn't in the last version.

For regulatory: it tracks changes to laws, standards, and frameworks affecting your industry and geography. Privacy regulations, employment law changes, industry-specific rules. The signal goes through filtering — only changes that would alter how your business operates make it to the daily briefing.

For operational risk: it flags when business activity is creating exposure. Customer data being handled in ways that don't match your stated privacy policy. Hiring practices that drift from compliance. Marketing claims that overshoot what's substantiable.

The CQO agent watches what your business actually delivers to customers, vs. what it promises. Quality metrics that matter for your specific business — defect rates, on-time delivery, customer satisfaction, support resolution time, returns or rework patterns.

For service businesses, the CQO tracks SLA performance, response times, and customer-perceived quality. For product businesses, it tracks defect rates, returns, and quality drift. For platforms like Forgehelm itself, the CQO tracks agent uptime, decision accuracy, and integration health.

It's also the agent that produces customer health scores at the platform level — not just “are they paying” but “are they getting value.” Engagement metrics, feature adoption, support burden, expansion signals. The kind of customer success monitoring that's usually a $150K/year CS leader role at most mid-market businesses.

The CTO agent owns the technical infrastructure of the business — the systems you depend on, the integrations between them, and the security posture protecting them. For mid-market businesses without a dedicated technical leader, this is the agent that knows what's running, what's at risk, and what needs to happen next.

It tracks system uptime, integration failures, security signals, and technical debt. When the email platform goes down, the CTO knows before customer support starts asking why nobody's getting their newsletters. When an API key is about to expire, the CTO flags it before the integration silently breaks.

For security, it monitors access patterns, flagged credentials, and posture drift. It works with the CLO on regulatory technical compliance and the CCO on security awareness across the team.

For technical roadmap, the CTO produces honest technical assessments — what's working, what's accumulating debt, what's a candidate for replacement, what'll break under scale. The kind of context owner-operators usually don't have unless they themselves are technical.

The CIO agent owns the data layer of the business. It connects the systems your other tools live in, manages the flow of information between them, and surfaces patterns that emerge when data from across functions gets cross-referenced.

The CFO sees financial data; the CRO sees pipeline; the CHRO sees team data. The CIO sees all of it together. When a customer's payment delays correlate with their engagement metrics dropping, the CIO catches it. When a new lead source is producing high revenue but low-quality customers, the CIO surfaces the pattern.

It also handles the data hygiene most businesses neglect. Duplicate records in the CRM, conflicting customer data across systems, integration sync failures that quietly leave data stale. The work that's important but never urgent — until something breaks.

For reporting, the CIO produces the cross-functional views — the kind of business-wide dashboards that usually require an analyst to build. Not slick visualizations; honest data that connects functions.