How to start a business with Quox

The platform is source-available, self-hosted, and built without per-seat pricing. That is not an accident. It is an invitation.

Every AI platform talks about ecosystems. Most of them mean "use our product and pay us monthly." The ecosystem is you, the customer, locked into their pricing page.

Quox is built differently. Source-available. Self-hosted. No per-seat licensing. A plugin architecture designed for extension. Protocols published as open specifications. This is not a SaaS product that tolerates third parties. It is infrastructure that rewards them.

That distinction matters if you are a developer, freelancer, or small agency looking at the AI automation market and wondering where to plant your flag. The opportunity is not just to use Quox. It is to build a business on top of it, selling services and products to others.

Here are four models that work. Some are viable today. Some depend on features in active development. The distinction is clearly marked.

1. Sell AI automations to local businesses

The simplest model, and probably the fastest to revenue.

Local businesses with 5 to 50 employees are drowning in repetitive operational work. Appointment scheduling, invoice chasing, inventory alerts, customer follow-ups, report generation, data entry between systems that do not talk to each other. They know AI exists. They have no idea how to deploy it. They cannot afford the consultancies that do.

This is your gap.

What you do: Deploy QuoxCORE for a client. Configure agents and workflows for their specific operations. A dental practice gets automated appointment reminders and patient follow-up sequences. An estate agent gets property listing syndication and viewing schedule management. A logistics firm gets fleet status dashboards and exception alerting.

None of this requires building from scratch. QuoxCORE ships with 49 specialist agents, a workflow engine (QuoxFlow), and a plugin system that lets you compose capabilities without writing custom code for every client. You configure, connect, and deploy.

Revenue model: a £500 to £2,000 setup fee per client, plus a £100 to £300 monthly retainer per client, adds up to £1 to £3K per month in recurring revenue across 10 clients.

Why Quox specifically: three things that matter when selling to small businesses.

First, self-hosted. The client's data stays on their infrastructure or yours. You are not asking a dental practice to send patient data to a third-party cloud service. That conversation kills deals in regulated sectors.

Second, no per-seat pricing. Your margin is not eroded every time the client hires someone. You pay nothing to Quox for each deployment. The entire margin on the service is yours.

Third, audit trails. AOCL gives clients a visible record of what their agents did and why. It is the thing that stops clients calling you at 9pm asking "what did the AI just do to my invoices?" They can see for themselves. That builds trust, and trust builds retention.

LIVE. This model works today with QuoxCORE and QuoxFlow.

2. Build a vertical SaaS product

Take a single industry problem and build a focused product on top of QuoxCORE.

The difference between model 1 and model 2 is scale. Selling automations to local businesses is a services business. Building a SaaS product is a product business. Both are valid. They compound differently.

What you build: a themed, pre-configured QuoxCORE deployment purpose-built for one industry. You are not selling "AI operations" to a recruitment agency. You are selling "RecruitOps," a compliance-ready candidate management system with automated screening workflows, interview scheduling agents, and GDPR evidence trails. The client never sees QuoxCORE. They see your product.

The plugin architecture means you can add industry-specific features as plugins without forking the core codebase. When QuoxCORE ships updates, your product inherits them. The multi-tenant organisation model means you can run multiple clients from a single deployment.

IN DEVELOPMENT. Enterprise workspace features (multi-tenant auth, RBAC, org scoping) are in active development. Early builders shape the architecture.

3. Custom deployments for mid-market companies

Mid-market companies in the 50 to 500 employee range are the most underserved segment in AI operations. They are too large for off-the-shelf automation tools and too small to build internal platform teams. They want a partner who understands their operations, deploys the infrastructure, and keeps the system running.

This is a consultancy model, but one anchored to a specific platform rather than selling time by the hour with no recurring value.

What you do: scoping workshops to identify high-value automation targets. QuoxCORE deployment on the client's infrastructure. Agent configuration and workflow design tailored to their operations. Integration with their existing systems via QuoxMCP (168 governed tools, growing). Ongoing support and optimisation.

For clients in regulated industries, the compliance angle is your differentiator. VOLT evidence chains provide cryptographic proof of what agents did and when. AOCL governance layers enforce policy boundaries. These are the specific things a compliance officer needs to see before signing off on AI in production.

Why this works with Quox:

1. Self-hosted. Data residency without negotiation. The data lives where the client says it lives.
2. No vendor lock-in. Source-available software with open protocol specifications. CTOs know what lock-in looks like. This is not that.
3. Governance stack. Other platforms orchestrate agents. Few can prove what those agents did and package the evidence for audit.

LIVE. This model is viable now for operators comfortable with Docker, Linux, and the current platform state.

4. Build and sell plugins

This is the model with the longest runway and the highest ceiling.

Quox is building a third-party plugin marketplace. The economics are deliberate: 90/10 revenue split in the developer's favour for the first six months, settling to 75/25 after that. No upfront costs. No minimum commitments. Build something useful, list it, earn from every sale.

What you build: plugins that extend QuoxCORE for specific use cases. Monitoring integrations for platforms not yet covered. Industry-specific agent packs. Compliance templates for specific regulatory frameworks. Connector plugins for niche SaaS tools. Visualisation components. Automation recipe packs.

Why early matters: plugin ecosystems follow a power law. The first plugin that solves a specific problem well becomes the default. Developers who build before the marketplace opens are positioned to capture early demand the moment it does.

PLANNED. The plugin system and store are live today. The third-party marketplace is planned, not yet open. Developers building plugins now will be ready when it launches.

The economics of not paying per seat

Most AI platforms charge per user, per agent, or per API call. That pricing structure punishes the person building on top of the platform. Every client you add, every user they onboard, your costs go up. Your margin compresses as you scale.

Quox does not do this. You deploy QuoxCORE. You run it. The cost is your infrastructure, which you control.

This is the structural reason Quox works as a platform for independent businesses. The economics are aligned. Your growth is not Quox's revenue extraction opportunity. It is just your growth.

Run your own business on Quox too

While you are deploying QuoxCORE for clients, there is no reason your own business should not be running on it as well.

Add your own organisation alongside your clients'. Use the same agents to manage your own operations: lead tracking, project management, client onboarding workflows, invoice automation, document management. Every workflow you build for a client teaches you something. Run a version of it internally and your own business gets better with every engagement.

Your own org on QuoxCORE:

• Client management: track leads, proposals, active contracts
• Project workflows: automated status updates, milestone alerts
• Financial ops: invoice generation, payment follow-ups
• Knowledge base: deployment playbooks, solution templates

You become your own best case study. When a prospect asks "does this actually work?" you can show them your own running instance. That is worth more than any slide deck.

Combining models

These four models are not mutually exclusive. The natural progression feeds each model into the next.

Each model feeds the next. Services revenue funds product development. Product development creates reusable assets. Reusable assets become marketplace listings. Marketplace listings generate passive revenue that funds the next cycle.

What you need to start

• Technical: Docker, Linux, basic networking. If you can deploy a web app and SSH into a server, you can deploy QuoxCORE.
• Financial: QuoxCORE is free. A £20/month VPS is enough for a single-client deployment.
• One client: one business with a problem that repetitive AI workflows can solve. That is the entire barrier to entry.

What you do not need: a venture capital round, a team of ten, an enterprise sales motion, or a year of development before you can charge your first client.

Deploy QuoxCORE. Configure the agents. Show them the results. Charge for the value. Then do it again.

Quox (quox.ai) builds source-available trust infrastructure for AI agent operations. Its protocols, AEE for agent messaging, AOCL for orchestration control, and VOLT for cryptographic evidence, are published as open specifications. The plugin marketplace and community features described in this article are in active development, with the plugin system and store live today.