# What must an AI-generated CRM prove before launch?

Canonical: https://uvilno.com/answers/how-to-verify-ai-crm-before-launch
Updated: 2026-10-27

A CRM must prove records, references, ownership, filters and failure states, not just charts. Uvilno can supply typed collections, real CRUD and transactional activity rules. Test one complete customer-to-task workflow with separate visitors, reloads and conflicting edits before treating a generated CRM as ready software.

Make the displayed metrics depend on actual returned rows. A pipeline chart fed by disconnected demo arrays can look convincing while every real create or update action is broken. Clearly label fictional seeds and keep real customer information out of early tests.

Define how users find a customer, add a task, change its status and return later. Inspect both the interface and the owner data manager, and test a failed or conflicting save. Avoid broader organization permissions or email automation claims unless those capabilities are actually implemented.

## What to verify

| Check | Published behavior | Verification |
| --- | --- | --- |
| Data flow | Lists and counters should derive from actual rows. | Create one task and inspect every dependent view. |
| References | Related customer/task identifiers must remain valid. | Try missing or unavailable references. |
| Reliability | A saved workflow includes failure handling. | Test reload, denied access and stale revision behavior. |

## Steps

1. Create a fictional customer and linked task.
2. Edit status and confirm filters and counts update.
3. Reload and test the same record with another visitor.

## Editable starting brief

Plan a focused CRM with private customers, contacts, tasks and activity_logs. Make lists, counts, filters and charts derive from Uvilno.db rather than disconnected arrays. Add a transactional task activity rule, field validation, conflict errors and two-visitor access tests. Use clearly disclosed fictional records and exclude live email sending or unsupported team permissions.

## Sources

- [Uvilno public SDK documentation](https://uvilno.com/docs)