Does the Website Work on Sundays?

I remember that day vividly. We were discussing a new website for a company. Everything was going smoothly — domain, hosting, design, content from the client. At one point, while going over the details, came the question:

“Will the website… work on Sundays?”

For a split second, I hesitated, unsure if I’d heard correctly. But I looked at the client — genuinely concerned, convinced this was a very important question.

Why Was Sunday So Important to the Client?

Then I understood. For him, Sunday wasn’t a typical rest day. His business operated mainly on weekends — that’s when customers searched for info, booked appointments, asked questions. In his world, Sunday was like Monday for others — a key business day.

I calmly explained that websites work all the time. Day and night. On holidays, weekends, even when we’re asleep or barbecuing in the garden.

How Does a Website Work 24/7?

Then I elaborated. A website runs not because my computer — or the client’s — is always on. It works because we purchase hosting — a space on a server that runs continuously.

Thanks to this, regardless of whether the business owner is celebrating a birthday or on holiday, the website remains online.

That’s why the quote includes both “hosting” and “domain”.

  • Without a domain, the site wouldn’t have an address to be found at.
  • Without hosting, there would be no space for it to exist physically.

Hosting is like the house, and the domain is the address. Together, they ensure the site is available seven days a week, twenty-four hours a day, three hundred and sixty-five days a year.

My Past Lesson — Never Assume Anything

That conversation reminded me of another situation — from early in my career. Back then, I believed the more I did for the client “as a bonus,” the better.

Once, while building a site, I set up SEO, submitted it to Google, and prepared all the marketing tools in advance.

I was proud. Until I learned the client had a contract with a marketing agency responsible for all of that. My good intentions caused confusion and unnecessary complications.

It was a valuable lesson for me. A lesson that you should never assume things on your own. That you must ask. And that it’s better to do less, but exactly what was agreed, than to do more and cause issues.

What’s Included in My Standard Quote?

Today, when preparing a quote, I clearly define the scope of basic work:

  • WordPress installation,
  • hosting setup,
  • layout design,
  • insertion of client-provided content,
  • site publication under the provided domain.

Just that — and already a lot.

All additional items — such as SEO optimisation, Google submission, backups, training, user accounts, or blogging — are separate services agreed individually.

This approach makes the cooperation fair and transparent. No misunderstandings. No unnecessary disappointments.

Why It’s Worth Asking Questions

That’s why I always say:

  • If you need something — ask.
  • If you’re unsure — ask.
  • If something seems obvious — ask anyway.

Good questions build the best websites. They build the best collaborations. They help both sides truly understand each other.

A List of Questions Worth Asking Before Building a Website

To make this easier, I’ve prepared a simple checklist — questions to ask your website developer before you start working together.

Not to quiz them like in school, but to ensure both sides are on the same page from the very beginning.

  • What platform will the site be built on?
  • If WordPress: why was WordPress chosen?
  • If HTML: does the site require maintenance and updates?
  • Will I have access to a content management panel?
  • Will the site be mobile-friendly?
  • Will I receive training on using the site?
  • Will you assist in editing or preparing content?
  • Will the site be optimised for speed?
  • Will you perform basic SEO optimisation?
  • Will the site be submitted to Google?
  • Will the site be protected against attacks?
  • Will you set up regular backups?
  • Will I be able to update the site and plugins myself?
  • What kind of technical support is available after launch?
  • Are extra features (e.g. blog, store) included in the price?
  • What is the policy for design revisions?
  • What will the ongoing costs be after a year?
  • Will the site comply with GDPR regulations?
  • Can I rely on your support in case of issues?

Final Thoughts

Remember:
Asking questions isn’t a sign of ignorance. It’s a sign of professionalism.

The more you know from the start, the better your website will perform — on Monday, Wednesday, and of course, on Sunday.