Your client works on your service too: count their effort before calling it convenient
Identify the time, preparation and decisions a client contributes before and after a service, and distinguish necessary participation from shifted work.
Article language: English

In this article
In a hypothetical company photo session, the photographer works for half a day. The client's coordinator has spent a week collecting availability, booking a room, explaining expectations and chasing a missing list of names. The supplier's time is visible. The client's time is scattered across a calendar and several conversations, so it has almost disappeared from the service description.
Yet convenience also depends on that work. The client collects materials, makes choices, brings participants and later uses the photos. Some participation is necessary because only their organisation knows its own decisions. Other work may come from unclear requests, repeated data entry or responsibilities passed over without explanation. Recognising the difference allows a more honest service design.
The service starts before the supplier arrives
Imagine the coordinator receives a message: “Please prepare everything as for a standard session.” The photographer knows what that means. The recipient is ordering such work for the first time. She must find out which room to choose, who should attend and what a finished list means. A short message convenient for the supplier has created several unknowns on the other side.
You cannot remove every client decision. Someone must identify the people and purpose of the photos. You can explain what information is for, what form it needs and when to provide it. The coordinator should understand the task without knowing the studio's internal vocabulary. A professional service should not require a client to guess the definition of professionalism.
Walk through your own offer from the moment someone begins considering it. What must they read, whom must they ask and what must they find before ordering? If choosing a package requires information available only after purchase, there is a dependency to explain. The form may work perfectly while the decision remains impossible.
In their 2007 SERVCON research, Seiders, Voss, Godfrey and Grewal consider service convenience through perceived time and effort at different stages of purchase and use. They developed a multidimensional scale and studied it in retail. We do not transfer those results to B2B photo sessions; the useful point is to look beyond the moment of the main work.
In our example, a fast photo session does not answer how much coordination was needed to gather the team. You do not have to convert every action into money. First see who performs it and why. If you cannot identify the task requiring a field or attachment, ask whether the request is needed at all.
Necessary participation and work shifted for the supplier's convenience
Divide activities according to who has the knowledge and ability to act. The client knows when their people are available. The photographer knows what is needed to prepare the session. A decision about the client's organisation may require the client's participation. Asking them to retype data already supplied into another template is a different matter.
In the fictional project the coordinator supplied a list of people when ordering, but before the session receives a new file with the same fields in another order. The supplier's team uses it internally. That alone does not justify making her do the work again. First check whether the existing information can be reused and only changes confirmed.
Point two of the UK Service Standard recommends reducing situations in which users give government the same information again and coordinating across organisations around the whole task. It is guidance for public services. A commercial supplier can ask a similar question about its own requests without treating the standard as an obligation on every business.
Some tasks can be done on either side. The coordinator may label files with names herself, or the studio may offer that work after receiving an approved mapping of people. Do not hide the choice. The client should know whether they are buying organised materials or must organise them after receiving the photos.
Also check decisions the supplier should not make for the client. Choosing a team representative may depend on internal agreements. The photographer can help show the options but cannot replace the authorised person in approving the choice. Make it possible for the right person to approve it efficiently.
A service map showing frontstage and backstage work (in Polish) can name visible actions and work outside direct contact. Add the recipient's perspective: what must they do before the supplier takes its next step? Without this, a service description may look complete from only one side.
Time alone does not show the whole burden
Two requests may take a similar number of minutes but require different effort. One involves sending an existing file. The other requires a choice to be agreed with several people, bringing waiting, reminders and conflicting comments. Do not reduce the difference to form-filling time.
The coordinator may complete a task quickly because she knows the company and prepared the information earlier. A new person might need extra conversations. Observing one smooth journey does not prove it will be equally easy for everyone. Account for different levels of preparation instead of treating difficulty as a client's personal failing.
Record waiting time separately from active work. Over two days a client may wait for confirmation while making only a brief call. In the same period they might instead collect several additions from different departments. These are different burdens. If merged into one number, you cannot see whether the sequence or the amount of work needs improvement.
Do not automatically add several people's contributions together as the duration of the service. Parallel preparation can burden the organisation without extending the deadline by the same amount. Conversely, a short action by a decision-maker can hold up the next stage. Preserve both people's effort and calendar dependencies without false precision.
These distinctions matter when measuring work time with AI (in Polish) too. Here, however, the viewpoint is the client's. If the studio automates its own stage, check whether the recipient must now prepare an additional data structure. Shorter supplier work can coexist with longer order preparation.

Do not immediately call that a deterioration. A client may knowingly choose greater participation in exchange for a different service scope. They should learn about the dependency before buying. The problem arises when the description promises simplicity but necessary tasks emerge one by one only after the order, making it hard to plan the team's participation.
Look at the work between messages
A supplier usually sees what the client sent and what has not arrived. The preparation path is less visible. In our example, the list of names passes through the coordinator, managers and participants. “One field is missing” can restart those conversations. Learn that consequence before sending another similar request.
Invite the client to walk through one completed case. Do not ask only whether collaboration was convenient. Ask what had to be found, whom they consulted and what had to be revisited after a correction. Such questions can reveal work that disappears from an overall rating because the client treats it as inevitable when ordering.
Watch for quiet workarounds too. The coordinator may alter the template herself, call a studio acquaintance or write extra instructions for colleagues. The order ends correctly, but partly because of work invisible to the supplier. This need not become an accusation. Check what repeats for other clients and deserves a change in service.
A client returning with the same question (in Polish) is therefore only one signal. No further contact does not establish convenience. The client may have solved the problem alone, abandoned part of the task or asked someone else. Assess the process itself, not just messages arriving at your team.
When choosing a change, check its effect on both sides. One joint request for all materials may reduce interruptions, but may also require data the client does not yet know. Explaining the order earlier may help more than a larger form. The solution should reflect the actual dependencies of the task.
For one session keep a simple history: the studio's request, the coordinator's action and the people she had to consult. When the same information is requested again, note whether the data changed or only the format required by the supplier. This shows which actions respond to a new situation and which repeat completed work.
Compare the next order on a similar scope. One team's session and photographs of people across several branches require different organisation. If the second needed more coordination, do not attribute the entire difference to a new form. Check what changed and how it affected the client's particular task. You do not need a seemingly precise average for every possible session to notice repeated retyping of the list.
After that investigation choose one change to test: reuse an existing list, clarify a request or move it to the right time. State which work the client should no longer have to repeat. That is more useful than a general instruction to make service friendlier.
Self-service does not remove the client's participation
In our scenario the studio could offer a photo-selection portal. The client would no longer need to describe every file in an email. They would still need to identify who approves the selection and which materials are ready to use. The technical feature helps with one action; it does not make every surrounding organisational decision.
When considering self-service and a named adviser (in Polish), identify when a conversation is needed. The scope may be unclear or several people may have conflicting comments. A button does not remove that need. On the other hand, a mandatory call for every small correction may create extra work for both sides.
Compare two hypothetical journeys. In the first the client selects materials and immediately sees what will be passed on. In the second they must ask what labels mean and, after selecting, wait for confirmation that they did the right thing. Both use the same type of portal. Effort also depends on the information and organisation around the tool.
Do not judge independence solely because the supplier did not intervene. If the coordinator spent an evening explaining the rules to colleagues, some service work moved into the client's organisation. That may be an agreed model, but it should be visible. The phrase “intuitive portal” does not document the work, however neatly it fits a headline.
The result still has to be used
After the session the company receives photographs. Can the purchaser identify the right files, pass them to the team and find information needed for later use? That is further client work. The order scope should explain what the studio prepares and what the organisation must organise itself. Receiving a link is not the same as using the material.
Consider returning after time has passed too. The coordinator may change roles and a new person may look for the earlier agreements. If reconstructing the order requires searching private correspondence, the visible duration of the main session did not describe the whole service experience. Clear labelling of scope and the place where agreed information is delivered can make the result easier to understand.
In a B2B client relationship review (in Polish), ask about work after acceptance as well. What was used, what required more preparation and which question returned to the organisation? Not every comment means expanding the offer. Sometimes it is enough to explain earlier what result the client receives and how to identify it.
Aeneia Design can use this picture to develop the offer structure, information needed before contact and the route to appropriate help. Start with how the service is actually used. Instead of promising general ease, a page can show what the client must prepare and where they can get an answer.
For our studio, a first improvement might be an agreed preparation list sent at the right time and reuse of data already provided at order. At the next order, check whether the coordinator can prepare materials without further explanation and whether the studio uses information already supplied. Only that journey will show whether the work disappeared or merely acquired a new name in the portal.








