| Positioning | Focused, report-first AI visibility monitoring. | Broader public AEO platform positioning. | Use AEO Table when focus and speed matter more than platform breadth. |
|---|
| Primary use case | Tasks, Runs, reports, citations, competitors, and visibility score. | Answer Engine Insights, Agent Analytics, agents, free AEO report, and additional public platform surfaces. | Do not assume one-to-one feature parity. |
|---|
| Setup path | Create a Task and use launch credits for a first report or sample check. | Public pages emphasize demo/get-started entry and free AEO report paths. | A first report is a useful low-risk evaluation step. |
|---|
| AI visibility monitoring | ChatGPT, Google AI Overview, and Perplexity are the confirmed public channels. | Public pages list a wider set of answer channels. | Broader channel needs may favor Profound after validation. |
|---|
| Citation evidence | Citations are kept with report evidence. | Public materials describe citation and source analysis. | Compare the exact evidence format during evaluation. |
|---|
| Reporting | The report is the central artifact. | Public materials include a free AEO report and broader analytics surfaces. | AEO Table is strongest when the report is the immediate deliverable. |
|---|
| Competitor benchmarking | Competitors are configured and reviewed inside the Task and report. | Public materials describe competitor and share-of-voice style positioning. | Stable competitor entity setup matters in either workflow. |
|---|
| Pricing and free entry | Launch credits support first-report entry without fixed free-Run promises. | This page avoids unverified Profound plan-price claims. | Budget comparisons should use current vendor materials. |
|---|
| Best-fit team | Teams validating AI visibility before buying broader platform scope. | Teams ready to evaluate a wider enterprise AEO platform. | Choose the smallest workflow that answers the business question. |
|---|