Splits is a feature that should be used to meet this requirement. Splits allows users to assign credit to opportunity team members based on the level of effort contributed by each person toward each deal. Users can create different types of splits, such as revenue or overlay splits, and specify the percentage or amount of credit for each team member. Reference: https://help.salesforce.com/s/articleView?id=sf.forecasts3_splits_overview.htm&type=5

Screen flow allows you to create a form that collects user input and performs actions based on that input. You can use screen components to display questions and instructions, and use flow logic to update records or send notifications.

Flow Builder supports creating a wizard that can collect user input and perform actions.

To automate an outbound message, the administrator should use a workflow rule that defines the criteria for sending the message and the actions to perform when those criteria are met. One of the actions available for workflow rules is sending an outbound message to a designated endpoint URL with specified fields as parameters. Process builder, task assignment, and flow builder are not able to send outbound messages directly. Reference: https://help.salesforce.com/s/articleView?id=sf.workflow_define.htm&type=5 https://help.salesforce.com/s/articleView?id=sf.workflow_action_outboundmessaging.htm&type=5

Two data loss considerations when changing a custom field type from Text to Picklist are:
Assignment and escalation rules may be affected, because the values in the picklist may not match the values that were previously entered in the text field, and the rules may not trigger as expected.
Any list view based on the custom field is deleted, because the filter criteria for the list view may not be valid for the new field type, and the list view cannot be displayed. There will be no data loss with use of a global value set or auto updates to Visualforce references, because these are not related to changing a custom field type from Text to Picklist. Reference: https://help.salesforce.com/s/articleView?id=sf.fields_changing_type_considerations.htm&type=5