Custom internal systems
We design and build the system around your processes: sales, billing, inventory, manufacturing, logistics, administration and the specific modules your operation needs.
Software studio · Argentina (UTC-3)
Custom software for businesses that have outgrown their systems.
We design and build internal systems, back-office platforms and bespoke SaaS around how your business actually works — not the other way around. We won't show you a demo: we'll show you a real, complex system running in production.
- business modules & processes
- 100+
- isolated data per company
- Multi-tenant
- ERP in production
- Since 2024
We work with companies that manufacture, sell and distribute — and with clinics that manage appointments, practitioners and patients.
The problem
Off-the-shelf software makes your business fit the tool
Generic software is designed for an average company. Yours isn't one.
It has its own way of quoting, collecting, manufacturing, purchasing and delivering. When the software ignores those processes, you end up bending your operation to fit the tool — or keeping spreadsheets, manual steps and parallel controls alive.
A custom system inverts the equation: the software adapts to your operation. Processes get centralized, data stays consistent, and the information is there when you actually need it.
Services
What we do
Four ways of working with us, all under the same principle: software that ends up running, documented, and under your control.
Modernizing existing systems
That old system everything depends on but nobody dares to touch. We map it, document it and modernize it in stages, without stopping the operation.
Integrations
We connect the systems you already use: invoicing, payment providers, e-commerce, APIs and the spreadsheets that still require manual entry.
Evolution & support
Development doesn't end at deploy. We stay with the operation: resolving incidents, monitoring the system and evolving the modules the business needs next.
Real-world case
A real system, not a list of technologies
The system that introduces us best is YSY Empresa: a multi-tenant ERP built end-to-end for Ripser — a manufacturer of commercial fixtures and refrigeration units — in production since 2024.
Sales and quotes, customers, receivables, cash, manufacturing with traceability, multi-warehouse logistics and payroll: the whole operation on a single platform.
Over a hundred business modules, multiple companies and warehouses, audited money flows and automated tests on critical processes.
Also built by us
YSY Agenda — online appointments
An appointment booking platform built end-to-end, in use at a multi-specialty medical clinic. Patients book against the real availability of each specialty, each practitioner manages their own schedule, and the clinic runs patients, practitioners and reports from a single panel.
- React
- Spring Boot
- Docker
Testimonials
What the people who use it every day say
Appointments used to mean phone calls, back-and-forth and empty slots. Now my patients book on their own against my real schedule, and I manage it from wherever I am. Double-bookings are a thing of the past.
Dr. Antonella BottaroPediatrician · uses YSY AgendaWe went from spreadsheets and parallel controls to running the whole operation — sales, factory, deliveries and payroll — through a single system. And when we need something new, it gets built around how we work, not the other way around.
Sergio RipollCEO of Ripser · uses YSY EmpresaI load my availability once and the system does the rest: patients only see the slots I actually have open. Less time coordinating, more time seeing patients.
Sacha CoronelPsychologist · uses YSY AgendaMethod
How we work — and where the trust comes from
Hiring a small studio has one advantage — you talk directly to whoever builds — and one fair question: what if they're gone tomorrow? The answer isn't a promise. It's how we work:
- You own the code.
- Everything we build for your company lives in repositories you own. No black boxes, no artificial vendor lock-in. The system, its documentation and the knowledge needed to maintain it stay under your control.
- Short, reversible releases.
- The system grows in stages. Each release reaches production in a controlled way and can be rolled back if something doesn't work as expected.
- Documented from day one.
- Process maps, technical decisions and operating manuals are written down. The project's continuity doesn't depend on one person.
- A direct line.
- From discovery to support, you talk directly to the person who designs and builds the system. No commercial layers, no middlemen, no tickets bouncing between teams.
The process, in 4 steps
- DiscoveryWe map your real operation: who does what, with which tool, and where it gets stuck.
- Solution designWe define scope, priorities and a first useful release. We don't quote "the whole system" before understanding how your operation works.
- Staged developmentEach stage ships to production and gets used; what we learn feeds the next one.
- Operation and evolutionSupport, monitoring and continuous improvement.
Stack
What we build with
We choose mature, boring-in-the-best-sense tools: proven, maintainable technology with professionals available in the market.
- Java 21
- Spring Boot
- React
- TypeScript
- MariaDB / MySQL
- Docker
- GitHub Actions
FAQ
What everyone asks before writing
The short, honest answers. For everything else there is the first conversation, which is free.
How much does a custom system cost?
There is no price list because no two operations are alike: cost depends on scope. What is fixed is the method: we map your operation, define a first useful stage and quote it as a fixed price before writing a line of code. You know what each stage costs before approving it — and the fair comparison isn't against spending nothing, it's against years of licenses for software that never quite fits, plus the hours your team loses to spreadsheets and parallel controls.
How long until we can actually use it?
We don't deliver "the whole system" at the end: the first useful stage reaches production in weeks, not years, and from then on the system is in daily use while it keeps growing. Each following stage builds on what the real operation teaches.
What happens to our current data, spreadsheets or legacy system?
It gets migrated. Part of the initial mapping is understanding where your data lives today — spreadsheets, a previous system, paper — and planning the import and cleanup. If needed, the new system runs alongside the old one until cut-over, without stopping the operation.
How do you bill?
Per stage: each one is quoted and approved before development starts, and invoiced against software delivered and working. After launch, evolution and support are agreed as a monthly service sized to the pace the business needs.
What if you disappear tomorrow?
The code, the documentation and the repositories are your property from day one. Any competent team can pick the project up and continue it: no black boxes, no lock-in licenses, no artificial dependency on the vendor.
Do you work with companies outside Argentina?
Yes — we work remotely, in UTC-3, with working hours that overlap both US and European time zones. Initial mapping is done over video calls, in English or Spanish.
Contact
Let's talk about your operation
Tell us what problem you have — even if you don't yet know whether the answer is a new system, fixing the current one, or connecting what already exists. We work remotely from Argentina (UTC-3), with working hours that overlap both US and European time zones. The first conversation is free and without obligation.
ysysoftwareadmin@gmail.com
You talk directly to Mariano Van Staden, founder of YSY Software — the same person who designs and builds the systems.
Team
Work with us
We don't always have open positions, but we're always interested in meeting developers who enjoy building real business systems: the kind that touch money, stock and data that cannot be lost. If you like how we work, we'd like to meet you.