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
Digital | Perks Consulting News

Posts Tagged ‘digital’


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

Internet Week at the Wix Lounge with Perks Consulting


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
Friday, June 17th, 2011

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

damien basile, kyle cameron studstill, bryce gruber, rosie siman at the Wix Lounge for Some Things Digital 2.0 with Perks ConsultingLast week the Perks Consulting team hosted an afternoon series of panels at the “Some Things Digital: Business 2.0″ Conference, a day-long series of panels on carefully curated topics that concern businesses of all sizes in today’s integrated world. Perks presented an “Engagement” segment of 3 panels covering the changes and evolution of the fashion industry, the landscape of female entrepreneurship, and a discussion on consumer innovation lifestyle trends.

The New Digital Fashion Experience: From Production to Engagement
Starting the afternoon off, Perks’ CEO Lauren Perkins was joined by Sammy Davis of Sammy Davis Vintage, the “Martha Stewart of Vintage”, and Jessica Moore of Stylebook, a fab mobile app to help you organize your closet. These two ladies have struck out on their own, building their careers and businesses based off of their social media and tech savvyness, while the power of crowdsourcing their audiences have kept their communities engaged and asking for more. The three women agreed that those brands and companies who set the stage for their communities and then let them create their momentum on their own will find their fans advocating and doing all the work for them. The amount of (mostly favorable) user-generated content has even crowded out official brand content among the results of YouTube or blog searches. Even for these smaller entrepreneurs the results are clear, Moore states that incorporating customer feedback in each new version release results in doubling app sales through word of mouth by her fans.

Lessons From Female Startup Founders
Continuing on female entrepreneurship, the mix of the newbie (Christy Purington of Clique), the serial founder (Beth Schoenfeldt, formerly of Ladies Who Launch and Collective-E), and the advisory (Kat Karimi, formerly of ASTIA), jumped on thoughts about money, males (vs. females), and management in the startup landscape. Bootstrapping and keeping things lean were encouraged among the group, knowing that having too much money makes a company lose control and direction. Angel and VC money should be saved for marketing and further development costs when the product is viable and ready to scale. Thoughts from the fashion panel were echoed again here, as Purington realized “listening to your customers from the beginning will save a lot of headaches” during product building and iteration.

How Businesses Can Harness Consumer Lifestyle Innovation Trends
The afternoon finished off into a diverse discussion of data, “utilitainment”, and the scourge of QR codes with Bryce Gruber of the Luxury Spot, Kyle Cameron Studstill of PSFK, Rosie Siman of Saatchi and Saatchi, moderated by Perks’ own Damien Basile. The year of data (and data exhaust) is coming according to the group, as the proliferation of available behavioral data is coming to fruition with mobile phones rapidly becoming attached to every part of our lives. Research firms like Nielsen will have nothing in comparison to the accuracy brought on by apps such as IntoNow, while it is inevitable that the concepts of data and privacy will eventually dissipate into acceptability, just like how Facebook statuses were once taken to be considered “creepy”. The fate of QR codes (if not already decided) lies in the establishment of best practices by the industry. Marketers have yet to clearly articulate the call to action in the use of QR codes - asking the scanner “do you want to know more” with the assumed answer of “yes”.

Big thanks to Perks’ Marketing and Media Director and Founder of Addieu, Damien Basile, Brett Petersel of Digital Somethings and The Community Manager, and the Wix Lounge for hosting us!


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

New Year, New Websites: Perks Launches Two Sites in One Week!


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, January 20th, 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

This week Perks had two websites launch! Make sure to check the new Women’s Media Center site and Eleanor Dubinsky’s music website.

Eleanor Dubinsky


Eleanor’s creative website, mirrors her artistic originality and truly encapsulates her musical brand. With social media infusion, Eleanor hopes to spread her music through various platforms.

The Women’s Media Center website has incorporated new digital features, social media and has a user-friendly aspect that really makes this site a home run!

Congratulations!Women's Media Center