Software.to spec, with judgment
I'm Nico. I build custom software with AI agents as my team, and I bring judgment to it: what's worth doing, what isn't, what it costs and when it ships, all before we start. I answer every message myself.
Things I built that are still running.
Enterprise · Toto, Diamond Computación, Sucan
VTEX stores
I work on these stores every week. Catalogs with thousands of products, checkout, speed, and dates like Black Friday where there's no room for anything to break. It's the most demanding work I do, and the one that taught me the most.
- VTEX IO
- Store Framework
- High traffic
EasyTraining
I built it for personal trainers who wrote workouts in Excel and never knew whether the client actually trained. You build the workout, send it over WhatsApp, and see every set they log from the gym.
My own product
easytraining.com.ar
Ecommy
A store for people who sell through WhatsApp and Instagram and lose orders between chats. The customer builds the order, pays by bank transfer or Mercado Pago, and it lands in your dashboard, organized.
My own product
ecommy.app
Paltech Software
Management systems for businesses, on a foundation that already works: sales, inventory, orders and users are solved, and each business's rules go on top. So you don't pay for building from scratch.
Custom software
paltech-software.vercel.app
Your project
It doesn't exist yet. Tell me what you want to achieve and I'll tell you honestly whether it makes sense to build it, and how.
Tell me
This is how I work when you hire me.
I use AI every day, but I don't ask it to "build me a store." I treat it like a team: I write down what I want, set the rules, and review everything it does. This is what one of my projects looks like from the inside.
Specification
Before an agent writes a single line, I write what needs to be built, the project rules, and how we'll know it's right. That lives in the repository and every agent reads it.
In parallel
I split the work into small tasks. One agent builds components, another researches, another reviews, and each one works connected to the project's tools, not in a vacuum.
Gates
Nothing gets merged unless it passes strict typing, the build and the tests. A reviewer agent looks for bugs and security issues before anything reaches me.
My review
I read every change before it ships. If I don't understand why it's there, it doesn't go out. The responsibility is mine, not the model's.
What I solved on the big projects.
VTEX stores
Toto, Diamond Computación, Sucan
Catalogs with thousands of products, bank promotions that change every week, and dates like Black Friday when the store simply can't go down.
- Ongoing evolution of the Store Framework: custom components that don't break when the platform updates.
- Checkout and purchase flow tuned for mobile, where most of the traffic comes from.
- Performance on category and product pages with large catalogs.
- Campaigns, installment plans and bank promotions shipped on time, with no pricing errors.
Ecommy
my own product, in production
Businesses that sell through WhatsApp and Instagram and lose orders between chats, screenshots and unconfirmed transfers.
- The customer builds the order in the store and pays by bank transfer or Mercado Pago. The seller gets it recorded in their dashboard.
- Stock by size and color, delivery zones drawn on a map, discounts and bulk price updates.
- A dashboard that shows what needs doing today: payments to confirm, orders to prepare, shipments to send.
- Multi-store on a single codebase, with Argentina's legal requirements already built in.
EasyTraining
my own product, in production
Trainers who write workouts in Excel or PDF and then don't know whether the client trained, or with how much weight.
- A workout takes minutes to build and goes out over WhatsApp. The client opens it on their phone without installing anything.
- Every set, weight and rep logged from the gym, and it keeps working when the connection drops.
- A trainer dashboard with live activity: who trained, what they did and how long ago.
- A free plan and a Pro trial with no credit card, so you can try it with two clients before paying.
I thought this page through the same way. Before designing anything I decided what it had to get across: that you're talking to a person here, that this person has judgment, and that the work is actually running. Everything came from that. Black and white, because the work has to speak for itself. A single typeface, so the words carry the weight. Ballpoint blue reserved for what I write by hand: notes, check marks, corrections. Screenshots of the real stores instead of illustrations. And none of the decoration that repeats on every look-alike site. Every decision aims at the same thing: that by the time you finish reading you feel you already know me a little, and that writing to me is the most natural thing in the world.
Services
I build and , sell online with and , and bring people in with and .
Landing pages that bring in clients
A page with a single goal: getting people to contact you. I write the copy, design it, make it fast, and set up tracking so you know where every lead came from.
typical timeline: days, not weeks
With your identity at every step.
A website or a system isn't just about working. It's how it feels to use, what it says about you before you speak, and whether the person on the other side can tell there's someone behind it. I work on that from day one, in three things:
How your business talks
The words, the tone, what you say and what you don't. I write it with you, in your voice, not an agency's.
How it looks
Type, color, rhythm. No template: an identity you'd recognize as your own on any screen.
How it feels
The human side: clear answers, nothing hidden, a system that helps the person using it instead of fighting them.
Landing pages that bring in clients
A page with a single goal: getting people to contact you. I write the copy, design it, make it fast, and set up tracking so you know where every lead came from.
Custom software
Dashboards, management tools, automations, integrations with what you already use. I adapt to how your business works, not the other way around.
E-commerce
From a simple store to enterprise VTEX. Catalog, payments, shipping, and what happens after each sale, which is usually where things get complicated.
Brand and design
First I learn how your business works: how it talks, who it sells to, what makes it different. Then I design the site or the system so that shows on every screen, not just in the logo.
Meta Ads
Instagram and Facebook campaigns connected to the site I build you. I watch one number: what each sale costs you.
SEO
Structure, content and speed so Google finds you without paying for every click. Slower than ads, but it's yours.
Four steps and a date.
by here you know the price and the date
day 1
We talk
A call or a few messages. You tell me what you want to achieve and I tell you what I'd do, even if it's less than you planned to hire.
days 2 to 3
Proposal
You get scope, a fixed price and dates on one page. If something's missing, we talk about it before starting, not on the invoice.
weeks 1 to 4
We build
Every few days I send you a link with what's there. You try it, give feedback, I adjust, we keep going.
launch
We launch
We go live, measure, and I teach you to run it yourself.
after
Still here
day 1
We talk
A call or a few messages. You tell me what you want to achieve and I tell you what I'd do, even if it's less than you planned to hire.
days 2 to 3
Proposal
You get scope, a fixed price and dates on one page. If something's missing, we talk about it before starting, not on the invoice.
by here you know the price and the date
weeks 1 to 4
We build
Every few days I send you a link with what's there. You try it, give feedback, I adjust, we keep going.
launch
We launch
We go live, measure, and I teach you to run it yourself.
after
Still here
Write to me whenever you want. Monthly support or one-off work.
I've been through every stage of a project. Including the ones that go wrong.
I started out writing code for other people. Over the years I built my own products, made systems for companies, and today I work on high-traffic VTEX stores in Argentina and Uruguay.
That gave me something you don't learn in a course: knowing what's worth doing and what isn't. Often the best answer I give a client is "you don't need that yet".
I take on few projects at a time, on purpose. If I'm booked, I'll tell you and give you a date.
When you shouldn't hire me
You want a generic site that does the job, and that's it.
Better: a template, and that's fine. What I do is build something that carries your identity at every step, and that takes more conversation.
You're looking for the lowest price on the market.
Better: a template or a freelancer marketplace. You'll find someone cheaper, and sometimes that's enough.
Nobody on your side can answer questions during the project.
Better: wait until you have someone. Without that it won't go well with anyone, and I'd rather not charge you for something that won't work.
You want twenty people in the meeting.
Better: a large agency. With me you talk to one person, and it's the same person writing the code.
What people ask me before we start.
How much does it cost?
It depends on the scope, and you get a fixed number before we start. A landing page starts well below a custom system. I invoice from Argentina, and what we agree on is what you pay: if something new comes up, we talk about it first, it doesn't just show up on the invoice.
How long does it take?
A landing page can be ready in days. A store, in weeks. A large system I deliver in stages, and each stage is something you can already use. The dates go in the proposal and I meet them.
How do you use AI?
Like a team I direct, not a shortcut. I work with agents that plan, code, test and review in parallel, with the project rules written in the repository. I write the spec, make the architecture calls and read every change before it ships.
What if something happens to you mid-project?
Everything is documented in your repository, with instructions so any senior developer can pick it up. On the big projects, like the VTEX stores, I work with a trusted team that already knows the code.
Do I own the code?
Yes. Everything I build for you is yours: repository, access, domain, accounts. You won't be tied to me to keep going.
What happens after launch?
I'm still here. You can hire monthly support or write to me whenever you need something specific. Several clients have been with me for years, and not because of a contract.
For teams and recruiters
Looking for a full stack or AI engineer for your team?
Besides my own projects, I take remote contracts: full stack development, multi-agent workflow design, system prompts, evaluations and model integration into real products.
- Role
- Full stack developer · AI engineer · prompt engineer
- Engagement
- remote, contract
- Time zone
- GMT-3 (Argentina)
- I work with
- Next.js, Node, VTEX IO, agents and subagents, MCP, evals
- Available
- let's talk dates
Tell me what you want to achieve.
I answer myself, usually the same day. If what you need isn't a fit for me, I'll tell you and point you in the right direction anyway, no runaround.