What people ask before booking the review

It depends on the process being solved and how many phases it needs, so it is quoted after the review, per phase, with a closed price in writing. We do not publish prices because a number without scope misleads in both directions. On the call we compare against what the manual process already costs you: hours per person per week, credit sales never collected, inventory that never matches.

Per phase: 50 % to start and 50 % against the delivery, which you accept by seeing it work, not by a date. Each phase includes two minor changes and 30 days of defect fixes. Ownership of code, database and accounts passes to you against full payment. No per-user licenses, no hidden fees for extra modules.

The 20 minutes tell you whether it makes sense to continue. The full review is work: a long session with the decision-maker and the operator, a look at your real files, a map of the process as it works today, a prioritized list, and a phased proposal with a closed price. The document works with any vendor, and it is credited to the deposit if you start with riel.

Stated per phase, with a date, and kept. The real reference: the Distribuidora del Golfo ERP, 19 modules in six phases, took about six weeks and has been in production since August 2026. A bounded automation or a lead-capture site is measured in weeks, not months.

Client data and decisions, not code. That is why the review asks for them first and every phase needs someone on your side who can decide within 48 hours.

Yes, and we recommend it when in doubt. The first phase solves the module that hurts most, and you can stop after it, keeping everything built and documented in your name. A single-task automation goes live in a few weeks and is absorbed into a system later without redoing anything.

You do, against full payment of each phase. Repository, database, domain, hosting accounts and backups stay in your name; we work with access you can revoke. It is a deliverable, written into the proposal.

You keep operating. Everything is documented so any developer can continue: technical manual, requirements met point by point, tested backup and restore procedure, credentials delivered outside the repository. For the ERP DG it was six delivery documents.

Yes. No penalty, no lock-in. You keep what was built, tested and documented, in your name, and the scope of the next phases is already written if you resume later.

It is designed from the process as they run it today, in their words, with minimal screens per role, and tested in the field before each phase closes. The user manual lives inside the application.

It is imported, as part of the scope. In the ERP DG, 183 products and 8 categories came in from the client's own file with a bulk import tool that previews every row and applies all or nothing.

Maybe not yet, and we will say so. AI enters when there is a repetitive task with text or documents: reading invoices into a table, answering frequent questions with hand-off to a person, summarizing. It never decides alone on money, health or anything irreversible; every action is logged and a metric is agreed beforehand.

Web applications with Next.js and TypeScript, PostgreSQL on Supabase, deployed on Vercel, all in accounts under your name. Permissions live in the database, not just the screen; every change is tested before it touches your operation. The ERP DG went live with 1,148 automated tests.

Daily automatic encrypted backups in two places, one of them your own account. The restore is tested before handover and the procedure is written in the document you receive.

Yes. Proposals and documentation can be delivered in English, and we work remotely with clients in the United States, Spain and Latin America. We quote in dollars or pesos depending on the country. The process is the same.