How we quote · Frequent questions

How this gets priced, no mystery.

If you are collecting quotes and cannot work out why one costs three times another, this page is for you. We explain how we quote and what to check in any estimate — including our competitors’.

// How we quote

Four steps to a price

We do not quote over the phone or on WhatsApp with two data points. A number thrown out casually ends up being a lie to one of us.

// 01
A 30-minute call

Online, or we visit if you are in Mexico City. It exists to understand the business problem, not to walk you through a catalogue. If we can already see we are not the right team, we say so on that call.

// 02
Diagnosis within two business days

You get in writing what we understood, what we propose and what it does NOT include. No cost, no obligation to continue. If you go with another vendor, the document is yours and it helps you compare.

// 03
Proposal with a closed scope

Price, deliverables, timeline and assumptions. Whatever falls outside the scope is listed explicitly, because that is exactly where mid-project conflicts are born.

// 04
Deposit and milestone payments

We start with a deposit and release the rest against verifiable deliveries. We do not charge the full amount up front, and we do not ask you to pay for progress you cannot inspect.

// How to compare

Why the same project costs five times more in another quote

This applies to judging us too. If our proposal does not answer these four points clearly, demand it before you sign.

Written scope vs. assumed scope

The cheap quote usually describes the deliverable in one line. The expensive one describes it in three pages. They are not the same work, but side by side in a spreadsheet they look like the same row.

Template vs. construction

A purchased theme, configured, costs a fraction of custom development — and for many cases that is the right call. The problem is being sold the first at the price of the second, or needing the second and receiving the first.

What happens after launch

Always ask what month one after delivery includes. Many budgets end on launch day; the bugs surface the following week and that is where a second invoice begins.

Who owns what gets built

Some vendors keep prices low because the site lives on their platform and their server. The day you want to leave, there is nothing to take with you. Ask who ends up owning the code and the domain.

Twelve straight answers

Grouped by topic. If yours is missing, write it in the contact form and we will answer — and if it repeats, we add it here.

// Commercial
Why are prices not published on the site?

Because the same request —"I want an online store"— can mean two weeks or six months of work depending on the catalogue, the integrations and the invoicing it requires. Publishing a starting price would attract projects that do not fit and frustrate both sides.

Do you charge for the initial audit?

No. The diagnostic meeting and the document that comes out of it are free. It is how we demonstrate judgement before asking you for money.

Do you work on a monthly retainer?

Yes, for website maintenance, managed hosting, SEO, campaigns and support of systems in production. It is billed monthly and can be cancelled with notice; we do not lock anyone into a minimum term.

// Technical
Which technologies do you work with?

We choose per case, not per trend. React, Vue, Svelte, Astro and Next.js on the frontend; Laravel, Django, Node.js and Go on the backend; and WordPress, Shopify or Magento when the platform solves it better than custom development.

Do you always recommend custom software?

No, and it is one of the things that sets us apart. If an off-the-shelf tool solves 90% of your process, we tell you to buy it. Building custom is justified when the process is genuinely yours and no platform respects it.

Where is what you build hosted?

Wherever suits your case: AWS, Google Cloud, or our own servers in Mexican and US datacenters. If your data must stay in a specific country, that is settled before we start.

// Legal and ownership
Who owns the code when the project ends?

You do. We work in your repository or transfer ours at close, with documentation. We do not hold code as payment collateral, and we do not leave you dependencies only we can maintain.

What about the domain and the accounts?

Always in your name, even when we register them. It is a principle, not a concession: a vendor who controls your domain controls your business.

Do you sign a non-disclosure agreement?

Yes, before you share anything sensitive. If your company has its own template, we review it and sign it.

// After delivery
What if something breaks after launch?

Defects in what we built are fixed at no cost within the agreed warranty period. New functionality that was not in the scope is different: that gets quoted separately, and we tell you clearly when you ask for it.

Can I move the project to another vendor?

Whenever you want. We hand over the repository, the accounts and the documentation. We would rather you stay because the work justifies it, not because leaving is complicated.

Do you support in English?

Yes. Meetings, documentation and tickets in English or Spanish, whichever your team prefers.

The diagnosis is free and yours to keep even if you do not hire us

Half an hour of conversation and a written document within two business days. If you go with another vendor, that document lets you demand the same from them.