Get found · Website and app

A website or app for a small business in India

They liked your posts and wanted to order. Your link opened a slow page with no prices. They closed it.

General information, not legal or tax advice.Read more

Parts of this page touch on law, tax or platform rules. Rules change and differ by state; check the official sources listed at the end, or ask a CA or lawyer before you act.

A small-business website is a few fast pages on a domain you own that say what you sell, what it costs, where you are and how to reach you, with a button that sends the order, booking or enquiry straight to you. A customer app only makes sense once regulars order or book often; until then a site that works well on phones does the job. Every account (domain, hosting, code, payments, app stores) should be in your name.

What it involves

A website is your own address on the internet: the one place where you decide the prices, photos, wording and what happens when someone taps the button. It has four parts worth knowing by name. The domain (yourshop.in), the hosting (the computer that serves the pages), the site itself (pages, forms, any ordering or booking) and the accounts around it (email, payments, analytics, app stores). Each is rented or registered separately, with its own renewal date.

An app goes a step further. A progressive web app (PWA) is a website that can be added to the home screen, opens full screen and can send notifications. A native app comes from Google Play or the App Store and can use more of the phone. Useful business apps are usually a customer app for people who reorder or rebook every week, or a staff app for teams on the road or across outlets.

What we build is on our studio pages: apps and websites, how we build, solutions by type of business and our process. This page explains the field in plain words, so you can judge any offer, ours included.

What it is not

  • Not a social media page. Instagram or Facebook is rented space with someone else's rules; see social media.
  • Not your Google Business Profile, which is how you appear on Maps; see Google Business Profile.
  • Not search ranking. A good site makes it possible, but getting found is its own job; see SEO.
  • Not a delivery-app or marketplace listing, which brings new buyers at a commission; see listings.

Things people get wrong

  • Myth Every business needs its own app.

    Actually Most people won't install an app for a shop they visit once a month. A fast mobile site or a PWA serves them without a download. A store app earns its cost when the same people order many times.

  • Myth A free site builder plan is free.

    Actually Free plans usually carry the builder's branding and subdomain and limit forms or payments. The real cost appears when you try to leave and find the design can't come with you.

  • Myth A privacy policy is a template you paste at the bottom.

    Actually Under the DPDP Act the notice must describe what your own forms collect and why. A copied policy that misses what you actually do helps nobody.

Why it matters

Before a first visit, most people check you on their phone: profile, then site, then prices and photos, then a decision to call or not. A slow site, a hidden phone number or last year's menu loses them quietly, and you never hear about it.

The second reason is margin. An order through a delivery app or marketplace carries a commission. A regular who reorders on your own site and pays by UPI costs a small payment fee instead, and you keep their number for the next offer, with their consent.

  • Orders without a middleman

    Regulars order or book direct, and the details land on your phone or WhatsApp.

  • Fewer repeat questions

    Timings, prices, parking and what to bring are answered on the page, so calls you get are ready to buy.

  • A record you control

    Customer list, orders and content stay in accounts you own if a platform changes its terms.

When it's ignored

  • The domain lapses because the renewal email went to a developer who left, and someone else registers it.
  • The contact form has been failing for months and enquiries go nowhere.
  • Regulars keep ordering through a delivery app, so you pay commission on customers you already had.

How it works

Behind a simple site is a short chain. Each link has an owner and a renewal date, and the chain is only as reliable as its weakest part.

  1. 01DomainYour name, via a registrar
  2. 02HostingServes pages fast and securely
  3. 03PagesPrices, photos, location, the button
  4. 04Order or bookingForm, cart or slot picker
  5. 05PaymentUPI or cards via an authorised aggregator
  6. 06To youWhatsApp, email or a dashboard
  1. The domain points people to you

    You register yourbakery.in or yourbakery.com through a registrar for a year or more. For .in, the registry is NIXI, which sells only through accredited registrars listed on its site. DNS settings decide which server shows the site and which service handles email.

  2. Hosting serves the pages

    A server or a builder's platform sends pages over HTTPS (the padlock). Good hosting keeps the site up, quick and patched, and keeps copies so a mistake or a hack can be undone.

  3. The pages answer and invite action

    On a phone the visitor sees what you sell, the price, where you are, when you're open and one clear button: call, WhatsApp, book, order or ask for a quote. Each extra second of loading on mobile data loses some of them.

  4. The order or enquiry is captured

    A form, cart or calendar collects only what you need (name, phone, what, when), shows a short privacy notice, asks for consent where needed and confirms to the customer that it went through.

  5. Payment goes through an authorised aggregator

    To take money online, a payment aggregator (a bank, or a company authorised by the RBI) runs KYC on your business, shows UPI, cards and net banking, and settles to your current account minus its fee. Your site never sees card numbers.

  6. It reaches you, and you reply

    The order arrives by WhatsApp, email or a simple dashboard, ideally more than one. The site collects it; the speed of the reply is still yours.

An app adds one more link: store listings on Google Play and the App Store, each with its own developer account, review and yearly policy changes. A PWA skips the stores and updates the moment the site does.

The full scope of the work

The full list of work, with app work at the end for when it's worth it. A one-outlet café needs a fraction of it; a clinic with booking needs more.

Plan and accounts

Week 1
  • The one main actionCall, WhatsApp, book, order or quote, and the few pages that support it, agreed before any design.
  • Domain in your nameA .in or .com through an accredited registrar, your email as owner, auto-renew on.
  • Builder or customDecided by what the site must do, how often content changes and what it must connect to.
  • Business emailAn address on your domain, so customers, payment providers and app stores see a real business.

Design and build

Weeks 1–6
  • Phone-first layoutDesigned on a mid-range phone: large tap targets, call and WhatsApp buttons always in reach.
  • Core pagesServices or menu with prices, about, location with landmarks, contact, and the policy pages your forms need.
  • SpeedCompressed images, few scripts and a Core Web Vitals check, so pages open quickly on mobile data.
  • Accessibility basicsReadable contrast, resizable text, labelled form fields and alt text, following WCAG.

Ordering, booking and payments

Weeks 3–8, if needed
  • Enquiry and quote formsShort forms that land on WhatsApp or email at once, with an auto-reply.
  • Online orderingCart, pickup or delivery, delivery area and minimum order, and a clear total with no surprise charges.
  • BookingSlots, staff or rooms, deposit rules, reminders, and cancel or reschedule rules decided in advance.
  • Payment gatewayAn aggregator account in your business name, refunds and settlement tested end to end with real money.

Privacy and policies

Before launch, then yearly
  • Notice and consentA plain notice on every form, unticked consent for offers, and a way to withdraw or ask for deletion.
  • Terms, refunds and deliveryWritten to match how you work; payment providers ask for these pages before approving you.
  • Business detailsLegal name, address, a complaints contact, and GST or FSSAI numbers where relevant.

Apps, when worth it

After the site proves demand
  • PWA firstHome-screen install, offline menu or catalogue and notifications, from the site's own code.
  • Store appGoogle Play and Apple developer accounts in your name, listings, privacy labels, in-app account deletion, reviews.
  • Staff and partner appsJobs, check-ins, photos and stock counts for teams on the road or across outlets.

Handover and upkeep

Launch, then monthly
  • Launch testsEvery form, payment and link tried on Android and iPhone, on mobile data.
  • Handover packEvery account, its owner and renewal date, and the source code or an export.
  • Backups and updatesAutomatic backups you have seen restored, and security updates applied monthly.
  • Content changesPrices, timings and offers updated the day they change in the shop.

22 pieces of work across 6 stages.

What we do, and what you do

We do

  • Work out what the site or app has to do, and what it doesn't need
  • Set up domain, hosting, email and developer accounts in your name, with us added as users
  • Design for phones, build, and test on real devices
  • Set up forms, ordering, booking and payments, and test with real money
  • Draft the privacy notice and policy pages for your review
  • Hand over every login and the code, and keep things updated if you want us to

You do

  • Decide what you sell online, at what price, and your delivery, booking and refund rules
  • Send real photos, or give us time in the shop for a shoot
  • Complete KYC with the payment provider and app stores; only you can
  • Approve every page, especially prices and policies
  • Answer orders and enquiries quickly, and train staff to do the same

What we need from you to start

  • Business name as registered, GST number if any, and the address customers should see
  • Access to any existing domain, hosting or app accounts, or the name of whoever holds them
  • Products or services with prices, or your current menu or rate card
  • Logo and colours if you have them; if not, see brand identity

How far it goes

It can

  • Give you an address that is yours, fast on phones, with current prices and one clear next step
  • Take orders, bookings and payments direct, without a commission on each sale
  • Answer routine questions before anyone calls
  • Keep everything in accounts you own, so you can change developers without starting over

It can't

  • Bring visitors by itself; that takes SEO, your profile, ads and word of mouth
  • Make people install an app they don't need; downloads follow repeat use
  • Fix slow replies; an order nobody confirms for two hours is lost
  • Replace marketplaces for buyers who have never heard of you

How long until it shows

  1. 3–10 days
    Domain, email and a one-page site

    Quick once content is ready; the wait is usually photos and approvals.

  2. 3–6 weeks
    Full site with forms

    Depends on the number of pages and how fast drafts come back.

  3. 4–10 weeks
    Ordering or booking with payments

    Aggregator KYC can take days to weeks, and every flow needs real-money testing.

  4. 6–16 weeks
    Store app published

    Developer verification, store review, and for personal Google Play accounts created after November 2023 a 14-day closed test with at least 12 testers.

Ranges, not promises: they depend on the factors below and on where you start.

What affects the result

  • Content readiness

    Prices, photos and descriptions delay more sites than code does.

  • Builder or custom

    A builder is quicker for a brochure site; custom fits unusual ordering, booking or integrations.

  • Integrations

    Links to billing, stock or accounting add time; see back-office software.

  • Languages

    Each extra language is more text to write, check and keep in step.

When it isn't worth doing

  • A store app when customers buy a few times a year; a fast site and WhatsApp serve them better.
  • Online payments when everyone already pays by UPI at the counter; add them when advance payment solves a real problem such as no-shows.
  • A redesign when the real problem is that nobody answers the phone.

How it differs for your line of work

The work is the same in outline; what customers search for, the channels that matter, the rules and the busy seasons are not.

Food and beverage

For a food business the site is mostly a menu, a map and a button, and the aim is moving regulars off commission-based apps.

  • What customers expect

    The menu as text with prices and veg marks, today's timings, delivery radius and an order button that reaches you.

  • Direct ordering

    Pickup or delivery, UPI at checkout, the order on the kitchen's phone. Delivery apps bring new people; your link is for regulars.

  • Rules to show

    Your FSSAI number on the site and app, honest allergen notes, and a refund policy for wrong or late orders.

  • When an app pays

    Tiffin, milk and meal-plan businesses whose subscribers pause, skip and top up every week.

Watch out Delivery-app prices on your own site with no reason to order direct. A small perk for ordering on your link gives people one.

Playbooks

Shops and retail

A shop's site rarely needs to be a full store. Often it shows what's in stock, takes a WhatsApp order and brings people through the door.

  • Catalogue or store

    A catalogue with an ask-on-WhatsApp button suits most shops; a cart with shipping suits those ready to pack and post daily.

  • Stock you can promise

    Linking to billing or stock software stops orders for what sold out yesterday.

  • Rules to show

    Selling from your own site makes you an e-commerce entity: legal name, address and grievance contact visible, and from January 2027 discounts must show the lowest price of the last 30 days.

  • Honest checkout

    No pre-ticked add-ons, fake countdowns or charges revealed at the last step; the dark-patterns guidelines name these.

Watch out Hundreds of products with stock photos and nobody keeping stock levels true. A smaller, accurate catalogue earns more trust.

Playbooks

Clinics and health

Clinics collect the most sensitive data of any small business, so the booking form, consent and security matter as much as the design.

  • What patients look for

    Doctors with qualifications and registration numbers, treatments in plain words, fees, timings and a booking button.

  • Book without over-collecting

    Name, phone, slot and a short reason is enough. Medical history belongs in the clinic's records system, not an emailed form.

  • Children

    Under the DPDP Rules a child's booking needs a parent's verifiable consent, with some healthcare exemptions.

  • When an app helps

    Repeat visits, home sample collection or reports to download.

Watch out A form that emails full patient details to a shared inbox several staff can read. Collect less and limit who sees it.

Playbooks

Salons, spas and gyms

Salons, spas, gyms and studios sell time, so the site's job is booking and filling quiet hours without double-booking staff.

  • Booking that matches the floor

    Service, stylist or trainer, duration and buffer time as the place really runs, with a reminder.

  • Deposits

    A small UPI advance for long or bridal bookings cuts no-shows; state the reschedule rules where people book.

  • Memberships

    Monthly plans suit an app or PWA for class booking, attendance and renewals.

  • Photos

    Transformation photos only with the client's written consent, and only honest ones.

Watch out Online booking that ignores walk-ins and phone bookings, so two people arrive for one chair. Use one shared calendar or none.

Playbooks

Schools and coaching

Parents compare for weeks, so an education site needs facts in the open: courses, batches, fees, refund rules and who teaches.

  • What parents check

    Batch timings and sizes, fees and instalments, refunds, faculty, address and safety for young children.

  • Demo classes

    A short form or WhatsApp button to book a trial, answered fast; admissions often go to whoever calls back first.

  • Children's data

    Forms for under-18s need verifiable parental consent under the DPDP Rules; design them for the parent to fill.

  • Claims

    The CCPA's 2024 coaching guidelines cover result and fee claims on your own site; publish results only with consent.

Watch out Fees hidden behind 'call for details'. Parents read it as a price that depends on who's asking.

Playbooks

Home and local services

Home services are sold on trust and speed: explain the job, give a price range, and get the request to you while the customer is deciding.

  • Quote and booking

    Service, area, preferred day and a photo of the problem; a fast WhatsApp quote beats a long form.

  • Readable prices

    Starting prices with what's included and what costs extra, so visits don't start with an argument.

  • Staff app

    Today's jobs, addresses, before-and-after photos and payment collection: often worth more than a customer app.

  • Trust

    Staff verification, licences (pest control needs one) and what happens if something is damaged.

Watch out No prices, and a form going to an inbox nobody checks at weekends, when most bookings are made.

Playbooks

Distributors, traders and makers

Trade buyers check your site before a first large order, looking for specifications and proof you're a registered business.

  • What buyers check

    Specifications, grades, minimum order, lead times, certifications, GST number and the works or warehouse address.

  • Quote requests

    Product, quantity, delivery location and GST details captured, so a quote goes back the same day.

  • Dealer portals

    Customer price lists, reorders, balances and order status, once enough buyers repeat.

  • Field sales app

    Orders, visits and collections linked to accounting; see our solutions.

Watch out A brochure PDF as the whole website. Buyers on phones won't download it.

Playbooks

Stays and travel

Every direct booking saves a booking-site commission, but guests book direct only if your site feels as safe and clear as the big ones.

  • What guests need

    Real room photos, inclusions, house rules, check-in times, directions, cancellation policy and a total with taxes.

  • Direct booking

    Availability, an advance through an authorised gateway, and instant confirmation by email and WhatsApp.

  • No double bookings

    If you also sell on booking sites, sync calendars through a channel manager or calendar links.

  • Long stays

    PGs and hostels gain from a resident app for rent, notices, menus and complaints.

Watch out A 'book now' button that leads to a booking site, so you pay commission on guests who had already found you.

Playbooks

Costs and effort

Ballpark, varies; verify. Fees are what third parties charge; app store fees are set in US dollars and charged in rupees at sign-up. Our work is a fixed price after the first conversation; here we show only the time.

ItemYour timeOur timeTools and fees
Domain and email30 minutes to choose and approveAn hour or two₹500–₹1,500 a year for .in or .com (renewals often cost more); email ₹0–₹2,000 a user a year
Hosting or builderNone once set upPart of setup₹0–₹3,000 a year for static hosting; ₹2,000–₹20,000 for builder plans or managed hosting
Design and build4–10 hours: content, photos, approvalsDays for one page; weeks with ordering or bookingPhoto shoot if needed, ₹5,000–₹25,000
Online payments1–2 hours of KYCA day or two to integrate and testUsually no setup fee; UPI low or nil; cards and net banking roughly 2% plus GST
Store app accounts1–3 hours of verificationPart of the app buildGoogle Play US$25 once; Apple US$99 a year, both charged in rupees at the day's rate
Upkeep15–30 minutes a monthA few hours a monthRenewals; message charges if you send SMS or WhatsApp alerts
Ballpark, varies; verify current rates before you budget.

Apple may waive its fee for eligible nonprofits, accredited educational institutions and government bodies.

Our work: a fixed price after the first conversation, once we know your business and what it needs. The first conversation is free.

What it pairs with

Nothing here works alone. This is where website and app sits in the order of things.

Where this fits in running a business: Start · customers. A simple, fast site is part of opening; apps come later.

Doing it yourself

You can get a decent site live yourself in a weekend. This order avoids the traps that cost most later, mostly around ownership.

  1. Register the domain yourself

    Through an accredited registrar, in your name and email, with auto-renew and two-step login on.

  2. Write content before choosing a tool

    What you sell, prices, timings, address with landmarks, phone, WhatsApp and a few daylight photos.

  3. Pick a builder you can leave

    Check you can use your own domain, export your content and cancel without losing the domain.

  4. Put the main button everywhere

    A call or WhatsApp button at the top of every page on phones; test it opens the right number.

  5. Test on a cheap phone

    Load each page on mobile data, run PageSpeed Insights and shrink the images it flags.

  6. Add a privacy notice to every form

    What you collect, why, who sees it and how to ask for deletion. No pre-ticked marketing box.

  7. Keep a list of every account

    Login email, renewal date and who has access, for domain, hosting, email and payments.

  8. Try a PWA before a store app

    If regulars ask for an app, add home-screen install first. Our guides go further.

Common mistakes and red flags

Mistakes owners make

  • The developer owns the domain

    When the relationship ends, so does your address. Register it, and everything else, to yourself.

  • An app before the site works

    If people don't order on your site, they won't download an app to do it.

  • A form nobody tests

    Forms fail silently when email settings change. Send yourself a test enquiry every month.

  • A wrapper app

    A website inside an app shell often fails store review; Apple's minimum-functionality rule expects more than a repackaged site.

  • Backups never restored

    A backup you've never restored is a hope. Ask to see a restore before you need one.

Red flags when hiring anyone for this

  • Accounts in their name

    Domain, hosting, gateway or store accounts on the agency's or a freelancer's personal email.

  • No code or export

    A custom build without source code, or a closed platform without export, ties you to one supplier.

  • Promises of orders or traffic

    A site doesn't bring visitors by itself. Anyone promising order numbers is selling something else.

  • Hidden yearly charges

    A low build price with large renewal or maintenance fees later. Get every yearly cost in writing.

  • Pirated themes or plugins

    Cracked paid software often carries malware and never gets security updates.

Questions people ask

Do I need a website if I have Instagram and a Google Business Profile?

You can start without one. But both run on someone else's rules, can't take direct orders the same way and don't hold your customer list. A small fast site ties them together.

Should I choose .in or .com?

For customers in India, .in says so and is often cheaper; .com is familiar everywhere. Many register both and point one at the other. A short name that's easy to say on the phone matters more.

Site builder or custom-built?

A builder suits a brochure site you edit yourself. Custom suits ordering, booking, staff apps or links to billing and stock. Either way, own the domain and be able to take your content. See how we build.

PWA or a store app?

Start with a PWA to test whether regulars want an app: one codebase, no store fees, instant updates, and notifications on Android and on iPhones once added to the home screen. Go to the stores when you need what a PWA can't do.

What does it cost to be on Google Play and the App Store?

Google Play charges US$25 once; Apple charges US$99 a year, shown in local currency at enrolment. Apple needs a D-U-N-S number for organisations. Personal Google Play accounts created after November 2023 must run a closed test with at least 12 testers for 14 days before going public.

Do app stores take a cut of my orders?

Not for physical goods or real-world services. Google Play's payments policy bars its billing for things like food delivery and gym memberships, and Apple's guidelines are similar; you use your own gateway. Store billing is for digital content and features.

How do I take UPI payments on my site?

Sign up with an RBI-authorised payment aggregator, complete its KYC, add its checkout and test a payment and a refund. For tiny volumes a UPI link or QR on WhatsApp may be enough.

Do I need a privacy policy?

If your site collects names or numbers, yes. The DPDP Rules were notified in November 2025, and most duties, including notice and consent, apply from about May 2027. Payment providers and app stores ask for one already.

Sources and further reading

  1. .IN Registry (NIXI): accredited registrars for .in domains · accessed 7 November 2026
  2. Play Console Help: Get started with Play Console (registration fee and verification) · accessed 7 November 2026
  3. Play Console Help: App testing requirements for new personal developer accounts · accessed 7 November 2026
  4. Google Play Developer Policy: Payments · accessed 7 November 2026
  5. Android Developers: Android developer verification · accessed 7 November 2026
  6. Apple Developer: Become a member (enrolment, D-U-N-S, fee) · accessed 7 November 2026
  7. Apple Developer: App Review Guidelines · accessed 7 November 2026
  8. RBI: Regulation of Payment Aggregators Directions, 2025 (press release, 15 September 2025) · accessed 7 November 2026
  9. PIB: Government notifies the Digital Personal Data Protection Rules, 2025 · accessed 7 November 2026
  10. MeitY: Digital Personal Data Protection Rules, 2025 and enforcement timeline · accessed 7 November 2026
  11. Department of Consumer Affairs: Guidelines for Prevention and Regulation of Dark Patterns, 2023 · accessed 7 November 2026
  12. PIB: Government amends E-Commerce Rules; Consumer Protection (E-Commerce) (Amendment) Rules, 2026 in force from 1 January 2027 · accessed 7 November 2026
  13. Supreme Court of India: Rajive Raturi v. Union of India (accessibility, RPwD Act), 8 November 2024 · accessed 7 November 2026
  14. W3C: Web Content Accessibility Guidelines (WCAG) 2.2 · accessed 7 November 2026
  15. web.dev: Web Vitals · accessed 7 November 2026
  16. web.dev: Learn PWA · accessed 7 November 2026
  17. WebKit: Web Push for Web Apps on iOS and iPadOS · accessed 7 November 2026
  18. Google: PageSpeed Insights · accessed 7 November 2026

Platform rules and government processes change. We check these sources when we update the page; check them again before you act.

Menu

Read

Ask an expert Ask an expertFree, real peopleHub
Ask an expert