[et_pb_section fb_built=”1″ _builder_version=”4.16″ global_colors_info=”{}”][et_pb_row _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.16″ custom_padding=”|||” global_colors_info=”{}” custom_padding__hover=”|||”][et_pb_text _builder_version=”4.16″ background_size=”initial” background_position=”top_left” background_repeat=”repeat” global_colors_info=”{}”]<\/p>\n
I remember that day vividly. We were discussing a new website for a company. Everything was going smoothly \u2014 domain, hosting, design, content from the client. At one point, while going over the details, came the question:<\/p>\n
\u201cWill the website… work on Sundays?\u201d<\/p><\/blockquote>\n
For a split second, I hesitated, unsure if I\u2019d heard correctly. But I looked at the client \u2014 genuinely concerned, convinced this was a very important question.<\/p>\n
Why Was Sunday So Important to the Client?<\/h2>\n
Then I understood. For him, Sunday wasn\u2019t a typical rest day. His business operated mainly on weekends \u2014 that\u2019s when customers searched for info, booked appointments, asked questions. In his world, Sunday was like Monday for others \u2014 a key business day.<\/p>\n
I calmly explained that websites work all the time. Day and night. On holidays, weekends, even when we\u2019re asleep or barbecuing in the garden.<\/p>\n
How Does a Website Work 24\/7?<\/h2>\n
Then I elaborated. A website runs not because my computer \u2014 or the client\u2019s \u2014 is always on. It works because we purchase hosting<\/strong> \u2014 a space on a server that runs continuously.<\/p>\n
Thanks to this, regardless of whether the business owner is celebrating a birthday or on holiday, the website remains online.<\/p>\n
That\u2019s why the quote includes both \u201chosting\u201d and \u201cdomain\u201d.<\/p>\n
\n
- Without a domain, the site wouldn\u2019t have an address to be found at.<\/li>\n
- Without hosting, there would be no space for it to exist physically.<\/li>\n<\/ul>\n
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.<\/p>\n
My Past Lesson \u2014 Never Assume Anything<\/h2>\n
That conversation reminded me of another situation \u2014 from early in my career. Back then, I believed the more I did for the client \u201cas a bonus,\u201d the better.<\/p>\n
Once, while building a site, I set up SEO, submitted it to Google, and prepared all the marketing tools in advance.<\/p>\n
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.<\/p>\n
It was a valuable lesson for me. A lesson that you should never assume things on your own<\/strong>. That you must ask. And that it\u2019s better to do less, but exactly what was agreed, than to do more and cause issues.<\/p>\n
What\u2019s Included in My Standard Quote?<\/h2>\n
Today, when preparing a quote, I clearly define the scope of basic work:<\/p>\n
\n
- WordPress installation,<\/li>\n
- hosting setup,<\/li>\n
- layout design,<\/li>\n
- insertion of client-provided content,<\/li>\n
- site publication under the provided domain.<\/li>\n<\/ul>\n
Just that \u2014 and already a lot.<\/strong><\/p>\n
All additional items \u2014 such as SEO optimisation, Google submission, backups, training, user accounts, or blogging \u2014 are separate services agreed individually.<\/p>\n
This approach makes the cooperation fair and transparent. No misunderstandings. No unnecessary disappointments.<\/p>\n
Why It\u2019s Worth Asking Questions<\/h2>\n
That\u2019s why I always say:<\/p>\n
\n
- If you need something \u2014 ask<\/strong>.<\/li>\n
- If you\u2019re unsure \u2014 ask<\/strong>.<\/li>\n
- If something seems obvious \u2014 ask anyway<\/strong>.<\/li>\n<\/ul>\n
Good questions build the best websites. They build the best collaborations. They help both sides truly understand each other.<\/p>\n
A List of Questions Worth Asking Before Building a Website<\/h2>\n
To make this easier, I\u2019ve prepared a simple checklist \u2014 questions to ask your website developer before you start working together.<\/p>\n
Not to quiz them like in school, but to ensure both sides are on the same page from the very beginning.<\/p>\n
\n
- What platform will the site be built on?<\/li>\n
- If WordPress: why was WordPress chosen?<\/li>\n
- If HTML: does the site require maintenance and updates?<\/li>\n
- Will I have access to a content management panel?<\/li>\n
- Will the site be mobile-friendly?<\/li>\n
- Will I receive training on using the site?<\/li>\n
- Will you assist in editing or preparing content?<\/li>\n
- Will the site be optimised for speed?<\/li>\n
- Will you perform basic SEO optimisation?<\/li>\n
- Will the site be submitted to Google?<\/li>\n
- Will the site be protected against attacks?<\/li>\n
- Will you set up regular backups?<\/li>\n
- Will I be able to update the site and plugins myself?<\/li>\n
- What kind of technical support is available after launch?<\/li>\n
- Are extra features (e.g. blog, store) included in the price?<\/li>\n
- What is the policy for design revisions?<\/li>\n
- What will the ongoing costs be after a year?<\/li>\n
- Will the site comply with GDPR regulations?<\/li>\n
- Can I rely on your support in case of issues?<\/li>\n<\/ul>\n
Final Thoughts<\/h2>\n
Remember:<\/strong>
\nAsking questions isn\u2019t a sign of ignorance. It\u2019s a sign of professionalism.<\/p>\nThe more you know from the start, the better your website will perform \u2014 on Monday, Wednesday, and of course, on Sunday.<\/p>\n
[\/et_pb_text][\/et_pb_column][\/et_pb_row][\/et_pb_section]<\/p>\n","protected":false},"excerpt":{"rendered":"
A real story (with a twist of humour) about a client who asked: \u201cWill the site work on Sundays?\u201d The answer reveals much more than uptime.<\/p>\n","protected":false},"author":1,"featured_media":1453,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"on","_et_pb_old_content":"
I remember that day vividly. We were discussing a new website for a company. Everything was going smoothly \u2014 domain, hosting, design, content from the client. At one point, while going over the details, came the question:<\/p>\r\n\r\n
\u201cWill the website... work on Sundays?\u201d<\/blockquote>\r\n\r\nFor a split second, I hesitated, unsure if I\u2019d heard correctly. But I looked at the client \u2014 genuinely concerned, convinced this was a very important question.<\/p>\r\n\r\n
Why Was Sunday So Important to the Client?<\/h2>\r\n\r\n
Then I understood. For him, Sunday wasn\u2019t a typical rest day. His business operated mainly on weekends \u2014 that\u2019s when customers searched for info, booked appointments, asked questions. In his world, Sunday was like Monday for others \u2014 a key business day.<\/p>\r\n\r\n
I calmly explained that websites work all the time. Day and night. On holidays, weekends, even when we\u2019re asleep or barbecuing in the garden.<\/p>\r\n\r\n
How Does a Website Work 24\/7?<\/h2>\r\n\r\n
Then I elaborated. A website runs not because my computer \u2014 or the client\u2019s \u2014 is always on. It works because we purchase hosting<\/strong> \u2014 a space on a server that runs continuously.<\/p>\r\n\r\n
Thanks to this, regardless of whether the business owner is celebrating a birthday or on holiday, the website remains online.<\/p>\r\n\r\n
That\u2019s why the quote includes both \u201chosting\u201d and \u201cdomain\u201d.<\/p>\r\n\r\n
\r\n
- Without a domain, the site wouldn\u2019t have an address to be found at.<\/li>\r\n
- Without hosting, there would be no space for it to exist physically.<\/li>\r\n<\/ul>\r\n\r\n
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.<\/p>\r\n\r\n
My Past Lesson \u2014 Never Assume Anything<\/h2>\r\n\r\n
That conversation reminded me of another situation \u2014 from early in my career. Back then, I believed the more I did for the client \u201cas a bonus,\u201d the better.<\/p>\r\n\r\n
Once, while building a site, I set up SEO, submitted it to Google, and prepared all the marketing tools in advance.<\/p>\r\n\r\n
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.<\/p>\r\n\r\n
It was a valuable lesson for me. A lesson that you should never assume things on your own<\/strong>. That you must ask. And that it\u2019s better to do less, but exactly what was agreed, than to do more and cause issues.<\/p>\r\n\r\n
What\u2019s Included in My Standard Quote?<\/h2>\r\n\r\n
Today, when preparing a quote, I clearly define the scope of basic work:<\/p>\r\n\r\n
\r\n
- WordPress installation,<\/li>\r\n
- hosting setup,<\/li>\r\n
- layout design,<\/li>\r\n
- insertion of client-provided content,<\/li>\r\n
- site publication under the provided domain.<\/li>\r\n<\/ul>\r\n\r\n
Just that \u2014 and already a lot.<\/strong><\/p>\r\n\r\n
All additional items \u2014 such as SEO optimisation, Google submission, backups, training, user accounts, or blogging \u2014 are separate services agreed individually.<\/p>\r\n\r\n
This approach makes the cooperation fair and transparent. No misunderstandings. No unnecessary disappointments.<\/p>\r\n\r\n
Why It\u2019s Worth Asking Questions<\/h2>\r\n\r\n
That\u2019s why I always say:<\/p>\r\n\r\n
\r\n
- If you need something \u2014 ask<\/strong>.<\/li>\r\n
- If you\u2019re unsure \u2014 ask<\/strong>.<\/li>\r\n
- If something seems obvious \u2014 ask anyway<\/strong>.<\/li>\r\n<\/ul>\r\n\r\n
Good questions build the best websites. They build the best collaborations. They help both sides truly understand each other.<\/p>\r\n\r\n
A List of Questions Worth Asking Before Building a Website<\/h2>\r\n\r\n
To make this easier, I\u2019ve prepared a simple checklist \u2014 questions to ask your website developer before you start working together.<\/p>\r\n\r\n
Not to quiz them like in school, but to ensure both sides are on the same page from the very beginning.<\/p>\r\n\r\n
\r\n
- What platform will the site be built on?<\/li>\r\n
- If WordPress: why was WordPress chosen?<\/li>\r\n
- If HTML: does the site require maintenance and updates?<\/li>\r\n
- Will I have access to a content management panel?<\/li>\r\n
- Will the site be mobile-friendly?<\/li>\r\n
- Will I receive training on using the site?<\/li>\r\n
- Will you assist in editing or preparing content?<\/li>\r\n
- Will the site be optimised for speed?<\/li>\r\n
- Will you perform basic SEO optimisation?<\/li>\r\n
- Will the site be submitted to Google?<\/li>\r\n
- Will the site be protected against attacks?<\/li>\r\n
- Will you set up regular backups?<\/li>\r\n
- Will I be able to update the site and plugins myself?<\/li>\r\n
- What kind of technical support is available after launch?<\/li>\r\n
- Are extra features (e.g. blog, store) included in the price?<\/li>\r\n
- What is the policy for design revisions?<\/li>\r\n
- What will the ongoing costs be after a year?<\/li>\r\n
- Will the site comply with GDPR regulations?<\/li>\r\n
- Can I rely on your support in case of issues?<\/li>\r\n<\/ul>\r\n\r\n
Final Thoughts<\/h2>\r\n\r\n
Remember:<\/strong>
\r\nAsking questions isn\u2019t a sign of ignorance. It\u2019s a sign of professionalism.<\/p>\r\n\r\nThe more you know from the start, the better your website will perform \u2014 on Monday, Wednesday, and of course, on Sunday.<\/p>","_et_gb_content_width":"","footnotes":""},"categories":[5],"tags":[92,93],"class_list":["post-1506","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-media-en","tag-client-communication","tag-website-availability"],"_links":{"self":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/posts\/1506","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/comments?post=1506"}],"version-history":[{"count":0,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/posts\/1506\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/media\/1453"}],"wp:attachment":[{"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/media?parent=1506"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/categories?post=1506"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pawelopitek.com\/en\/wp-json\/wp\/v2\/tags?post=1506"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}