Define what will be sold
Separate products, services, packages and subscriptions to avoid a confusing catalog.
Organize products, services, prices and variations so sales happen with more context inside CRM and proposals.
To create a catalog, register products or services with price, category, variations, images and sales rules; then connect items to orders, proposals and opportunities.
The animated mockup shows product registration, category organization, order creation and linking to a contact or deal.
Novo produto
ativoNome
Vestido Floral
SKU
VERAO-001
Categoria
Roupas
Preço
R$ 159,00
Unidade
unidade
Status
Ativo
Descrição
Vestido leve para coleção de verão, disponível para retirada ou entrega.
Vestido Floral
SKU VERAO-001 · Roupas
R$ 159
7
Campos
4
Categorias
13
Ativos
Separate products, services, packages and subscriptions to avoid a confusing catalog.
Include name, description, price, SKU, category, images and variations when relevant.
Use catalog items to build orders, proposals and opportunities with more consistency.
Keep availability, price and status updated so the team does not promise the wrong thing.
To create a catalog, register products or services with price, category, variations, images and sales rules; then connect items to orders, proposals and opportunities.
Before opening AbstractOS, gather lead list, sales stage, owner, SLA, conversation history, offer, and qualification rule. Better inputs reduce the chance that AI creates something polished but disconnected from real operations. Configure the flow around one simple hypothesis: prioritize the action that reduces context loss, improves response speed, and creates a verifiable next step. Avoid starting with visual details or automations before validating the core intent.
Review process owner, next action, SLA, data quality, and pipeline effect. If any of these points are weak, treat the output as a draft and run another iteration before publishing or scaling. Finish by recording lead, company, deal, ticket, task, and support history. This turns the learning moment into operational memory and makes auditing, collaboration, and measurement easier later.
Use this module when the flow needs to become an operational routine, not just a one-off action. The goal is to leave with a usable artifact, a clear decision, and a recorded next step.
Before opening AbstractOS, gather lead list, sales stage, owner, SLA, conversation history, offer, and qualification rule. Better inputs reduce the chance that AI creates something polished but disconnected from real operations.
Configure the flow around one simple hypothesis: prioritize the action that reduces context loss, improves response speed, and creates a verifiable next step. Avoid starting with visual details or automations before validating the core intent.
Review process owner, next action, SLA, data quality, and pipeline effect. If any of these points are weak, treat the output as a draft and run another iteration before publishing or scaling.
Finish by recording lead, company, deal, ticket, task, and support history. This turns the learning moment into operational memory and makes auditing, collaboration, and measurement easier later.
A clinic can register appointments, packages and procedures, then insert those items into proposals and orders linked to the CRM contact.
In Business Studio, use Products to create a catalog, build orders and connect sales items to contacts, deals and proposals.
Create catalogTurn a CRM opportunity into a clear, trackable proposal ready to move the deal forward.
Create a public schedule for services, time slots, team and confirmations without losing the CRM and operation link.
Build a visual routine to track opportunities, prioritize deals and reduce stalled sales.
Yes. Services, packages, plans and physical products can all be organized as sales items.
Only when it makes sense for the business. For services, category, price and availability already help a lot.
The team reuses standardized items in proposals and orders, reducing pricing and description errors.