A large client wants one more feature: when an offer starts to belong to one customer
Separate an individual client adaptation from a change to a standard service, and assess maintenance and the public promise.
Article language: English

In this article
The report works for everyone until the most important client asks for a report of its own. The new layout looks sensible. The account manager knows the audience, the team can produce it and the client is willing to pay. The harder conversation begins months later, when the basic service changes but the individual version must still work as before.
Consider a fictional company that regularly checks displays at locations and sends clients the results. Its standard report presents observations, photographs and matters requiring clarification. A large chain operator wants a breakdown using its own regions and internal codes instead. This is an existing, repeatable service. The company must decide whether to produce a separate output for one account or change the standard used by everyone else.
There is no need to begin either by refusing or by being dazzled by the client's standing. First establish whether the request reveals a gap in the shared offer or comes from the chain's own organisation. Both can justify the work. They lead to different futures for the product, different maintenance duties and different descriptions of what the company sells.
Who else needs the outcome of the change?
The operator asks for a regional breakdown because managers must be responsible for their locations. That describes a need. Its own region codes and column order are already a proposed solution. The supplier should separate the two before treating the requested format as the basis for the entire service.
GitLab's product process handbook recommends identifying the problem and the way a requested feature would be used. It notes that a solution may already exist or another response may meet the need.
In our example, the shared need might be to distribute results among people responsible for groups of locations. Some customers divide them by region, others by brand or account manager. Putting one operator's codes in every report would create a problem for the others. An ability to assign responsibility, however, could merit separate investigation as part of the standard.
Write down two outcomes: what the operator wants to do with the report and what each subsequent customer will receive. If the second sentence says, “they will see our largest client's region names”, the company is still describing work for one account. It need not call that work development of the shared offer for it to have a commercial rationale.
Also check whether other organisations actually have a similar task. “Would a better report be useful?” settles little. Ask how they have handed over results: who receives them, what they compare and how they assign follow-up work. A similar department name does not guarantee the same use. Another customer may want grouping but need a completely different division.
A customer advisory council (in Polish) can help collect those perspectives. Group enthusiasm alone does not approve a standard change. The company must establish whether it can support the identified way of working as a repeatable service. A large client is entitled to explain its own needs well. It need not represent every future buyer as well.
If the material points to an individual need, a separate adaptation may be appropriate. If it reveals a shared task, test a solution across different uses. Both routes can begin with the same conversation. The difference appears in who the company intends to promise the result to later.
Payment for delivery does not answer the question of next year
The operator may pay for preparation of its report. What happens, however, when its organisation, location names or the basic method of assessing displays changes? A one-off job can create an ongoing duty to adapt the output. The company should identify it before accepting the proposal, not at the first dispute over an update.
In Hidden Costs, an essay in Getting Real, Basecamp's creators describe further work brought by a new feature: testing, support, presenting the product and checking existing promises. This is a practitioner perspective on their own approach to developing applications. It includes work on materials and service after a feature is added.
Trace two subsequent releases of our report. The company adds a new standard way to describe matters requiring clarification. Does the individual report receive it too? Does the operator want the old breakdown? Who checks that the result is consistent? Without answers, “we will support this format” includes an unknown that payment for preparation did not settle.
Examine the client's data separately. Region codes can change during the relationship. The operator should provide an identifiable, current basis for assigning locations. The supplier must know what to do when a code is missing or versions conflict. It should not quietly infer assignments from similar town names just to make the report look complete.
A useful division is maintaining the common method for assessing displays and preparing output in an individual layout. If the company cannot separate them in delivery, it has a dependency to investigate. The special report may require changing the service itself, although the client presented it as a cosmetic file addition.
A change in the scope of one service project (in Polish) helps assess delivery of a particular modification. Here there is also a decision about future work for all customers. Even a properly agreed extra assignment does not itself decide whether the company now sells a new standard or who maintains it.
Agree both the first deliverable and subsequent support. Answer an ordinary event: the operator changes regional divisions while the display-assessment method stays the same. Does the company update input data, prepare a new report or reopen the scope discussion? The terms of the relationship must reflect the chosen route.

In a modular service (in Polish), such boundaries may be planned in advance. Do not call any manual task a module merely because one account manager can perform it. If every change requires the team to rediscover the meaning of codes and repair the file, the company maintains an individual delivery method regardless of its name in the price list.
Name the end of the variant too. The operator may no longer need it, move to a new system or return to the standard report. The supplier should know what output and history it will hand over at the end. Ending further individual reports should not erase previously agreed access to work already completed.
A large client can help development, but size does not make the decision
Research on major customer relationships does not produce one simple slogan. Check what was measured, the market sampled and the relationship described. Do not look for a percentage at which every company should stop listening to a client. Our decision concerns a particular request and its place in our own offer.
Krolikowski and Yuan studied US firms from 1980 to 2005 in a 2017 publication. The original abstract in the author's university repository distinguishes customer concentration, the share of sales held by a small number of buyers, from their bargaining power and associates them with different innovation outcomes. It does not assess customised reports or small Polish service firms. It does show why a large customer's share alone does not describe the whole relationship.
Li, Yang, Li and Geng used data from Chinese manufacturing companies for 2013-2022 in a 2026 study. Their original abstract deposited at Cardiff separately analyses supplier and customer concentration in relation to open innovation, which involves cooperation with outside organisations. The relationships also depend on company characteristics and network position. This is a different research question from evaluating our single request.
In practice, look at how the client affects the order of work. Does it request a result and leave the company to choose how to achieve it? Or does it expect to approve every future change to the basic service? The second expectation may move control over the offer much further than ordering one extra format.
There is no need to assume bad intentions. The operator may have its own implementation deadline and legitimate needs. The supplier is responsible for reconciling them with its other commitments. When setting priorities for a limited team (in Polish), identify the work displaced by the adaptation. “We'll fit it in” hides the choice rather than making it.
If the company wants to promise everyone both quick delivery and arbitrary individual changes, check whether those promises fit its way of working (in Polish). A large customer's request may reveal a broader contradiction in the model. The decision then concerns the limits of the whole offer, not just funding that customer's report.
Also examine decisions within the company. The account manager may know the operator's need well but not own the common reporting standard. The person developing the service may understand dependencies but not know what has already been promised. They need a shared description of the request and the current agreements before the customer hears different answers.
The company may conclude that developing the standard is justified. It should then specify what from the original request becomes part of the common offer and what remains the customer's own layout. A new ability to group locations need not transfer all of its labels. That separation lets the company learn from a customer without copying the customer's whole organisation into the product.
Test it on the next order. A new client wants to group locations by type of display while the operator still needs regions. If the shared part of the service can produce results for both, the company has a basis for further assessment of the standard. If serving the new client requires rewriting rules designed solely for the operator, the first implementation remained an adaptation. Describing it as flexible reporting on the website does not change that dependency. A new tab in a file does not assign someone to maintain it.
The company can also choose to maintain an individual variant. It is not worse simply because it does not suit everyone. It needs an identifiable scope, an update method and a place in the team's work. The problem arises when a private exception begins to govern all deliveries while the company still presents it as a one-off courtesy.
The next client should recognise the standard too
After the decision, check the offer page. If the company announces “a report adapted to the client's organisation”, a new buyer may expect the same amount of individual work as the large operator. The sentence should match what the company really intends to provide. An old exception should not accidentally become a public promise.
Aeneia Design helps present the approved distinction in the site's structure and copy. The input needed is a standard scope and an identified individual variant. Only then can the page explain what a customer chooses independently and what requires a conversation before agreeing to work together.
Keep a route to the basic version in the catalogue too. A detailed description of special reporting may lead a smaller client to ask for a solution it does not need. Let the buyer recognise the normal output and the point at which an additional conversation makes sense. The level of detail should serve the purchase decision.
Simplifying a product range (in Polish) raises a similar question about the role of a rarely selected variant. Here, however, the special version may only be emerging. Establish its place before the offer grows into several options understood only by the team that remembers each customer's history.
Before answering the operator, walk through a future month: the standard changes, a region is divided and an ordinary client orders the basic report. Ask the team what must be done in each case and who resolves uncertainty. If everything leads to one person quietly correcting files, you have identified work that needs an agreement.
The answer might be: we will prepare a separate output for this account, develop a defined part of the standard, or return with a different way to meet the need. Any of these decisions may be sensible. What matters is that the company knows what it will sell and support after the first extra job is done.








