The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Back to feedPost
Built a customer churn prediction system using Python, Pandas, NumPy, and scikit-learn. The project covers data preprocessing, exploratory analysis, model training, evaluation, and prediction. The trained model was integrated with FastAPI and deployed in Docker, creating a complete ML-to-API workflow that was built and tested locally.
The network for creativity
Join 1.25M professional creatives like you
Connect with clients, get discovered, and run your business 100% commission-free
Creatives on Contra have earned over $150M and we are just getting started
Related posts
Rosso Archive — Gallery Website
Rosso Archive is a website for a contemporary art gallery — a calm, editorial space built around a single idea: twenty-four works.
We kept the interface quiet so the images can speak. Monospaced captions, a soft grey palette and generous white space give the archive the feel of a printed catalogue, while small interactions make it feel alive online.
What's inside:
— Index list view with a live preview of the hovered work
— Grid view with a colour-on-hover state for the active piece
— Work detail page with specs, description and related works
— Seamless zoom-in transitions between artworks and screens
Have a project in mind? Let's talk.
Great work, Dmytro!
AI Agent Landing Page | Figma, Framer & AI Workflow
Designed and prototyped an AI Agent landing page using Figma, animated in Framer, and accelerated with an AI-powered workflow.
Focused on a bold visual identity, immersive motion, modern typography, and a high-converting SaaS experience.
Ashar, the motion and the dark red palette work well together. One thing I see on a lot of AI agent sites is that visitors can't tell what the agent actually does in the first five seconds. A short live demo of one real workflow above the fold usually does more than another feature grid.
An AI-built app can work perfectly while any stranger can read its customers' data. Nothing on screen shows it.
Ask whoever built it: which tables hold user data, and what stops a logged-out stranger from reading each one? A good answer is a list. "It should be fine" means nobody has checked.
Andrés, this is the check most founders never run, because nothing breaks until someone looks. Asking for the list of tables and who can read each one is a test any owner can do without writing code. Row level access belongs on the launch checklist, not the cleanup list.
