The people who scope itare the people who build it.

You work directly with two developers. Whoever scopes your project builds it, and is the one who responds if something breaks in production.

How we decide

  1. Something working every two weeks

    Once the build starts, you see a working demo in a real environment every two weeks. We go live with a small first version so your team can start using it early.

  2. Code someone else can read

    We write for whoever maintains it next, even if that's us. If another team takes over tomorrow, they'll find tests and up-to-date docs.

  3. Saying no early

    If something doesn't help your business or isn't worth what it costs, we'll suggest skipping it, and we'll say so before we start. That's cheaper than finding out later.

  4. Everything in your name

    The repository, cloud accounts, domains and data are yours from day one. If we stop working together, you keep all of it and don't need us to run it.

Who you'll work with

We're two partners in Montevideo.

  • Lucas

    Co-founder · Product and UI

    Designs and builds the screens, and the backend too. Since 2024 he's maintained two production apps for a healthcare company.

    ex Moove It (Qubika) · ex Mayeutic

    LinkedIn ↗
  • Partner

    Co-founder · Backend and infrastructure

    Takes care of what you don't see: databases, servers, and keeping the system up as it grows. Right now he's leading the migration and scaling of a platform in production.

Montevideo, close to your time zone.

We're in Montevideo, Uruguay, one or two hours ahead of the US East Coast depending on the time of year. We work remotely, in English, and invoice in USD.

Talk to the people who'll build it.