One foundation.
Your industry.
The gateway and the asset aren't rebuilt sector by sector. They adapt to yours through configuration — not through a new piece of software. The same foundation, your industry language.
The same system,
your vocabulary.
The Vertaya platform — the gateway and the asset — isindustry-agnostic. We don't rewrite anything for your sector: we configure it. The industry taxonomy, the routing policy, the vocabulary and the knowledge base specific to your activity make the foundation specific — without a single extra line of code.
The industry taxonomy
The categories, entities and document types of your sector. The foundation knows what a quote, a specification, a condition report or a purchase order is — because it has been described to it, not recoded.
The routing policy
Which model for which task, in your context. A simple task doesn't go to the top-tier model: we route it, aiming for −60 to −80% off the bill with no loss of quality.
The vocabulary
The exact terms of your profession. The system answers in your language — that of your teams, your clients and your documents — instead of generic jargon.
The knowledge base
Your procedures, reference frameworks and past cases, made searchable through semantic search. The AI draws on what your business already knows — and that's where your judgement is banked.
A horizontal foundation,
an asset that is yours.
For every industry, the same mechanics: the gateway sees, routes and brings the bill down; the asset banks the judgement specific to your activity. Here's what that looks like, sector by sector.
Quotes, sites, public tenders, on-site HR.
Costings, site reports, tender responses: every AI call traced and routed to the right model, with spend under control.
The tradesperson's know-how — prices, methods, trade-offs — banked quote after quote rather than lost with every departure.
Property management, transactions, block management, condition reports.
Listings, viewing reports, follow-ups: routed and budgeted per agency. Staff shadow AI becomes visible again.
Knowledge of the portfolio and management trade-offs stay within the company, banked — not just in people's heads.
Project tracking, specifications, planning, compliance.
Drafting written documents, analysing files, summaries: the right model for each task, the bill routed downwards.
Design decisions and validated technical details become a reusable memory, from project to project.
Solicitors, accountants, notaries, consultants.
Research, drafting, case summaries: every use routed, traced and budgeted per matter or per client.
The firm's doctrine — chosen sources, document templates, judgement — banked instead of being replayed on every matter.
Planning, fleet, clients, ADR compliance.
Route optimisation, correspondence, client responses: behind a single auditable gateway, at the right cost per use.
Operating rules and dispatch trade-offs codified and replayable — the know-how no longer leaves with an operations manager.
Maintenance, stock, quality, traceability.
Non-conformity analysis, reports, technical documentation: everything passes through a single, budgeted gateway.
The maintenance practices and quality decisions of your experts banked — before retirements carry them away.
CRM, orders, suppliers, catalogue.
Product descriptions, follow-ups, sales responses: routed to the right model, the AI bill cut with no loss of quality.
Customer knowledge and purchasing trade-offs remain a company asset, enriched with every correction.
Planning, records, care coordination.
Reports, correspondence, summaries: behind a self-hosted gateway. Sensitive data doesn't go off to a consumer tool.
Protocols and professional judgement banked, under your exclusive control.
The foundation adapts to it
all the same.
These eight sectors aren't a closed list: they're configurations. Any company with recurring processes, from20 to 100 people, can plug in the gateway and build its asset. There's nothing to rebuild — there's your taxonomy, your vocabulary and your rules to describe.Configuration, not code.
Frequently asked questions
Yes. The gateway and the asset form a horizontal foundation, identical whatever the sector. What changes from one trade to another isn't the code: it's four configuration levers — the taxonomy, the routing policy, the vocabulary and the knowledge base. We describe your activity to the foundation; we don't recode it.
Through description, not development. We set up the entities and document types of your sector (quotes, specifications, condition reports, purchase orders and so on), route each task to the right model, load your exact vocabulary and make your procedures searchable through semantic search. The system then answers in your language, with your rules.
Construction & trades has its own native application, Lucas AI. The other sectors listed — real estate, architecture, professional services, transport, industry, retail, health — are configurations of the same foundation, rolled out case by case according to your processes.
These eight sectors aren't a closed list, they're configuration examples. Any company with recurring processes, from 20 to 100 people, can plug in the gateway and build its asset. There's nothing to rebuild: there's your taxonomy, your vocabulary and your rules to describe. See “Don't see your industry?”.
It all starts with a 30-minute audit of your current AI usage. Configuration then draws on your existing documents and rules — there's no new software to write, only the foundation to set up for your trade. Getting in touch is the way in.
The gateway traces and routes every AI call behind a single, auditable door. For the most exposed sectors — health in particular — the gateway can be self-hosted, with enhanced sovereignty, so that data never goes off to a consumer tool.
Start by seeing.
30 minutes to understand what you spend on AI, and where it goes. The audit is the way in: the gateway and the asset are then configured for your industry.