# Aloria Enterprise Evaluation Kit

Version: 2026-08-23  
Primary contact: jovan@aloria.mx  
Website: https://www.aloria.mx

## 1. Flagship products

### Autonomous Revenue Engine (ARE)
Purpose: governed autonomous revenue operations across market/account signals, research, qualification, offer construction, controlled action and evidence.

Availability: enterprise evaluation.  
Evidence: technical diligence available.  
Important boundary: a remaining external authenticated-session evidence gate is disclosed; do not infer universal production readiness.

### AI Governance Control Tower (AGCT)
Purpose: AI inventory, risk, policies, controls, approvals/exceptions and executive evidence in one governance operating layer.

Availability: enterprise evaluation.  
Evidence: public demo + technical diligence.  
Important boundary: public demo data is representative/synthetic and does not prove customer deployment, certification or guaranteed compliance.

## 2. Engagement model

### Evaluation
Planning envelope: 3-10 business days.

Buyer provides:
- operating problem and accountable owner;
- target users;
- systems/data snapshot;
- security, authority and evidence constraints.

Aloria provides:
- product-fit hypothesis;
- architecture/control map;
- relevant diligence evidence;
- pilot recommendation or no-go rationale.

Exit criteria: bounded use case + owner + prerequisites + go/no-go.

### Scoped pilot
Planning envelope: 4-8 weeks after prerequisites.

Buyer provides:
- sponsor and working SME;
- approved non-sensitive test data or synthetic equivalent;
- access/integration decisions;
- acceptance and stop criteria.

Aloria provides:
- configured bounded workflow;
- authority/control model;
- pilot integration evidence;
- acceptance evidence and gap register.

Exit criteria: acceptance evidence + scale / reshape / stop decision.

### Enterprise deployment
Schedule is scoped after pilot / diligence.

Production commitment requires closure of identity, data, security, AI-provider, integration, operational, support and commercial requirements.

Exit criteria: signed scope + closed prerequisites + production acceptance plan.

Planning envelopes are starting points, not delivery commitments.

## 3. Acceptance framework
- Functional: agreed bounded workflow performs defined tasks.
- Authority: AI actions and human approval boundaries are explicit.
- Integration: required systems/data operate within the agreed scope.
- Evidence: decisions, approvals and execution can be inspected.
- Security: buyer-specific prerequisites are understood and closed for scope.
- Business workflow: agreed process metrics support scale, reshape or stop.

## 4. Design Partner principles
A Founding Design Partner is not a free beta. The goal is to validate one high-value enterprise workflow and reach a paid pilot/customer decision.

Evidence permissions are private by default. Named logos, metrics, quotes or case studies require separate written authorization after the evidence exists and can be substantiated.

Program: https://www.aloria.mx/design-partner

## 5. Diligence
- Trust Center: https://www.aloria.mx/trust
- Evidence Center: https://www.aloria.mx/evidence
- Security & Architecture: https://www.aloria.mx/security-architecture
- Security & Architecture PDF: https://www.aloria.mx/aloria-security-architecture-brief.pdf
- Why Aloria: https://www.aloria.mx/why-aloria
- AI Solution Architect: https://www.aloria.mx/solution-architect
- Enterprise review: https://www.aloria.mx/enterprise-review

## 6. Decision record
Use case:  
Owner:  
Primary product:  
Acceptance criteria:  
Known dependencies:  
Decision: Proceed to pilot / Reshape / Stop