What to build first in a web app is the part that replaces your biggest daily manual task, plus login, an admin screen and one way to get paid or notified. Leave everything else for version 2. A focused web app starts from ₹9,999 with us, and a complete system with many roles, payments and reports runs ₹2.5 to ₹10 lakh, so what you put in version 1 decides which end of that range you land on.
This post is for owners and founders who have an idea for a web app and need to decide what goes into the first release. After reading it you will have a one-page v1 list, a v2 list,
and a way to defend both when someone asks for "just one more feature".
Key takeaways
Version 1 should do one job end to end for one type of user. It should not do ten jobs halfway.
Always build the admin screen in v1. Without it, you run the business from the database or from WhatsApp.
Move a feature to v2 unless you can finish this sentence: "Without it, a paying customer cannot complete the main task."
Use a spreadsheet, a form or a no-code tool for v1 if your process is still changing weekly. We will say so ourselves.
What should you build first in a web app?
Version 1 of a web app should include the single main task, sign-in, an admin panel, basic notifications, and one way to take payment or capture the lead. That is enough to put it in front of real users and learn from them.
Think of it as a shop opening day. You need the door, the counter and the billing machine. The loyalty cards and the home delivery app can wait.
A useful rule is to write the main task as one sentence: "A patient books a slot, the clinic confirms it." "A dealer places an order, the factory sees it. " If a feature does not help that sentence happen, it is a v2 candidate.
What goes into v1 and what waits for v2?
Features that complete the main task go into v1, and features that make it faster, bigger or prettier wait. The table below sorts the usual requests for an Indian small business.
Feature | v1 or v2? | Why |
Sign-in with phone OTP or email | v1 | Users need an identity before anything else works |
The main task (booking, order, enquiry, case entry) | v1 | This is the reason the app exists |
Admin dashboard to see and edit everything | v1 | You need to run the business from day one |
WhatsApp or SMS confirmation for key events | v1 | Customers expect it, and it reduces calls to you |
UPI or card payment for the main task | v1 if you charge for it | Without it you chase payments by hand |
GST invoice PDF | v1 if you bill business customers | Missing invoices cause accounting trouble |
Multiple user roles (staff, manager, owner) | v1 only for two roles, rest v2 | Each extra role multiplies testing |
Reports and charts | Basic table export in v1, charts in v2 | You need real data before you know what to chart |
Discount codes, loyalty points, referrals | v2 | They help growth, not the first transaction |
Mobile app | v2 | A web app that works on a phone covers the first months |
AI features (search, chatbot, prediction) | v2 | They need real data from v1 to work well |
Integrations with Tally, Zoho or ERP | v2 unless it blocks the main task | Each integration brings its own testing |
Not sure which fits your project? Send us 3 to 4 lines on WhatsApp and we'll tell you honestly, even if the answer is a tool you can set up yourself.
How do I decide if a feature is v1 or v2?
Ask four questions about each feature, in this order. If the answer to the first is yes, it is v1. If not, move down.
1. Can a paying user complete the main task without it? If no, it is v1.
2. Will you break a law or a contract by launching without it? GST invoices, consent for customer data and refund terms fall here. If yes, it is v1.
3. Can you do it manually for the first 50 users, using WhatsApp or a spreadsheet? If yes, it is v2.
4. Will you only know if it is needed after real users arrive? If yes, it is v2.
Question 3 saves the most money. Founders often want an automated report on day one. The honest alternative is to download a CSV every Monday for two months, then automate the report you actually read.
Which features do founders usually put in v1 by mistake?
The usual mistakes are user roles, in-app chat, a native mobile app, complex search filters and a fancy dashboard. Each looks small in a requirements list and turns out large in testing.
In-app chat. Customers already use WhatsApp. Use a WhatsApp link in v1.
Five user roles. Start with customer and admin. Add roles when a real person needs one.
Native Android and iOS apps. Add them when you see users coming back on phones. Our post on Android or iOS first covers that choice.
Custom reports. Export to Excel first.
Everything configurable. Each setting is more code and more bugs. Hard-code values for v1 and change them when needed.
The same list explains many budget overruns.
What does a real v1 look like?
A real v1 is small enough to explain in three lines. One of our clients in vehicle rental needed online booking with document upload, plus an admin dashboard for bookings, vehicles, customers and inventory. That is the shape of a focused build: one customer
task, and one admin view to run it.
Notice what is missing from that sentence: loyalty schemes, referral codes, fancy
analytics. Those can be added once bookings are flowing and you know what customers
ask for.
Here is a one-page v1 template you can copy:
Who is the main user? (one type)
What is the one task they must complete? (one sentence)
What does the admin need to see and change? (list)
What must be sent by WhatsApp or SMS? (events only)
How does money move? (UPI, card, invoice, or none)
What is explicitly NOT in v1? (write this list; it protects you later)
How long does it take, and how do the releases work?
A build every two weeks is how we work, so you see a working link after each cycle and can say "stop","change" or "continue" . The total time depends on the scope you set above, and we give it in the fixed written quote.
The cost of changing your mind is lowest early. Moving a feature from v1 to v2 before the build costs nothing. Moving it after it is built costs rework.
When should I not build a custom web app for v1?
Do not build custom if your process changes every week, if fewer than about 10 people will use it, or if an existing tool already does 80 percent of the job. In those cases a spreadsheet, Google Forms, Zoho or a no-code tool is the cheaper way to learn.
Build custom when the workflow is stable, when you have outgrown Excel and WhatsApp groups, or when owning the data and code matters. Our posts on replacing Excel with a web app and no-code vs custom app help you choose.
We are the wrong choice if you want a lowest-price copy of a big platform in two weeks, or if you cannot spend time answering questions during the build. A web app needs an owner on your side who can decide quickly.
How does Ureka scope a web app?
One call, then a fixed written quote. The price only moves if the scope does. You own the code, domain, hosting accounts and data from day one, and one person on WhatsApp knows your project.
FAQ (visible section at the end of the post, not counted in the word count)
What features should be in the first version of a web app?
Include the one main task, sign-in, an admin panel, basic WhatsApp or SMS confirmations, and a way to take payment or capture the lead. That is enough to put the app in front of real users. Reports, loyalty schemes, extra user roles and a mobile app can wait for version 2.
How do I decide which features go into version 1 and which into version 2?
Ask whether a paying user can finish the main task without the feature. If not, it is version 1. Also include anything the law or a contract needs, such as a GST invoice. Anything you can do by hand for the first 50 users, or only need after launch, is version 2.
How much does a first version of a web app cost in India?
A web app starts from ₹9,999 with Ureka, and complete app systems with many roles, payments and reports run ₹2.5 to ₹10 lakh. You get a fixed written quote after one call. The shorter and clearer your version 1 list, the lower and firmer the price.
Should I build a web app or a mobile app first?
Build a web app first if your task is forms, bookings or orders, because it works on any phone and on desktop from one codebase. Build a mobile app first when push notifications, offline use or the camera are central to the product. Many founders add the mobile app in version 2.
Can I use a spreadsheet or a no-code tool instead of a custom web app?
Yes, and it is often the right first step. If your process changes every week, or fewer than about 10 people will use it, a spreadsheet, Google Forms or a no-code tool teaches you more per rupee. Build custom once the workflow is stable and you have outgrown those tools.