ENES
[ CUSTOM SOFTWARE · LATAM ]

Custom software development for your operation

We build the system no off-the-shelf product solves: internal copilots, data pipelines and tools that connect to what you already run. Shipping every two weeks, with code that stays yours.

A 45-minute technical call, at no cost, with the person who will build it.

Need to connect AI to the tools you already have? See AI integration

Technical call
45 min, no cost
First delivery
Every 2 weeks
Ownership
The code is yours
[ THE PROBLEM ]

When off-the-shelf software stops being enough

  1. The critical process lives in a spreadsheet

    It works because one person knows it by heart. When they go on holiday the process stops and nobody knows which formula broke what.

  2. You bought a tool and use 30% of it

    The rest does not match how you work, so your team patches around it with Excel exports and WhatsApp messages between departments.

  3. The quotes you receive are not comparable

    One talks about sprints, another about modules, and none says what you will be able to use in month one. Signing on that is a bet.

Systems where AI is part of the design

·01

Internal copilots for your operation

Tools your team uses daily that understand the business context. In logistics we built one that resolves status queries and exceptions without going through the coordinator.

·02

Data and classification pipelines

Processing that runs on its own and flags what needs a human eye. One of our projects classifies suspicious transactions and prioritises the review queue.

·03

Decisions with mandatory human verification

When a mistake is expensive, the system proposes and a person approves. That is how the patient triage we built works: no clinical decision leaves without review.

·04

Integrations with what you already run

ERP, electronic invoicing, banks, payment gateways and internal APIs. Integrations are quoted separately from the build so you can see what each one weighs.

·05

Tooling for technical teams

Internal automation of the development cycle, like the interface documentation generator that runs from source code in one of our projects.

The rules of the project, in writing

·01

Delivery and control

  • A working delivery every 2 weeks, deployed and usable rather than a demo
  • MVP scope closed in writing before any code is written
  • Repository in your name from the first commit
  • Direct WhatsApp access to whoever is building
  • A weekly 30-minute call covering what shipped and what comes next
·02

What you keep when we finish

  • Documented code and tests over the critical business logic
  • Infrastructure in your own cloud account, in your name
  • Deployment and operations manual for your team or the next supplier
  • A recorded technical handover, with a follow-up questions session
  • One month of stabilisation support included after launch

Out of scope: third-party licences, cloud infrastructure costs, migrating historical data older than two years, and ongoing operations support. Each is quoted separately and we tell you what it weighs before you sign.

[ IN THE PORTFOLIO ]

Real projects, not a list of capabilities

02
LLM products in production: Yasper and Ariel
05
Named projects with screenshots in the portfolio
12+
Years building software

Both LLM products have a name, a link and screenshots in the portfolio on this site. Yasper is a booking agent that quotes, schedules and holds the deposit inside a chat, on Python, AWS, PostgreSQL and N8N. For Ariel, a legal assistant for Colombian law, we built the initial core and the LLM that answers with verifiable sources, on Python, Azure and PostgreSQL. Each case says which part we built ourselves.

[ THE PROCESS ]

From the technical call to handover

  1. Technical call

    45 min

    No cost, with the person who will build it. We go through the process, the systems we have to touch and where the real risk sits.

  2. Scope document and estimate

    5-7 days

    What is in the MVP, what waits, what it integrates with, and what each integration weighs on its own.

  3. Build in increments

    From 6 weeks

    Every two weeks something is deployed that you can use. If scope changes, it is requoted before we build.

  4. Handover and stabilisation

    1 month

    Documentation, a recorded handover session and a month of support for whatever real use surfaces.

[ QUESTIONS ]

What a technical team asks first

  • It depends on the scope of the first version and, above all, on what it has to integrate with. Connecting to a tax authority, a bank or an existing ERP is what moves the number most, so we quote those integrations separately and you decide which ones go in now and which ones wait. The price comes out of the 45-minute technical call, in writing and with a date.

[ NEXT STEP ]

The system you needdoes not exist yet.Let's build it.

Tell us which process you want to solve and how you handle it today. We come back with a scope document and an estimate.

We reply on WhatsApp within 24 hours.

  • A working delivery every two weeks
  • Repository and infrastructure in your name
  • One month of stabilisation included