A landing page is one page built to get one action. A marketing site or website is a set of pages that explain a business. A dashboard presents data and controls, while a web app lets people complete software tasks in a browser. The more your product has accounts, data and logic, the more engineering it needs, and the cost climbs steeply at that point.
The definitions
| Type | What it is | Main job | Users sign in? |
|---|---|---|---|
| Landing page | One focused page | Get one action: sign up, enquire, book | No |
| Marketing site | Several pages about a product or company | Explain, build trust, rank in search | No |
| Website | Broader term: marketing site plus blog, careers, resources, sometimes a shop | Be the public face of the organisation | Usually no |
| Dashboard | A screen showing data and controls, often for staff or customers | Let people view and manage data | Often |
| Web app | Software in the browser with application logic, often backed by stored data | Let people complete tasks | Often |
"Website" is often used loosely to cover everything. Here it means public, content-led pages. These are planning categories rather than strict technical definitions: a public calculator can be a web app without a login, and a dashboard can be public.
Effort and cost drivers
Effort grows with what must be remembered and protected.
- Landing page: design, copy, a form, tracking. Days to a couple of weeks.
- Marketing site: more templates, navigation, content modelling, SEO setup, often a CMS. Weeks.
- Dashboard: authentication, permissions, a database, APIs, charts, empty and error states. Weeks to months.
- Web app: all of the above plus workflows, notifications, payments, admin tooling and testing. Months, and then ongoing.
Pricing follows the same ladder. For how scope moves cost, see how much a custom website costs in India.
Stack that fits each
| Type | Reasonable stack | Why |
|---|---|---|
| Landing page | Static HTML, or Next.js static page, with a form handled by a small script or form service | Public page can be static; the form still needs safe processing |
| Marketing site | Next.js or a CMS-backed site (WordPress, Webflow, headless CMS) | Content editing and SEO matter |
| Dashboard | Next.js or React front end, API, PostgreSQL | Auth, data and permissions |
| Web app | Next.js plus a back end such as NestJS, PostgreSQL, queues, monitoring | Workflows and scale |
Choosing among CMS options is covered in how to choose a CMS, and the WordPress question in WordPress vs Next.js for business websites. For apps, see a startup tech stack without overengineering.
Examples
Landing page. Apex built the Netwrkhub community landing page. Form submissions go into Google Sheets through a Google Apps Script, which avoids running a back end for a simple sign-up flow.
Restaurant landing page. Amruta Pure Veg is a restaurant landing page. A single page can cover menu, location and contact for a local business.
Public site plus admin portal. Offease is an office-space marketplace in India. Apex built the public listings site, where people search by city and locality and send an enquiry, and an admin portal for managing it. The public site behaves like a website. The admin portal behaves like a web app. Many real products are both, built on shared data.
How to choose
Ask these in order:
- Do users need to log in? A login introduces identity and permissions work, but a no-login tool may still need application logic.
- Does the data change per user? Personal data means a database and permissions.
- Does search traffic matter? Then you need real pages, content and SEO structure. See Next.js SEO checklist.
- Who edits content? If non-developers, plan a CMS.
- Are you validating an idea? Start with a landing page, then build only what proves demand. See how to build an MVP.
Turn the label into a brief
Write the main action, who performs it and what happens afterwards. For a lead-generation site, that might mean a visitor sends a brief, staff receive it in the CRM and someone follows up. Include validation, spam handling, confirmation and delivery failures in the scope.
For an application, describe what each role can read and change, which records persist and how mistakes are corrected. State who publishes public content and who owns support. These requirements help a supplier estimate real work; the word “website” alone does not.
Common mistakes
- Building a web app when a landing page and a spreadsheet would test the idea.
- Calling a marketing site "just a website" and skipping content structure and SEO.
- Adding a login to something that does not need one.
- Treating a dashboard as a design task only. The cost is in permissions and data.
Summary
Match the type to the job. One action: landing page. Explain a business: website. Let users manage their own data: dashboard or web app. If you are weighing options, our web team can help you pick the smallest thing that does the job.