Lessons learned from Social Content 2.0 Circle of Life – Part 3

My outside your firewall, shared listening and engaging Community Product Manager service offering for social software vendors/providers.

Sharing

Sharing does have its advantages

According to wikipedia

Shared Services refers to the provision of a service by one part of an organization or group where that service had previously been found in more than one part of the organization or group. Thus the funding and resourcing of the service is shared and the providing department effectively becomes an internal service provider. The key is the idea of ‘sharing’ within an organization or group.

Background

As the title suggests, this is the third and final part of my Lessons Learned series and where I’ll propose the business model I’ve come up with. Here’s my previous related posts:

  1. How to infuse Social Content 2.0 into your social software lifecycle
  2. Trial offer to test the Social Content 2.0 Circle of Life
  3. Lessons learned from Social Content 2.0 Circle of Life – Part 1
  4. Lessons learned from Social Content 2.0 Circle of Life – Part 2
The Business Model
  1. I will assume the overhead costs associated with:
    1. Monitoring the social software market. Using Radian6, I would create a Topic Profile including keywords for social software vendors / providers like Socialtext, Atlassian, Blogtronix, MindTouch, Cynapse, Liferay, Vignette…
    2. Filtering out and tagging relevant buzz about product features and directions across the market
    3. Offering free service exporting tagged content and publishing on blog
  2. Offer monthly fee-based services where I would:
    1. Net out tagged content with respect to product features and publish on permission-based site (Say for example there’s a few posts about “permissions”. I would then write a 1-liner describing the “permission feature” and link to the original supporting content published Step 1.3)
  3. Offer hourly, or, tiered fee-based services where I would:
    1. Collaborate with respective social software vendors’ / providers’ (Customers’) Product Managers to determine which features described in Step 2.1 should be elaborated
    2. Engage with original content authors and elaborate on product features selected in Step 3.1
    3. Privately share results of Step 3.2 with respective Customer Product Managers
    4. Collaborate with respective Customer Product Managers to determine which features described in Step 3.3 require further assistance / services

Other variations
I could resell Radian6 Seat licenses – governed by certain permission restrictions and share my Topic Profiles for those:

  1. Customers whose only pain is the cost of Radian6 (who can then determine later on if they want Steps 2 and/or 3)
  2. Potential colleagues who would collaborate on Steps 1, 2 & 3
Thoughts?

What do think? If you’re a social software vendor/provider, is this a service that may be of interest to you? Do you currently have a Product Manager? If so, is your Product Manager able to keep up with the social content? Do you see the any value in consolidating the redundancy? Do you see where it really is just a matter of per·spec·tive? Where …

one piece of content can yield dividends for many investors 

I’d love to hear from you folks in the field & prove there is a way we all could succeed at doing more with less.

Reblog this post [with Zemanta]