We build the software your operation needs when no off-the-shelf product fits.

You see a working demo every two weeks, and the code is in your name from day one.

Custom software

A system built around how your team already works.

When the spreadsheet or the generic tool stops working, we build the system that fits how your company actually runs.

A Uruguayan distributor tracks stock, prints sale receipts and takes WhatsApp orders from a system we built. See the case .

Who it's for
Teams running on spreadsheets and WhatsApp, or on a system nobody understands anymore.
Who it's not for
If an existing SaaS covers 90% of it, we'll tell you.
Tell us which process you want to get off spreadsheets.

What we handle

  • Customer and supplier portals
  • Internal management and operations systems
  • Dashboards and real-time reporting
  • Modernizing legacy systems

Deliverables

  • Web application in production
  • Repository and cloud accounts in your name
  • Tests on the critical flows
  • Technical and user documentation

Typical stack

  • Next.js
  • React
  • NestJS
  • PostgreSQL
  • TypeORM
  • Redis
  • BullMQ
  • Docker
  • AWS

Management systems

Inventory, sales and customers in one system.

When stock lives in one spreadsheet, sales in another and orders in someone's WhatsApp, nobody knows which number is right. We build the management system that brings all of it together, with the steps and names your team already uses.

A Uruguayan distributor tracks stock, prints sale receipts and takes WhatsApp orders from a system we built. See the case . A benefits club manages members, benefits and workshops from its own admin panel. See the case .

Who it's for
Companies tracking stock, sales or customers in spreadsheets, or in a generic system that no longer fits how they work.
Who it's not for
If an existing management system covers what you need, we'll tell you.
Tell us what you track in spreadsheets today.

What we handle

  • Inventory with a history of every movement
  • Sales with receipts printed on the spot
  • Catalog and WhatsApp ordering
  • Customers, members and sales follow-up
  • Users, permissions and audit log
  • Reports to see how the business is doing

Deliverables

  • System in production, with users and permissions
  • Migration of the data that lives in spreadsheets today
  • Repository and cloud accounts in your name
  • User documentation for your team

Typical stack

  • Next.js
  • NestJS
  • PostgreSQL
  • React Native
  • Expo
  • Docker

SaaS products and MVPs

A first version that can start charging.

If you're launching a product, we cut scope to what it takes to start charging, on a base that can take more customers without a rewrite. A well-built MVP takes a month or less, depending on complexity.

Commit, our internal tool, went from first commit to the version we use every day in two weeks. See the case .

Who it's for
Founders with a validated problem and no tech team.
Who it's not for
If you haven't talked to customers yet, start there.
Tell us what you want to launch.

What we handle

  • MVP scope definition
  • Multi-tenant architecture and permissions
  • Subscriptions and payments with Mercado Pago
  • Onboarding and usage metrics

Deliverables

  • Product in production, ready to sell
  • Admin panel
  • Payments integration
  • Roadmap for the next versions

Typical stack

  • Next.js
  • Supabase
  • Tailwind CSS
  • shadcn/ui
  • Prisma
  • Mercado Pago
  • Resend
  • Vercel

AI automation

Repetitive work handled by a workflow you can audit.

We build n8n workflows that connect the tools you already use, like forms, WhatsApp, email, spreadsheets or your CRM, so your team stops copying data from one place to another. Where it helps, an AI step reads or sorts the information. Before the workflow acts, someone on your team reviews what it proposes.

Commit, our internal tool, uses Claude to find leads and draft proposals, and won't let one go out with a field missing. See the case . Gastito pulls the amount and category of an expense from a photo or a PDF. See the case .

Who it's for
Teams that handle the same documents or messages by hand every day.
Who it's not for
If the process isn't defined yet, we sort it out without AI first.
Tell us which task you want to automate.

What we handle

  • Document extraction and classification
  • Internal assistants over your own information
  • n8n workflows across forms, WhatsApp, email, spreadsheets and your CRM
  • Choosing the right model for each task and budget

Deliverables

  • Production workflows with monitoring, visible step by step in n8n
  • A review step where a person approves what the AI proposes before it runs
  • Usage cost tracking
  • Data in your own cloud account. We spell out what goes through the model provider, and can run a local model when it has to stay in-house.

Typical stack

  • Claude API
  • OpenAI
  • Gemini
  • Groq
  • Ollama
  • n8n
  • Python
  • NestJS
  • BullMQ

Integrations

Data moves between your systems without anyone copying it.

Copying data by hand between systems causes errors. Every integration we ship retries on its own and alerts you when something breaks.

We've maintained two production apps for a healthcare company since 2024.

Who it's for
Teams moving data by hand between two or more systems.
Tell us which systems you want connected.

What we handle

  • WhatsApp, Instagram and other messaging channels in one inbox
  • Payments and subscriptions with Mercado Pago
  • Data sync across your systems

Deliverables

  • Integration in production
  • Per-operation log and error dashboard
  • Automatic retries and failure alerts
  • Docs for every integration

Typical stack

  • NestJS
  • Socket.IO
  • Redis
  • BullMQ
  • Mercado Pago
  • WhatsApp
  • Meta
  • AWS

Platforms at scale

Your platform keeps up as your user base grows.

If your company or startup already has a product, and maybe a dev team, we come in to build what's missing or get the system ready for more load. We work inside your architecture: we move heavy work to queues and add monitoring so you can see what production is doing. We're a nearshore team in Montevideo, Uruguay. We work in English, one to two hours ahead of US Eastern time, so most of your day overlaps with ours. Most teams bring us in on Ongoing development, as an extension of their own team.

We've maintained two production apps for a healthcare company since 2024. We build NestJS backends with DDD on AWS.

Who it's for
Companies and startups with a product in production that needs to grow, or a dev team that needs more hands.
Who it's not for
If you're still validating the idea, start with an MVP. Getting ready for thousands of users before you have ten is money you won't recover.
Tell us how much load your system needs to handle.

What we handle

  • Architecture that can grow without a full rewrite
  • APIs and services that hold up under traffic spikes
  • Queues that move heavy work out of the user's request
  • Load balancing across instances
  • Monitoring, logs and alerts in production
  • Migrating legacy systems piece by piece, without stopping operations
  • Working inside your team, in your repos and your workflow

Deliverables

  • Written review of your current architecture and its bottlenecks
  • Staged plan of changes, prioritized with your team
  • Changes shipped to production with code review and tests
  • Dashboards and alerts for load and errors
  • Architecture docs for your team

Typical stack

  • AWS
  • Docker
  • NestJS
  • PostgreSQL

Three ways to work together

  1. Fixed-scope project

    After a 30-minute call, you get the scope and a fixed price in writing, and we don't start until you approve the quote. If part of the work can't be estimated without a closer look, we propose a short first phase, priced on its own. The proposal is free.

    MVPs, portals, one-off integrations

  2. Ongoing development

    One or both of us work on your product as part of your team, with an agreed number of hours per month. Every two weeks we review priorities with you.

    Live products that keep adding features

  3. Maintenance

    The people who built it keep maintaining it: monitoring, alerts and a set number of hours each month for improvements. If your system goes down in production, we're on it as soon as you let us know, even if we're in the middle of other work.

    Systems already in production