Does Your Business Need a Website?

Finding the Channels That Work for Your Business

The goal isn't to have a website. The goal is to reach the right people and give them a clear path to working with you. A website is one way to do that—but it's not the only way, and for some businesses, it's not the best starting point.

A Google Business Profile (GBP) puts you directly in front of people searching for what you do in their local area. It shows your hours, phone number, reviews, photos of your work, and lets you post updates. For a local service business, that's often exactly what a potential customer needs to make a decision. Yelp works similarly for certain industries. These platforms are free, well-trusted, and already have the audience.

The question worth spending time on is: where are your customers actually looking? If they're searching Google Maps for someone nearby, GBP is your priority. If they're browsing portfolios and comparing options before reaching out, a website makes more sense. Most established businesses eventually want both—but knowing which one to invest in first is worth thinking through.

What a Website Actually Needs from You

A website needs ongoing attention to stay useful—not technical attention, but content attention. Your services change. Your pricing changes. You add new work. You want to share something with your customers. A website that doesn't reflect the current state of your business gradually becomes less useful, simply because it stops being accurate.

That's the real maintenance question: not whether you can keep the server running, but whether you can keep the content current. If you have the time and interest to do that yourself, great. If your plate is full running your business, that's completely reasonable—and it's worth factoring in the cost of having a web developer manage the site month-to-month as part of what a website actually costs. For a lot of businesses, that arrangement makes a lot of sense.

On Having a Blog

A blog can be a genuinely valuable part of your site if you have things to say and the time to write them. Sharing expertise, helping customers understand your trade, answering common questions—that kind of content builds trust and helps people find you. If you're not in a position to produce it consistently, it's completely fine to skip it for now. You can always add it later when you're ready. A site without a blog is better than one with a blog that stopped two years ago.

If You Do Build, Plan Before You Touch Anything

The websites that hold up well over time are the ones where someone thought carefully about structure before anything was built. What pages do you need? What do you want people to do when they arrive? What does your brand look like, and does your site reflect that consistently?

These are much easier decisions to make before a site exists than after. Changing the fundamental structure of a website once it's live—especially once it's grown—is real work. Getting the architecture right at the start means you're not doing that work later.

If you're building on WordPress, a developer can help you set things up with proper content organization, custom post types, and taxonomies that scale cleanly as your business grows. If you're on something like Next.js, the same principle applies—early decisions have a long reach. Good advice at the start of a project is almost always worth it.

A Note on Using AI Tools

AI can be genuinely helpful when building or planning a website. It works best when you're specific about what you need and give it clear context—like the documentation for whatever platform you're working in. It doesn't carry knowledge between sessions, so treat each conversation as a fresh start and be explicit about what you're building. Used thoughtfully, it's a useful tool. Used as a substitute for understanding your own site, it can create problems that are harder to untangle later.

The clearer your plan, the more useful any tool — AI or otherwise — becomes. Vague input produces vague output. The thinking and research has to come first.

Key Takeaways