Data Panda lands the data from your CRM, ERP, ecommerce and finance systems in a warehouse, then lets QuickSight read from one curated model. Dashboards, embedded views and Amazon Q answers come off the same numbers, and SPICE capacity stops being a monthly surprise.
Amazon QuickSight became generally available in November 2016 as AWS's native cloud BI service, built around SPICE (Super-fast, Parallel, In-memory Calculation Engine), an in-memory columnar store that holds dataset extracts for fast dashboard queries. The pricing model is the unusual part: Authors pay a monthly seat (Standard at $24/user, Author Pro at $40/user), while Readers can be billed per active session ($0.30 per 30-minute session, capped at $5/user/month) or per seat. That per-session option is why QuickSight shows up so often as the engine behind embedded customer-facing analytics, where seat counts would be unworkable.
The platform layers Amazon Q in QuickSight on top, generally available since April 2024, for natural-language questions, dashboard summaries and generative dashboard authoring. Native connectors lean heavily into the AWS stack: S3, Athena, Redshift, Aurora, RDS, OpenSearch, Timestream and the Glue Data Catalog, plus the usual Snowflake, BigQuery and Databricks for cross-cloud setups. The strength is the AWS gravity: if your data already sits in S3 or Redshift, QuickSight is a single VPC hop away. The weakness is the same one that hits Power BI and Tableau pages: SPICE refreshes multiply, capacity bills creep, and embedded sessions stack up across tenants. We curate the warehouse so SPICE holds a small set of well-shaped tables and the per-session bill tracks actual reader behaviour.
Curated warehouse tables feed every QuickSight analysis, embedded view and Q topic from one source.
SPICE refresh schedules and capacity track actual dashboard usage, not historical extract sprawl.
Q in QuickSight answers off curated topics with named measures, not from raw warehouse columns.
Customer-facing embeds read the warehouse, and per-session pricing tracks real product usage.
A list of concrete reports, automations and AI features we have built on Amazon QuickSight data. Pick the one that matches your situation.
Why did our QuickSight SPICE bill grow faster than our reader count?
SPICE bills against stored capacity and refresh frequency, not against active readers. A tenant that loaded twenty datasets early on and kept refreshing them hourly keeps paying for those refreshes whether dashboards open or not. Pulling QuickSight onto a curated warehouse means SPICE holds a smaller set of well-shaped marts, refresh cadence matches how often the source itself changes, and the bill tracks readership instead of historical setup choices.
Are we paying Reader seats or per-session, and which is cheaper for our usage?
QuickSight Readers can be billed per active 30-minute session at $0.30, capped at $5 per user per month, or as a Standard Reader seat at $3 per user per month. Per-session is the right call for embedded customer-facing dashboards or internal users who only check in occasionally; per-seat wins for daily power users. Looking at actual session telemetry against the seat list usually shifts the mix in one direction or the other and surfaces a real saving.
How do we keep Amazon Q answers consistent with what Finance sees in the dashboards?
Q in QuickSight answers off topics, which are curated layers over datasets with named fields and synonyms. If topics are built ad-hoc per dataset, the same question gets different answers in different parts of the org. Building Q topics alongside the warehouse marts, with one definition of revenue, customer and order, keeps the natural-language answers aligned with the same numbers Finance reads in the board pack.
Finance gets one revenue and margin definition that feeds every QuickSight analysis and any Amazon Q answer about turnover, reconciled to the boekhouding. The board pack and the analyst's exploration view land on the same number, and the SPICE capacity bill becomes a line item Finance can put in the next quarterly forecast with confidence.
Sales sees pipeline, win rate and forecast in QuickSight analyses that join Salesforce or HubSpot to billing and product usage on the warehouse. The same numbers travel into embedded customer-facing dashboards inside the product, so internal QBRs and customer scorecards do not contradict each other.
Operations leads see throughput, SLA and cost-to-serve from the same warehouse Finance reads, and SPICE refresh schedules align with real source-change frequency. Embedded session usage becomes a knob ops can pull, instead of a surprise on the AWS bill at month end.
You keep the reporting tool you already have. We connect it to the warehouse where your Amazon QuickSight data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Both, by design. SPICE holds the marts that need sub-second dashboard response or that get hit by many embedded sessions, with refresh cadence matched to how often the underlying warehouse table itself changes. Direct query stays in play for low-traffic analyses, ad-hoc exploration on Redshift or Athena, and anywhere the cost of an extra SPICE refresh outweighs the latency saving.
Reader sessions are billed at $0.30 per active 30-minute window, capped at $5 per user per month for named readers, with anonymous embedded sessions priced through capacity bundles instead of named seats. For a customer-facing portal where most users open one dashboard a week, per-session is dramatically cheaper than buying every customer a seat. We model the expected session pattern against the capacity-bundle break-even and pick the structure that fits.
It is the strongest fit when your data already lives in S3, Redshift, Athena or Aurora, because the connectors are first-class and the network path stays inside AWS. QuickSight does connect to Snowflake, BigQuery, Databricks, Postgres and the usual SaaS sources, so a cross-cloud setup is supported. The honest answer is that if you are not already in the AWS account graph, Power BI or Looker often fits the BE/NL mid-market motion better, and we will say so.
We review your Amazon QuickSight setup and the systems around it. Together we pick the first thing worth building.