Why website briefs fail in Indian SME buying
Voice notes, changing scope after the cheapest quote, and stack religion without a job. Vendors then pad or under-scope. You cannot compare.
English polish is optional. Completeness is not. Tamil/Hindi notes are fine if the page list is still a list.
“Make it like Apple” is not a requirement
Apple has a product org. You have six services and a GSTIN. Reference sites in your category with reasons. Aspirational luxury without a catalogue is how landers get marble textures and no CTA.
The one-page brief we actually use
Company one-liner, primary conversion, page inventory, must-have integrations (WhatsApp, Razorpay, calendar), editor persona, deadline, budget band, domain status, and out-of-scope list.
Out of scope is kindness: “no blog in v1,” “no customer login,” “no Tamil site yet.” It stops heroic scope creep.
- Job in one sentence
- Page list with notes
- Who edits weekly
- Budget band and deadline
- Domain and email owner
- What v1 will not include
A sentence that saves two weeks
“This is a brochure for inbound WhatsApp, not a store.” Or the reverse. Ambiguous commerce is the most expensive unwritten line in Indian briefs.
Page list, not adjectives — inventory is the product
Home, About, 4 services, Work, Contact, Privacy. If a page has no owner and no content source, it is not a page. Cut it.
If you only have one offer, you may need a landing page, not eight empty nav items. See landing vs full website.
Service pages need a promise, not a synonym
“GST filing” and “GST returns” might be one URL. Duplicate near-synonyms waste budget and confuse SEO.
Who edits and who approves — put names
Receptionist on WordPress, founder on WhatsApp, CA on legal pages. If nobody will log in, consider static from ₹18,000 instead of a CMS you will fear.
One approver. Write the name. “The family” is not an approver. This is the same rule that keeps timelines honest.
After-hours editors need mobile-admin reality
If updates happen on a phone in a shop, do not brief a fragile custom builder. WordPress with locked patterns may be the brief, not a Figma playground.
Budget honesty and published floors
State a band. We publish floors so you can sanity-check: landing ₹7,500; static from ₹18,000; business ₹28,000; e-commerce ₹38,000; dynamic + SEO ₹50,000 + ₹15,000/mo; custom from ₹50,000. Asking for custom app behaviour on a lander budget will get a no — which is cheaper than a bad yes.
If finance needs a range for board, say so. Mystery shopping five agencies with no number wastes everyone’s GST.
Split build versus ads versus SEO in the brief
The website invoice is not the media invoice. SEO is a retainer if search is the channel. Mixing them makes every quote incomparable.
References that help versus moodboards that lie
Live URLs, three bullets each: keep, ignore, never. Screenshot the mobile menu you hate. That is gold.
Motion-heavy marketing sites may be Framer jobs; editor-heavy service sites may be WordPress. Do not paste a Framer award winner as the brief for a CA firm’s intern-edited blog.
Competitor sites are not a legal copy deck
We will not clone. We will infer IA and proof patterns. If you want their copy, that is a different ethical problem — we will not.
Payments, GST, and legal pages belong in v1 scope
Stores: UPI/Razorpay, invoice fields, shipping, refunds. Brochure: Privacy, Terms if you collect leads, address, GSTIN if you show it. Brief them so they are not “week six extras.”
Detail lives in GST-ready websites. The brief only needs “must appear on footer / invoice.”
If you take money, say how
WhatsApp UPI is a process. Shopify checkout is a process. “We will see” is how you buy the wrong package.
Access, hosting, and ownership — write the custody model
Domain registrar owner, hosting owner, analytics owner, ad pixels owner. Agency as collaborator. This prevents the 2019 freelancer hostage pattern.
If you have no domain yet, the brief says “buy in company name in week one.”
Repo and CMS admin in your email
Handover is a brief item, not a favour. WordPress admin, Shopify owner account, Git org — named.
Questions you should ask every vendor
Which stack and why? What is out of scope? Who owns DNS? How many revision rounds? What happens after 30 days? Show two sites that are not the same theme.
If they will not name a stack, they will name one after you pay — usually whatever intern is free. Push for platform honesty.
Ask to see a handover artefact
A login sheet and a 10-minute Loom from a past project tells you more than a credentials wall of logos.
Sample brief for a Chennai SME (steal the shape)
“Adyar physiotherapy clinic. Job: WhatsApp bookings from Google and Instagram. Pages: Home, About (doctors), 5 treatments, Contact with map, Privacy. Editor: front-desk on phone. Budget: business website band ₹28,000. Deadline: before Pongal camp. Domain: we own clinicname.in, email on Zoho. Out of scope: patient login, Tamil v1, blog.”
That paragraph is bid-ready. Add two reference URLs. You are done. Send it to consultation.
Store variant of the same shape
Replace treatments with SKU count, COD yes/no, GST invoices required, and Shopify as the likely OS unless you already live in WordPress commerce.
After the call: SOW that matches the brief
If the SOW invents pages you did not list, stop. If it drops GST and ownership, stop. The brief should be an appendix, not a memory.
Brevia will map the brief to a floor and a calendar from Thousand Lights. Contact Us when the Doc is shareable. Hub: Website Development.
Change control is part of briefing
New pages after sign-off are new quotes. Write that expectation in the brief so nobody performs surprise later.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.