How do I introduce a buyer to my web studio’s developers without losing them?

Decide who the key people are, and tell them yourself, early and privately. Do not let them learn about the sale from a client or a chat message. Explain what you know, what you do not yet know, and what stays the same. Silence feels worse than uncertain news, and developers talk to recruiters quickly.

Prepare the first meeting with the buyer. Let the buyer explain their plans for the team in their own words, and make sure nothing is promised that cannot be kept. People remember promises. Give each developer a chance to ask private questions, and ask the buyer afterward what they learned about the person’s role.

Then think about retention. Ask the buyer whether they will offer new terms, a bonus for staying through a transition, or a clearer role. A lawyer should draft any employment changes, and the seller should not make them alone. Keep daily routines steady during the sale, and name one person developers can come to with worries. Check in again after the first weeks, because worries often surface late. Ask the developers privately what would make them stay, and share what you learn with the buyer only with their permission. People answer honestly when they know where the answer goes.

Key takeaways

• Tell key developers yourself, before rumours do.
• Never promise what the buyer has not agreed to.
• Ask what retention terms the buyer will offer, and in writing.
• Name one person developers can bring worries to.