Hernandez Landscape
Bilingual local-service site with real project photos, service pages, and an estimate path.
DeKalb websites, lead flow, and automation
I clean up the digital front door and the follow-up behind it.
Websites that look current, quote paths that are easy to find, Spanish pages that actually help, and simple automations when leads start falling through the cracks.
Local
DeKalb-area focus
Bilingual
English + Spanish clarity
Ops
Websites plus workflow cleanup
Public proof
Website, service pages, photos, and Google clarity
Lead path
Quote forms, calls, handoff notes, and bilingual copy
Follow-up
Inbox routing, n8n workflows, and owner visibility
First pass
I look for the parts a customer notices before the owner does.
The best fixes are usually plain: make the work visible, make the next step obvious, and stop losing leads after the first message.
AuditFixFollow up
Homepage
Ten-second read
Can somebody land on the page and immediately know what you do, where you work, and how to reach you?
Lead flow
Quote path
The call, form, and next step should be obvious on mobile without making people hunt through the page.
Bilingual
Spanish clarity
If Spanish-speaking customers are part of the real business, the site should not treat Spanish like an afterthought.
Follow-up
Owner handoff
Once a lead comes in, the owner should see enough context to reply without digging through texts and tabs.
Proof
Less theory. More things people can click.
A local-business site should show the work, make the next step obvious, and be easy to inspect without a long explanation.
Live sites a prospect can open
Screenshots that show the work
Lead paths and service pages, not just pretty images
What I Do
The work is practical on purpose.
Most small businesses do not need a giant digital transformation. They need the public stuff cleaned up, the lead path tightened, and a few repeat tasks automated.
Fix the website people actually see
Mobile layout, service pages, photos, trust sections, calls, quote forms, and the stuff that makes a local business look alive.
Clean up the lead path
Forms, missed-call handoff, follow-up notes, review asks, and simple automations so leads do not vanish after the first click.
Make bilingual pages useful
Not just a toggle. Clear Spanish service pages for businesses that already serve Spanish-speaking customers around DeKalb.
Build the private ops pieces
Dashboards, CRM cleanup, invoice/payment glue, n8n workflows, and internal tools when the business outgrows a brochure site.
Visual systems
The work should be easy to understand without a sales call.
These are the three visuals I want a local operator to understand quickly: what the public sees, what bilingual customers need, and what the owner receives after a lead comes in.
Local proof stack
Website, Google listing, photos, reviews, service area, and quote path should reinforce each other instead of telling six different stories.
Bilingual service clarity
Spanish service pages should carry the same practical detail as English pages: services, photos, location cues, and an easy estimate path.
Owner handoff
The form is only the start. The owner needs a readable summary, next step, reminder, and follow-up path without digging through tabs.
Lead Flow
A customer should not have to work this hard.
This is the map I keep coming back to on local-business work: how someone finds you, trusts you, asks for help, and gets followed up with.
What gets cleaned up
The website is only one piece of the path.
A better homepage helps, but it does not fix a hidden quote form, stale Google proof, unclear Spanish copy, or a follow-up process that lives in somebody's memory.
Make the public proof obvious
Put the quote/call path where people expect it
Capture enough context to reply without guessing
Add light automation only where it removes real friction
Private Flagship
There is also a bigger build behind the scenes.
The public examples show the front door. The private construction-platform work is the stronger operations story, but it stays anonymized until the client signs off.
Stack
Next.js, Supabase, Invoice Ninja, Stripe, n8n
Goal
Replace a monthly SaaS with a custom operations platform
Why it matters
Public website, client records, project status, invoices, payments, and automations in one system. That is a different level of work than just making a nice homepage.
I wrote the case-study draft, but it is intentionally unpublished. No client name, no private screenshots, no internal details until permission is clear.
Start small
Send me the site, the Google listing, or the workflow that keeps annoying you.
I will look for the obvious gaps first. If it is a 30-minute cleanup, I will say that. If it needs a full sprint, I will map it out.
Good first asks
- Can people tell what you do in the first 10 seconds?
- Can they request a quote without hunting?
- Are English and Spanish customers getting the same clarity?
- What happens after a lead submits the form?