WordPress or Custom? What a Restaurant Actually Needs

We build custom websites. We also tell a fair number of people that they do not need one. Here is how we decide, using a restaurant as the example because it is the clearest case.

What a restaurant website is actually for

Someone is standing on a footpath at 8pm deciding where to eat. They want, in this order: are you open, where are you, what does the food look like, what does it cost, and can I book or order.

That is it. That is the whole job. Everything else on a restaurant website is decoration.

When WordPress is the right answer

- You need the site live in two weeks. - Your budget is under ₹40,000. - Someone on your team will update the menu weekly and they are not technical. - You need standard things: menu, gallery, contact, maybe a booking plugin.

For this, a well-chosen theme configured properly beats a custom build that costs four times as much and does the same job. Anyone who tells you otherwise is describing their preferences, not your needs.

The catch is "configured properly". Most bad WordPress sites are not bad because of WordPress — they are bad because someone installed fourteen plugins and never opened it again.

When custom earns its cost

- You are a chain and each location needs its own page, hours, and menu, managed centrally. - You want online ordering that does not hand 25% to an aggregator. - Your table booking needs to talk to the system you already use. - Speed matters commercially — you are spending on ads and every second of load time is costing you clicks you paid for. - You have been through two WordPress sites already and are tired of the plugin conflicts.

The honest test: **does the site need to do something specific to your business?** If yes, custom pays back. If it needs to show information beautifully, it usually does not.

The middle path most people miss

Headless: a modern fast front end, with a simple editor behind it your team can use. You get the speed and the design freedom, and your manager still updates the menu from their phone. It costs more than a theme and less than a full custom application.

What actually matters more than this decision

Whichever way you go, these move more business than the platform ever will:

1. **Your Google Business Profile.** For a restaurant this outranks your website on most searches. Photos, hours, and reviews. Free. 2. **Load time on a phone on mobile data.** Not on your office WiFi. 3. **Menu with prices, as text, not a PDF or a photo.** Google cannot read your PDF, and neither can someone squinting at it on a footpath. 4. **Phone number and WhatsApp as tap-to-open links.**

We have watched restaurants spend ₹1,50,000 on a beautiful site while their Google profile had no photos and the wrong closing time. The profile was costing them more than the website was earning.

Start with the free things. Then decide what you actually need to build.