Case study
GestorTaller: from a 3-day tool for one mechanic to a multi-tenant SaaS for auto repair shops
Independent repair shops in Argentina ran on paper and memory. We built a first version for a single mechanic in three days, then turned it into a SaaS with isolated data per shop, subscriptions and a free trial.
At a glance
- Our role
- Product, design, development and launch
- Type
- Own SaaS product
- Market
- Independent auto repair shops, Argentina
- First version
- 3 days
- Pricing
- ARS 28,000/month, 7-day free trial, no credit card
The problem
Most independent repair shops weren’t digitized at all. Owners couldn’t tell what had been done to a car four weeks earlier, how much they were spending on parts, or how much they were actually making.
The information existed, scattered across paper, WhatsApp and memory. None of it could be searched or added up.
The solution we designed
Version 1: one mechanic, three days. The first version was built for a single working mechanic. No login, no payments, nothing that didn’t serve the core: recording work orders and keeping each vehicle’s history. The goal was to prove the model on a real shop before building any infrastructure around it.
Version 2: a real SaaS. Once the core worked, we rebuilt it as a product any shop could sign up for:
- Multi-tenant architecture, with each shop’s data isolated from the rest.
- One data model for the whole shop: clients, their vehicles, work orders, spare parts and finances, all connected.
- Accounts and subscriptions, so a shop can sign up and pay without talking to anyone.
- A landing page with a demo video and a 7-day free trial with no credit card required.
Takeaway
Two lessons we now apply to every project. First, ship the smallest version that solves the problem for one real user before building anything around it: three days of work validated what months of planning wouldn’t have. Second, for non-technical users, onboarding is part of the product, not something to add after launch.