Web design agency that decides what people understand first.

There is no single price because there is no single project. What moves it is measurable: how many pages and how many services have to be structured, whether the content exists or has to be worked on, whether it is built on WordPress or calls for custom development, and whether there is a shop, a private area or integrations. We would rather look at the starting point and give a fixed quote with the scope in writing before starting, instead of a range that means nothing.

It depends on the scope, but what stretches a project is almost never the design: it is the content that is missing and the internal sign-offs. That is why the first stage closes the objective and the scope in writing and the second closes the structure before anything is drawn. Once those two decisions are made, the rest moves at a predictable pace.

Yes, and it is half of what we do. Before touching anything we look at which pages get traffic today and for which searches, so we know what has to be kept: those URLs, their useful content and their heading structure. Anything that changes address gets redirected. A redesign loses rankings when the site is rebuilt as if the previous one had never existed, not because it was redesigned.

With both, and the choice belongs to the project, not to us. WordPress makes sense when the team wants to publish and extend on its own without depending on anybody. Custom development makes sense when control matters: performance, features of your own, integrations or a structure no off-the-shelf CMS holds well. We decide it in the third stage, once we know what the site has to do.

The knowledge of the business comes from the company: what it sells, how it works, what sets it apart and which figures it can show. What we bring is the order and the shape —what goes on each page, in what sequence, at what length— and the rewriting of what you hand over so it fits that structure. If content production beyond that is needed, we say so up front and it goes into the scope.

On a normal project they go together: we design and build the site, which is why what gets proposed in structure and interface is always buildable. They are two different capabilities, though. Experience design decides what the visitor understands and lives through; custom development comes in when the project needs logic of its own —processes, panels, integrations, a product—. When that point arrives we say so, because it changes the scope and the budget.

No, and it is worth being wary of anyone who does: sales depend on the offer, the price, the market and the sales team, and a website does not rule over any of that. What can be sustained is that the site stops getting in the way: that people understand what you do, that visitors find their part, that there is a clear next step and that what happens can be measured. If with all that resolved the problem is still somewhere else, we will say so.