Custom systems
The spreadsheet stopped being the system.
Five people editing the same file, nobody sure which copy is current, and hours every month spent on something that should run by itself.
- Closed timeline in the proposal, before you decide
- Fixed price per stage
- Yours, in your account, documented
What this usually looks like.
If you recognise two of these three, this is the page you want.
- 01
The same customer is loaded twice, spelled two different ways, and nobody knows which record is the good one.
- 02
Closing the month means chasing numbers across WhatsApp, email and three spreadsheets.
- 03
Only one person knows how the process really works, and when they take a week off everything stops.
What is included.
- A walkthrough of your real workflow, before anything is proposed
- The system built for how your company works, not the other way round
- A CRM inside the system: customers, follow-up and collections in one place
- Migration of the data you already have
- Automations between the tools you already use
- WhatsApp bots that answer and hand over to a person when needed
- AI agents connected to your own data, not to the internet
- Training for the team that will use it
- Which task to automate first, worked out with a simple sum
- AI search over your own documents
- Dashboards and reports that build themselves
- Billing and subscriptions that run on their own
What you keep.
The system runs in your account, with infrastructure as code and written documentation. If tomorrow you work with someone else, they read the repository and carry on. Nothing is held hostage.
A system already in use.
No numbers here yet — only work you can open and check for yourself.
How we would work.
Four steps, always in this order.
Diagnosis
Five questions about how the work really runs today, before anything is proposed.
Proposal
The process written down: who does what and in what order, on paper and signed off by you.
Development
Something working every two weeks, not six months in the dark.
Handover and support
It ends up in your own account, documented, with the infrastructure as code.
After it ships.
- Monthly retainer with hours included
- Changes and new features without opening a project every time
- Someone watching the errors before a customer reports them
Frequently asked.
How long does it take?
It depends on which process we automate. After the free 45-minute walkthrough you get a closed timeline in writing, before you decide anything. Then something usable ships every two weeks — not six months in the dark.
How much does it cost and how is it paid?
A fixed price per stage, agreed before the stage starts. You always know what the next payment is and what it buys. No open-ended hourly billing.
Is it mine?
Yes. It runs in your cloud account, under your billing, with the infrastructure written as code and the repository in your hands. There is no licence to keep paying me for.
Do you work with companies outside Rosario?
Yes. I am based in Rosario and work remotely with companies across Argentina. The walkthrough, the development and the handover all happen remotely.
Let's start.
Tell me in two lines what you are dealing with. The first call is 45 minutes, free: we work out how we would do it and what it would cost.