Autonomous Web App Intelligence System — the defense and observability category we created. 66 rules, 53 signatures, 261 root causes, public incident log, public red-team program. No market equivalent.
Where you’ll see it/awais →
Gladius
LoadingThe Gladius vocabulary
If you’ve read more than two pages of this site, you’ve already met some of this. Here’s the canon — the in-group words we use specifically, defined once, in one place, with the public surface they live on.
28 terms · 4 categories · 0 fabrications
Looking for industry terms (T.O., pencil, F&I, RO)? That’s the automotive glossary. This page is Gladius-specific.
Platform
The words we use for the system itself — the defense category, the federation, the data layer, the community, the palette, the hill.
Autonomous Web App Intelligence System — the defense and observability category we created. 66 rules, 53 signatures, 261 root causes, public incident log, public red-team program. No market equivalent.
Where you’ll see it/awais →
Cross-vertical CRDT federation of AWAIS rules across every Gladius rooftop and product surface. Sub-30-second propagation when a new rule, signature, or root cause lands in one tenant — every other tenant gets it next.
Where you’ll see it/awais/mesh →
Shorthand for Sentinel Mesh. You'll hear it on the site and from operators — "the Mesh caught it," "the Mesh shipped that signature in 14 seconds."
Where you’ll see it/awais/mesh →
Internal name for the BDC ↔ CRM shared-Supabase data layer. Not an HTTP integration — a single source of truth across the BDC product and the CRM product, so leads, activities, and appointments are one row, not two systems syncing.
The annual Gladius operator summit — the in-person gathering of dealership operators running on the platform. Less conference, more guild meet.
Where you’ll see it/the-forge →
The private operator community — invite-only, working dealership professionals only. Where the next features get pressure-tested before they ship.
Where you’ll see it/the-council →
The brand palette — deep navy (#0B1221 / #111D32) with teal accent (#34C3A6), gold (#B89248), and a Milky Way radial-gradient backdrop. If a Gladius page does not look like this, it is not finished.
The one hill we die on: the dealer owns the data. Postgres-portable, no vendor extraction fees, no held-hostage exports. Everything else is negotiable; this is not.
Where you’ll see it/commandments →
Product surfaces
What you'll actually touch when you log in or sit at the desk — the Pencil, the Floor, the Radar, Smart Tasks, Cadence, Speed-to-Lead.
The live, math-checked desking tool that replaces the four-square. Price, trade, down, term, payment — reconciled in real time, with the floor math and the desk math always equal.
Where you’ll see it/features/desking →
The real-time view of every desk's state — who's up, who's in negotiation, who's in F&I, who's a be-back walking back through the door. The single screen a floor manager actually runs the shift from.
Where you’ll see it/managers →
The opportunity-flagging surface — trade-in equity, service-drive sales-ready customers, declined-work re-presents, lease maturities. The cheapest leads in the building, surfaced before the rep has to think about it.
Where you’ll see it/features/speed-to-lead →
Tasks that generate themselves from lead state. No manager assigning, no rep typing — the system reads the conversation, the deal stage, and the cadence position, and writes the next action.
Where you’ll see it/features/ai →
The multi-touch follow-up sequence on every lead that hasn't closed yet — 1-minute response, then 1d, 3d, 7d, 21d, 60d. Industry standard on paper, almost never run in practice. We run it.
Where you’ll see it/features/speed-to-lead →
The Morning Operator Brief — a one-screen daily orientation for owners and GMs. A future product surface; the widget is code-complete but currently DEFERRED until the first paying rooftop is live, per our shipping rule.
Time from lead arrival to first meaningful response. Our standing SLA is under 30 seconds. The industry average is 2-6 hours; after 30 minutes, conversion drops ~80%.
Where you’ll see it/features/speed-to-lead →
Method
The framing, the thesis, and the categories we created — Dealership Revenue Intelligence, the service-to-sales flywheel, the 5 fronts, the 12 moments, the 10 Commandments.
Dealership Revenue Intelligence — the category we're creating. CRM is a 2008 framing; DRI is the modern one: every customer touch is a revenue moment, and the system reads the whole floor, not just the inbox.
Where you’ll see it/dri →
Using service-drive activity — RO frequency, declined work, equity position, lease maturity — as the highest-converting sales pipeline a dealership owns. 22-35% conversion when done right, costs nothing to acquire.
Where you’ll see it/service-drive →
The multi-vertical bet: CRM, BDC, Detail, Stone, Turf. Five engines sharing the same Sentinel Mesh, the same AWAIS layer, the same Postgres-portable data model. Five fronts, one platform.
Where you’ll see it/ecosystem →
The 12 high-leverage customer touchpoints across the dealership lifecycle — from first inquiry to delivery to first service visit to lease maturity. Internal framework today; public detail forthcoming.
The 10 declarative statements of Dealership Revenue Intelligence — what we believe, in complete sentences. Read alongside the 5 Beliefs, the 5 Rituals, and the one hill we die on.
Where you’ll see it/commandments →
The cross-rooftop learning loop: a defense signature, a winning cadence, a recovered objection — whatever one rooftop figures out, every other rooftop on the Mesh has it within the propagation window.
Where you’ll see it/awais/mesh →
The feedback path from won and lost deals back into the AWAIS rule set and the AI prompts. A deal that fell out because of a desk error isn't just a lost deal — it's the next signature.
Where you’ll see it/awais →
Voice & brand
The words we use for our audience and our writing — The Operator, The Principal, floor-language, receipts, and the rules that govern what ships.
Our audience persona — a working dealership professional with 5+ years on the floor. Sales rep, F&I manager, sales manager, GSM, fixed-ops director. Not the dealer principal (that's a different persona).
Where you’ll see it/managers →
The dealer principal — the owner. Different persona than The Operator, different page set, different pricing conversation. Reads /owners, not /managers.
Where you’ll see it/owners →
We write in operator vocabulary, not marketing vocabulary. "Be-back," "T.O.," "pencil," "green pea" — words a rep would actually use. If a page reads like a SaaS landing, it gets rewritten.
Where you’ll see it/glossary →
Public proof of every claim we make. Live incidents log, public status page, named case studies, dated changelog. "Trust us" is not a brand strategy; receipts are.
Where you’ll see it/awais/incidents →
The shipping rule. A feature isn't shipped until prod is 200, every CTA leads somewhere real, and every empty state is branded. If a board member walked it tomorrow, would it embarrass us? Then it's not shipped.
Where you’ll see it/manifesto →
The vendor rule. We propose homegrown before any third-party tool. Vendor lock-in is the enemy of "legendary, leap years ahead." Auth, MFA, telemetry, dunning — homegrown. Postgres-portable always.
Where you’ll see it/our-stack →
About this vocabulary
Every term on this page is a term we actually use — in product, on the site, in writing, in operator-facing materials. Nothing was invented for the page. Where a term already has a public destination, we link to it. Where a term is still internal, we say so.
For automotive industry terms — T.O., pencil, F&I, RO, holdback — see the automotive glossary. If something on this page is unclear, missing, or off, email ricardo.gamon99@icloud.com.
Gladius Technologies LLC · 2026