An AI-Native CompanyOperations Dashboard and Metrics
A company hires people, the people do the work, and the work produces goods and services. This one hires agents. What follows is the same account any company gives of itself — what it consumed, and what that produced: five marketplaces it builds, operates and governs.
But the harder thing being built here is a machine worth trusting, and trust is not something a page can assert. So this one is built to be checked instead. Figures that cannot be measured show a dash, never a zero. Two separate stamps say how old each half of the data is, because one would flatter the slower half. Three of the four DORA metrics are computed and withheld — we cannot yet measure them honestly. Costs derived from a judgement say so. And a whole section counts where the machine was stopped and made to ask a person. Nothing here is a claim you have to take on trust; that is the point.
The AI-Native Company — the paper behind this dashboard: the architecture these figures measure, and the verification standard that makes them worth checking.
Platform activity measured just now · codebase measured 41 min ago
Engineering
Built output from the repository: code, documentation and releases to production.
DORA is limited to deployment frequency. Lead time, change failure and restore time are withheld until they can be measured from reliable release evidence.
Operations
Live tracker counts: work raised, closed and released through the operating system.
Counts only. Ticket text, assignees and keys are not fetched for this public page.
Marketing
Agent-produced content and discovery signals, published with the current limits visible.
Cadence is a setting, not proof of recent output. AI chatbot mentions are a weekly Gemini-only probe, not a cross-model search measure.
Revenue
Real Tutorwise marketplace data only. Test, synthetic, internal and other-vertical rows are excluded before any public commercial metric is shown.
Data-quality diagnostic: 340 raw profiles → 5 real Tutorwise marketplace users. Excluded: 11 test/synthetic, 17 internal, and 3 other vertical, plus 304 profile-only rows.
Zero means measured zero. Dash means withheld or no genuine denominator.
Financials
Measured API spend and modelled subscription allocation are shown separately.
20.7M tokens in and 709k out over three months — the consumption behind the measured API cost. The workforce subscription card is modelled from the £180/month plan and rolls forward every calendar month from the first measured month. The unit costs are modelled from that same subscription over a 12-month accounting period: allocated 40% engineering, 30% operations, 20% marketing, 10% other, then divided by what was produced in the same period. The allocation is a judgement, so treat them as the right order of magnitude rather than an audited cost.
Content-reviewer is internal workforce work, so it is excluded from public metered API spend and included in the subscription workforce story.
Legal & Compliance
Controls that stopped, reviewed or required human approval for agent work.
Only control counts are public. Finding details, reviewers and blocked content stay private.
Multi-vendor AI Workforce
One message bus across Claude, Codex and Gemini seats. Work can move between vendors without depending on one supplier. The design is explained in our thought-leadership series.
30 seats have sent messages across 189 distinct routes — the coordination is many-to-many, not one central queue. Awareness traffic adds 32,178 reports and 0 announcements. Counts only: no topic, sender, recipient or message body is published. Reply reliability requires exactly one reply.
What we’re building
This is what all of it was for. Every figure above — the code, the tickets, the articles, the money, the controls, the messages between agents — was consumed producing these. A human company would show goods and services here; this one shows marketplaces. And a marketplace is only worth building for the people in it: a student who finds a tutor they can trust, a tutor who fills their week, an agency that grows.
Five of them on one shared platform. Roughly 80% of what each needs — accounts, scheduling, payments, messaging, reviews, referrals — is platform code every vertical inherits; only the remaining fifth is specific to its market. That is why a new marketplace starts most of the way built, and why the counts below are high before a market has launched.
The four above are services marketplaces — you engage a professional’s time. Adspots sells physical advertising surfaces instead, which is why it inherits the same platform but sits in its own column here.
These counts come from the application’s own vertical configuration — the same switches the running product reads — not from a slide. Deliberately absent is any figure describing how heavily a given market is used: that describes demand rather than what has been built, and is nobody else’s business.
The org chart
94 agents and not one of them a person. Each holds a role with its own brief, its own authority, and its own inbox on a shared message bus. This is read from the roster the running system uses, so it is the organisation as it actually is — including the parts that are unglamorous.
Executive seats
The workforce
- Builder (instance 1)
- Builder (instance 2)
- CMO / Growth
- Codex
- Codex Analyst
- Codex Coordinator
- +31 more
- Campaign Manager
- Content AEO Optimizer
- Content Coordinator
- Digital-PR / Authority Agent
- Content Reviewer
- Content Strategist
- +5 more
- Billing Agent
- Booking Agent
- Change Manager
- Help Desk Agent
- Incident Manager
- Observability Analyst
- +3 more
- Adspots Design Specialist
- Beautywise Design Specialist
- Component Systems Designer
- Product Management Coordinator
- Traderwise Design Specialist
- Trainerwise Design Specialist
- +2 more
- Attribution Analyst
- Data Quality Auditor
- Analyst Agent
- Growth Analyst
- Retention Monitor
- Scorecard Analyst
- Account Manager
- Outreach Specialist
- Revenue Analyst
- Revenue Operations Manager
- Supply Success Manager
- Cost Analyst
- Finance Coordinator
- Financial Modeller
- Fundraising Analyst
- CCO (Trust & Safety / Compliance)
- CFO
- CIO
- Co-founder
- Contract Reviewer
- IP Specialist
- Regulatory Researcher
- Org Designer
- Performance Analyst
- Recruiter
- Dependency Auditor
- Privacy Analyst
- Security Auditor
- Codex Technical Author
A seat is a role, not a chatbot: it holds authority in its area, escalates what is above it, and is accountable for what it ships. The structure is deliberately ordinary — an executive tier and functional groups — because the unusual part is not the shape, it is who is filling it.
These numbers include bad days. A dashboard that only ever shows healthy figures is a brochure; the useful version is the one you can catch having a slow week.