project file / mar–sep 2026
Churnary
A retention workspace that explains which regular customers may be drifting away and drafts a win-back for a business owner to review.
- my role
- Co-founder and engineer, with the Churnary team
- status
- Early access
- field
- Startup / customer retention
- tools
- Python · FastAPI · React · TypeScript · PostgreSQL · Square / Stripe
01 / the problem
Why this exists
Small businesses often notice a missing regular too late. Churnary turns payment and visit history into a prioritized, explainable list rather than another dashboard that asks the owner to do all the interpretation.
02 / the build
What I worked on
Built retention operations around Square, Stripe, and CSV histories, including customer timelines, risk reasons, and approval-gated outreach workflows.
Worked on the dashboard, pricing research with source evidence, acquisition flow, and product analytics as the team moved from a hackathon idea toward early users.
Helped shape the product around a simple question: who is drifting, why, and what can the owner do today?
03 / engineering notes
Choices that mattered
- Risk scores expose their reasons, including changes in visit rhythm or spend, instead of asking users to trust a number alone.
- Campaigns are drafts first. Customer-facing sends require a deliberate approval path.
04 / reflection
What I took away
Working on a product for busy owners made clarity a technical requirement. A sophisticated pipeline is only useful if its next action can be understood and checked quickly.
05 / public links