Do You Actually Need a Website? The Honest Answer to Expect From Anyone You Hire

A Small Task That Showed Me What My Job Really Is

A client on a small monthly agreement sent me one blog post to publish. It was a few minutes of work.

The agreement said publish it, so I could have published it, noted the time and been done. No one would have asked me for more.

But this client could not see what was happening across the rest of their site. They did not know which pages mattered, or whether something was quietly broken. So with their approval, I looked at the whole site instead of only the page I had just touched.

That is how I think about my work: I care about what the work is for, not only what I am paid for. I build in Webflow and in custom code, and the standard stays the same whatever the size of the agreement. That includes telling someone when a website is not what they need.

Filling Hours or Solving Problems

Some people hired to help with a website think: that is outside my paid hours, so it is not my job. There is nothing dishonest about that. They are doing what they were hired to do.

Others ask a different question: what is this meant to achieve for the business, and is it achieving it?

I try to be in the second group. A long-term relationship of trust is worth more to me than a single invoice. Clients often cannot judge a technical decision for themselves, so they rely on me to be honest, including when the honest answer is that they need less than they thought. I see that as part of the job, whether or not anyone is checking.

What It Looked Like in Practice

The audit was outside the agreement, so I asked for approval before starting and kept that time separate from the agreed work.

I used an AI tool to help me check everything, because on a large site one person can miss things. I looked at what affects how a site appears in Google and in AI answers: SEO, AEO, schema, links, and the image that shows when a page is shared. Then I sent a report of what I found, with an estimate for fixing it. The share images needed design, so I made them in Figma and gave the client the file to approve before I changed anything. Once the fixes were done, they received a final report.

The site is in much better shape now, and the client knows what was wrong and what to keep an eye on.

So, Do You Actually Need a Website?

Sometimes yes, sometimes not yet, and sometimes no. The answer depends on your goals, your customers and what you need the site to do, not on whether having a website feels like the thing a business should have.

A website usually helps when:

• People search for what you offer and you want them to find you.
• Customers who have never heard of you need a reason to trust you.
• You need something a social profile cannot do, like bookings, payments, a course area or a login.
• You want a place you control, instead of one that depends on another platform’s rules.

Social media or another platform may be enough when:

• Your customers already find you and message you there.
• You are still testing the idea and things may change.
• You mainly share updates and answer questions.
• Most of your work comes by word of mouth.

It becomes necessary as you grow when:

• You answer the same questions or take the same bookings by message every day.
• You want customers from outside your current circle.
• A platform changes how many people see your posts.
• Bigger clients or partners expect a proper place to check you out.

If you are not sure which group you are in, that is the right moment to talk to someone before you spend anything.

What an Honest Advisor Does

1. Tells you what you do not need

Sometimes the honest recommendation is less work, or none. Someone who answers “you need a website” to every question is selling, not advising. I would rather lose a job than have you pay for something that does not help.

2. Admits what they do not know

Nobody knows everything. The answer to look for is: “I do not know yet. Let me look into it and come back to you.” That is far better than a confident guess you pay for later.

3. Starts with your business, not the deliverable

Before they discuss tools, page counts or features, they should ask who your customers are, how those customers find you, and what you want to change. The right solution follows from those answers.

4. Uses AI without handing over the thinking

AI tools help me work faster. On sites I build in code, they speed up the writing. On Webflow sites I build by hand, using the Client-First structure so you can see what each class is for, and I use AI afterwards as a second pair of eyes, because a person can forget something.

But AI does not replace my judgment. I stay responsible for the decisions, the quality and the final result. Understanding your business problem matters more than which tool I use, so be careful with anyone who says AI makes those decisions unnecessary.

5. Keeps you informed and asks first

Anything outside the agreed scope should come with an estimate and your approval before it starts. Afterwards, you should get a written report of what changed. If you are paying, you should be able to see what you paid for.

Questions to Ask Before You Spend Anything

• Do I need a website right now, or would something simpler do?
• What problem do you think my business needs solved?
• Is there anything I was planning to buy that I do not need?
• What happens if something comes up outside our agreement?
• How will I know what you changed?
• What do you do when you do not know the answer?

Someone worth hiring will answer these easily, and will not mind that you asked. Sometimes the honest answer is that you need less than you thought, and that is worth knowing before you spend anything.