What people ask before hiring

A website starts at $790 and an online store at $1,450. A custom web application starts with a $1,500 assessment that ends in a fixed quote, and the first usable version starts at $9,500. Every service publishes its plans on the pricing page. The final number depends on scope, which is why after the first call you get a proposal with scope, milestones and a fixed price per milestone.

With a call to understand the problem, and from there a written proposal covering the scope, the milestones and the price of each one. Whatever is not included is listed as out of scope in the same document, so it never turns up mid-project as an extra cost.

It is delivered in parts, every one or two weeks, and the first usable version arrives long before the whole project does. We would rather you see something working early and correct course than have us disappear for three months and return with a surprise.

Someone who can decide and answer questions, whatever content you already have — text, photographs, catalog — and access to the systems that need touching. If the content does not exist yet it gets handled inside the project, but it is worth knowing up front because it is usually what delays things most.

That is the most common case. When there is no technical counterpart, Luic also takes on the architecture decisions and explains them in business terms: what costs more, what can be changed later and what cannot. What we don't do is make those decisions without telling you.

Yes. It starts with a review of what exists: how it is built, how risky it is to touch and whether continuing or rebuilding makes more sense. That review is delivered in writing, and it is useful to you even if you carry on with someone else.

There is a live link from the first week and it updates with every delivery. No waiting for a meeting, and no settling for screenshots to know how it is going.

Yes, and they usually appear once you see the system working — that is why it ships in parts. Small adjustments are absorbed as we go. Anything that moves the scope is quoted separately before it is built, so the budget never shifts without you knowing.

Whoever is building it. There is no intermediate layer translating what you said and returning the answer three days later.

What has been delivered is already in your repository and works as far as it got. There is nothing held back to force you to continue.

You do. The repository is in your name from the first commit and the infrastructure is deployed in your accounts, not ours. If one day you decide to continue with another supplier, there is nothing to claim back or migrate.

There is a warranty on what was delivered and an optional maintenance plan for updates, monitoring and support. Whoever built the system is who keeps it running, so there is no handover period and no learning curve in between.

Yes. It starts with a review of what exists — how it is built, what is out of date, which backups exist and whether they work — and from that we define what maintenance covers and what should be fixed first.

You take everything, because you already have it: repository, domain, infrastructure accounts and documentation are in your name from the start. Working this way is precisely so that leaving costs you nothing.

Yes. Luic works remotely and already builds for several countries in Latin America; the architectures handle currency, time zone and tax rules per territory from the design stage. Meetings are booked in your time zone, in Spanish or English.

Next.js and React on the browser side, NestJS and Node on the server side, PostgreSQL with Prisma for data, and deployment on Cloudflare or on whichever provider you already use. The rule is not to pick the fashionable tool if nobody will be able to maintain it afterwards.

Yes, as a working tool, the same way as an editor or a compiler. What does not change is who answers for it: the architecture decisions, the code review and what gets delivered all have a person behind them.

The data lives in your infrastructure and is not copied into ours to work on it. When a project involves personal data, who can access what — and what gets logged — is defined from the design stage.

Because you can open the work. AI LABS, LabsChats, Los Churrascos and Propqix are online: go in, look at them and judge whether they are well made. This site has no testimonials and no project counts because you would have no way to verify them.