July 2026
Built from the intake you shared on WhatsApp. If anything below is off, reply on the thread and we'll fix it before the next phase (site blueprint + brand direction).
The Curry Culture & Co is a casual dining Indian restaurant. The operator came to us to build their first website, with two concrete jobs for it to do: take online food orders and let guests book a table. There is no existing website to audit and no established online footprint we could verify, so this brief is written from what the operator told us at intake, plus honest flags on everything that still needs confirming. Treat it as the working document for the build, and treat the "Questions before we start" section as the shortlist the client needs to answer before we lock the brand direction and page plan.
A note on grounding: we ran online recon against the exact registered name "The Curry Culture & Co" and found no matching business. There are several similarly named Indian restaurants in other places (Curry Culture in Colorado Springs, The Curry Culture in Nanaimo, Chestermere and Singapore, Curry Culture in Mumbai, and Instagram handles referencing Indore), but none of them carries the "& Co" suffix, and the intake gave us no city to disambiguate against. So we are not assuming any of those is this business. Where this brief states a fact, it comes from the operator's intake or is clearly labelled as an open question. Nothing about location, menu, pricing, or contact details has been carried over from a lookalike.
The Curry Culture & Co is a casual dining Indian restaurant that is building its online presence for the first time. Beyond that, the intake did not capture the founder or owner story, when the restaurant opened, or who runs the kitchen and floor day to day. We are not going to invent that, because this section is exactly the kind of content a client and their guests will read closely, and getting it wrong is worse than leaving it open.
What we can say with confidence is what the decision to build points to. A restaurant that reaches out specifically to set up online ordering and table booking is one that already has a working operation and wants to reduce friction on the parts that happen before a guest sits down or a meal goes out the door. That usually means an owner who is close to the business, feels the daily churn of phone-order taking and walk-in wait management, and wants the website to carry some of that load. The website is being asked to do practical work, not just to exist as a brochure.
The founder story, the number of years operating, the size of the team, and what drives the people behind the kitchen are all blanks we want to fill during the next conversation. Casual dining Indian restaurants live or die on a small number of human specifics: who cooks, what region or style the food leans toward, and the reason the owner opened the doors in the first place. Those details are what make a restaurant page feel like a real place rather than a template. They are listed as questions below, and they matter more here than in most briefs precisely because we are starting from a blank page.
The intake describes the core business plainly, and the detailed products and services were sent as a separate document ("Design - CC draft 1.pdf") that we have not yet read into this brief. So the list below is the honest floor of what we know, not a full menu. It should be expanded once that document is reviewed.
Everything beyond this list, including the actual menu, dish photography, any catering or events offering, festive or seasonal specials, and combo or family-pack options, should be read out of the "Design - CC draft 1.pdf" the operator supplied. That document is the missing half of this section, and reviewing it is the first content task once the brief is approved.
The intake did not spell out the customer base, so this section reasons from the format rather than from stated facts, and each point should be confirmed.
A casual dining Indian restaurant with online ordering and table booking is almost always serving a local, everyday market. The typical guest is someone within the restaurant's immediate area looking for a sit-down meal without the occasion, price, or formality of fine dining, plus people nearby who want to order in or collect food on the way home. The two site goals map cleanly onto two guest behaviors: booking a table is the plan-ahead, eat-in guest, and online ordering is the convenience, eat-at-home guest. A good site has to serve both without making either feel like an afterthought.
On pricing tier, casual dining sits in the mainstream middle. It is not budget quick-service and it is not premium fine dining. That positions the restaurant as accessible for regular visits, family meals, and casual group outings rather than special-occasion splurges. We do not have actual price points, average spend, or portion and combo structures, so the tier read here is from format alone and needs the client's confirmation.
Likely guest segments to design for, pending confirmation: families and groups wanting a relaxed meal out, local professionals and residents ordering takeaway or delivery on weeknights, and small groups booking ahead for weekends. Whether the restaurant also leans on any specific community, corporate lunch trade, or catering audience is unknown and worth asking, because it changes how much weight the site should give to group bookings and larger orders.
This is the biggest gap in the brief. The intake did not capture a city, address, service radius, or operating hours, and online recon could not verify any location, phone number, email, social handle, or directory listing tied to the exact name "The Curry Culture & Co." We are not carrying over an address from any similarly named restaurant, because we cannot confirm it is the same business.
What the intake does tell us is the channel mix the business wants the website to support. The restaurant clearly operates a physical dine-in location (casual dining implies a storefront with table service), and it wants to add two online channels through the site: ordering and booking. Intake itself came in through the WhatsApp bot, which suggests WhatsApp is at least one channel the business is comfortable using, though we have not confirmed whether WhatsApp should be a customer-facing contact or ordering channel on the site.
Before the site can go live, we need the exact business address (or addresses, if there is more than one location), the phone number and email guests should use, the full opening hours including any different weekend or holiday hours, and the service area for delivery if delivery is offered. These are hard requirements for a restaurant site: guests expect to find them in seconds, and search visibility depends on them. They are all listed as questions below.
The intake did not give us a differentiation story, so we are not going to manufacture one. Claiming a restaurant is different on authenticity, freshness, or family recipes without the owner's own specifics would produce exactly the generic copy this brief is supposed to avoid. What genuinely sets a restaurant apart is concrete and comes from the people who run it.
Here is what we would need to hear from the client to write this section honestly, and each of these is a real potential point of difference worth drawing out:
Until the client supplies these, the "how they're different" story is unwritten by design. We would rather flag it plainly than fill it with claims we cannot stand behind.
The website should sound warm, welcoming, and straightforward, the way a well-run casual dining restaurant greets a returning guest. It should feel like a real neighborhood place run by people who care about the food, not a corporate chain and not a fine-dining establishment putting on airs. Language should be plain and appetite-led, leaning on the food and the experience rather than on adjectives about quality. The two things the site is asking guests to do, order online and book a table, should feel easy and inviting at every step, so the calls to action should read as friendly invitations rather than transactions. Because the restaurant serves Indian cuisine, the voice can carry a genuine sense of hospitality and generosity, but it should stay grounded and specific rather than florid.
Sample phrases that fit this voice: