Skip to content

Software that works three months later.

We build websites, internal systems, and integrations for businesses in Nicaragua and remote clients worldwide — written to be maintained, handed over right, and built for the long run.

Software development  ·  Managua, Nicaragua  ·  Remote worldwide

Work

Camelias inventory dashboard

Camelias — Inventory for clothing stores

The situation
Small clothing retailers track stock across notebooks, phone photos, and spreadsheets. There's no easy way to see what an item cost versus what it sells for — so margins stay invisible, and price changes get lost.
What we built
An inventory system built specifically for clothing stores: catalog with product photos, sales records, cost tracking, full price change history, and financial reports — all in one place. Local stores are using it today.
The outcome
Owners see their margins at a glance and know exactly what their inventory is worth at any moment. Price changes are recorded automatically — there's always a clear history of what changed and when.

camelias.shop →

Flor de Luna — Online store migration and maintenance

  • 90%faster page loads
  • 0minutes offline during the migration
  • Todaywe still maintain it
The situation
A lingerie store in Mexico that sells online every day. The site was slow, hosting cost more than it was worth, and the previous provider wasn't maintaining it — plugins kept falling behind.
What we did
We moved the store to its own server and updated every plugin, planning each step so orders kept coming in the whole time.
The outcome
The store loads 90% faster, costs less to run, and the business never noticed the switch — not a single moment offline. We still maintain it today.

flordelunaluxury.com →

Services

Websites and catalogs
For businesses that sell through WhatsApp and Facebook today
The customer picks their vehicle's make, model and year, and sees only the sizes that fit — with the quote already written, ready to send to the nearest branch.
Custom software
What lives in a spreadsheet today, and nobody knows which copy is the right one
The price gets changed in one place and stays changed everywhere, instead of in four files someone has to remember.
Integrations
To stop copying data by hand from one system to another
An order comes in through the site and goes out invoiced, without anyone typing the same data for the third time.
Project rescues
Inherited projects nobody wants to touch
First understand what's there and write it down. Then move pieces — never the other way around, which is how sites that already worked get broken.

A website can be dressed up. A product can't.

On delivery day everything looks fine. The truth shows up later: in whoever inherits the code and has to make sense of it without calling anyone, in the person opening the site on a phone with a capped data plan, on the Tuesday afternoon when the business needs to change something and can't wait for someone to get back from vacation.

That's why we work the other way around. When something seems worth doing, we build it first and show it running. A proposal gets debated; a thing that works gets tried — on the phone of whoever makes the call, in a minute.

No templates that break on the next update. No licenses that bill every month. No code only its author understands. We say what we don't know.

How we work

  1. Understand the problem first

    Before writing a line of code, we map what exists and what causes friction. We ask until the real constraint is clear — not just what you asked for, but why.

  2. Build before proposing

    When something is worth doing, we build a working version and show it running. A working thing gets tried; a proposal gets debated. The difference matters.

  3. Review on the actual device

    We review on the phone of whoever will use it, not on a designer's screen. Real feedback from real use shapes what we adjust before handoff.

  4. Hand over clean

    Documented code, a handoff session, and no dependency on us to make changes. If your team can maintain it without calling us, that's a good sign.

  5. Available after handoff

    We're reachable for maintenance, updates, and new features — but you're never locked in. The software is yours to run, change, or hand to someone else.

Who's behind this

Portrait of Pablo Gutiérrez

Pablo Gutiérrez

Madero Labs is a small studio led by Pablo Gutiérrez, based in Managua, Nicaragua. I lead every project directly — with a team of developers available when the scope calls for more hands.

When you describe the problem, you're talking to the person responsible for it. When you have a question three months after launch, it's the same person who answers.

We work in Spanish and English, and serve clients in Nicaragua and remotely worldwide.

LinkedIn profile →

Tell me what you need to solve.

It doesn't have to be figured out yet. Just tell me which part of your operation is costing you time, and we'll start there.

Studio
Madero Labs
Location
Managua, Nicaragua
Run by
Email
hola@maderolabs.com

© 2026 Madero Labs