← The Quick Suite AI Layer

Starts this lesson and continues through 15 more to the end of the course.

What Quick is now — the pieces, the plans, the price

Why this matters

Q0 taught the rename; this lesson is the map of what got added. Since October 2025 the product you knew as a BI tool has been repositioned as an AI workspace with BI inside it. If you're going to be the Quick expert in the room, you need to name every component, say which plan it comes with, and know the three meters that generate the bill. That's this lesson.

The components

The what-is page defines the product as "an AI-powered service for automating tasks, analyzing data, building web applications, and conducting research" and confirms, again: "Amazon Quick evolved from Amazon QuickSight. QuickSight continues as Amazon Quick Sight, a feature within Quick. All existing QuickSight APIs, SDKs, and integrations continue to work without changes." (What is Amazon Quick?, verified 2026-08-26)

The named components (same page, verified 2026-08-26), and where this module covers each:

The launch framing, from the announcement blog: "a new agentic teammate that quickly answers your questions at work and turns those insights into actions for you" (launch blog, 2025-10-09, verified 2026-08-26).

Naming, one more time — because it moved again

The October 2025 blog says "Amazon Quick Suite". The current docs and product pages say "Amazon Quick" — aws.amazon.com/quicksuite/ now serves a page titled "AI Assistant - Amazon Quick - AWS" (verified 2026-08-26). Same product, third name in under a year. Meanwhile everything programmatic still says quicksight: the API reference is quicksight-2018-04-01, IAM actions are quicksight:*, ARNs are arn:aws:quicksight:… — including for the brand-new features (flows, agents, automations all live in the QuickSight API, as later lessons show).

Rule from Q0, still undefeated: search the docs for "Quick", write code that says quicksight.

Plans: four tiers, two worlds

From pricing (verified 2026-08-26; grid cells re-checked across two fetches — one ambiguity flagged below):

⚠️ Two fetches of the pricing page disagreed on whether Flows is included at Free or starts at Plus — cite "Plus and up" and re-check the page before quoting it in a proposal. Also note the docs' own hard gate for Automate: it "is available only for Amazon Quick accounts provisioned through the AWS Management Console" (using-amazon-quick-automate, verified 2026-08-26) — i.e. not the standalone signup.

The "two worlds" part: Free and Plus exist without an AWS account (standalone signup at aws.com/quick); Professional and Enterprise are the AWS-account-connected tiers where the BI product, IAM, and data governance live. When your company already runs QuickSight, you are in the Professional/Enterprise world, and the old Standard/Enterprise edition language still gates features like Topics (Q9.4) — both models live in the docs simultaneously (Q0 lesson 2).

The three meters

Everything beyond seats bills on three meters (pricing page + capacity page, verified 2026-08-26):

1. Infrastructure fee — $250/account/month on Professional and Enterprise. Flat.
2. Index storage — 25/50 GB per user, pooled at the payer-account level; overage $5/GB/month; measured as original file size at the source, before any processing (manage-data-capacity). Capacity provisioned outside your home Region is overage from the first byte.
3. Agent hours — the included 4 or 8 hours cover Research, Flows, and Automate usage; overage $3 per agent hour.

"Agent hours" is the one that surprises people: agentic features are metered like compute, not like seats. A single Research run takes 20–40 minutes (lesson 6) — a team of ten on Professional shares 40 hours/month, and heavy Automate use eats it fast. Watch the usage logs (lesson 6) before the first bill does the teaching.

A 30-day trial covers up to 25 users (pricing page, verified 2026-08-26).

What this means for your support posture

Three questions you can now answer on any call:

• "Do we have feature X?" → which plan/edition gates it (this lesson + the feature's lesson).
• "Why did the bill jump?" → one of three meters; the index meter counts source bytes, the agent meter counts runtime.
• "Is this the old product or the new one?" → both: same APIs, same quicksight namespace, new surfaces on top.

Check yourself

1. Name the Quick components that did not exist before October 2025.
2. A startup signed up at aws.com/quick on the Plus plan and asks where their dashboards are. What's the answer?
3. Which three meters produce the non-seat charges, and which one is measured in source bytes?
4. Your org has 10 Professional users. How many agent hours are in the monthly pool, and what does hour 41 cost?
5. Why does aws quicksight list-flows work even though "Flows" postdates the QuickSight name?

Teaching this section

• Open with the component table and have learners place features they've heard of into it — surfaces immediately who's read marketing vs docs.
• Demo: the pricing page and the What-is page side by side; point at the two product names.
• Good discussion: "Your CFO asks for a cost forecast for enabling Research org-wide. What three numbers do you need?" (users × tier hours, expected runs × 20–40 min, overage rate).
• Watch for: conflating plans (Free/Plus/Pro/Enterprise) with editions (Standard/Enterprise) — both are live in the docs; Q0 lesson 2 has the untangling.
• Timing: 20 min presented.