Private proposalSacramento, California

Big flavor.
All plants.
A front door to match.

A website for the taqueria whose food already does the talking — built around your real menu, your real dishes, and one obvious way to order.

Find us9123 Kiefer Blvd
Call(916) 898-2691
ServiceDine in · Take out

Prepared by Luis Guzman
Brandcore · for El Cantaro Next The audit

Fig. 00 El Cantaro, served as a plate

01 · The audit

The food is there.
The proof isn’t.

Read on 31 October 2026 across the three public pages. Every count below is from the live HTML, not an estimate. The food photography is genuinely good — it simply never gets names, prices or a clear next step.

CriticalSOURCE · /menu

The menu page has no menu.

Six food photographs. Zero dish names. Zero prices. A diner cannot read a single thing they might eat.

6 photos · 0 names · 0 prices

HighSOURCE · / · /menu · /contact-us

Every page opens with the same interruption.

An “Are you Hungry?” pickup pop-up covers the content on all three pages, including the menu and contact pages.

3 of 3 pages · 1 pop-up

HighSOURCE · ordering page

The real menu lives somewhere else.

135 priced items across 23 categories exist on the public ordering site. The restaurant’s own domain shows none of them.

135 priced items · 0 shown here

HighSOURCE · /

One sentence, ten times.

“The Best Vegan Mexican Restaurant in Sacramento” appears ten times in the homepage’s visible text, inside two identical H1s.

10× the same claim · 2 H1s

MediumSOURCE · <head>, all 3 pages

Search has almost nothing to read.

No meta description on any page. One shared title. The social blurb is seven words.

0 meta descriptions · 7-word social blurb

MediumSOURCE · / · /contact-us

A diner can’t tap the address.

Zero map links on any of the three pages. The address is plain text, and the footer still reads 2022.

02 · The gap

Friday, 8:41 PM.
Six taps to dinner.

A diner searches “vegan Mexican near me.” This is the path the live site offers, next to the one we would build. The evening is an illustrative scenario; the steps are real.

Today6 steps

01
Search result
A title, and no description written.
02
Homepage
A pickup pop-up arrives before the food.
03
Same sentence
The claim repeats five slides deep.
04
Menu
Six photos. No dish names, no prices.
05
Contact
Hours in four separate lines; no map link.
06
Ordering site
A second brand, and the search is over.

Nothing here is broken enough to report. It is simply enough to leave.

Proposed3 steps

01
Search result
A real description, the cuisine, the address and today’s hours.
02
Menu
Every category, the actual dishes, prices and photographs.
03
Order or call
Pickup is one tap away; so is the phone.

Two fewer chances to lose the table. No analytics are claimed here. This is the observed path, not a measured funnel.

03 · The new front door

The menu, finally
in the room.

A working concept, not a picture of one. The real dishes, the real hours and pickup in one place. Use the tabs and the filters — this is live HTML.

01

One menu, one source

The 135 priced items from your public ordering page, readable on the restaurant’s own domain.

02

Pickup stays yours

The existing ordering destination, framed as the next step instead of a competing brand.

03

Hours that answer

Today’s status is computed from the verified schedule, so Saturday never looks open.

Illustrative concept · menu names and prices are from the public ordering page, 31 Oct 2026 · confirm all items, prices and hours with the restaurant before launch.

Enchiladas on a red plate from El Cantaro’s official photography

Visit

Sacramento

A table, or a bag.

Open today

Sun – Thu: 11 – 9
Friday: 11 – 3:30
Saturday: Closed

9123 Kiefer Blvd
Sacramento, CA 95826 Call (916) 898-2691 Directions

Phone view · live HTML

04 · The system

Six things.
One restaurant.

Not a package of generic features. Each piece below exists because of something the live site is missing right now.

01

Website & menu architecture

One canonical menu, built to stay readable on a phone and quick to update when the kitchen changes a dish.

Deliverable · menu, categories, dish pages

02

Local search foundation

A real title and description per page, consistent hours, address and cuisine in the markup Google reads.

Deliverable · metadata, LocalBusiness schema

03

Order handoff

Your existing pickup provider, framed as the next step instead of a competing destination.

Deliverable · pickup page, tracked handoff

04

Photography direction

A consistent crop and colour treatment for the dishes you already photograph, with names that match the plate.

Deliverable · art direction, image guidance

05

Reviews & proof

Ask at the table, then show the real thing on the site. No invented testimonials, no borrowed stars.

Deliverable · review ask, on-site proof block

06

Growth partner

A monthly pass on menu changes, seasonal hours and the calls and pickup clicks the site produces.

Deliverable · monthly update, 60-day review

A spread of El Cantaro dishes: soup, tacos, beans, rice and salsas — Your kitchen, on the pageReal dishes. Real names. Real photographs.

05 · The proof

We’ve done this before.
Here’s the work.

United Facilities Group arrived with a dated site and its services buried in dense text. The rebuild puts the brand, the work and the next action in the first screen.

United Facilities Group website before the Brandcore rebuild

United Facilities Group website after the Brandcore rebuild

The rebuildufgworks.com

A legacy layout rebuilt into a clear, mobile-first front door. Same company, same services, a legible hierarchy. Drag the seam to see both.

BeforeDated layout · services buried

AfterBrand first · one obvious action

06 · The roadmap

Three days to plan.
Seven to build. Sixty to grow.

A proposed schedule to confirm at kickoff. Luis coordinates the work with your team; timing depends on approved menu content, access and feedback.

01Days 1–3 · Plan

Get the facts on the table.

Meet with Luis to settle the menu, the prices, the hours and the pickup destination — the things a diner checks before choosing.

Confirm all 135 menu items and prices
Verify hours, address and pickup link
Choose the pages and the launch scope

Owner · Luis + El Cantaro

02Days 4–10 · Build

Build against the real menu.

Design and build around your own dishes and photography, then review every page on an actual phone before it goes live.

Menu, pickup and visit pages
Local metadata and hours logic
Phone review and approval

Owner · Brandcore Target launch · Day 10

03Days 11–70 · Grow

Keep the front door current.

After launch, keep the details honest and watch what diners actually do: call, open pickup, or come back to the menu.

Monthly menu and hours updates
Review calls and pickup clicks
Seasonal content and a 60-day review

Owner · Brandcore + Luis

Your partner Luis Guzman Launch target Day 10 First review Day 70

What you’ll supply

Confirmed menu names, descriptions and prices
Current hours, including holiday closures
Access to the pickup link and photo originals
One approval contact for the build

07 · The engagement

Three ways to put it live.
One recommended.

Scope is specific; the fee is not invented here. After a 20-minute call, Brandcore quotes a fixed fee for the chosen scope.

Front DoorOne page

A clean reset for a restaurant that needs the basics to be right.

One-page site with hero, menu summary and hours
Call and pickup actions
Local title, description and address markup
Launch-day phone check

Best for · a fast, honest reset

Recommended

Full TableMulti-page

The complete front door, built around the real 135-item menu.

Menu, pickup and visit pages
All categories, dishes and prices
Hours logic and directions
Photography direction and local search foundation
60-day review after launch

Best for · El Cantaro now

Growth PartnerOngoing

Full Table, then a partner who keeps it current.

Everything in Full Table
Monthly menu, price and hours updates
Seasonal content and review ask
Monthly call on calls and pickup clicks

Best for · a changing menu

Start with the menu. The rest follows.

Not sure which one? Walk through the working concept with Luis first. Ask for a 20-minute scope call

Fixed feeQuoted after the scope is agreed, not before.

Real phone reviewEvery page checked at 390px before launch.

No invented proofNo borrowed reviews, rankings or metrics.

08 · Let’s talk

Give the food
a front door.

Walk through the concept with Luis, then decide which parts fit your restaurant and your timing. No pressure, no invented promises.

Your Brandcore contact

Luis Guzman

Client Success · Brandcore

A menu diners can read, hours they can trust, and one tap to pickup. That is the whole proposal.

luis@brandcore.io Direct · (669) 310-0700 Office · (669) 281-0188

San Francisco Bay Area Sales Solutions

Pick a time

Let’s talk.

Thursday at 1 PM or Friday at 2 PM Pacific — or choose any weekday time that fits.

Preferred date (Pacific) Preferred time (Pacific)

Open an unsent email draft

All times Pacific. This prepares an email draft in your mail app; nothing is booked until Luis confirms.

A menu people can read is a table worth finding.

Big flavor.
All plants.
A front door to match.