Andrew Schultz Named “America’s Top 1,200 Advisors: 2019 State-by-State”


Warning: mysqli_query(): (HY000/1021): Disk full (/tmp/#sql-temptable-3a1d1-b36bd-e4d39.MAI); waiting for someone to free some space... (errno: 28 "No space left on device") in /home/communitynewspap/public_html/wp-includes/class-wpdb.php on line 2349

Warning: mysqli_query(): (HY000/1021): Disk full (/tmp/#sql-temptable-3a1d1-b36bd-e4d3a.MAI); waiting for someone to free some space... (errno: 28 "No space left on device") in /home/communitynewspap/public_html/wp-includes/class-wpdb.php on line 2349

Morgan Stanley announced today that Andrew Schultz, a Managing Director Private Wealth Advisor in the Firm’s Miami Beach Wealth Management office, has been named to Barron’s list of “America’s Top 1,200 Advisors: 2019 State-by-State.”

The “Barron’s Top 1,200 Advisors” is a select group of individuals who are screened on a number of criteria. Among factors the survey takes into consideration are assets under management, revenue produced for the Firm and quality of service provided to clients.

“I am extremely proud that Andrew is representing Morgan Stanley Wealth Management on this list,” commented Kevin McCarty, Complex Manager of Morgan Stanley’s Miami offices. “Competition is steep to be selected for this list, and those who make the cut represent a very high level of achievement in serving their clients’ wealth management needs.”

Morgan Stanley Wealth Management, a global leader, provides access to a wide range of products and services to individuals, businesses and institutions, including brokerage and investment advisory services, financial and wealth planning, cash management and lending products and services, annuities and insurance, retirement and trust services.


Connect To Your Customers & Grow Your Business

Click Here


Warning: mysqli_query(): (HY000/1021): Disk full (/tmp/#sql-temptable-3a1d1-b36bd-e4d38.MAI); waiting for someone to free some space... (errno: 28 "No space left on device") in /home/communitynewspap/public_html/wp-includes/class-wpdb.php on line 2349