Two WhatsApp channels, one per audience.
Alerts for the team and messages for students never mix.
Status: accepted
Your business,in order
I'm Lautaro Guebel, a Systems Engineering student at UTN (Argentina). I turn the manual tasks, spreadsheets and WhatsApp threads of your business into custom systems and automations.
What changes day to day
This is how an online sales academy worked before automating, and how it works now. If your business repeats the same steps after every sale, the change is the same. See the full case
Before
- After every payment, the owner sent the welcome email by hand.
- Platform access and the contract were set up by hand, one student at a time.
- Pending instalments lived in a spreadsheet.
- Reports meant pulling numbers together from several places.
After
Every new student, set up with nobody touching a thing. Illustrative screen.
- From the sale to a student ready to start, with no manual steps.
- Email, access and contract go out on their own, in order.
- If something fails, the system retries and alerts the operator.
- The owner only approves, from WhatsApp.
What happens after every sale
- Sale recorded
- Welcome email
- Platform access
- Contract to sign
- WhatsApp alert
If something fails: retry and alert the operator
A sample day of the automation system, with made-up data: a sale is recorded, the welcome email goes out, platform access is turned on, the contract is sent and signed, and instalment reminders go out without anyone sending them by hand.
Each step triggers the next. Nobody has to remember anything.
See the real workflow, inside
How I work, step by step
Every step leaves something concrete you can see before we move on. These are the academy's.
First, I listen.
I learn how you work today and where time gets lost.
How the work was done
- Welcome email
- By hand, after every payment
- Platform access
- By hand, one student at a time
- Contract
- By hand, chased personally
- Pending instalments
- In a spreadsheet
- Ads report
- By hand
Survey summarised for this page. Then, we map the problem.
I draw the process end to end and we write a shared glossary.
The process, end to end
- Onboarding
- The moment a student is ready to start.
- Operator
- The person who gets the alerts and approves.
Map and glossary simplified. Together, we decide in writing.
Every important decision is written down with its reason.
A real decision, summarised. Next, I build it and we test it.
Every part ships with tests that run on their own, and the server gets a health check.
Server health check
- Every service is running
- The automations are loaded
- Backups exist
- WhatsApp is connected
A few of the checks, in plain words. And we keep tuning it.
The system grows with the business, and every change is reviewed before it goes in.
Every change
- Proposed
- Reviewed
- Merged and on record
How each change gets into the system.
Sports club and padel academy
A smaller second case: a club with an adult school, a kids' programme, football and a barbecue area, running on informal records.
See the full case
Plan of the system
Roles
One system and six roles: everyone sees their own part.
Stock
Warns you when something is about to run out.
Cleaning
A checklist per shift, with who did it.
Grill
Bookings without overlaps, at most two a day.
Kids fees
Each month, who is up to date and who isn't.
The problem
- Informal records, scattered everywhere.
- The school's programmes got mixed up.
- Data leaked from one area to another.
What I built
- Works on phone and desktop.
- A change history that can't be erased.
How it ended
- Demo approved on 17/09/2026.
- Two changes requested in the demo, added the same day.
What your business can do on its own
You don't need to know anything about technology. Tell me how you work today and I'll turn it into a custom system that does the repetitive work for you.
Customers book on their own
Before:
Bookings over WhatsApp at all hoursThey book online and get a confirmation and a reminder before the appointment: fewer messages and fewer no-shows.
Stock that warns you before it runs out
Before:
Counting by hand and finding out too lateEvery item in and out is recorded on its own, and you get an alert when something is about to run out.
Payments that chase themselves
Before:
Chasing instalments with a spreadsheetPayment reminders go out on their own, and you see at a glance who has paid and who hasn't.
Every sale moves on without you
Before:
Emails, access and contracts by handAfter every sale the welcome email, the access and the contract to sign go out on their own, in order and with nothing forgotten.
Your numbers come to you
Before:
Building reports from scattered dataEvery week a summary of sales, payments or ads reaches your WhatsApp or inbox, without you putting it together.
One place, everyone with their part
Before:
Spreadsheets, notebooks and WhatsApp groupsOne system on your phone and computer: your team sees only their part, and every change is on record.
We start with whatever eats most of your time, and you see it working before we move on to the next thing.
Let's start with your case
I study Systems Engineering at UTN (Tucumán Regional Faculty) and build systems and automations for real clients. Tell me what your business does: I'll reply with questions to understand it and, if it's a fit, a written proposal.
Your first message, already written
Hi Lautaro. After every sale I repeat the same steps by hand (emails, access, spreadsheets). I'd like them to happen on their own. Can we talk?
- contacto@lautaroguebel.techI reply here
- Tucumán, ArgentinaWhere I study and work