# Qualyo public knowledge and comparison policy

Last reviewed: 2026-09-01

## Evidence hierarchy

1. Deployed behavior and hosted schema/function state.
2. Versioned migrations and server-side enforcement.
3. Typed product, billing, use-case, and comparison registries.
4. Current interface and public pages.
5. Generated knowledge files.
6. Historical plans and marketing prose.

## Claim rules

- Do not invent a customer, testimonial, conversion percentage, rank, award, certification, native integration, legal entity, jurisdiction, retention duration, or refund promise.
- Describe Qualyo primarily as a lead qualification platform, not as a generic form builder. A form is the lead-facing interface for the qualification flow.
- State that the customer defines what a qualified lead means and that Qualyo applies those customer-defined criteria.
- Keep agencies and high-ticket service businesses with meaningful, mixed-quality inbound demand as the primary ICP. Broader use cases must not erase that initial focus.
- Do not describe Qualyo as a built-in CRM, Kanban pipeline, payment product, or managed contract e-signature product.
- Describe Qualyo Public API v1 and MCP accurately: both expose the same 14 account, workspace, form, submission, analytics, schema, and health operations.
- Describe file uploads and drawn signatures precisely: supported response fields, 15 MB per file, 10 files and 25 MB total per submission; not a general file-transfer or contract-signing system.
- Use “optional AI qualification,” not a guaranteed lead score.
- State that the route graph remains authoritative and every Qualifier has an explicit fallback.
- Treat competitor pricing as observed evidence with market, cadence, access date, and an official link.
- Use “Not verified” when official documentation did not establish a feature.
- Explain which product fits a scenario instead of naming a universal winner.

## Update policy

Comparison claims are scheduled for review at least every 90 days. Product, pricing, route, legal, and knowledge files must be updated in the same change when a durable fact changes. The generated-file check fails when public knowledge drifts from the typed registries.

Corrections: support@qualyoforms.com.