How we work

Six steps, the same on every project. We didn't design them to sell: they come from years of shipping software on teams where improvising wasn't an option. Today they sustain production systems that run real businesses every day, and they're exactly what will happen with your project, with what you receive at each step in writing.

PRINCIPLES · WHAT GUIDES US

Three principles that shape every engagement.

01

We work in the open, not in black boxes.

You have access to the repository, the project board, and the decision log from the first sprint. There's no curtain: there's a process you can open and review as it moves, without asking permission.

02

Big decisions happen early.

Technical architecture, brand direction, and scope are settled in writing before we build. Mid-project changes are rare because the heavy thinking happens upfront, and when they do occur, they're documented and approved before execution.

03

We leave you better than we found you.

At the end you keep the documentation, code, files, and training, all in your name. If you continue with us, it's by choice. If you continue with another team, they have everything they need to take over without calling us.

THE SIX STEPS · IN DETAIL

The six steps, in detail.

  1. DISCOVERY CALL
    30 MIN · FREE · NO COMMITMENT

    A conversation, not a sales presentation.

    You tell us what you need to solve and talk directly with whoever designs the strategy and whoever builds the system. If another option suits you better, we tell you on that same call.

    WHAT YOU GET
    • 30 minutes with the people who would make the decisions on your project
    • An honest read on whether we are the right option
    • If we proceed: a committed date for receiving the proposal
  2. DIAGNOSIS AND PROPOSAL
    5–7 BUSINESS DAYS

    The essentials in writing, so you can decide with confidence.

    You get a clear, signable proposal with objective, phases, timelines and investment. The detailed analysis comes as the first deliverable, with your full context.

    WHAT YOU GET
    • A proposal with objective, phases, estimated timelines and investment
    • A 30-minute meeting to review it line by line
  3. KICKOFF AND PLANNING
    1 WEEK

    Access to everything, clear calendar, your role defined.

    We turn the analysis into a plan with milestones and dates, and open the repository, the board and the decision log from day one.

    WHAT YOU GET
    • The detailed analysis with every deliverable named
    • A plan with milestones, dates and meetings on the calendar
    • Access with your own user to the repository, board and documentation
  4. EXECUTION BY SPRINTS OR PHASES
    VARIES BY SCOPE

    The actual work, visible as it happens.

    Demos on working software and a staging environment you can check anytime. Every scope change is approved in writing before it happens.

    WHAT YOU GET
    • A staging environment with your own URL from the first demo (software projects)
    • A demo or review at the close of each sprint
    • Responses within 3 business hours during the workday
  5. DELIVERY AND TRAINING
    1–2 WEEKS

    Full handoff. We don't disappear.

    We document why the system is built the way it is and train every role on your team, so you can run it with us or without us.

    WHAT YOU GET
    • Architecture documentation and, when applicable, a brand book with source files
    • Training (1–2 hours base) for every role
    • Repository, credentials and access transferred to your name
  6. POST-DELIVERY SUPPORT
    30 DAYS INCLUDED · OPTIONAL RETAINER

    How the backing works, concretely.

    For 30 days, bugs, minor adjustments and questions are handled at no cost, by the same person who built your system. After that, the retainer is optional.

    WHAT YOU GET
    • 30 days of support included, at no extra cost
    • Optional retainer with hours and scope in writing, or a clean exit
COMMITMENTS · HOW WE BACK THEM

Four commitments that back every engagement.

01

30 days of support included after delivery.

The real fear of hiring a project like this is paying and being left alone. That's why post-delivery support isn't an add-on: it's included in every project, in writing, in the proposal.

02

Written proposal before anything starts.

Objective, phase-level scope, timelines, and investment in writing and signed. The full detail is developed as the project's first deliverable, and changes are documented and approved before execution.

03

Documentation, code, and files are yours.

At delivery, everything is in your name: repository, source code, infrastructure, design files, brand book, training. No post-delivery dependency.

04

Under 3 business hours response time.

Direct communication with the people who decide and build, no intermediaries, in Spanish or English.

THE CONVERSATION

Does this sound like the way to work on your project?

If this is how you'd want your engagement run, book the discovery call. If you're not sure how it applies to your specific case, also book it. That's what the call is for. It's 30 minutes, and the person on the other side is the same one who would be on your project start to finish, including the 30 days after delivery.

Prefer WhatsApp?
+503 7109 5449

Hours: Mon–Fri,
9 AM – 6 PM GMT-6