Corta-ai
A barbershop runs its schedule, billing and analytics in one product. Its clients book by chat.
Problem
A barbershop needs one place for schedule, clients and billing. Its clients and barbers already live in a chat.
Decision
I proposed it, validated it with the team and the PO, and built it on the automation base I designed as a Jr. The chat is one more way in.
What I did
- Web admin
- API
- Roles
- Billing
- Analytics
StatusTwo barbershops are testing it.
- OTP login, roles per barbershop
- Schedule, services and cancellations
- Daily billing: Pix, trial, grace period, block
- Analytics by plan
- Chat: fixed flows, an LLM for the rest
- Self-hosted Evolution API, cheaper than Meta's
- Web admin
- Chat
- BFF
- NestJS API
- Schedule, billing, analytics
- Next.js
- NestJS
- PostgreSQL
- n8n
- Pix billing






