Why Data Analysts Should Learn Flask in 2026

# app.py — your first analyst Flask app
from flask import Flask, render_template, request
import pandas as pd

app = Flask(__name__)

def load_sales():
    df = pd.read_csv("data/sales.csv", parse_dates=["date"])
    return df

@app.route("/")
def index():
    df = load_sales()
    month = request.args.get("month")

    if month:
        df = df[df["date"].dt.strftime("%Y-%m") == month]

    total = round(df["revenue"].sum(), 2)
    rows = df.groupby("region")["revenue"].sum().reset_index()
    rows = rows.sort_values("revenue", ascending=False).to_dict("records")

    return render_template(
        "index.html",
        total=total,
        rows=rows,
        month=month or "all",
    )

@app.route("/api/summary")
def api_summary():
    df = load_sales()
    return {"rows": len(df), "revenue": float(df["revenue"].sum())}

if __name__ == "__main__":
    app.run(debug=True)

<!-- templates/index.html -->
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8" />
  <title>Sales Summary</title>
</head>
<body>
  <h1>Sales Summary — {{ month }}</h1>
  <p>Total revenue: <b>₹{{ total }}</b></p>

  <form method="get">
    <label>Month
      <input type="month" name="month" value="{{ month }}" />
    </label>
    <button type="submit">Filter</button>
  </form>

  <table border="1" cellpadding="6">
    <tr><th>Region</th><th>Revenue</th></tr>
    {% for r in rows %}
    <tr>
      <td>{{ r.region }}</td>
      <td>₹{{ r.revenue }}</td>
    </tr>
    {% endfor %}
  </table>
</body>
</html>

# automation.py — reports that run themselves
from apscheduler.schedulers.background import BackgroundScheduler
from flask import Flask
import pandas as pd
from datetime import datetime

app = Flask(__name__)
scheduler = BackgroundScheduler()

def build_daily_report():
    df = pd.read_csv("data/sales.csv", parse_dates=["date"])
    today = datetime.now().date()
    daily = df[df["date"].dt.date == today]

    summary = {
        "date": str(today),
        "orders": int(len(daily)),
        "revenue": round(float(daily["revenue"].sum()), 2),
    }

    pd.DataFrame([summary]).to_csv(
        f"reports/daily_{today}.csv", index=False
    )
    print("Report built:", summary)

@scheduler.scheduled_job("cron", hour=7, minute=0)
def morning_job():
    build_daily_report()

scheduler.start()

if __name__ == "__main__":
    app.run(debug=True, use_reloader=False)

# download.py — let users export what they see
from flask import send_file, request
import pandas as pd
import io

@app.route("/download")
def download():
    df = pd.read_csv("data/sales.csv", parse_dates=["date"])
    month = request.args.get("month")

    if month:
        df = df[df["date"].dt.strftime("%Y-%m") == month]

    buffer = io.BytesIO()
    df.to_csv(buffer, index=False)
    buffer.seek(0)

    return send_file(
        buffer,
        mimetype="text/csv",
        as_attachment=True,
        download_name=f"sales_{month or 'all'}.csv",
    )

# Rule: never rebuild the analysis twice.
# One function → page, API and download.

# Deploying an analyst Flask app

1. requirements.txt
--------------------
flask
pandas
gunicorn
apscheduler

2. Procfile (Render / Railway / Heroku)
---------------------------------------
web: gunicorn app:app

3. Start command locally to test prod mode
------------------------------------------
gunicorn app:app --bind 0.0.0.0:8000

4. Environment variables (never commit these)
---------------------------------------------
DATA_PATH=/var/data/sales.csv
SECRET_KEY=change-me
PORT=8000

5. Checklist before you share the link
--------------------------------------
□ Debug mode OFF
□ SECRET_KEY set via env
□ Data file reachable in production
□ /healthz route returns 200
□ One screenshot in the README

# Sales Dashboard — Flask

A one-page dashboard that replaces the weekly
Excel email. Live link: https://your-app.example.com

## Problem
The sales team waited until Monday for a
spreadsheet that was stale by Tuesday.

## What it does
- Shows revenue by region for the selected month
- Lets anyone download the filtered CSV
- Rebuilds a daily report at 7:00 AM automatically

## Stack
Python, Flask, Pandas, Jinja2, APScheduler,
Gunicorn, deployed on Render.

## One trade-off
I cache the grouped query in memory for 10 minutes
instead of adding Redis — the dataset is small and
it saved a dependency. At 1M+ rows I would move it
to Redis or a materialised table.

## Run locally
pip install -r requirements.txt
python app.py

6-Week Flask Project Planner:

WEEK 1
☐ Install Flask, run hello world
☐ Add @app.route for /
☐ Load data with Pandas

WEEK 2
☐ Create templates/ folder
☐ render_template with a dict
☐ Loop rows in HTML
☐ Add a filter form (GET)

WEEK 3
☐ Add APScheduler daily job
☐ Write report to reports/
☐ Add /download CSV route

WEEK 4
☐ Cache the heavy query
☐ Add /healthz
☐ Handle empty data gracefully

WEEK 5
☐ requirements.txt + Procfile
☐ Deploy to Render / Railway
☐ Test on mobile

WEEK 6
☐ Write README with screenshots
☐ Record a 2-min walkthrough
☐ Prepare one trade-off answer

Daily Log:

Date: _________
☐ 30 min reading Flask docs
☐ Built / changed: ______________
☐ Broke something? ______________
☐ Fixed it? ☐ yes ☐ no
☐ Committed to GitHub ☐ yes

Tomorrow's single task:
_______________________________

Rule: one meaningful change per day
beats a weekend rewrite.

Scope Guard — say NO to these in v1:

✗ User login and roles
✗ A database if a CSV works
✗ Real-time WebSockets
✗ A React frontend
✗ Kubernetes deployment
✗ Microservices
✗ Custom charts library you must learn

Allowed in v1:
✓ One page
✓ One filter
✓ One download button
✓ One scheduled job
✓ One deployment

Ship v1. Add v2 only after someone uses v1.