AI software agency
The hours you lose every week have a fix
I build custom systems that solve the manual work pulling you away from the business. Entering the same data twice, reconciling spreadsheets, answering the same questions. No per-seat licences, and the system ends up in your name.
- years building software
- 14+
- Systems large companies use today, built and maintained by me.
- What you keep
- The system
- No per-person licences, no lock-in, and no depending on me to keep using it.
- Where I work
- LATAM
- Buenos Aires. I work remotely with companies across Argentina and Latin America.
Where this starts
The most common problems in companies under 50 people
Each of these consumes hours every week and never appears in a cost report. If you recognise any of them, there is something concrete to fix.
The same data, typed in twice
From email to spreadsheet, from spreadsheet to your system. Every hop is minutes, and an error that shows up at month end.
Licences built for a different company
Charged per person per month. Forty features shipped, six actually used. You pay the scale of a company ten times your size.
Everything goes through one person
The one who knows where things are and how they were done. When they take leave, the company slows down.
Month-end close is a race
Reconcile, review, correct. It ends late at night with the spreadsheet open, and something is always missing.
You don't know where to start with AI
You hear the term every day and nobody explains what is useful to you, what it costs, or what to begin with.
Repetitive admin work consumes between 4 and 8 hours per person per week. That time is already paid for in salaries.
Services
What can be solved with custom software
Six services, each with a defined problem, a deliverable and an estimated timeline. If what you need is not here, I will say so.
Assessment and roadmap
Two weeks to learn what is worth fixing first in your company, and what is not.
2 to 3 weeksAssistants that answer from your documentation
You stop answering the same ten questions by hand every day.
4 to 8 weeksProcess automation
The programs you already use pass data to each other, with no copy and paste.
3 to 6 weeksInternal knowledge search
Find in seconds the fact only one person knows today.
4 to 8 weeksCustom product with AI
The system you need, with no per-person licences and everything in your name.
8 to 16 weeksAI evaluation and security
Know whether your AI answers well, and that it does not say what it shouldn't.
3 to 5 weeks
How I work
Four stages, each with its own deliverable
Before building anything you need to know which problem is being solved and what solving it is worth. That order avoids the most common waste: paying for something nobody ends up using.
Assessment
Two or three weeks looking at how your company works today, with real numbers. You leave with a list of what to fix first, and what to leave alone.
Definition
Before any building starts, I write down what will be done and how you will know it works. It is in writing and it is yours.
Build
You see something working every week, not a demo at the end. Every delivery checks itself before it reaches you.
Production
It ends up genuinely running, with alerts if something breaks and a manual of how it is built. All in your name.
The investment
What it costs and how long it takes to pay back
The price depends on scope. But the decision criterion is always the same: how many hours a week the process consumes today, and what that hour costs in your company. From there you get how many months of savings cover the investment.
Only what you use gets built
No modules that ship in the package and nobody opens. That is the price difference against an off-the-shelf product.
The system ends up in your name
No per-seat licences, no lock-in, and no depending on me to keep using it. Another team can pick it up.
The effort estimate is the deliverable
The assessment is a short piece of work with its own result. You get a list of processes ranked by return, and how many hours each one takes.
I do not publish prices because a figure without knowing your process means nothing. After the first call you receive a written quote with scope, timeline and a fixed price. If the return does not justify the investment, you will know before you sign.
Who's behind this
Who will build your system
I am Juan Mujica, a software engineer with 14 years of work in development and architecture, now focused on bringing AI solutions into production. Nidra is new and does not have a client portfolio yet. What you can verify is where each of those years was spent.
Track record
- FreelanceAI Engineer2025–Present
- EPAM Systems · BayerSenior Full Stack Software Engineer2019–2025
- GireFull Stack Developer2018–2019
- GrinboldFull Stack Developer2016–2018
Technologies
What I build your system with
Industry-standard tools, not in-house inventions only I know how to maintain. If you work with another provider tomorrow, they will recognise everything inside.
I build on these platforms. I am not a commercial partner and I am not certified by any of them: these are the tools I work with, nothing more.
Artificial intelligence
- OpenAI
- Anthropic
- Hugging Face
- LangChain
- n8n
Databases and messaging
- PostgreSQL
- MySQL
- MongoDB
- Redis
- Supabase
- Qdrant
- Elasticsearch
- Apache Kafka
- RabbitMQ
Cloud and infrastructure
- Amazon Web Services
- Google Cloud
- Docker
- Kubernetes
- Cloudflare
- Vercel
- Terraform
- GitHub
Development
- Python
- TypeScript
- Node.js
- FastAPI
- NestJS
- Spring
- React
- Angular
Which process is consuming the most hours?
Describe it in the form. In a 30-minute call you will know whether automating it is worth it. You will also know the scope and how long it takes to pay back.