01
Objective and scope
What the website must achieve, which journeys are priorities and what is explicitly outside the first delivery.
I build the website your business needs to receive enquiries, sell or connect an internal process. We agree what the user needs to do and how the information reaches your team before choosing the solution.
The public cases show work where commerce, lead capture, automation and technical continuity are part of the outcome.
Review the case and delivered scopeArafilum: catalogue and online sales built around a real craft operation.
Integraleón: lead capture and a digital structure for professional services.
Integrations and forms prepared to operate, measure and maintain.
A custom website is easier to estimate when the objective, users, systems and validation process are visible from the start.
01
What the website must achieve, which journeys are priorities and what is explicitly outside the first delivery.
02
I can start from Figma, an existing identity or an agreed structure, with owners and review rounds made clear.
03
Forms, CRM, analytics, APIs, automation, migrations and access that shape the real solution.
The budget follows verifiable product and operational complexity, not a page count in isolation.
01
Responsive frontend, real states, accessibility, performance and a backend or CMS when the project needs one.
02
Robust forms, consent, CRM, notifications and measurement to complete the commercial journey.
03
Testing, deployment, documentation, returned access and prioritized next steps for continued evolution.
The minimum worth clarifying before opening a collaboration.
Yes. I can implement from Figma, evolve an existing base or propose the required structure. Before estimating, I review its state, dependencies and who will validate delivery.
It depends on journeys, content, design, integrations, migration, permissions and ongoing operation. I first define a verifiable delivery and then propose a fixed project or phases.
Yes. The architecture depends on who will edit content, which data must move and which systems the company already uses.
Yes. When the agency owns the client relationship, the specific offer is white-label web development with NDA support and a handoff adapted to its process.
Required user journeys, roles and permissions, availability of design and content and integration complexity. An enquiry website with one form and a store with payments, orders and administration have different scopes. The proposal defines deliverables, dependencies and acceptance criteria before price and timing are fixed.
If you are still comparing options, these routes help narrow the decision.
With objective, timing, current state and the technical blocker, I can reply with the next step.