Notes / Siteworks
What should your service website explain about working together?
Help prospective clients understand their role, the work they receive and the dependencies that shape a service engagement.
By Edu Rigonato. Published Sep 28, 2026. 10 min read.
Imagine a business owner reading a website redesign page. The work looks strong. The services sound relevant. A process section moves neatly through discovery, design, development and launch.
The owner still has practical questions. Who writes the content? Will their team need to attend frequent meetings? Who has to approve the design? Does the proposed timeline include the time they need to collect photos and get feedback from colleagues?
Those questions concern the experience of buying and participating in the service. They deserve an answer before someone has to commit to a conversation.
A service website should explain the next step, what the provider does, what the client contributes or decides, what they receive, and what can change the timing. Put the essential explanation beside the service. Use a separate process page when it makes a substantial explanation easier to understand and maintain.
This is a practical way to set expectations. It is not a promise that adding a process section will increase conversions or eliminate project delays. The useful goal is simpler: let a prospective client recognize what working together would involve.
What does a prospective client need to know before booking?
Start with the commitments that could affect someone's decision to inquire. A person may like the proposed outcome while being unable to provide the access, information or attention the engagement requires.
For a website project, that might mean access to the current site, someone who can confirm business information, and a person responsible for collecting feedback. For a consulting engagement, it might mean access to relevant records and participation from people who understand the problem. A straightforward appointment-based service may need only a brief explanation of preparation and what happens during the visit.
Frequently asked questions
Should we list every document a client will need?
List the materials that affect whether someone can take the next step. Provide the detailed, project-specific checklist when it becomes relevant. Avoid asking visitors to gather or upload sensitive records merely to explore whether the service fits.
Who should be responsible for client feedback?
Explain how feedback will be collected and who can confirm a decision. The named person and exact arrangement can be agreed during scoping. Do not assume that everyone attending an introductory call has authority to approve the work.
What if we do not know the project duration yet?
Explain what you need to assess before confirming it, such as scope, material readiness and availability. Tell the client when that discussion will happen. Avoid borrowing a standard range from another provider.
How often should we review the process explanation?
Review it whenever the service, responsibilities or booking experience changes. Repeated questions from prospective clients can also identify places where the explanation needs attention. Check the service page, process page and booking copy together.
Explore Siteworks