Upselling and best practices

Our goal is that you, as an agency, consider our client your client as well.We encourage our network to increase the number of assignments with current and new clients coming from Simbiosis.

For this reason, we share a guide of recommendations, best practices, and particular cases where we intend to maintain and improve the client relationship.

Recommendations and best practices ⭐

• Once kick-off emails are sent, store the client’s email.

- Introduce yourself as the agency representative who will keep track of the developer’s performance. Be open to scheduling calls to discuss concerns, questions, or anything related to the project and the developer.

• Schedule periodic 1:1s with the developer, especially during the first weeks of the assignment.

 - Ask for the developer’s sincere opinion on how they feel about the project, their team, and                 their leaders. This works as a way to have a proper follow-up with him/her, as well as to prevent situations where collaboration is put at risk.

• Reach out to the client and Simbiosis for any concerns or questions without hesitation, we’re all here to help.

            - Keep in mind, you can reach out to the client via the Simbiosis chat or via email by cc’ing   hello@simbiosis.team or pau@simbiosis.team for any specific concerns, questions, permissions (developer’s days off), or to request a meeting to discuss further.

• Be attentive and request feedback on the developer’s overall performance during the feedback sessions.

 - Be prepared prior to the meeting → Check the date when the developer started activities with the client, take a look back at the role expectations, preferably talk to the developer to know how he/she felt and make sure his/her activities are aligned with what was requested in the job description.

 - This way is easier to argue when much more is being requested to the developer or if there  is a work overload that falls beyond the developer's responsibility.

‍

What to avoid ⚠️

• Not keeping a record of the developer’s performance once assigned.
• Failure to maintain active communication with the developer
• Being unresponsive with Simbiosis or the client when needed.
• Not having regular meetings with the developer to review progress and solve concerns.

FAQ ❓

Can I reassign a candidate that resigned or was released from a project from Simbiosis in the past?The short answer is, it depends.

• If it’s for the same client, the following steps must be covered in order to evaluate if it’s convenient or not to move forward.

1. It would be necessary to speak with Simbiosis and understand the context of why the developer resigned in the first place.
2. Simbiosis will provide guidance on whether or not is convenient for the partner to open this request to the client.
3. If it proceeds, the partner should list out specific measures that will prevent the developer from abandoning the project, as well as solutions that would be taken into account in the event of a problem. *These measures should be shared and approved by Simbiosis prior to contacting the client.
4. After discussing with Simbiosis and receiving their approval (considering that the developer didn’t cause big trouble by leaving, nor left a bad experience for the client). Then, the agency can contact the client through the Simbiosis chat or via email and ask if they would consider having the developer assigned again along with the list of preventive measures.

*The partner may ask for the client’s email to Simbiosis and always include them in the email conversations.

5. The decision will be made under the client’s criteria, whether it proceeds or not.

• If it’s for a new client, follow the next steps.

1. Speak with Simbiosis and share the context of the reason why the developer resigned from his last project.
2. Simbiosis will provide guidance on whether or not is convenient for the partner to apply the candidate to a new project.
3. If it proceeds, Simbiosis will request the partner the specific measures that will be taken in order to prevent the developer from abandoning this new project. The partner will take full responsibility in a scenario where the developer is put at risk of exiting the project. Simbiosis will evaluate the measures and reserves the right to approve or reject the petition.
4. If Simbiosis approves the request, the partner can apply the candidate to a new project.

*The client reserves the full right on starting the hiring process with that candidate.

💡 Simbiosis reserves the right to deny the request at any point of the process, as well as to cancel, interrupt, suspend, or terminate the collaboration without prior notice, and without expression of cause.

Can I reassign a candidate that resigned or was released from a project from Simbiosis in the past?

The short answer is, it depends.

• If it’s for the same client, the following steps must be covered to evaluate if it’s convenient or not to move forward.

1. It would be necessary to speak with Simbiosis and understand the context of why the developer resigned in the first place.
2. Simbiosis will guide whether or not is convenient for the partner to open this request to the client.
3. If it proceeds, the partner should list out specific measures that will prevent the developer from abandoning the project, as well as solutions that would be taken into account in the event of a problem. *These measures should be shared and approved by Simbiosis before contacting the client.
4. After discussing with Simbiosis and receiving their approval (considering that the developer didn’t cause big trouble by leaving, nor left a bad experience for the client). Then, the agency can contact the client through the Simbiosis chat or via email and ask if they would consider having the developer assigned again along with the list of preventive measures.
5. *The partner may ask for the client’s email to Simbiosis and always include them in the email conversations.
6. The decision will be made under the client’s criteria, whether it proceeds or not.

*Simbiosis and the client may ask for additional tests, pre-screenings, or calls to validate the developer’s knowledge and professionalism

• If it’s for a new client, follow the next steps.

1. Speak with Simbiosis and share the context of the reason why the developer resigned from his last project. An investigation will be opened to understand the facts.
2. Simbiosis will guide whether or not is convenient for the partner to apply the candidate to a new project.
3. If it proceeds, Simbiosis will request the partner the specific measures that will be taken to prevent the developer from abandoning this new project. The partner will take full responsibility in a scenario where the developer is put at risk of exiting the project. Simbiosis will evaluate the measures and reserves the right to approve or reject the petition.
4. If Simbiosis approves the request, the partner can apply the candidate to a new project and complete the whole process (pre-screenings and tests).

*The client reserves the full right to start the hiring process with that candidate.

💡 Simbiosis reserves the right to deny the request at any point of the process, as well as to cancel, interrupt, suspend, or terminate the collaboration without prior notice, and expression of cause.