CASE STUDY · PLATFORM
sparx
A modular content & commerce OS where AI is a first-class operator — not a chatbot bolted on the side.
THE PROBLEM
A dozen disconnected tools, none built for AI
Businesses were told to assemble their web presence from a pile of disconnected SaaS — a storefront here, a CRM there, email somewhere else — each with its own data model, login, and monthly bill. Nothing shared a source of truth, and none of it was built for AI agents to operate. sparx starts from the opposite premise: one governed platform where the modules you need sit on shared data, and where an assistant can actually run the business.
WHAT I BUILT
One platform, activated by module
One data spine
Commerce, CRM, and CMS share one source of truth — a customer, an order, and a page are the same records everywhere, not copies to reconcile.
Activate only what you need
Storefront, B2B/wholesale, dropship, scheduling, email — modules switch on per tenant, so a business runs exactly the surface it needs and nothing it doesn't.
A real site builder
Pages authored as structured node trees, saved themes, reusable layouts, and a draft/publish pipeline. This very site is built and running on it.
Governance built in
Per-tenant isolation with scoped, audited access — the foundation that makes handing an AI agent real write access safe rather than reckless.
MCP-NATIVE
An assistant can run the business — not just chat about it
Every tenant gets a first-class MCP server. An assistant can read the pipeline, adjust inventory, draft an email campaign, or publish a page through scoped, audited, per-agent access — not brittle scraping or copy-paste. “Run the business by talking to an agent” is a real workflow, by design. This entire site was built end-to-end through that MCP.