More than a brand layer
The foundation connects conversations, agents, knowledge, and systems to support governed business actions. Your offer is built on an operational platform, not only a customized interface.
Back to home
White Label Program
Take SON.IA technology to market under your own brand
Assess a SON.IA offer under your company's identity. Brand, domain, commercial relationship, implementation, onboarding, and support are defined according to technical feasibility, proposal, and contract.
Understand responsibilities and criteria before deciding to continue.
Why structure your offer with SON.IA
Build your own offer on an Operational AI foundation designed to evolve by scope.
In the White Label model, SON.IA technology becomes part of an offer under the partner's brand and within the validated scope. The operation evolves as capabilities, integrations, owners, and governance are prepared.
Evolution aligned with operational maturity
Channels, agents, integrations, and processes evolve in stages, considering technical feasibility, permissions, data, operating capacity, and agreed responsibilities.
Clear roles from the proposal
The model makes clear what belongs to onsmart.AI, the partner, and both parties together. Brand, implementation, onboarding, support, data, and governance are defined before activation.
Operational AI foundation · identity by scope · formalized responsibilities
White Label does not imply unrestricted customization, a dedicated environment, a specific SLA, automatic compliance, or universal integration. Identity, architecture, support, data, billing, and commercial terms depend on technical assessment, proposal, and contract.
Requirements to move forward
What your company needs to prepare for a White Label operation
The assessment considers market proposition, commercial and operational capacity, and readiness to define brand, data, integrations, and continuity.
Defined company and market proposition
Positioning, audience, intended offer, and enough commercial capacity to assess fit and feasibility.
First-level operating capacity
An existing or planned structure for customer relationships, onboarding, support, and follow-up within the agreed role.
Readiness for technical and contractual governance
Owners for brand, data, integrations, security, billing, and continuity available for detailed design.
Commercial rules and accreditation
SON.IA White Label rules and requirements
A business under the partner's brand: the customer contracts with the partner, who sets price, invoices, and provides N1 support.
- Role
- Create and operate an own business.
- Customer contracts with
- Partner.
- Who invoices
- Partner.
- Who sets the final price
- Partner.
- Economic model
- License + consumption; the partner retains its own margin.
- Compensation
- Own margin; no RLC commission.
- Renewal commission
- Not applicable
- Commercial target
- There is no commercial target tied to the MRR generated by the partner from end customers. The selected plan's monthly fee, consumption, and other terms still apply.
- Brand
- Partner brand.
- Certification
- Mandatory, including approval and maintenance of the applicable certification.
- Minimum team
- 2 enabled technical pre-sales professionals + 2 dedicated sales professionalsMinimum structure maintained throughout the partnership term.
- Customer support
- Partner — N1 support.
- Technical support for partner
- onsmart.AI — N2/N3 support for the partner, under the applicable instrument.
For enablement and continued accreditation: complete and pass certification; pay program fees; maintain at least 2 enabled technical pre-sales professionals and 2 dedicated sales professionals; have capacity for N1 support; and keep certification and eligibility current.
Program pricing and limits
White Label plans
Choose the initial capacity according to the number of environments (tenants) in the operation.
Partner
R$6,990
monthly fee
3 tenants included
Growth
R$12,990
monthly fee
5 tenants included
Scale
R$24,990
monthly fee
10 tenants included
The listed monthly fees and tenant limits are definitive. Consumption, scope, taxes, and other applicable terms are detailed in the proposal and agreement.
Enablement depends on assessment, certification where applicable, payment of program fees, and formalization. This page does not replace a proposal, program rules, or agreement.
Expected partnership milestones
How a White Label operation advances safely
These milestones guide operational readiness; final scope, sequence, and responsibilities depend on assessment and contract.
Initial offer and scope validated
Audience, value proposition, capabilities, limits, and responsibilities documented before any activation.
Operation prepared for the first customer
Sales, onboarding, support, escalation, and governance processes defined between the partner and onsmart.AI.
Evolution based on operating evidence
New capabilities, channels, or integrations advance according to use, maturity, technical feasibility, and observed outcomes.
Support from onsmart.AI
What onsmart.AI provides to support this model
Technical and operational support defined by the scope and the formalized arrangement between the parties.
Brand, architecture, support, data, billing, and service levels depend on technical feasibility, proposal, and contract.
Technology foundation and platform evolution
Access to SON.IA capabilities included in scope and to applicable platform developments under the contracted arrangement.
Technical design and shared responsibilities
Support to define architecture, integrations, data, security, escalation, and operating boundaries between the parties.
Second-level support under the arrangement
Handling of matters assigned to onsmart.AI through the channels, owners, and service levels established in the contract.
How we evaluate the partnership
Understand the brand role, operating responsibilities, and criteria before sharing your details.
If you choose to proceed, first provide essential contact details and then the operating profile in a separate step.
If there is alignment, scope, responsibilities, and commercial conditions are formalized in a proposal and contract.
Submitting the form does not represent automatic approval. Technical scope, service levels, and commercial conditions are defined after reviewing the company's profile.
Optional next step
Does it make sense to explore this model further?
Only then begin the assessment. We first request basic contact details; qualification follows in a second step.
The selected model remains visible throughout the assessment.
The first step requests only identification and contact details.
Commercial and operating information is grouped into the second step.
Explore scope, responsibilities, and technical feasibility if this model fits your company. No data is sent until final confirmation.