Selling It
How Vizzy reaches customers: a credit-based subscription, a clear compliance path, and multi-tenant isolation already in place.
Customer pain
Enterprises want two things that pull against each other. They want expert help at any hour — the answer at 2 a.m., not the answer the next business day. But their buying and compliance teams are wary of AI. They worry about where data goes, which provider sees it, and whether an agent can act without a person watching.
The offer answers both. Expert help is there around the clock through Vizzy. And the architecture is built so the compliance answer is designed in, not bolted on.
Positioning
Vizzy is a holistic, all-inclusive, subscription-based service, built on VisiCore's expertise. It is not an MSP contract, and it is not sold as one.
The difference matters for the sale. The customer subscribes to a result and an on-call expert, not to a staffed managed-service tier. What they pay for is the knowledge base and the review process. The tools underneath are a commodity.
The subscription model
Credit-based
Usage is metered in credits. Subscriptions start at 20 credits per month.
One credit, fully loaded
One credit covers both the infrastructure and the model cost of the work it buys. The rest of the subscription is margin.
Bring your own model
Bring-your-own-model (BYOM) lets a customer supply their own model API key and still connect to the knowledge base. Then the customer's own AI provider and terms apply.
Scales sensibly
Vizzy handles the volume. Core engineers handle edge cases and platform work. The pricing reflects that split.
BYOM is also the fastest way through a customer's model-approval review. When the AI provider is the customer's own choice, a whole class of objections goes away. See the objections.
The path to customer-facing
Vizzy runs for internal tenants today. Reaching outside customers means clearing a set of gates. Each one also makes the platform stronger.
Security assessment of the codebase
A formal security review of X10. Passing it also lifts the current pause on AI-assisted work on the X10 codebase, so it speeds up building as well as sales.
Code-security sign-off on portal endpoints
Each portal endpoint that outside tenants would touch gets a code-security sign-off.
Data Access Policy
A written policy for what telemetry comes back to VisiCore, and on what terms, agreed with the first outside engagement.
External tenants
With the gates cleared and isolation in place, the first outside customers come online.
Multi-tenant isolation — already built
Multi-tenant means many customers share the same platform. Each one is walled off from the others. That isolation is not a future item. It is built.
Credentials in ConnectWise
Each tenant's connections live in ConnectWise, which holds SOC 2 Type 2 certification — an outside audit of its security controls. Credentials never touch a filesystem.
Isolation in the harness
The harness (the software that runs the agent) hands the agent a ready-authenticated client object. So one tenant can never reach another's environment. Isolation lives in the harness, not the agent.
The pilot pipeline
Pilot demand is already lined up. Enterprise accounts are ready to pilot Vizzy the moment the compliance gates clear. The pattern holds every time: the customer's engineers want it, and their compliance team is the gate the steps above are built to clear.
The opportunity is commercial, not technical. Vizzy is built and running. Clearing the gates and closing the first paid job turns an internal tool into revenue.