Owners rarely ask us "what should I build first". They say "nobody finds us" or "customers call all day for updates". The right first piece follows from which sentence is yours, and from one distinction: are you finding new customers, or serving the same ones again?
Who finds you, and who comes back
A website is how strangers find you. Somebody searches, or taps an ad, or asks an assistant, and your site is where they land and leave an enquiry. An app is how regulars come back. A chemist reordering every week, a parent checking fees, a client checking a file: they do not search for you, they open you. If your growth depends on new faces, the website comes first. If your day is spent answering the same people, the app comes first.
Five questions to decide
- Where did your last ten customers come from? Search, ads and referrals point to the website. Repeat orders from people you already know point to the app.
- How often does one customer order in a month? Once a year: website. Every week: app.
- What do people call you about? "Do you do this?" is a website question. "Where is my order?" is an app question.
- Who types the order today? If your team retypes orders from calls and messages, an app removes that work.
- What happens after the enquiry? If enquiries vanish into a notebook, the back office behind the website matters as much as the website.
What each costs and how long it takes
A website takes about two weeks, a customer app about four, and a back office about five. On a SamaStack plan you do not pay per piece: From ₹9,999 to ₹49,999 a month plus GST for teams of up to 25, set by what you need and your team size. The price is set by what you need and your team size, and you start with one piece and add the rest when you need it.
What changes when both share one record
Built separately, a website and an app are two places where orders arrive and two lists someone has to reconcile. On one record, an enquiry from the website and an order from the app land in the same back office, the stock drops once, and the bill goes out once. The owner can ask which ad brought customers who later ordered in the app, because it is the same customer all the way through. Follow one order from the first ad to the last rupee.
By trade
- Pharma distributors: app first. Chemists reorder weekly, and the retailer app ends the order by chat message.
- Jewellery manufacturers: back office first, for the karigar ledger, then a buyer app.
- Modular kitchens: website first, because most customers buy one kitchen and find you through search.
- Schools: website for admissions, then the parent app for fees and circulars.
- Financial advisors and DSAs: back office first, then a client app for documents and status.
Mistakes to avoid
- An app nobody opens. An app only earns its place if customers come back often. Once a year is a website job.
- A website with nowhere for enquiries to go. If enquiries land in an inbox nobody watches, the website is not the problem.
- Building both separately. Two vendors, two lists of customers, and an order typed twice. If you will need both, plan them on one record from the start.
- Ads before either. Paying for clicks that land on a weak page wastes the budget. Fix the page first.
When you need both from the start
Some businesses need both on day one: a school opening admissions for a new campus, or a distributor whose retailers want to order and whose new customers come from search. Then build them together on one record, website first because it takes about two weeks, and the app following in about four. The price is still one monthly number set by team size, not a price per piece.
How to test demand before building an app
Before an app, check that customers will use one. Count how many orders or status calls you take from the same customers each week; if it is a handful, an app can wait. Ask your ten most regular customers whether they would order from an app with your name on it, and what they would want to see first. And watch the website: if returning visitors keep coming back to the same pages to check something, that is the screen your app should open on. An app built around the one thing regulars already do with you is the app they keep on their phone.
Questions people ask
What if my customers mostly order by phone today?
Then the app can start small: let regular customers reorder what they ordered last time, see what they owe and track the delivery. Those three screens remove most of the calls. Phone orders can still be taken by your team and entered once, on the same record the app reads, so nothing is lost while customers move across at their own pace.
How long does each take to build?
A website takes about two weeks, a customer app about four, and a back office about five. You see a live link every week while we build, and nothing goes live without your yes.
Do I need an app if I have a good website?
Only if the same customers come back often to order, book or check something. If they buy once, a good website is enough.
Can the app and website share customer accounts?
Yes, when they are on one record. A customer who enquires on the website is the same customer who later orders in the app.
Android, iPhone or both?
Both, and the web, from one build, so a customer on a laptop gets the same app.
Which is cheaper to start with?
On a SamaStack plan you do not pay per piece. Plans run from ₹9,999 to ₹49,999 a month plus GST, set by what you need and your team size.
Your numbers
Get your exact price in 48 hours.
From ₹9,999 to ₹49,999 a month plus GST for teams of up to 25, set by what you need and your team size. Tell us what you run, and the exact number comes in writing.