RLL City

Who it is for: B2B. Buyer: a founder or engineering leader at a North American organization running 10+ production agents. User: the stakeholders they must answer to — board, investors, customers — who need a legible surface. Also sold as the embeddable @rll/city-sdk. — source: products/xml/AI and Engineering Product Nodes/rll-city.xml#investor-model/market-sizing/sam@filter='North America · organizations running 10+ produ…

What it is: The operating system for AI workforces: makes agent work visible, governable and legible to non-engineers. Distinct from Consulting (services) and Labs (showcase). — source: same node <identity> + domains/investment-terms.xml#portfolio ('The OS for company infrastructure, doctrine management, and autonomous-agent …

Why now: The agent-visibility and ops-tooling slice runs about $0.7B (2025) toward ~$4.6B (2030), arriving exactly as organizations first put ten or more agents into production and discover nobody outside engineering can read what they do. — source: same node #investor-model/market-sizing/tam + sam@filter's 10+ production agents threshold

The opportunity: An organization's AI agent work is invisible — logs, dashboards and API traces no stakeholder can read. Founders, investors and teams cannot trust, sell or coordinate a workforce they cannot see. Abstractions do not sell; a watchable running company does. — source: products/xml/AI and Engineering Product Nodes/rll-city.xml <problem> + intent/rll-city.intent.xml <problem>

Year-1 ARR — not yet measured. Node models SOM as ~$1.5-2.5M ARR by Year 5, no year-1 point. Checkout is not live and the posture is waitlist-capture, so a year-1 ARR would be a guess about a funnel that does not yet exist.

Where it lives: rllcity.reaveslabs.ai · North America, organizations running 10+ production agents — source: product-registry url + the SAM filter's geography and qualifying threshold

GTM strategy: Pilot-form qualification by agent count (11-50 / 51-200 / 200+), landing in either the hosted surface or the embeddable @rll/city-sdk. Waitlist capture until checkout is live. — source: same node sam@filter (the pilot form's own agent-count field defines the qualifying segment) + intent/rll-city.intent.xml distribution (waitlist-ca…

Why us: Network effects compound as companies adopt the XML-first architecture — the node calls this the moat. RLL runs its own fleet on it, so the product is proven on the hardest customer first. — source: domains/investment-terms.xml#portfolio ('Network effects compound as companies adopt the XML-first architecture

Right in front of us: Pilot-capture surface live with the qualifying question built into the form (11-50 / 51-200 / 200+ agents), plus the embeddable @rll/city-sdk showcased. Waitlist posture: checkout is not live, so nothing has converted. — source: products/xml/AI and Engineering Product Nodes/rll-city.xml (pilot-capture surface and the embeddable @rll/city-sdk) + intent/rll-city.intent.xml di…