Skip to content
Interface language: English
Imperium / Signal

A client returns after two years: the old proposal does not know their business today

When a client returns after a break, their business may need a different service. Check the goal, people and current scope, using the history without copying old agreements.

Article language: English

Concept illustration: a woman rests her hands on the outer two of three round discs mounted on an axis in a navy and red interior.
In this article

“Can you do the same thing you did last time?” It is easy to say yes, find the old proposal and change the date. The harder question is which parts of the previous situation still apply. Two years later, the same company name may lead to a different team, a different group using the service and a different task. Knowing the history helps start the conversation. It does not automatically bring that history up to date.

Imagine a studio that runs presentation workshops for companies receiving a message from a former client. Last time it worked in person with one group of salespeople. Now a new contact in employee development is writing. The company has teams in several locations, and the participants need to prepare presentations for different audiences. The message still says “the same workshop”. The studio needs to establish what, in fact, is the same.

Return to the reason for the enquiry

The first reply can acknowledge the history while opening a current question: “We remember the workshop for your sales team. What does the group need to prepare now, and in what situations will they use it?” There is no need to pretend this is a first meeting with an unfamiliar company. Nor is it useful to confirm the old scope before anyone has described the present need.

In the abstract of a 2015 study by Kumar, Bhagwat and Zhang, previous experiences, the reason for leaving and the type of win-back offer were associated with different outcomes when service relationships resumed. Having been a customer before did not provide a complete account of the situation. We cite that distinction without treating the abstract as a recipe for winning back a particular client or a promise of revenue.

At our studio, first check why there was a break in contact. The previous group may have completed its task. It may have changed providers or stopped using workshops after a reorganisation. The new contact may not know. Do not force them to judge their predecessors’ decisions. Use what the history tells you, and establish what matters to the current order.

If the earlier task was completed well, do not present the return as a repair of a lost relationship. The end of a client’s need and the loss of a client (in Polish) call for different descriptions. A new enquiry may simply be the start of another task. The team does not then need to apologise for two years of silence or offer a special rescue programme nobody needs.

If a real problem remains, however, keep it visible alongside the new need. A contact person can change faster than participants’ memories of the earlier work. Repairing a relationship after a service mistake (in Polish) requires naming the mistake and taking appropriate action. Do not hide it beneath a new proposal, but do not assume a problem exists every time a client returns.

The company remembers, but its people may remember something different

In a 2022 study, Poblete and co-authors examined the reopening of a Swedish mine after a break. They showed how both old and new relationships contributed to rebuilding its business environment. This was a single case study. Existing connections remained an asset, but reopening did not mean simply switching the entire old network back on unchanged.

At the workshop studio, the contact history may point to someone who knew the previous group well. Check whether that person is still involved. The record does not automatically confirm their current role. The former account manager may work in another department, while the person sending the message may only be gathering options for someone else who will decide the scope.

Ask who will use the service, who will help prepare the material and who will agree on the choice. This does not have to become an elaborate organisation chart. It is enough to identify the people needed for the current task. If one manager agreed everything in the previous engagement, do not assume their successor has the same authority or knows the earlier arrangements.

Prepare a short reminder of the previous scope in terms the new contact can use. The workshop name, the group and the intended outcome will be more helpful than a long chain of old correspondence. Mark which information relates to the past assignment. A returning client should be able to benefit from the provider’s memory without inheriting every old shorthand and meeting joke.

The old proposal is a point of comparison

Open the previous scope and compare it with the current task. In-person work with one group does not explain how to organise sessions for teams in different locations. Old presentation examples may not fit the new audiences. An existing exercise may still be useful, but assess it against what participants need to do now.

Do not change everything simply because two years have passed. Common elements can save both sides preparation. Record what can be kept, why it is suitable and what needs to be agreed again. That differs from copying the old proposal and adding “scope unchanged”. In that case, the lack of discovery would disappear beneath a sentence that looks like a considered decision.

For a larger change, consider the limits of adapting a modular service (in Polish). The studio could retain its way of preparing participants’ work while considering a different subject or delivery format separately. It should not promise the same outcome after removing a component needed to achieve it. The name of the old package does not settle that question.

Aeneia conceptual photography

Also agree on the current preparation conditions. Does the client have sample presentations? Can they be used with this group? Who will choose them and confirm what material is needed? An answer from two years ago may not cover new content or new people. Settle this concrete issue before the work rather than assuming the previous engagement makes all the same preparation possible.

In conversation, the studio learns that the current group no longer prepares sales meetings. It needs to present its own work to colleagues in other departments. The exercise for organising a presentation can stay, but the old examples of customer questions do not fit this use. The request for “the same workshop” turns out to refer to the way of working, not confirmation of identical content. That distinction could not have been read from the archived file alone.

A note before preparing the proposal could therefore say: keep work on each participant’s presentation; select the speaking situation and examples again; the organisation of a shared exercise for people in different locations remains undecided. The client can see what follows from the current goal and what is still a question. The studio can plan to clarify the final point before promising a finished agenda.

Keep the history without copying old promises

HubSpot’s documentation on creating records, updated on 2 September 2026, describes linking a new record to existing ones and adding earlier activities. A new matter can therefore use the history without being treated as the old assignment. The user still has to select the history needed for the new task.

Whatever the tool, keep the current work’s arrangements separate. The former scope can remain available for comparison. Record the present goal, people and conditions as current, making clear what has been confirmed. Cleaning up a company and contact database (in Polish) raises a similar need to establish an entity’s identity. Here, there is the additional distinction between the relationship’s history and the content of a new order.

Check information that may be out of date. A contact at an old domain, a department name and the person approving materials may all need confirmation. Do not overwrite the historical role as though it had always been different. The record of the previous assignment should describe that assignment. New information should support the current work while leaving the earlier course of events understandable.

Pay particular attention to automated confirmations. If a system sends the old preparation instructions or directs a returning client to a former account manager, it can make a promise that conflicts with the current conversation. Follow the ordinary enquiry path and check the message the recipient actually receives. A correct note in a salesperson’s record does not automatically change a notification sent from elsewhere.

Check changes on your own side too. The workshop may previously have been led by a specialist who no longer works at the studio. Available formats and material preparation may also have changed. Before referring to the client’s earlier experience, establish which elements you can provide today. A client’s return does not freeze a provider inside their best memory from two years ago.

If the former facilitator is important to the request, discuss it openly. You can introduce the current person, their role and how they will prepare, instead of leaving the impression that the team is identical. Likewise, the old price related to the scope and conditions at the time. Explain the basis of the current task in the new proposal instead of treating the archived figure as confirmation of the price for changed work.

A returning client should not have to pass a test on their own history

On the website, allow a company to indicate that it has used the service before and give a short reference to the earlier engagement. Do not make a project number the only route to an enquiry when the client may not have it to hand. The team needs a way to identify the matter and understand the present task. The former relationship should make the beginning easier, not turn the form into a memory test.

Aeneia Design can help design that return path and organise the description of current service options. The questions on the site should collect what the team needs to start a conversation. They do not have to demand a full brief or suggest that the former package has already been ordered again. Discovery and confirmation of scope have their own place later in the conversation.

Also provide a route for someone who remembers the former account manager but no longer has their contact details. A short message on the current website should reach a team able to find the history. Do not make the client repeat an enquiry through several channels simply because the name in an old email signature no longer leads to the right inbox. Maintaining that continuity is a separate task from confirming the scope of the next workshop.

After the first conversation, send a short summary: the current task, the part of the former scope being retained and the issues that need a new agreement. A B2B client relationship review (in Polish) can later help assess the ongoing relationship. On return, the first need is a shared basis for starting it under current conditions.

At our studio, discovery may lead to retaining some proven exercises and changing how the group prepares. It may also reveal that the client needs a different kind of work. Both answers are more useful than immediately restarting the old proposal. Before entering a new date, ask what the service needs to make possible today. History can suggest better questions if you do not let it answer for the client.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear