Deprecated: Assigning the return value of new by reference is deprecated in /homepages/5/d238907679/htdocs/news/wordpress/wp-settings.php on line 520

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/5/d238907679/htdocs/news/wordpress/wp-settings.php on line 535

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/5/d238907679/htdocs/news/wordpress/wp-settings.php on line 542

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/5/d238907679/htdocs/news/wordpress/wp-settings.php on line 578

Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/5/d238907679/htdocs/news/wordpress/wp-settings.php on line 18

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/wp-db.php on line 306

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/cache.php on line 431

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/http.php on line 61

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GoogleSitemapGeneratorLoader::Enable() should not be called statically in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/plugin.php on line 339
Oz Sultan | Perks Consulting News

Posts Tagged ‘Oz Sultan’


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 55

Perks Consulting Participates in #140conf NYC


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 55
Wednesday, April 28th, 2010

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/link-template.php on line 135

At April’s #140conf in NYC, Oz Sultan, Perks Executive Adviser, spoke on a panel titled “Remembrance in the Real-Time Web.” The panel was based on the idea that the internet is a place where one records his or her legacy, and that social media can serve as a reference to remember and reflect on those who have passed. To hear more, click on the video below:

Tags: , , , ,
Posted in Success: Our Chance to Shine | 28 Comments »


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 55

Perks Consulting Acquires Esultancy


Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/functions.php on line 55
Tuesday, March 2nd, 2010

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/link-template.php on line 110

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/5/d238907679/htdocs/news/wordpress/wp-includes/link-template.php on line 135

NEWS ALERT: PERKS CONSULTING ANNOUNCES ACQUISITION OF SOCIAL MEDIA CONSULTANCY, ESULTANCY

NEW YORK, NY, MARCH 2, 2010 – With social media influencing the way we communicate, Perks Consulting announces today their commitment to expand their social media and technology capabilities by acquiring Esultancy, a social media consultancy based in New York.

“The marketplace has changed, as has the way consumers interact and make purchasing decisions. As consumers push their needs and demands to the companies that service them, businesses are forced to respond,” Lauren Perkins, Founder and President, Perks Consulting, said enthusiastically. This timely business move will allow Perks to build out its social media department as well as further develop its campaign and delivery methods in this arena to better serve current and prospective clients.

After a strong year in growth in 2009, in which Perks doubled in business, Esultancy is excited about Perks’ infrastructure and ability saying, “The Perks acquisition will create a new organization that’s poised to deliver on the 21st century marketing and social media needs of a wide variety of companies”.

With fearless vision, creative passion and aggressive drive, working in tandem with a rockstar team of business strategists, social media buffs, web designers, seasoned journalists and marketing visionaries, Perks Consulting devises strategic marketing and branding solutions that synergize both traditional and digital media to create insightful innovative campaigns. “Social media builds audiences faster. It took television 14 years to reach a market audience of 50 million people. It took Facebook two years” (Stone).

As of today, the companies will begin the execution of the acquisition in which Oz Sultan (@ozsultan) will be retained as an executive advisor to Perks Consulting through 2011. Khayyam Wakil (@iamkhayyam), of Esultancy, will join the Perks Consulting team as Social Media Director. With strategy being the foundation of both businesses, the infusion of Esultancy into Perks Consulting will support the breadth and depth of the digital reach that Perks began in 2008.

NewsOK.com. Renzi Stone, 26 Aug. 2009. Web. 9 Sept. 2009. <http://newsok.com/rising-social-media-our-world-atwitter/article/3395598>.

ABOUT PERKS CONSULTING

Perks Consulting entered the marketing and media industry in 2004.  Today, Perks Consulting is, a strategic Marketing and Branding Consultancy based in Soho, New York City.  Led by Lauren Perkins, entrepreneurial business strategist and digital marketing maven, with a constant focus on emerging trends and tools to consistently exceed client objectives and achieve desired metrics.

With a brand-centric, bottom line focus cultivated by work with Nike, Crunch Fitness and Laser Cosmetica as well as consulting for ABC, Toyota and Bloomingdales the Perks Consulting team has leveraged content and event marketing tactics combined with marketing know-how to create engaging multi-faceted strategies and campaigns for clients. Perks Consulting has also worked closely with start-ups such as ADRail, Yoga Local, and AB skincare from business strategy to brand. From entrepreneurs to emerging brands including 85 Broads and eDiets, our team of experts have the industry savvy, and ability to fulfill businesses creative, marketing, and media needs.

Tags: , , , , , ,
Posted in Shout Outs, Success: Our Chance to Shine | No Comments »