One workspace, shaped for how your business actually runs

A university doesn't call the people it serves "contacts," and a sales team doesn't call its customers "students." But underneath that vocabulary, both organizations are doing the same fundamental thing: tracking people, conversations, and commitments to completion. VIRO's answer to that is Blueprints -- not a separate product per industry, and deliberately not a learning-management system bolted onto a mail client.

Shared engines, not forked ones

Every workspace runs the same Mail, Contacts, Calendar, and Actions engines. A Blueprint only relabels and reorders what's already in the navigation -- it doesn't fork the underlying feature for each industry. A Higher Education workspace sees Students, Faculty, Classes, and an Academic calendar instead of the general-business defaults, but it's the same Contacts and Calendar systems underneath doing the work.

Choosing a Blueprint doesn't lock you in

Onboarding asks a new organization to pick its category as one part of a single setup screen, alongside optional size and business-need questions. That choice isn't permanent -- an owner or admin can change a workspace's Blueprint later from workspace settings if the label stops fitting.

What Blueprints are not, on purpose

They are not a course catalog, a programme/curriculum system, or an academic-term calendar with its own preset scheduling rules -- those would make VIRO into a learning-management system, which isn't what this is. There's also no separate "student" account type yet beyond the external-user terminology the platform already has. We'd rather ship a relabeled, honestly-scoped set of engines that fit twelve different kinds of organizations today than a half-built vertical product for one of them.

Twelve Blueprints exist today -- general business, sales, professional services, higher education, school, microfinance, banking, NGO, retail, government, and healthcare, plus a custom option for anything that doesn't fit the list. Every one of them is the same VIRO underneath, wearing the vocabulary your organization actually uses.