20 tested prompts across 4 stages. Works with ChatGPT, Claude, and Gemini.

Grok combines strong reasoning with real-time information access, making it useful for data analysis tasks that require current context: interpreting industry benchmarks, understanding whether a metric deviation is industry-wide, or getting the latest information on how to use a specific analytics tool. These prompts help you use Grok to analyze data, write queries, and turn numbers into decisions. Built across 4 distinct stages covering Understand and Frame the Analysis, Write Queries and Code, Interpret and Validate Results and more, this guide gives you one tested prompt per step so you never have to write from scratch or guess what the AI needs. The prompts work in ChatGPT, Claude, and Gemini and are designed to get usable output on the first try.
Stage 1
Good analysis starts with the right question. These prompts help you frame what you are actually trying to learn before touching the data.
Define the analysis question
I have data about [DESCRIBE DATASET]. The business question I need to answer is: [DESCRIBE QUESTION]. Help me clarify the exact analysis question: what specifically am I measuring, what comparison or change will answer the question, and what data do I actually need versus what I have? Flag any assumptions in my question that I should test.
Choose the right analysis approach
My question is: [ANALYSIS QUESTION]. My data includes: [DESCRIBE COLUMNS AND TYPES]. What type of analysis is most appropriate: descriptive statistics, trend analysis, cohort analysis, A/B test evaluation, regression, or something else? What are the key assumptions this approach requires that I should check first?
Benchmark a metric against current industry standards
My [METRIC NAME] is currently [VALUE]. Is this good, bad, or average for [INDUSTRY/BUSINESS TYPE]? What are the current industry benchmarks? Has this benchmark changed recently? What factors typically explain variance above or below benchmark in businesses like mine?
Identify what data I am missing
I want to answer the question: [QUESTION]. My current data includes: [DESCRIBE]. What data am I missing that would make this analysis more reliable or complete? For each gap, tell me: how important it is, where I might be able to get it, and what I can do in the meantime if I cannot get it.
Plan a multi-step analysis
I need to analyze [COMPLEX TOPIC] to inform a decision about [BUSINESS DECISION]. Break this into a logical sequence of analysis steps. What do I need to understand first before I can answer the harder questions? What is the right order to build up from simple to complex? What are the decision points where earlier results will determine which analysis to run next?
Stage 2
Grok can write the data manipulation code you need. These prompts help you get working queries and scripts.
Write a SQL query
Write a SQL query that answers: [QUESTION]. My relevant tables are: [DESCRIBE SCHEMA]. Conditions: [DESCRIBE FILTERS, JOINS, AGGREGATIONS]. Return: [DESCRIBE DESIRED OUTPUT COLUMNS]. Optimize for: [DESCRIBE CONSTRAINTS — SIZE OF TABLE, INDEX ON X]. Add a comment explaining any non-obvious logic.
Write a Python analysis script
Write a Python script using pandas to: [DESCRIBE ANALYSIS TASK]. My data is in [CSV / DATAFRAME / FROM SQL QUERY]. The data has these columns: [LIST COLUMNS]. Steps needed: [DESCRIBE STEPS]. Output should be: [DESCRIBE OUTPUT — SUMMARY TABLE / CHART / SAVED FILE]. Include error handling for missing values.
Write a pivot or aggregation query
I need to aggregate [TABLE/DATASET] by [GROUPING DIMENSIONS] and calculate [METRICS — COUNTS, AVERAGES, PERCENTILES]. The result should show [DESCRIBE DESIRED SHAPE — ONE ROW PER X, COLUMNS FOR EACH Y]. Write this in [SQL / PYTHON PANDAS / DPLYR]. Include a version that handles nulls appropriately.
Write a data transformation script
I need to transform raw data from [SOURCE FORMAT] to [TARGET FORMAT]. Transformations needed: [DESCRIBE — RESHAPE WIDE TO LONG, JOIN TWO TABLES, CALCULATE DERIVED COLUMNS, FILTER ROWS BY CONDITION, FILL MISSING VALUES WITH X]. Write the transformation in [SQL / PYTHON / R]. Show the before and after schema.
Debug a query that returns wrong results
This query is supposed to [DESCRIBE EXPECTED RESULT] but returns [DESCRIBE ACTUAL RESULT]: [PASTE QUERY]. Walk through what this query is actually doing step by step. Identify where the logic diverges from my intention and show me the corrected version.
Stage 3
Numbers need interpretation to become decisions. These prompts help you draw valid conclusions from your analysis.
Interpret a statistical finding
I ran [DESCRIBE ANALYSIS] and got: [PASTE RESULTS]. My sample size is [N]. What does this result mean in plain English? Is it statistically significant? Is the effect size meaningful for a business decision? What are the most important caveats on what I can conclude?
Check for data quality issues before drawing conclusions
I have this analysis result: [DESCRIBE FINDING]. Before I present this, help me check: could the result be an artifact of data quality issues (missing data, outliers, biased sampling)? What would I need to check to be confident the result is real? Are there any obvious ways this analysis could be wrong?
Find alternative explanations for a correlation
My data shows [CORRELATION OR RELATIONSHIP — E.G., CUSTOMERS WHO DO X HAVE 40% HIGHER RETENTION]. Before I present this as causal, what are the three most plausible alternative explanations? How could I test whether the relationship is causal or just correlational with the data I have?
Validate a segmentation
I segmented my data by [SEGMENTATION CRITERIA] and found [DESCRIBE DIFFERENCES BETWEEN SEGMENTS]. Is this segmentation meaningful? Are the groups large enough? Is the difference between groups statistically significant? Could the segmentation be creating an artifact that does not reflect real underlying differences?
Identify what the data does not tell me
My analysis shows: [DESCRIBE FINDINGS]. Before I use this to make a decision about [DECISION], help me identify: what the data CANNOT tell me, what additional data I would need to be fully confident, and what assumption I am implicitly making when I use this data to justify the decision.
Stage 4
Analysis only creates value when it drives decisions. These prompts help you translate findings into clear communication.
Write an executive summary of analysis findings
My analysis found: [LIST KEY FINDINGS]. The business question was: [QUESTION]. Write a three-paragraph executive summary for [AUDIENCE — EXECUTIVES / BOARD / PRODUCT TEAM]. Paragraph one: what question we were answering and the key finding. Paragraph two: three most important supporting data points. Paragraph three: the recommended action and next steps.
Explain a complex finding simply
I need to explain this finding to a non-technical audience: [DESCRIBE FINDING]. Write an explanation in plain English with: an analogy that makes the concept immediately clear, the specific business implication (so what), and what action this finding suggests. Maximum two sentences plus the analogy.
Choose the right chart for each finding
I have these findings to visualize: [LIST FINDINGS]. For each one, recommend the most effective chart type: bar, line, scatter, heatmap, funnel, histogram, or other. Explain why that chart type best communicates each specific insight and flag any common visualization mistakes I should avoid for that type of data.
Turn analysis into a recommendation
My analysis shows: [DESCRIBE FINDINGS]. The decision we need to make is: [DESCRIBE DECISION]. Help me write a one-page recommendation that: states the recommended action clearly, cites the three strongest data points that support it, acknowledges the main uncertainty or risk, and defines what we will watch to know if the decision was right.
Write a data story for a presentation
I am presenting analysis about [TOPIC] to [AUDIENCE]. My key findings are: [LIST]. Build a narrative structure for the presentation: the setup (why this analysis matters now), the complication (what the data reveals that is unexpected), the resolution (what we should do), and the call to action. Map each finding to a slide in this structure.
Yes. Grok can write SQL and Python for data manipulation, interpret statistical results, and help you design analysis approaches. Its real-time web access is useful for benchmarking your metrics against current industry standards or finding documentation for recent tool updates.
Yes. Give Grok your schema description and what you need to answer, and it will write well-structured SQL. It handles joins, aggregations, window functions, and CTEs. Always review the query logic before running on production data.
Both are strong for analysis code and interpretation. Grok's advantage is real-time information — helpful for checking current tool documentation, benchmarking metrics, or understanding recent changes to analysis frameworks. Claude is typically stronger for very long analytical documents and complex reasoning chains.
Yes, paste a sample of your data (20-50 rows) and Grok can analyze it, identify patterns, and answer specific questions about it. For large datasets, describe the schema and key statistics rather than pasting the raw data.
Grok can write code for Python (pandas, NumPy, scikit-learn), R, SQL (most dialects), Excel formulas, and can describe approaches for Tableau, Looker, and other BI tools. It is strongest on widely-used tools and frameworks.
AI Prompts for Gemini for Data Analysis
Gemini connects to Google Sheets, BigQuery, and Looker Studio natively, making it one of the most practical AI tools for data work within the Google ecosystem.
See promptsAI Prompts for Claude for Data Analysis
Data analysts spend hours on the wrong things: cleaning messy data, writing boilerplate code, and translating findings into language that non-technical stakeholders understand.
See promptsAI Prompts for ChatGPT for Research
ChatGPT does not browse the internet in its base form, but it is still a powerful research tool for synthesizing what you already know, building frameworks for investigation, structuring literature reviews, and pressure-testing conclusions.
See prompts