Website, landing, store or portal: what does your business really need?

Needing a website sounds like a clear request until you start asking questions.

Do you need it to be found on Google? To explain various services? To send traffic from a campaign to a single offer? To sell and charge online? Or to get your customers to log in with an account, check documents and track something?

All that can happen from a browser, but it's not the same project.

The most useful decision does not start by asking how many pages you want or what technology is in fashion. Start with something much simpler:

What do you need someone to be able to do when they arrive?

If you answer that first, it's much easier to know if you need a landing page, a corporate site, a store, a portal or just improve what you already have.

The short answer

• If you have a specific offer and want people to take one clear action, you probably need a landing page.
• If your business needs to explain who it is, what it offers, and the different areas it covers, while building trust, you probably need a website.
• If you want someone to be able to choose products, buy, pay and receive confirmation without relying on a manual conversation, you are entering e-commerce.
• If customers, employees or other users need to sign in and work with their own information, requests, statuses, files or processes, you probably need a portal or web application.
• If your current website already does much of the work, you may not need to start from scratch. It may be better to correct, reorganise or connect what already exists.

These are not steps from a small website to a large one. They are different tools.

1. A landing page: when there is an offer and a clear next step

A landing page works best when you don't need to explain the whole business.

Imagine that a company offers five different services, but during this month it is promoting only one: a free evaluation, a new plan, a course, a property, an event or a specific offer.

Someone clicks an ad or a link and reaches a page designed to answer only what matters about that offer: what it is, who it is for, what it includes, why it may be relevant and what to do next.

That next step could be booking a call, completing a form, sending a WhatsApp message, signing up or making a purchase.

A good landing page avoids sending someone through an entire website when we already know what they came to find.

WHEN IT MAKES SENSE

A landing may be enough if:

• You're trying out a new offer;
• you will send traffic from ads, social media, email or a QR code;
• you have a very specific service;
• you want to measure a campaign without mixing it with other things;
• the visitor needs little information before taking the next step.

EXAMPLE

A training center opens an Excel workshop for companies during October.

You don't need to rebuild your entire website to promote it. You can create a landing that explains the program, the dates, who it's intended for, and how to book.

In addition, a landing does not have to live in isolation: it can be part of the same domain and coexist with a corporate site. A company can use its website to explain the business and create specific landings for specific campaigns or offers.

WHEN IT IS NO LONGER ENOUGH

A landing page is no longer the best answer when visitors are likely to ask: What else do they do? Who are they? Do they have experience with this? Where can I see their other services? What if I still don't know exactly what I need?

If you need to answer all that, you're already trying to put a whole site inside a single page.

2. A corporate website: when the person needs to understand the business

A corporate site is not just a landing with more pages.

Its job is to give context to someone who is still evaluating their options.

It can include a home page, services, projects, FAQs, company information, resources and contact details. The goal is not to have lots of pages for their own sake. Each page should answer a real question.

It makes sense when:

• you offer several services;
• different customers come looking for different things;
• trust weighs before buying;
• you need to show jobs, processes or cases;
• you want to publish content that can be found in search engines;
• the customer normally compares several options before contacting you;
• you want a presence that remains useful beyond a single campaign.

EXAMPLE

A firm that offers accounting, payroll, taxes, and consulting should not attempt to explain everything in a one-off landing.

One person can come looking for taxes and another looking for payroll. Both need different paths, but they also want to check who is behind the business and how it works.

In that situation, a full website makes much more sense.

WHAT YOU DON'T NEED TO DO

Having a corporate site does not mean inventing pages just to look bigger.

A services page with six repetitive descriptions adds little value. A separate page for each service is worthwhile only when it helps explain differences, answer questions and guide customers.

The structure must grow because the business needs it, not because an agency has a ten-page package.

3. An online store: when selling involves more than showing products

Many people ask for an online store when what they really need is a catalog.

It's not the same.

A catalog can show products, photos, prices and a button to ask about them on WhatsApp. That can work well for a business that still confirms availability, customizes orders or takes payment another way.

A real online store adds a complete operation around the purchase.

The customer can normally:

• browse products;
• choose variants;
• add to cart;
• enter their details;
• choose delivery or pickup;
• pay or choose a payment method;
• receive confirmation;
• check their order information.

And the business has to figure out what's going on behind it:

• inventory;
• orders;
• payments;
• deliveries;
• taxes where applicable;
• refunds;
• notifications;
• customer service;
• product updates and prices.

That is the important point: a store is more than a website with products.

EXAMPLE

A gift shop that sells 20 products on Instagram and confirms every order on WhatsApp may not need a full e-commerce tomorrow.

It could start with a well-organized catalog that makes products easy to discover and request.

But if you already receive enough orders for the team to spend the day asking for address, variant, payment method and availability, a store with a structured purchase process begins to solve a real problem.

A USEFUL QUESTION

Do I want the person to be able to complete the purchase without someone on my team having to intervene in every order?

If the answer is yes, you probably need e-commerce.

If the answer is no, there can be a simpler solution.

4. A portal or web application: when users need to work with their own information

This is where the idea of needing a website begins to mean something else.

A portal is not only designed to read public information.

It usually exists because someone needs to sign in and do something based on their own account or information.

For example:

• a client signs in and checks the status of their project;
• downloads documents;
• uploads files;
• sends a request;
• approves a deliverable;
• reviews invoices;
• consult orders;
• updates information;
• reserves a service;
• sees information that should not be visible to other users.

That already looks more like software than an information page.

THE PRACTICAL DIFFERENCE

On a website, one hundred visitors can see the same service page.

In a portal, each client can enter and view different data.

That difference changes the project: it now needs accounts, permissions, security, data, statuses, notifications and business rules.

WHEN IT MAKES SENSE

A portal begins to be worthwhile when there is a repetitive process that today is distributed between mail, WhatsApp, spreadsheets, calls and loose files.

EXAMPLE

A service company regularly receives questions like: What is the status of my request? Can you resend the document? Where do I upload this file? Has my application been approved?

If these questions are a normal part of the operation, a portal can give the client direct access to that information and remove repetitive work from the team.

A WORD OF CAUTION

Having a login doesn't automatically turn an idea into a good project.

If the process occurs five times a month and an existing tool already solves it, building a custom system can be a bad investment.

First you have to understand the problem. Then you decide whether to use an existing tool, connect several or develop something of your own.

5. Sometimes you don’t need a new website

This option often gets left out of proposals, but it deserves consideration.

You may already have a website.

And the problem may not be that you need a new one.

Perhaps:

• it loads too slowly;
• it is difficult to use on mobile;
• people do not understand what your business does;
• its information is outdated;
• forms do not arrive where they should;
• important pages are hard to find on Google;
• updating it has become difficult;
• there are several tools that are not connected;
• the contact process has too many steps.

In such cases, redoing everything from scratch can be unnecessary.

Sometimes the best solution is to keep what works and correct what doesn't.

That may mean redesigning some sections, reorganizing content, improving performance, connecting a form to another tool, or adding a specific function.

Not every digital project needs to start with a demolition.

A simple way to decide

If you are still among several options, answer these questions in order.

1. Am I promoting a single offer to a fairly defined audience?

Yes: consider a landing page.

2. Does the person need to know several parts of my business before deciding?

Yes: You probably need a website with a more complete structure.

3. Do I want the customer to be able to buy and complete the order without talking to someone on my team?

Yes: evaluate an online store.

4. Do you need to log in, view your own information, or complete a recurring process?

Yes: you are talking about a portal or an application.

5. Is there already a tool that does 80% of what I need?

Yes: Before developing something from scratch, it is worth studying whether it can be configured or integrated.

6. Do I already have a website that does much of what is necessary?

Yes: Check first if an improvement is enough.

Five real-world examples

Case 1: A salon wants to appear on Google and receive bookings

It has several services, schedules, photos, location and frequently asked questions.

It probably needs a clear website showing its services and a simple booking or contact system. It does not need a custom app just because bookings happen online.

Case 2: A professional promotes specific advice with advertisements

The person arriving is already interested in that offer.

A well-focused landing can work better than sending it to a home page where there are six different services.

Case 3: A company sells uniforms, but each order is quoted according to quantity, embroidery and customization

Having products does not automatically mean needing cart and immediate payment.

An organized catalogue with a good flow of quotation request can be more useful.

Case 4: A store sells products at defined prices and receives many repetitive orders

If the customer can choose, pay and define delivery without prior negotiation, an e-commerce can remove friction and manual work.

Case 5: A company manages projects for clients and receives too many status requests

Here a portal can make sense because the problem is not to present the business. The problem is to give access to information and actions that change for each client.

A quick comparison

Before asking for a quote, prepare this

You do not need to start by asking for Next.js, WordPress or an app.

That decision comes later.

To have a much more useful conversation, try to answer:

• What do you want to accomplish?
• Who will use it?
• How does that person get to you today?
• What should that person be able to do?
• What does your team do manually afterward?
• What tools do you already use?
• What part of the process is giving you trouble?
• What would have to happen in six months for you to say it was worth it?

Those answers lead to a much better decision than starting with technology.

The best solution is not always the biggest

A landing is not a cheap version of a site.

A corporate site is not automatically better than a landing site.

A store is not necessary just because you sell products.

And a portal is not worthwhile just because user accounts and dashboards sound more professional.

The right solution does the job your business needs without making you pay for and maintain complexity that brings no value yet.

If you do not know what to call the thing you need, that is fine.

Start by explaining what you want to happen.

The technology comes later.

Next step