AbstractPrisma
Business guide

How to create a custom report in Business Studio

Build reports that answer real operational questions instead of relying only on generic dashboards.

Direct answer

To create a custom report, choose a management question, select metric and dimension, define filters, compare periods and save the view for recurring review.

9 minAdvanced
Start step by stepView Business track
Report BuilderGrafico aplicado

Report Builder

Receita ganha por etapa

Metrica

won_value

Dimensao

stage

Visualizacao

bar

Periodo

90 dias

7

Campos

3

Graficos

CSV

Export

Resultadobar chart
Lead · R$ 8.40012 deals
Proposta · R$ 18.9008 deals
Ganho · R$ 31.2009 deals

Step by step: create a custom report in Business Studio

Create a report by pipeline stage, source, team or SLA.

Report QueryConsulta rodada

Report Builder

Win rate por source

Metrica

won_value

Dimensao

stage

Visualizacao

bar

Periodo

90 dias

8

Linhas

R$42k

Valor

22%

Win

Consulta executada

Periodoultimos 90 dias
Representantetodos
Sourceinbound
1

Write the question

Define the expected result and the context needed before using the module.

2

Choose metric and dimension

Configure the key fields, rules or assets that make the flow traceable.

3

Apply useful filters

Run a first version and review the output before scaling the process.

4

Save and make it routine

Measure the result and turn what worked into a reusable routine.

Fundamentals, context, and decision

Operational goal

To create a custom report, choose a management question, select metric and dimension, define filters, compare periods and save the view for recurring review.

Decision rule

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.

Quality criterion

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.

Practical application checklist

  • Write the question
  • Choose metric and dimension
  • Apply useful filters
  • Save and make it routine
  • Review result before scaling.
  • Register owner and next action.
  • Validate the input before asking for another AI generation.
  • Compare the result with the original intent.
  • Record the decision, owner, and next review.

Metrics and quality signals

  • clear owner for each record
  • next action created with a deadline
  • data useful for reporting and forecasting
  • Leads with next action
  • Time in stage or SLA
  • Conversion by source or owner
  • Operational rework avoided

Module field guide

When to use it

How to create a custom report in Business Studio

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.

Inputs

Write the question

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.

Setup

Choose metric and dimension

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

Apply useful filters

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.

Handoff

Save and make it routine

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.

Recommended operating model

  1. 1Define the main intent of the flow in one sentence: who is affected, which problem is solved, and what action should happen next.
  2. 2Run it on a small sample first. In AbstractOS, validate the flow, review AI suggestions, and adjust fields, tone, rules, or integrations before scaling.
  3. 3Compare the result with the expected signals: clear owner for each record; next action created with a deadline; data useful for reporting and forecasting. These signals show whether the module is ready for real use or still a draft.
  4. 4Document the decision, owner, and next review. This prevents rework when another team member continues the process.
  5. 5After validation, connect the result with automation, reporting, or a sales playbook so one-off use becomes a process.

Practical example

Cross won opportunities by source and owner to discover which channels generate better sales.

Common mistakes

  • Creating reports without a business question.
  • Measuring volume without quality or time.
  • Saving reports nobody reviews.

How to do it in AbstractOS

In AbstractOS, use the Business Studio flow to apply this guide with connected context, mockups and operational next steps.

Create report
Saved ReportsRelatorio salvo

Relatorios salvos

Receita por etapa

bar · hoje

Forecast por rep

line · ontem

Win rate por origem

table · 12 jul

Tabela pronta

4

Salvos

5

Colunas

ok

Export

Lead · R$ 8.4k · 12
Proposta · R$ 18.9k · 8
Ganho · R$ 31.2k · 9

Keep learning

How to measure sales and support

See whether the operation is moving forward: leads become pipeline, tickets get answered and revenue appears in forecast.

How to create a sales pipeline with AI

Build a visual routine to track opportunities, prioritize deals and reduce stalled sales.

How to organize support in Help Desk

Centralize requests, customer context, SLA and replies to reduce noise and improve response time.

Where should I start?

Start with the operational objective, then choose the module and validate the first result before automating.

Do I need to configure everything at once?

No. Create a simple version, measure it and evolve from real usage.

How do I know it worked?

Define a result metric before executing: click, lead, reply, sale, publication or reduced rework.