01 — Portfolio
Aria is the spotlight product. Here are the additional systems Velzyx has engineered.
Velzyx is built around Aria, the voice operator for appointment-driven practices. Alongside Aria, the engineering practice has shipped two further systems that share the same engineering layer — AgentCentric for luxury real estate and AnalytixCRE for commercial real estate underwriting. They are evidence of the engineering range, not headline offerings. The portfolio is the body of work; Aria is the product the company is built around.
02 — What "portfolio" means here
Not case studies. Not screenshots. Systems that run.
Most AI companies have a portfolio that is, in practice, a marketing surface — logos collected from pilots, screenshots from product demonstrations, and a vague claim of impact attached to each one. Velzyx is structured differently, and the portfolio reflects that. Each entry on this page is an AI system Velzyx engineered, owns, and operates as production infrastructure for the customers who use it. There is no system on this page that Velzyx is not currently responsible for in the field.
That structural choice matters because it changes what the portfolio is for. The portfolio is not a sales artifact. It is the body of work that the engineering practice can be evaluated against. When a new operator asks Velzyx to build something, the most honest answer to "what have you done before?" is the list below, with each entry written in language that matches what the system actually does. The portfolio is also how the engineering practice itself stays sharp: every new system in production raises the floor of what the underlying primitives can do for the next one.
The three systems on this page sit on top of the same engineering layer. The platform page describes that layer in detail. Each system is configured per operator on top of those primitives, which is why a single small engineering team can run three production systems in three industries without compromising on the operational depth of any of them. The engagement process behind each one is described on the how it works page.
03 — The thread that runs through all three
Engineered around a workflow, owned end-to-end, deployed for real.
The three systems serve three different industries and three different kinds of operators. A dental front office and a commercial real estate underwriter do not share a vocabulary, let alone a software stack. But the engineering posture behind each Velzyx system is consistent: the system is engineered around an operational workflow that already exists, it is owned end-to-end by the team that built it, and it ships into production from the first real interaction rather than living indefinitely in a pilot environment.
That consistency is what makes the portfolio readable as a single body of work. The dental engagements taught the engineering team how to handle live voice traffic, structured intake, and the operational realities of healthcare-adjacent data. The real estate engagements taught the team how to handle the long lifecycle of an inquiry through a deal, the integrations that listing data flows through, and the editorial demands of a luxury brand. The commercial underwriting engagement taught the team how to handle dense financial workflows where the system's outputs feed an analyst's judgment. Each system added something to the primitives that the next one inherits.
Operators evaluating Velzyx for a new engagement should read the three product pages below as a way of triangulating the engineering posture, even if their industry is not on the list. The pattern of work is the same. The configuration is what changes.
04 — The systems
Aria is the spotlight. These are the additional Velzyx-built systems alongside it.
Voice operator for appointment-driven practices.
A custom AI receptionist that answers every call, verifies insurance, books across providers, and runs hygiene recall outreach. Configured per practice. Live with paying dental operators and configured for twenty appointment-driven verticals across the United States and Canada. Read the WizKids Dental case study.
Read —> 02 — AgentCentric · DeployedWeb platform for luxury real estate.
Engineered websites with custom IDX for individual agents and small teams. Editorial templates, fast deploy, full-lifecycle inquiry handling. Active brands include Solis Muscolino, Home with Miriam, Templer First Homes, and PropNation, with new agent deployments shipping on a steady cadence.
Read —> 03 — AnalytixCRE · In marketUnderwriting engine for commercial real estate.
An AI underwriting system for hotel, multifamily, office, and retail deals. A full underwriting analysis in minutes. Live with commercial real estate investors who run it against real deals before committee. Engagement scoped per client.
Read —>05 — Aria, in context
The system that taught the platform how to listen.
Aria is the oldest of the three Velzyx systems and the one that anchors the platform's voice runtime. The deployment is, on the surface, an AI receptionist for dental practices — the system that picks up the phone when the front desk cannot, verifies insurance, books appointments across providers, runs emergency triage, and follows up on overdue hygiene recall. Underneath the surface, Aria is the canonical configuration of the Velzyx workflow engine. Every dental practice on the deployment is a separately-configured instance, with the provider names, insurance acceptance, recall language, and emergency protocols of that specific operator.
The Aria portfolio extends beyond dental. The same voice runtime is configured for twenty appointment-driven verticals, each one a distinct deployment with its own intake flow, its own scheduling logic, and its own escalation rules. The dental engagements remain the largest live segment, but the underlying engineering is industry-agnostic at the runtime layer and operator-specific at the configuration layer. Read the full product page on the Aria site.
For a closer look at a specific deployment, the WizKids Dental case study walks through what a single Aria practice configuration delivers in production — the operator's reality, the system as it runs today, and what changed inside the practice. The case study links from the Aria card above.
06 — AgentCentric, in context
The system that taught the platform how to host a brand.
AgentCentric is the Velzyx web platform for luxury real estate. The deployment is, in shape, a set of engineered websites with custom IDX surfaces for individual agents and small teams, but the engineering underneath is heavier than the surface suggests. Each AgentCentric brand has its own editorial template, its own listing flow, its own inquiry lifecycle, and its own integration set against the systems the agent or team already runs. The platform supports brands without forcing them into a uniform shape, which is what makes it usable for operators whose brand identity is part of their business model.
Active brands on AgentCentric today include Solis Muscolino, Home with Miriam, Templer First Homes, and PropNation, with additional agent deployments shipping on a regular cadence. The engineering work on each one is meaningful — AgentCentric is not a template marketplace where agents pick from a dropdown. It is an engineered platform that Velzyx configures per agent, with the same discipline that runs through Aria. Read the full product page on the AgentCentric site.
The reason AgentCentric belongs in the portfolio alongside an AI voice product is that the same engineering primitives sit underneath both. The workflow engine that handles a call for Aria is the same workflow engine that handles a listing inquiry for AgentCentric. The integration layer that writes to a practice management system is the same integration layer that writes to a real estate CRM. The platform is one body of work.
07 — AnalytixCRE, in context
The system that taught the platform how to underwrite.
AnalytixCRE is the Velzyx underwriting engine for commercial real estate. The deployment takes a deal — hotel, multifamily, office, retail — and returns a full underwriting analysis in minutes. The system is live with commercial real estate investors who run it against real deals before committee. The engagement is scoped per client.
The engineering work behind AnalytixCRE is in the workflow engine and the observability stack. Underwriting is a dense workflow with a long sequence of decisions, each one feeding the next, and the system has to be legible to an analyst who is using the output to inform a real capital allocation decision. The observability layer makes every decision the system makes visible to the analyst, so the engine functions as an assistant to the underwriter rather than a black box that hands back a number. The engagement is structured so the analyst always remains the decision-maker. Read the full product page on the AnalytixCRE site.
AnalytixCRE is the youngest of the three systems and the one whose surface area is growing fastest as new deal types are added. The same engagement pattern that shaped Aria and AgentCentric runs through it: a specific operational problem in a specific industry, engineered around an existing workflow, deployed in production, and owned end-to-end by the team that built it.
08 — What comes next
More industries, more configurations, more work in the field.
The portfolio will grow in two directions. The first is more configurations of the existing systems. Aria's twenty-vertical roadmap is well underway, with new appointment-driven industries being added on a regular cadence. AgentCentric continues to bring on agent brands. AnalytixCRE is expanding the deal types it underwrites. The platform absorbs each new configuration, which means the engineering team can take on additional operators without diluting the depth of the work on any given engagement.
The second direction is new systems in adjacent industries where the same engineering posture works. The criterion is consistent: a focused operational problem, a real workflow to design around, and an operator willing to run the system in production from the first day. Where those conditions hold, the next Velzyx system can be built. Where they do not, the engagement is the wrong shape and the engineering team will say so during discovery.
Operators considering an engagement should start with the how it works page, which walks through the engagement process in detail, and continue to the case studies for closer reads on specific deployments. From there, the right next step is a discovery conversation. The system that follows from it is what eventually shows up on this page.
Contact
Bring us the operational problem.
The portfolio grows when an operator brings the right kind of problem and the right willingness to run the system that gets built. Discovery is the place to find out whether your problem is one of them.