Phoenix Downtown Core Website Design

Design for the ninety seconds between two meetings

Picture an office manager with a phone in one hand and a meeting about to start. Every screen on your order path has to earn its place in that short gap.

She's standing outside a conference room. The meeting starts in four minutes, and somebody just asked if lunch is sorted for Thursday. She opens your site on her phone with one thumb, because the other hand is holding a laptop and a coffee. If she can send the request before the door closes, you get the order. If she can't, she'll try the next caterer in the results, and you'll never know she was there.

We plan catering sites around that moment. A desktop layout matters too, but the phone gap is where orders are won or lost, so we design it first and let the bigger screens follow. Think of it as a time budget. Each part of the page gets a slice of her ninety seconds, and anything that doesn't pay its way gets cut or moved lower.

We like this picture because it settles arguments. Should the home page open with a slideshow of the chef's awards? Picture her thumb. Should the order form ask for the company's billing address? Picture the door closing. Most design debates on a catering site end the moment someone pictures that hallway.

• A pop-up asking for her email before she's seen a single tray.
• A menu that opens as a PDF and makes her zoom with two fingers she doesn't have free.
• A form that asks for the event name, the budget and the billing address before the headcount.
• A send button hidden below a long block of legal text about cancellations.
• A confirmation that says thanks and nothing about when anyone will reply.

Buttons a thumb can hit while the other hand holds coffee

Accessibility standards set a floor for how big tap targets must be, and meeting it spares every buyer the mis-tap that orders the wrong tray size.

None of these fixes is exotic. They're the kind of thing you only notice when you try to order lunch from your own site while walking down a hallway. We do exactly that during testing, and we'd encourage you to try it tonight. Hand your phone to someone who has never seen the site, ask them to order for twenty, and watch their thumb without helping.

Spacing counts as much as size. Two good-sized buttons pressed right up against each other still invite the wrong tap, especially on a bumpy walk between meetings. We leave breathing room around anything that changes the order, and we keep destructive buttons, like remove or cancel, well away from the send button.

While you're watching, count the times they squint. Small gray text on a white background is another hallway killer, and so is light type laid over a food photo. If a helper has to tilt the screen to read your cutoff time, that line needs darker type or a plain background behind it.

Every field on the order form, and the keyboard it should open

Each field should ask one plain question and open the right keyboard, so nobody types a phone number on a letter keyboard or wonders what a box called details wants.

The date box deserves extra care, since it's where impossible orders sneak through. Gray out the days the kitchen is closed, holidays included. Once today's cutoff passes, block the next day as well. Then say why in a short line under the box, such as: past our 2 p.m. cutoff, so the first open day is Thursday. Below that line, put a tap-to-call link for anyone who needs lunch sooner. A few of those calls become orders you can squeeze in, and none of them become angry emails about a lunch that never came.

Error messages matter just as much. If a required field is empty, the form should say which one in plain words, right beside it, and keep everything else she typed. Nothing sends a busy buyer to a rival faster than a form that wipes itself after one mistake.

Autofill helps here more than people expect. When fields are labeled the standard way, a phone can offer to fill in her name, email and mobile number with one tap. That turns five fiddly fields into one, and it's a small setting we check on every form we build.

We also design the other end of the form: the alert your kitchen receives. Many form tools send a jumble of labels in the order the fields were built. We'd rather the alert read like a ticket, with the date, delivery window, headcount and suite on the first lines and diet notes right under them. Whoever checks the inbox at 7 a.m. should be able to say yes without scrolling or calling back to ask.

The confirmation screen has more jobs than saying thanks

Once someone taps send, the next screen should repeat what you received, say when the kitchen will answer and give a way to fix a mistake without starting over.

1. Give the confirmation its own address Send people to a real page, such as a thank-you address, instead of swapping text in place. That one page view becomes your cleanest signal of a sent request.
2. Create the event in Google Analytics Name it generate_lead and trigger it on views of that page. Test it by sending yourself an order and watching it arrive.
3. Keep the page out of search A thank-you page isn't something a stranger should land on, so we'd mark it noindex and leave it out of the menu.
4. Compare requests with real orders Each month, line up the event count with the orders you actually took. A big gap points to spam, test sends or buyers who changed their minds.

The automatic email she gets should match that screen, line for line. If the page says two business hours and the email says 24 hours, she'll trust neither. We write both at the same sitting and test them together. Then we send a few pretend orders from different phones to make sure the details come through the way she typed them.

Food photos that finish loading before the meeting does

Big lunch photos sell, and heavy ones are a common reason a menu page drags on a phone. Google measures that drag with three numbers you can check yourself.

• Size the top photo for a phone screen, then serve a larger version only to larger screens.
• Save photos as WebP where you can, and keep a JPEG fallback only if your platform needs one.
• Set a width and height on every image so the page doesn't jump as photos arrive.
• Let photos far down the page load when someone scrolls to them.
• Crop tight on the food. A wide shot of a whole room shrinks every tray to a speck on a phone.
• Check the page on a phone after every new photo goes up, since one giant upload can undo a month of care.

Diet labels are a promise your kitchen signs

A vegan or gluten-free label is a promise about someone's lunch, so the kitchen should approve every label and the page should explain what each one means.

If you run one kitchen under one name, that federal calorie rule likely isn't aimed at you, though your own advisor can confirm it. That leaves your diet labels resting on nothing but your kitchen's word. Which is exactly why the kitchen should own them. We'll build the labels, but we won't write a single one your chef hasn't approved.

There's a practical upside, too. When the labels are clear and approved, your phone staff field fewer of the same allergy questions each morning. That's time they can spend confirming orders instead of repeating themselves, and it's a quiet win nobody puts in a slide deck.

• Put a short legend near the top of the menu that says what each label means in your kitchen.
• Write labels as words next to each dish, and add icons only as a bonus, since a screen reader can't read a leaf.
• Add filter buttons above the menu, such as vegan or gluten-free, that hide the dishes that don't fit and show how many are left.
• Size each label close to the dish name and give it strong contrast. It's part of the order, so it shouldn't look like a footnote.
• On a narrow screen, keep each label on the same line as its dish, so it can't wrap down beside the wrong tray.
• Repeat the chosen labels on the confirmation screen, so a buyer sees gluten-free next to the tray she picked before she locks her phone.

One order link, used everywhere your name appears

Your Google profile, email signature, invoices and social bios can all point to the same order page, each tagged so you can see which one sent the request.

Pick one spelling for each tag and write it on a sticky note by the register. The tags look fussy, but after three months they answer a question every caterer argues about: which of these things actually brings orders? Add a campaign name to each one, such as lunch-orders, so all five roll up into one line in your reports.

We set these tags up once and hand you the list, so nobody has to remember the spelling later. When you add a new place for the link, such as a catering marketplace listing, we add one more row. The whole system fits on an index card, which is exactly how simple it should stay.

The Friday test that catches a form failing in silence

Order forms can stop sending without any warning when a plugin updates or an inbox fills up, so send yourself a test request every Friday and time the alert.

1. Order from a phone on cell data Skip the office wifi and your desktop. You want the same path a buyer takes from a hallway, with the same slow connection.
2. Check the confirmation screen Make sure it repeats the details you typed and names a reply time. A blank thank-you page is the first sign something's off.
3. Find the alert in the kitchen inbox Look in the main inbox and the spam folder. Note how many minutes it took to arrive.
4. Reply the way you would to a buyer Hit reply and confirm it reaches a real inbox. A reply that bounces off a no-reply address is a lost order.
5. Write it in the log Date, time sent, time received and anything odd. A missed Friday test is cheaper than a missed Monday lunch for forty.

We know it sounds tedious. It takes about three minutes, and it's the only way to learn a form broke before a customer tells you, or worse, doesn't bother to. The week a test fails, you'll be glad you spent those three minutes on a Friday instead of learning about it from a hungry boardroom.

If you'd rather not do it yourself, hand the Friday test to whoever opens the kitchen that day and give them the log sheet. The job doesn't need a web person. It needs someone who notices when a normal thing stops happening, and every good kitchen already has that person.

• No alert at all: check the form's email settings first, then whether a recent plugin or platform update changed them.
• Alert in spam: move it to the inbox, mark it as safe and tell whoever manages your domain's email.
• Alert arrives late: note the delay and test again an hour later before anyone panics.
• Confirmation screen missing: the form may be sending but the page broke, so check the thank-you address still loads.
• Anything else odd: tell us that day, and we'll look before the weekend orders pile up.

Straight answers to what a caterer asks before a rebuild

Straight answers to the practical worries a caterer tends to raise before a rebuild, from payments to delivery maps, so you can plan before we ever talk.

Should buyers be able to pay on the order form?

Only if your orders are simple and priced up front. When headcounts and menus shift until the day before, a request form followed by your confirmation and invoice saves refunds and awkward emails. Some office buyers need an invoice for their accounts team anyway.

Do we need ordering software, or will a form do?

Start with a good form unless you sell fixed menus at high volume. Ordering software earns its fees when most orders look the same. When every lunch needs a human answer, a clear form plus a fast reply usually serves buyers better.

How should the site show where we deliver?

Write it out in words: the neighborhoods or rough boundary you cover, plus any minimum for longer trips. A map picture on its own leaves screen reader users and search engines guessing unless the same details sit in the text.

How many photos does the menu page need?

Enough to show each format once, well lit and cropped close. Ten sharp photos that match what arrives beat forty that don't. If a tray looks different in real life, retake the photo before someone notices.

Can we get an outside read before paying for a rebuild?

Yes, and the first look is free: our scan walks through up to 100 pages. If you want more, ninety-nine dollars buys the full audit. That one covers a site of up to 3,000 pages. It also grades up to three competitors of your choosing with the same checks, and a single rescan after you've fixed things comes with it.

One more thing we'd talk you out of: the chat bubble. On a catering site it often sits right on top of the send button on a phone, and nobody is staffing it at 7 a.m. anyway. A tap-to-call link and a clear form do the same job without covering anything. If you already have a chat tool you love, we'll move it somewhere it can't block an order.

What we'd test on your phone during our first call

We'd open your order page on a real phone while we talk, send a pretend order together and note every spot where a busy buyer would stall.

• How long it takes to get from the home page to the order form.
• Whether the menu reads without pinching or zooming.
• Which buttons are too small or too close together for a thumb.
• What keyboard pops up in each field of the form.
• What the screen says after sending, and how long the kitchen alert takes.

We'll say it plainly: we're an Indianapolis agency, and we haven't built a site for a downtown Phoenix caterer, so there's no local example to show you. What we do have is Jeff Clerisier, a web builder since 2016, and more than 1,400 live sites we keep running. Thumb problems turn up again and again across them, so we know where to look first.

The call itself is a working session. You drive the phone, we take notes, and by the end you'll know which three fixes would matter most on your order path. If the honest answer is a smaller job than a rebuild, you'll hear it from us on that call.

After the call, our first fixes are usually small and fast to test: bigger buttons, a shorter form, a confirmation screen that says something useful. We'd rather you see those working on your own phone within a few orders than wait on a grand relaunch that nobody can measure.

Will anyone need to visit our kitchen?

Nobody has to fly in. Our side of the work happens over video from Indianapolis, and your team can shoot the photos we need on a phone. Stand near a window, fill the frame with the tray and skip the flash. We'll tell you which shots are missing once we see the first batch.

Who writes the words on the new pages?

We draft them from what you tell us on calls and from the questions your staff answer every day. Your kitchen checks every dish name, label and cutoff before anything goes live, because you're the ones who'll be held to it.