Session 26: Capstone Project Presentations
Session Objectives
- Present a complete insurance analytics project integrating multiple tools, datasets, and concepts from the course
- Defend your methodology, tool selection, and business recommendations in a Q&A session
- Demonstrate the ability to translate data analysis into actionable business insights
- Receive constructive feedback from peers and faculty to improve your analytical and presentation skills
- Connect the course concepts to career pathways in insurance analytics, InsurTech, risk management, and consulting
1. Capstone Project Overview & Requirements
The capstone project is the culminating assessment of the Insurtech & Digital Risk Solutions course. It requires you to integrate the tools, techniques, and domain knowledge from all 25 preceding sessions into a comprehensive insurance analytics solution. The project is not just a technical exercise — it is a demonstration of your ability to think like an insurance analytics professional: identify a business problem, apply the right analytical approach, generate actionable insights, and communicate them effectively.
1.1 Project Options — Choose One
| # | Project Title | Primary Tools | Key Skills Tested | Best For |
|---|---|---|---|---|
| 1 | Insurance Claims Dashboard | Power BI or Looker Studio | Data visualisation, KPI definition, dashboard design, business storytelling | Students focusing on business intelligence and reporting |
| 2 | Fraud Detection System | Python, KNIME | ML classification, SMOTE, model evaluation, operations workflow | Students focusing on ML and fraud analytics |
| 3 | Insurance Chatbot | ChatGPT / LLM | Prompt engineering, system prompt design, escalation logic, use case evaluation | Students focusing on generative AI and customer experience |
| 4 | Customer Risk Scoring Model | Python (Scikit-learn, XGBoost) | Feature engineering, risk scoring, Random Forest, SHAP explainability | Students focusing on underwriting analytics |
| 5 | Claims Analytics Using Python | Python (Pandas, Matplotlib, Seaborn) | Data cleaning, EDA, time series, regression, predictive modelling | Students focusing on data science foundations |
| 6 | Parametric Insurance Product Design | Python (NumPy, Matplotlib), Excel | Parametric modelling, Monte Carlo simulation, basis risk analysis, product design | Students focusing on climate risk and product innovation |
| 7 | Customer Churn Prediction | Python (Scikit-learn, XGBoost), KNIME | Churn modelling, feature engineering, retention strategy design, ROI analysis | Students focusing on customer analytics and marketing |
| 8 | Digital Risk Assessment Framework | Power BI, Excel, ChatGPT | Risk assessment, compliance monitoring, regulatory analysis, governance framework design | Students focusing on risk management and compliance |
1.2 Deliverables
Every project, regardless of option, requires three deliverables:
1. Project Report (PDF, maximum 10 pages excluding appendices — structured as: Problem Statement, Data & Methodology, Analysis, Findings, Recommendations, Limitations). The report must document all assumptions, data sources, analytical steps, and business conclusions — so that another analyst could reproduce your work.
2. Presentation Slides (maximum 8 slides — structured as: Problem, Data, Method, Results, Insights, Recommendations, Limitations, Appendix). Slides are for the 10-minute presentation and must focus on business insights, not technical detail — the technical detail goes in the report.
3. Live Demonstration (5 minutes within the 10+5 format — showing your working solution: dashboard interacting with slicers, Python code running end-to-end, KNIME workflow executing, or chatbot responding to test queries). The demo is not optional — it is the most important evidence that your solution works.
2. Project Option 1 — Insurance Claims Dashboard
Summary: Build an interactive analytics dashboard that provides comprehensive visibility into claims patterns, settlement efficiency, fraud indicators, and operational performance. The dashboard should enable a claims manager to: identify trends, spot anomalies, track KPIs, and drill down into specific claim segments.
Technical requirements:
- Use the cleaned insurance dataset (insurance_cleaned.csv from Session 05)
- Dashboard tool: Power BI Desktop or Looker Studio
- Minimum: 3 pages, 15+ visuals, 5+ slicers/filters
- Must include: KPI cards with conditional formatting, trend charts with annotations, category comparisons, a detail table with drill-through, and an exception/alert section
- DAX measures: minimum 8 custom measures including time-intelligence (MoM, YoY comparisons)
- Design: follow the principles from Session 23 — "one page, one question," executive summary first, annotations on trends, consistent colour coding
Evaluation emphasis: Data preparation (20%), Visualisation design (25%), KPI selection and analysis (25%), Business interpretation (20%), Presentation professionalism (10%).
3. Project Option 2 — Fraud Detection System
Summary: Build an ML-based fraud detection system that identifies suspicious claims before payment. The system should combine supervised and unsupervised techniques, provide explainable predictions, and include an operational workflow for investigators.
Technical requirements:
- Use the insurance_cleaned.csv dataset with fraud_flag as the target
- Tools: Python (Scikit-learn, XGBoost, Imbalanced-learn) + KNIME workflow (replicating the Python pipeline)
- Minimum 10 engineered fraud indicator features (use Session 15-16 frameworks)
- Train: Random Forest + XGBoost + Isolation Forest ensemble. Compare performance using PR-AUC (not ROC-AUC)
- Optimise decision threshold using cost-based analysis (fp_cost = ₹500, fn_cost = ₹75,000)
- SHAP explainability for at least 3 individual predictions
- KNIME workflow that replicates the scoring pipeline (from data input to scored output)
- Concusion matrix, decile lift chart, and precision-recall curves
Evaluation emphasis: Problem definition (15%), Technical implementation (30%), Insights and recommendations (25%), Visualisation (15%), Innovation and ethics (15%).
4. Project Options 3–8 — Summarised
Option 3: Insurance Chatbot
Scope: Design and test a GenAI-powered customer service chatbot for an insurance company. Write a system prompt with clear scope boundaries, escalation rules, and disclosure requirements. Test with 5 customer scenarios. Evaluate the bot's responses for accuracy, safety, and tone. Provide a critical assessment of where the bot works well and where it fails. Include: the system prompt, the 5 test scenarios with outputs, a limitations analysis, and a deployment recommendation (what use cases to launch, what to hold back).
Tools: ChatGPT, Claude, or any LLM platform. Python optional (for RAG implementation).
Option 4: Customer Risk Scoring Model
Scope: Build a risk scoring model (0–1000) for motor OR health insurance underwriting. Engineer at least 15 features including ratios and interactions (Session 12). Train a Random Forest model, perform hyperparameter tuning, and report feature importance. Map risk scores to premium recommendations (discount/standard/loading/decline). Evaluate calibration (does risk score 600 mean 60% claim probability?). Provide SHAP explanations for 3 individual predictions. Design a phased rollout approach (shadow → assisted → full STP).
Tools: Python (Scikit-learn, Pandas, SHAP).
Option 5: Claims Analytics Using Python
Scope: End-to-end claims data analysis from cleaning to visualisation to predictive modelling. Clean and merge Customer-Policy-Claims data (Session 05). Create 6+ publication-quality visualisations (Session 06 — trend, distribution, correlation, comparison, heatmap, pairplot). Build a simple severity prediction model (linear regression + XGBoost). Perform a claims seasonality analysis using time series decomposition (Session 21). Write a 500-word business report synthesising all findings.
Tools: Python (Pandas, Matplotlib, Seaborn, Scikit-learn, statsmodels).
Option 6: Parametric Insurance Product Design
Scope: Design a parametric insurance product for a climate risk of your choice (rainfall-index for drought, wind speed for cyclone, temperature for heatwave). Use Session 19's framework: define the index, trigger, exit, and payout function. Simulate 20+ years of historical payouts. Calculate pure premium and commercial premium (with 35% loading). Perform sensitivity analysis on the trigger level (50%–80%). Analyse basis risk with ±15% spatial variability. Write a product launch memo covering: target customer, distribution strategy, pricing, basis risk disclosure, and key risks.
Tools: Python (Pandas, NumPy, Matplotlib) + Excel for the risk matrix. Weather data from weather_data.csv.
Option 7: Customer Churn Prediction
Scope: Build a churn prediction model using policy, claims, and customer data (Session 22). Engineer at least 12 churn features. Train XGBoost with scale_pos_weight. Find the optimal decision threshold using cost-based analysis (retention offer cost = ₹200, CLV estimated from premium and retention data). Design a segmented retention strategy with at least 3 different interventions. Calculate the ROI of the retention programme and the break-even save rate. Build a KNIME workflow for weekly automated churn scoring.
Tools: Python (Scikit-learn, XGBoost) + KNIME.
Option 8: Digital Risk Assessment Framework
Scope: Build a comprehensive digital risk assessment framework for a mid-size Indian insurer. Include: (a) a cyber risk matrix (Session 17 — 8 threat types × 5 likelihood/impact levels), (b) a compliance monitoring dashboard (Session 24 — solvency, expense ratio, settlement ratio, rural business, grievance redressal), (c) an AI governance framework (Session 25 — governance structure, risk classification, development standards, monitoring), and (d) a DPDP Act compliance checklist. Integrate all components into a coherent "Digital Risk Report" that the CRO could present to the board.
Tools: Power BI (compliance dashboard), Excel (risk matrix), ChatGPT (governance framework draft).
5. Report & Presentation Guidelines
5.1 Report Structure
The project report (maximum 10 pages excluding appendices) must follow this structure:
| Section | Pages | Content |
|---|---|---|
| 1. Executive Summary | 0.5 | Problem statement, approach, key finding, and recommendation — in 300 words or less. A busy executive should understand the entire project from this section alone. |
| 2. Problem Definition | 1 | What business problem are you solving? Who is the stakeholder? Why does this problem matter (quantified impact)? What is the scope and what is explicitly out of scope? |
| 3. Data & Methodology | 2 | Data sources, key variables, data quality assessment (missing values, outliers, biases). Analytical approach — why this method and not another? What assumptions are you making? |
| 4. Analysis & Findings | 3 | The core of the report. Visuals + interpretation. Each finding must include: what the data says, why it matters (business impact), and what action it suggests. |
| 5. Recommendations | 1.5 | Specific, actionable recommendations with: implementation timeline, responsible owner, expected impact (quantified), and dependencies. Not "improve retention" but "launch auto-renewal feature by Q2 2027, targeting 5-point retention improvement in the digital channel." |
| 6. Limitations & Next Steps | 1 | What does your analysis not cover? What would you do with more data, more time, or more resources? How would you validate your results in a real-world setting? |
| 7. Appendix | As needed | Code listing (key sections, not full scripts), additional charts, data dictionary, references. The appendix is for technical supporting material — do not put content here that is essential for understanding the main argument. |
5.2 Presentation Format (10+5 Minutes)
Each presentation is strictly 10 minutes followed by 5 minutes of Q&A. The 10-minute presentation should be structured as follows:
PRESENTATION STRUCTURE (10 minutes — 8 slides maximum)
Slide 1: Problem Statement (60 seconds)
• What problem are you solving? Who cares? Why does it matter?
• One sentence: "Premium growth is strong but the combined ratio is deteriorating
because motor TP claims are growing faster than premium adjustments."
Slide 2: Data & Approach (60 seconds)
• What data did you use? What was your analytical approach?
• Not a data dictionary slide — a "how I tackled this" slide.
• "I analysed 10,000 policies with 15 engineered features using XGBoost..."
Slide 3: Key Finding #1 — The Main Insight (90 seconds)
• The most important finding — lead with this, not with technical details.
• Chart/graph + one-sentence interpretation + business impact.
Slide 4: Key Finding #2 (90 seconds)
• The second most important finding. Same format: data → insight → impact.
Slide 5: LIVE DEMO (3 minutes — non-negotiable)
• Show your solution working. Dashboard with slicers. Code running. KNIME workflow executing.
• Practice this — demo failures are the #1 cause of marks deduction.
Slide 6: Recommendations (60 seconds)
• What should the business DO? 3 recommendations maximum. Each with owner + timeline + impact.
Slide 7: Limitations & Next Steps (30 seconds)
• What are the caveats? What would you do next? Honest about limitations = marks bonus.
Slide 8: Q&A Prep (backup — only if needed)
• Anticipate questions and have a backup slide.
• Common questions: "How did you handle missing data?" "What was the biggest assumption?"
"How would you validate this in production?"
Q&A Period (5 minutes)
• Listen to the full question before answering.
• If you don't know, say "I don't know" and explain what you would do to find out.
• Faculty will ask: "What was the most difficult part of the analysis?"
"If you had one more month, what would you add?" "How would your approach change
if the dataset were 10× larger?"
6. Presentation Day — Logistics and Evaluation
6.1 Timetable
SESSION 26 — TYPICAL TIMETABLE (90 minutes for ~6 presentations)
┌─────────────────────────────────────────────────────────────────────┐
│ 09:00 09:05 │ Setup and briefing — Presentation order, │
│ │ timekeeping rules, evaluation criteria review │
│ 09:05 09:20 │ Presentation 1 (10+5) │
│ 09:20 09:35 │ Presentation 2 (10+5) │
│ 09:35 09:50 │ Presentation 3 (10+5) │
│ 09:50 10:00 │ Break / Transition │
│ 10:00 10:15 │ Presentation 4 (10+5) │
│ 10:15 10:30 │ Presentation 5 (10+5) │
│ 10:30 10:45 │ Presentation 6 (10+5) │
│ 10:45 10:55 │ Faculty synthesis — Key themes across all projects │
│ 10:55 11:00 │ Course wrap-up, career pathways, final Q&A │
└─────────────────────────────────────────────────────────────────────┘
6.2 Evaluation Rubric
| Criteria | Weight | Exceeds (80–100) | Meets (55–79) | Does Not Meet (< 55) |
|---|---|---|---|---|
| Problem Definition | 15% | Clear, specific, well-quantified problem statement. Stakeholder identified. Business impact estimated. | Problem stated but vague. Limited quantification of importance. | Problem unclear or missing. No stakeholder or impact identified. |
| Technical Implementation | 30% | Appropriate tool selection. Clean, well-documented code/workflow. Robust methodology with sensible assumptions and validation. | Adequate implementation. Some coding/documentation issues. Basic validation. | Incorrect or incomplete implementation. Code does not run. No validation. |
| Insights & Recommendations | 25% | Insightful findings backed by data. Specific, actionable, quantified recommendations. Connected to course concepts. | Reasonable findings but lacking depth or specificity. Recommendations vague. | No meaningful insights. Recommendations generic or unconnected to analysis. |
| Visualisation & Communication | 15% | Clean, professional visuals. Clear narrative structure. Effective live demo. Appropriate charts for the data. | Acceptable visuals but some clarity issues. Basic narrative. Demo functional but rough. | Unclear, cluttered, or inappropriate visuals. No narrative flow. Demo failed or missing. |
| Innovation & Ethics | 15% | Creative approach. Acknowledges limitations and biases. Considers ethical implications. Shows original thinking. | Standard approach. Some awareness of limitations/ethics. | No original thinking. Ignores limitations and ethical considerations. |
7. Course Wrap-Up & Career Pathways
You have completed 26 sessions covering the full spectrum of insurance analytics — from insurance fundamentals and risk management (Sessions 1–4) through data analytics and visualisation (Sessions 5–7), InsurTech innovation (Sessions 8–10), artificial intelligence (Sessions 11–14), fraud analytics and cyber risk (Sessions 15–17), climate risk and parametric insurance (Sessions 18–20), advanced analytics and BI (Sessions 21–23), and governance, compliance, and ethics (Sessions 24–25). The capstone project (Session 26) is the culmination — a demonstration of your ability to integrate these skills into a real-world insurance analytics solution.
7.1 What You Have Learned — The Three Pillars
CILO-1 — Insurance Domain Knowledge: You can now analyse the insurance ecosystem, risk management frameworks, InsurTech business models, and the regulatory landscape with confidence. You understand: how insurers make money (the combined ratio, float, underwriting vs. investment income), why risk pooling works (the law of large numbers), and what makes insurance fundamentally different from other financial services (it is a social good, not just a product).
CILO-2 — Analytics Tools: You have hands-on proficiency with six industry-standard tools — Python (Pandas, NumPy, Matplotlib, Seaborn, Scikit-learn, XGBoost, statsmodels), Excel (P&L models, risk matrices, premium calculations), Power BI (DAX measures, 3-page dashboards, drill-through, KPI cards), KNIME (visual fraud and churn workflows), Looker Studio (executive dashboards, Google Sheets integration, scheduled PDF snapshots), and ChatGPT (prompt engineering, policy summarisation, insurance research, governance framework drafting).
CILO-3 — Solution Design: You can design and evaluate data-driven insurance solutions — from risk scoring models and fraud detection systems to parametric insurance products and compliance monitoring dashboards. You can bridge the gap between technical analytics and business decision-making. This is the most valuable skill in the insurance analytics job market.
7.2 Career Pathways
| Career Path | Typical Roles | Key Skills Required | Target Companies |
|---|---|---|---|
| Insurance Analytics | Data Analyst, BI Analyst, Actuarial Analyst, Pricing Analyst | Python, SQL, Power BI, statistical analysis, insurance domain knowledge | General insurers, life insurers, reinsurers, insurance brokers |
| InsurTech Product Management | Product Manager, Product Analyst, Growth Manager | Data analysis, customer research, product design, A/B testing, regulatory awareness | InsurTech startups (Acko, Digit, Plum, Riskcovry), InsurTech arms of traditional insurers |
| Risk Consulting | Risk Analyst, Risk Consultant, ERM Specialist | Risk assessment frameworks, Excel modelling, regulatory knowledge, communication skills | Consulting firms (McKinsey, BCG, Deloitte, EY, PwC, KPMG), insurance advisory firms |
| Actuarial Data Science | Data Scientist, Predictive Modeller, Pricing Actuary (data science track) | ML, Python, statistical modelling, actuarial science (pursuing or completed), domain knowledge | Insurers with actuarial teams, InsurTechs with actuarial functions, reinsurers |
| Compliance & AI Governance | Compliance Analyst, AI Governance Specialist, Data Protection Officer | Regulatory knowledge (IRDAI, DPDP Act, Solvency II), AI ethics, audit, risk assessment | Insurers, InsurTechs, consulting firms, regulatory bodies (IRDAI) |
7.3 Continuing Your Learning
- Certifications: AINS (Associate in General Insurance), CPCU (Chartered Property Casualty Underwriter), CFA (Chartered Financial Analyst — relevant for insurance investment), FRM (Financial Risk Manager), and insurance data science certifications from IITs and IIRM.
- Industry bodies: Insurance Institute of India (III), Institute of Actuaries of India (IAI), NASSCOM Centre of Excellence for InsurTech, and the Insurance Information Bureau (IIB) for industry data access.
- Reading: IRDAI Annual Report (published annually — the single best source for industry data and regulatory direction), NASSCOM InsurTech reports, Swiss Re sigma reports (global insurance trends), and the Insurance Journal and Asia Insurance Review for industry news.
- Networking: InsurTech conferences (InsurTech India Summit, Global InsurTech Summit), LinkedIn insurance analytics groups, and the Woxsen School of Business alumni network in insurance and financial services.
Eight Projects, One Course — The Journey
Insurance is a risk transfer and pooling mechanism — the law of large numbers makes it work, and the combined ratio measures whether it is profitable. Every analytics project should reference these foundations.
Data cleaning is 60–80% of insurance analytics work. The integrated dataset — 6 tables, 45K records — is the analytical foundation of the entire course. Without clean data, no model can be trusted.
InsurTech is not a separate industry — it is a technology-enabled transformation of the insurance value chain. The five business models (Aggregator, Digital Carrier, Enabler, Embedded, B2B SaaS) coexist and converge.
AI in insurance — from Random Forest underwriting to XGBoost fraud detection to GenAI chatbots — follows a consistent workflow. The business insight matters more than the algorithm. A simple model with clear insights beats a complex black box every time.
Insurance is a social good. Ethical AI, climate risk, fair pricing, and regulatory compliance are not constraints — they are the foundations of a sustainable, trustworthy industry. The best insurance analytics professionals are those who understand both the power and the responsibility of what they build.