SoConnective

Overview

Product Overview

The problem

Agencies run on a sprawl of subscriptions: a CRM here, a scheduling tool there, a separate inbox, an automation platform, a proposal tool, a reporting add-on. Each one bills per seat, per sub-account, or per contact, and the costs compound as the agency grows. Platforms like GoHighLevel consolidate some of this, but at a recurring cost the agency never escapes, on infrastructure the agency never owns, with data that lives on someone else's servers.

For an agency that also resells to its own clients, the math gets worse: every sub-account is another line item, and white-labeling is a premium tier on top.

The solution

SoConnective is the consolidation, self-hosted and owned. It brings the CRM, conversations, automation, and AI into one multi-tenant product that runs on infrastructure SoConnective controls. There is no per-seat tax, no per-sub-account billing imposed by a vendor, and no ceiling on how the platform can be extended — because the platform is the codebase.

Because it is multi-tenant and white-label from the ground up, an agency can stand up sub-accounts for its clients under its own brand, with strict data isolation between them (see tenancy & data isolation).

Who the tiers are for

  • Platform (master) — SoConnective. Operates the platform, onboards agencies, and curates the module marketplace. The Platform account is invisible to the tiers below it.
  • Agency — an agency operating on the platform. Manages its own book of business and the sub-accounts it owns. Sees its accounts and nothing above.
  • Sub-account — an agency's client. Works inside a single account, with no visibility into the agency's other clients or the platform itself.

The philosophy: manual-efficient → automation → AI

SoConnective is built in that order, deliberately.

  1. Manual-efficient first. Every core workflow has to be fast and pleasant to do by hand before anything is layered on top. A clean, well-scoped CRM is the foundation — not an afterthought to the automation.
  2. Automation next. Once a workflow is solid manually, it gets a native automation path: hooks fire actions, repetitive steps disappear, and the human stays in control of the exceptions.
  3. AI on top. With clean data and reliable automation underneath, AI becomes genuinely useful — drafting, summarizing, answering questions over the CRM, and operating tools on the user's behalf. Every AI action is scoped to the active account and written to the audit log.

This ordering keeps the system trustworthy: AI is an accelerant on top of a sound foundation, not a substitute for one.

The white-label angle

White-labeling is structural, not a paid tier. The stack is de-identified — the session cookie is the neutral fs_session, the X-Powered-By header is disabled, and the Platform account is blinded from the tiers beneath it. An agency presents the platform as its own product to its clients, and a sub-account never sees evidence of the platform or the agencies it does not belong to.

Previous
Introduction