Why I built a system for sewing studios

Every management software I knew talked about stock, invoices and sales orders. A made-to-measure sewing studio does not talk about that. It talks about fittings, alterations, hems, "the client is picking it up on Friday". The information exists — in a notebook, in the owner's head, in a WhatsApp thread nobody can find anymore.

It works. Until the day it doesn't.

What breaks

A small studio breaks in predictable places. A piece runs late because the deadline lived only in someone's memory. A commission turns into an argument because nobody wrote down who made which piece. A client calls three times to ask whether it is ready, and every call interrupts someone who is sewing. None of that is carelessness — it is the lack of a place where things stay.

I wanted to build that place. Not a shrunken ERP: a system that starts from the seamstress's day and has only what she needs.

What AteliePro does

Every order gets a QR code. The client scans it and sees the status without calling; the seamstress scans it and opens the spec sheet, with measurements and photos, on the spot. Clients have a history: measurements, past orders, what was agreed. The team gets its commission calculated when the order is paid, with no spreadsheet at the end of the month. Finances show income, expenses and profit without exporting anything. The "it's ready" and "you can pick it up" notices go out by WhatsApp with one tap. And there is an Android app, because a studio is rarely sitting in front of a computer.

How it is built, for those who like to know

AteliePro is built in Laravel — the first language I truly learned and, to this day, the one that makes me fastest. PostgreSQL, real-time updates, one API consumed the same way by the dashboard and the Android app. Payment by Pix or card. Each studio's data is isolated from the others by construction, not by convention. And there are automated tests covering every flow that touches money or somebody's order.

I also decided to host as little as possible with third parties: the server is mine, the monitoring is mine, the usage statistics are mine and use no cookies. Not out of ideology — because it is the business of someone who trusted me, and I want to know exactly where it is.

Why now

Because it is already running. This post is the first public announcement of AteliePro as a product of my own. If you have a studio, or know someone who does, the door is open.

If you are a developer and want to talk about what it was like to build this — the multi-tenancy, the app, the decision to swap an international payment gateway for a Brazilian one halfway through — the next posts will be about that.