git404hub

what is customer-churn-prediction fr?

awe-builds/customer-churn-prediction — explained in plain English

Analysis updated 2026-05-18

0Jupyter NotebookAudience · dataComplexity · 3/5Setup · moderate

tl;dr

A machine learning tool that predicts which telecom customers will cancel their service, deployed as a working API in a Docker container.

vibe map

mindmap
  root((repo))
    What it does
      Predicts telecom churn
      Deployed as API
      Runs in Docker
    Tech stack
      Python
      scikit-learn
      XGBoost
      FastAPI
    Use cases
      Churn risk scoring
      Model deployment demo
      SHAP explainability
    Audience
      Data scientists
      ML learners
      Beginners in deployment
    Key findings
      Fiber customers churn more
      Contracts protect against churn
      Simple model tied complex one

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Predict which telecom customers are at risk of canceling their subscription.

VIBE 2

Study a real example of choosing a simpler model over a more complex one.

VIBE 3

Learn how to deploy a trained machine learning model as a Docker-packaged API.

VIBE 4

See how SHAP explains individual predictions in a churn model.

what's the stack?

Pythonscikit-learnXGBoostSHAPpandasFastAPIDockerJupyter

how it stacks up fr

awe-builds/customer-churn-predictionakashsingh3031/python-librariesakshit-python-programmer/text-detection-using-neural-network
Stars00
LanguageJupyter NotebookJupyter NotebookJupyter Notebook
Last pushed2020-12-03
MaintenanceDormant
Setup difficultymoderateeasyeasy
Complexity3/51/52/5
Audiencedatavibe codervibe coder

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · moderate time til it works · 30min

Requires Docker Desktop, or a local Python environment with pinned dependencies to avoid version mismatch errors.

No license information is provided in the README.

in plain english

This project builds a complete machine learning system that predicts which telecom customers are likely to cancel their service. It goes from raw customer data all the way to a working API you can call over the internet, packaged in a Docker container so it runs the same way anywhere. The goal is not to chase the highest possible accuracy score. The dataset is imbalanced, with about 73 percent of customers staying and only 27 percent leaving, so a lazy model could just guess "no churn" every time and still look accurate while being useless. Instead the project is built and judged around recall, meaning how many actual churners the model correctly catches, since missing a customer who is about to leave costs a business far more than a false alarm. The final chosen model is a Balanced Logistic Regression that catches 79 percent of customers who actually churn. A more complicated XGBoost model, tuned through 60 different configurations, only reached 81 percent recall, a tiny improvement, and it actually did worse on a combined accuracy measure called F1 score. The simpler model was picked instead because it is easier to understand, faster to run, and simpler to deploy. Using exploratory analysis and an explainability technique called SHAP, the project found that customers with fiber optic internet churn more often, even after accounting for their monthly bill, suggesting a real product problem rather than just a pricing one. Customers on two year contracts and long time customers were the least likely to leave, while brand new month to month customers were the highest risk. The steps covered are data cleaning, fixing a hidden bug where charges were stored as text instead of numbers, trying several models, explaining the results, and finally wrapping the trained model in a FastAPI web service and a Docker container. The tech stack includes Python, scikit-learn, XGBoost, pandas, and FastAPI. The author notes that deployment problems, not the modeling itself, were the hardest and most educational part of building this.

prompts (copy fr)

prompt 1
Explain how the Balanced Logistic Regression model in this repo decides if a customer will churn.
prompt 2
Show me how to run this customer churn API locally using Docker.
prompt 3
Walk me through the data cleaning steps used to fix the total charges bug in this project.
prompt 4
Help me adapt this churn prediction pipeline to a different customer dataset.
prompt 5
Summarize why recall was chosen over accuracy for this churn model.

Frequently asked questions

what is customer-churn-prediction fr?

A machine learning tool that predicts which telecom customers will cancel their service, deployed as a working API in a Docker container.

What language is customer-churn-prediction written in?

Mainly Jupyter Notebook. The stack also includes Python, scikit-learn, XGBoost.

What license does customer-churn-prediction use?

No license information is provided in the README.

How hard is customer-churn-prediction to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is customer-churn-prediction for?

Mainly data.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.