1
Customer enters
Kilian Escudero
Your website should sell while you work. I make that happen.
I design websites for businesses that do not just want to look good: they want to capture leads, receive bookings, automate replies, and keep every request under control.
New leadBooking receivedEmail sentPanel updated
2
Leaves details
3
Data is checked
4
Request is stored
5
You receive an alert
6
You reply sooner
The problem
Your website should not be just a digital business card.
During a busy shift, one booking comes through WhatsApp, another by phone, another on Instagram, and another through a form. If nobody organizes them, the customer waits and chooses somewhere else.
A beautiful website helps. A website that works for you sells much more.
Messages scattered across channels
WhatsApp, Instagram, calls, emails, and forms compete for attention while the business keeps running.
Bookings handled by hand
The customer wants to book or ask for a price, but everything ends up in notebooks, notes, and manual confirmations.
Replies arrive too late
If nobody answers at the right moment, the request cools down even when the customer was ready to act.
Unowned messageMissed callCold emailManual booking
Customer
Hi, I want to book for this week. Can you confirm a time?
Business
Written in a notebook while calls and messages keep arriving.
Result
By the time someone checks it, the customer has found another option.
Restaurant during the rush
the booking sits between calls, notes, and service
Salon with three inboxes
Instagram, WhatsApp, and calls compete for attention
Academy replying too late
the form arrived, but nobody saw it in time
The visible layer is not enough if everything turns messy afterward.
no ownerduplicatependingno alert
Live demo projects
See how it works in real demos.
These are not decorative screenshots. They are flows designed to capture requests, organize data, and trigger automatic replies.
4
public demos currently online
2
active portfolio languages
24/7
VPS and n8n stack running live
Public site / Programs / Contact
New vertical
BrightPath Learning Center Demo
Public academy website with guided lead capture, consultation access from the website itself, and a legal base prepared for analytics and marketing.
BookingConfirmationPanel
Open demo
Admin panel / Pipeline
Protected access
BrightPath Learning Center admin panel
Panel to review requests, filter by program, grade level, and urgency, update statuses, and export leads. Admin token required.
AppointmentIntakeFollow-up
Open panel
Public site / Menu / Bookings
Website demo
Restaurante Inaki Demo
Public website with bookings, automated email, an internal panel, and daily availability control.
BookingEmailPanel
Open demo
Admin panel / Metrics / Table
Protected access
Restaurante Inaki admin panel
Panel to review bookings, update statuses, and open or close reservations for the day. Admin token required.
PendingConfirmedDaily status
Open panel
Appointment landing / Services / Booking
New vertical
Juniper Row Salon Demo
Public website focused on appointment requests, daily intake control, automated email, and first-visit handling for a premium US salon.
AppointmentIntakeAlert
Open demo
Admin panel / Metrics / Table
Protected access
Juniper Row Salon admin panel
Panel to review appointment requests, update statuses, and open or close the daily intake flow. Admin token required.
RequestsStatusesDaily intake
Open panelTransformation
From showcase website to operational website.
After the demos, the logic is simple: the website attracts, the form organizes, the automation alerts, and the business replies with less friction.
ClinicsRestaurantsGymsAcademiesReal estateHair salons
01Unowned message
02Missed call
03Cold email
04Manual booking
no owner
duplicate
pending
01Website
02Form
03Automation
04Database
05Email
06Panel
Public
Portfolio and demos online
The main website plus the restaurant, hair salon, and academy demos are published and reachable as separate but connected assets.
Operations
Connected lead, booking, and appointment flows
Forms and requests already move through API routes, n8n workflows, Postgres persistence, and email notifications.
Control
Internal panels and QA criteria
The demos do not stop at the public frontend: they include protected panels, quality reviews, and full-path validation.
Reusable
Shared base for new businesses
The reusable template already absorbs structure, deployment, visible legal pages, and a neutral technical base so the work does not restart from scratch.
The point is not the tool stack. The point is that fewer requests are lost, fewer steps are manual, and the business can reply sooner.
Services and formats
Choose the level your business needs.
Not every business needs a huge custom build. These four levels make a connected website easier to understand, buy, and test.
Essential website
For businesses that need a clear presence, well-structured services, and reliable contact capture.
Outcome: published professional website, sharper commercial message, and basic lead capture in place.
Lead generation website
For businesses that need leads, basic qualification, and a simple way to stop losing requests.
Outcome: conversion-focused website, working form, and inbound automation.
Operational website with bookings or appointments
For restaurants, salons, academies, and local services with scheduling, intake, or confirmation flows.
Outcome: public website, connected workflow, notifications, and lightweight internal control.
Standalone automation
For businesses that already have a website but still solve repetitive tasks manually.
Outcome: one concrete automation, validated and documented to save real time.
How I work
Four steps so the website ends up working.
I keep the process short: understand the business, design for conversion, connect forms and alerts, and test the complete journey.
01
Flow diagnosis
Define where the lead or booking enters, which data matters, and what response the business needs.
02
Visible build
Shape the website, copy, CTA structure, and customer-facing experience.
03
Operational connection
Connect the project to API routes, n8n, email, and a working panel so the flow is not manual.
04
Testing and deployment
Validate the full journey and leave it online with VPS, HTTPS, and a maintainable setup.
FAQ
What matters when a business wants more than a nice-looking website.
What does this portfolio actually prove
It proves that the visual layer, the automation layer, and the deployment layer are already connected in projects that can be tested right now.
Can the same foundation be adapted to another local business
Yes. The structure is designed to reuse forms, dashboards, and automations while changing the copy, branding, and main business flow.
What role does n8n play in these projects
n8n acts as the operational engine for storing records, sending emails, classifying requests, and coordinating actions without manual follow-up.
Tell me about your project
Tell me about your project.
Use this form if you want to discuss a website, a booking flow, lead capture, or a concrete automation for your business.
Tell me about your project
Real request to assess scope, business context, and next step.
Only for testing the technical demo
Use those values only when deliberately testing the technical flow. For a real project inquiry, describe your case with your approximate details.
Method foundation
How I work before building.
Before designing or automating, I organize the flow: what the customer wants to do, what data the business needs, which states exist, and which response should trigger.
See how I workThe result is a clear base for building screens, forms, panels, and automations without improvising the journey halfway through the project.
Discovery with specific questions
Before designing anything, I clarify actors, current friction, minimum data, and the response the business expects from each request.
Specification without ambiguity
Needs, states, and fields are translated into use cases, stories, forms, and screens that can later be automated for real.
Verification and validation
A flow is not done just because it looks good. It is reviewed both for technical correctness and for whether it solves the business and operational problem.
Next step
Make your website work for you.
If your website only informs, there is still room to turn it into a working base for capturing requests, organizing them, and replying better.