Module 3.2: GenAI for Analysts — Data Summarisation, Reports, and Insights

YOUR PROGRESS — GENERATIVE AI: ZERO TO JOB-READY ← Course home
9 of 20 modules complete
GENERATIVE AI: ZERO TO JOB-READY  ›  UNIT 3  ›  MODULE 2 OF 4

GenAI for Analysts — Data Summarisation, Reports, and Insights

⏱ 14 min read 📝 Assignment inside Hands-on examples

In Module 3.1 you saw how developers use GenAI for code generation and debugging. This module is for the other half of every Indian IT team — the analysts, business analysts, and data analysts who work with data, reports, dashboards, and stakeholder communication every day.

If you are in a data analyst, business analyst, or reporting role — or planning to enter one — this module shows you exactly where AI saves the most time and produces the highest quality output.


Why analysts are the biggest beneficiaries of GenAI

50%+
of standard financial reports will be AI-generated within two years — Deloitte 2026 State of AI
40–60%
productivity boost for analysts using GenAI for information retrieval and summarisation — BCG
18%
annual growth in data analytics roles in India in 2026, with ₹4–8 LPA entry-level salaries

The analyst role is shifting fast. Natural language querying, automated insight generation, analytics code generation, and RAG-based internal data search are the highest-ROI GenAI use cases in data analytics in 2025. The analysts who learn to use these tools effectively are completing in 30 minutes what used to take a full day.

The shift in the analyst role: GenAI does not replace analysts — it replaces the mechanical parts of the job: writing SQL from scratch, formatting reports, summarising long documents, drafting routine stakeholder emails. What it cannot replace is business judgement — knowing which insight matters, why a number looks wrong, and what a stakeholder actually needs to hear. That judgement is where your value now sits.

Use case 1 — SQL generation from plain English

📊
Writing SQL queries using natural language

For analysts who are not SQL experts — or who write SQL but spend time on complex joins and window functions — AI dramatically accelerates query writing. Give the model your table schema and what you want to know, and it generates correct SQL in seconds.

EXAMPLE — Sales analysis query for Indian retail data
You are a senior data analyst writing SQL for a MySQL database.

I have these tables:

  • orders (order_id, customer_id, order_date, city, state, total_amount, status)
  • order_items (item_id, order_id, product_id, quantity, unit_price, category)
  • customers (customer_id, name, tier, registration_date, city)

Write a query that shows:

  1. Top 5 product categories by revenue in Q4 FY2025 (Oct 2024 – Mar 2025)
  2. Month-over-month revenue growth % for each category
  3. Only include completed orders (status = ‘delivered’)
  4. Show results sorted by Q4 total revenue descending

Use window functions for the month-over-month calculation. Format the revenue columns as integers (no decimals).

Key elements: Full schema provided, exact date range defined (Q4 FY2025 = Oct–Mar in Indian fiscal year), filter condition specified, window function explicitly requested, output format defined. Without the schema, the model generates plausible column names that may not match your actual database.
EXAMPLE — Explaining an existing complex query
Explain what this SQL query does, step by step. Use plain language — the explanation is for a non-technical product manager.

SELECT c.tier, COUNT(DISTINCT o.customer_id) AS active_customers, SUM(o.total_amount) AS total_revenue, AVG(o.total_amount) AS avg_order_value, SUM(o.total_amount) / COUNT(DISTINCT o.customer_id) AS revenue_per_customer, RANK() OVER (ORDER BY SUM(o.total_amount) DESC) AS revenue_rank FROM orders o JOIN customers c ON o.customer_id = c.customer_id WHERE o.order_date >= DATE_SUB(CURDATE(), INTERVAL 90 DAY) AND o.status = ‘delivered’ GROUP BY c.tier HAVING COUNT(DISTINCT o.customer_id) > 10 ORDER BY total_revenue DESC;

Why this matters for Indian IT analysts: At TCS, Infosys, and Wipro client deliveries, analysts frequently need to explain queries to non-technical stakeholders or document them for handover. AI generates clear explanations in seconds — saving 20–30 minutes of documentation per query.
ChatGPT — best SQL generation, widest dialect support Claude — better for long schema analysis GitHub Copilot — best inline in SQL editors

Use case 2 — Data summarisation and insight generation

📈
Turning raw numbers into business insights

This is where most analysts underuse AI. They use it to format tables but not to interpret them. AI is excellent at identifying patterns, anomalies, and business implications in data — if you give it the right context about what the data represents and who will read the summary.

EXAMPLE — Monthly sales summary for Indian FMCG client
You are a senior business analyst preparing a monthly performance summary for the India operations head of an FMCG company.

Here is the sales data for March 2026:

Region | Revenue (₹ Cr) | vs Feb | vs Mar 2025 | Units Sold | Returns % North | 142.3 | +8.2% | +23.1% | 48,200 | 2.1% South | 118.7 | -3.4% | +11.4% | 39,800 | 1.8% West | 167.9 | +12.1%| +31.2% | 54,100 | 3.7% East | 89.2 | -7.8% | +4.2% | 31,900 | 4.2% Total | 518.1 | +3.6% | +18.9% | 174,000 | 2.8%

Write a 3-paragraph executive summary. Paragraph 1: overall performance vs targets. Paragraph 2: key highlights and concerns by region. Paragraph 3: 2 specific recommendations.

Tone: direct and factual. No fluff. The reader has 2 minutes for this.

Why the tone instruction matters: Without "direct and factual, no fluff", AI defaults to corporate language full of phrases like "it is encouraging to note" and "moving forward". Indian operations heads and managers want direct numbers and recommendations — the role instruction and tone constraint together produce a genuinely useful summary.
EXAMPLE — Anomaly detection in data
You are a data analyst reviewing weekly transaction data for anomalies.

Here is transaction volume data by day for the past 4 weeks (in thousands):

Week 1: Mon 42, Tue 45, Wed 43, Thu 47, Fri 89, Sat 134, Sun 98 Week 2: Mon 41, Tue 44, Wed 46, Thu 45, Fri 91, Sat 128, Sun 95 Week 3: Mon 43, Tue 46, Wed 44, Thu 48, Fri 87, Sat 131, Sun 97 Week 4: Mon 40, Tue 12, Wed 45, Thu 46, Fri 88, Sat 133, Sun 96

Identify any anomalies. For each anomaly:

  1. State what is unusual and by how much it deviates from the pattern
  2. List 3 possible business explanations
  3. State what additional data you would need to confirm the cause

Think step by step before identifying anomalies.

CoT trigger for analysis: "Think step by step before identifying" prevents the model from pattern-matching to the most obvious answer. The model will correctly identify Week 4 Tuesday (12K vs ~44K average — a 73% drop) and generate plausible hypotheses: system outage, payment gateway failure, bank holiday. The structured output format makes it directly usable in an incident report.
Claude — best analytical reasoning and writing quality ChatGPT with data analysis — can read CSV/Excel directly Gemini — good for research-backed context

Use case 3 — Python for data analysis

🐍
Generating Python analysis and visualisation code

For analysts who know what they want to do with data but are not strong Python coders, AI generates working pandas and matplotlib/seaborn code with the same specificity-equals-quality principle from Module 3.1. For experienced analysts, AI accelerates the boilerplate — freeing you to focus on interpretation.

EXAMPLE — Customer churn analysis for Indian telecom data
You are a data analyst writing Python for a telecom company's churn analysis.

I have a CSV file ‘customers.csv’ with these columns: customer_id, circle (Delhi/Mumbai/Chennai/Kolkata/etc), tenure_months, monthly_recharge_avg, data_usage_gb, voice_minutes, complaints_last_90d, last_recharge_days_ago, churned (0/1)

Write Python code that:

  1. Loads the data with pandas
  2. Creates a summary showing churn rate by circle (bar chart, sorted descending)
  3. Shows distribution of tenure_months for churned vs non-churned (overlapping histogram)
  4. Prints a correlation table between churned and the numeric features, sorted by absolute correlation

Requirements:

  • Use matplotlib for charts, seaborn for the histogram
  • Figure size 10x6, title and axis labels on every chart
  • Save charts as PNG files: churn_by_circle.png, tenure_distribution.png
  • Print all outputs clearly labelled
  • Include comments explaining each step
India-specific framing matters: Using "circle" (telecom regulatory term in India) instead of "region" produces code that matches actual Indian telecom data structures. This saves a round of editing. Always use your actual column names and domain vocabulary — the model generates directly usable code instead of skeleton code you have to rename.
EXAMPLE — Excel automation with Python
Write Python code to automate a weekly sales report that currently takes me 2 hours manually.

Input: ‘weekly_sales.xlsx’ with sheets: RawData, Targets

  • RawData columns: date, salesperson, region, product, units_sold, revenue
  • Targets columns: salesperson, weekly_target_revenue

Output: A formatted Excel report ‘weekly_report.xlsx’ with:

  1. Sheet “Summary”: pivot table — salesperson vs region showing total revenue, with grand totals
  2. Sheet “Performance”: each salesperson’s actual vs target, % achieved, status (✓ Met / ✗ Missed)
  3. Sheet “Top Products”: top 10 products by units sold this week

Formatting requirements:

  • Header rows: bold, background #1565C0, font white
  • Met target rows: light green background (#e8f5e9)
  • Missed target rows: light red background (#ffeaea)
  • All revenue columns: Indian number format (₹1,23,456)

Use openpyxl. Include error handling for missing files.

This prompt eliminates a 2-hour weekly task. Indian number formatting (1,23,456 instead of 123,456), specific colour codes matching your theme, and the exact sheet structure mean the output is production-ready. The model knows openpyxl's Indian locale formatting — specifying it explicitly ensures you get it.
Claude — best for complex multi-step Python with clear logic ChatGPT — can execute Python directly (Advanced Data Analysis mode) GitHub Copilot — good inline for pandas operations

Use case 4 — Report and presentation writing

📄
Writing reports, dashboards narratives, and presentation content

The highest-value analyst output is not the data itself — it is the narrative that explains what the data means. This is where AI saves the most time and where prompt engineering skill produces the biggest quality difference.

EXAMPLE — Power BI / Tableau dashboard narrative
You are a senior analyst writing the narrative text for a Power BI dashboard for a mid-size Indian e-commerce company.

Dashboard context: Q4 FY2026 (Jan–Mar 2026) performance review Audience: Senior leadership team (CMO, CFO, COO) — non-technical

Key metrics from the data:

  • Total GMV: ₹847 Cr (+22% YoY)
  • Orders: 2.3 million (+18% YoY)
  • Average Order Value: ₹368 (+3% YoY)
  • Customer Acquisition Cost: ₹312 (-8% YoY — improvement)
  • Return Rate: 14.2% (+1.8pp YoY — deterioration)
  • Mobile orders: 78% of total (+6pp YoY)
  • Top category: Electronics (31% of GMV)
  • Weakest region: East India (-3% YoY)

Write:

  1. A 2-sentence headline summary (for the dashboard title area)
  2. A 4-sentence performance narrative for the overview section
  3. One “watch out” callout (the metric that needs attention)
  4. One “opportunity” callout (the metric that suggests upside)

Keep language sharp. Each sentence should contain a number. Avoid passive voice.

"Each sentence should contain a number" is one of the most effective constraints for analyst writing prompts. It forces the model to anchor every claim in data — exactly what leadership dashboards require. Without this constraint, AI produces hedged language that adds no value over the numbers themselves.
EXAMPLE — Converting data findings into presentation slides outline
Convert these analysis findings into a 5-slide presentation outline for a quarterly business review at an Indian IT services company.

Findings:

  • Project delivery on-time rate: 73% (target was 85%)
  • Top delay cause: requirement changes mid-project (41% of delayed projects)
  • Second delay cause: resource unavailability (28% of delayed projects)
  • Client satisfaction score: 7.8/10 (down from 8.3 last quarter)
  • Projects using AI-assisted testing: 23% faster delivery, 91% on-time rate
  • Headcount utilisation: 84% (industry benchmark: 78%)

For each slide provide:

  • Slide title (max 8 words)
  • 3 bullet points (one key data point each)
  • One “so what” statement — the business implication

Slides: Executive Summary, Problem Analysis, Root Causes, Solution (AI-assisted testing), Next Steps

The "so what" instruction transforms a data dump into a business argument. This is the difference between an analyst who presents data and one who tells a story with data. The model generates the business implication for each slide — which is exactly what separates a good QBR presentation from a great one.
Claude — most natural, least AI-sounding report writing ChatGPT — strong for structured business writing

The AI-assisted analyst workflow

RECOMMENDED WORKFLOW — AI-ASSISTED DATA ANALYSIS
1
Understand the business question first. Before writing a single query or prompt, write down in one sentence what decision this analysis will support. AI cannot supply business context it was not given.
2
Use AI for SQL and Python first drafts. Provide the full schema, the business question, and any constraints (date ranges, filters, output format). Review every line before running on production data.
3
Verify the numbers yourself. AI-generated queries can have subtle logic errors — wrong date filters, incorrect joins, missed NULL handling. Always spot-check the output against known data points before sharing with stakeholders.
4
Use AI for the narrative, you provide the judgement. Paste your verified numbers into the report-writing prompts. AI writes the first draft — you add context the model cannot know (why a number is unusual, what changed in the business this quarter).
5
Use Gemini for research context. When you need to contextualise a finding against industry benchmarks or market trends, Gemini's live search grounding is more reliable than ChatGPT or Claude for current figures.
6
Never paste raw client data into consumer AI tools. Aggregate or anonymise data before prompting. A table with 500 customer IDs, names, and transaction values is a DPDP Act compliance violation if pasted into ChatGPT's consumer tier. Use your company's enterprise AI tool for sensitive data.

The most important analyst-specific risk: AI-generated SQL queries can produce results that look correct but have subtle logic errors — incorrect date boundary conditions, wrong join types that silently drop or duplicate rows, or aggregations applied at the wrong level. A query that runs without error and returns plausible-looking numbers is not the same as a query that is logically correct. Always verify AI-generated query output against at least one known data point before presenting to a stakeholder.

The three things to remember

KEY TAKEAWAYS — MODULE 3.2
  1. Schema and context are everything for SQL and Python generation — paste your actual table schema, column names, Indian-specific terms (fiscal year, circles, LPA), and exact output requirements. Vague prompts produce skeleton code you have to rewrite. Specific prompts produce production-ready first drafts.
  2. AI writes the draft, you provide the business judgement — AI can generate the narrative from numbers but cannot know why a number is surprising, what changed in the business, or what a specific stakeholder needs to hear. Your value as an analyst is that contextual judgement — not the mechanical writing.
  3. Always verify AI-generated query output before sharing — a query that runs without error is not necessarily logically correct. Spot-check against known data points. This one habit separates analysts who trust AI appropriately from those who create problems for themselves and their teams.

Assignment 3.2 — Apply AI to a Real Analysis Task

Three tasks covering the core analyst use cases. Each should take 15–20 minutes.

  1. SQL generation: Write a prompt asking AI to generate a SQL query for a real analysis you need to do — or a practice dataset you are working with. Include your full schema, the business question, and any filters or output format requirements. Run the query (if you have access to a database) and note any corrections needed.
  2. Data summarisation: Take any table of numbers you have worked with recently — a report, an assignment dataset, or publicly available data (Kaggle India datasets work well). Paste the key numbers into a prompt and ask AI to write an executive summary with specific constraints: two paragraphs, every sentence must contain a number, direct tone. Compare the output to how you would have written it.
  3. Report narrative: Take one insight from your analysis — a pattern, an anomaly, or a performance gap — and ask AI to write a "so what" statement explaining the business implication. The model should generate the business argument, not just repeat the number. Note whether the implication is accurate for your domain context.
  4. Add all three prompts to your AI Learning Journal under "Module 3.2 — Analyst Prompts." These go into your prompt library in Module 3.4.

After this assignment you will have a concrete sense of where AI genuinely accelerates analyst work and where your own business judgement is irreplaceable.

Sources and data references
ClaimSource
50%+ of standard financial reports will be AI-generated within two yearsDeloitte 2026 State of AI in the Enterprise, cited in sranalytics.io March 2026
40–60% productivity boost for analysts using GenAI for information retrievalBCG Stairway to GenAI Impact, cited in sranalytics.io January 2026
Natural language querying, automated insight generation, analytics code generation are highest-ROI use casesLatentView Analytics GenAI in Data Analytics, April 2026
18% annual growth in data analytics roles in India 2026; ₹4–8 LPA entry salarieslearninglabb.com Data Job Trends 2026, December 2025
Data analyst role in India: SQL, Tableau/Power BI, Excel, Python — standard toolkitdvanalyticsmds.com Data Science Career Paths India 2026
Diagrams: original — CC0No attribution required