Distribution App: The business model canvas

Key Partners:

To make the application a true success, and to ensure the user has a seamless experience across different device types, a strong connection to app developers, graphic designers and marketers would be necessary.

Most of all, the developers would need a strong connection with social media platforms themselves in order to maximise the number of customisations.

Key Activities:

In order to keep the efficiency and usability of the application, and to keep up with changes to social media, the application would need to be updated regularly across all mobile, tablet and desktop formats.

In addition, the application would also need to include new social media platforms as they become available. These additions would allow the user to make the most of these social media platforms in order to maximise their reach to new audiences.

Key Resources:

A key resource to keep the application efficient for its user includes a simple, but effective support page. This should include a method of contact for a technical support team, as well as how-to support guides for DIY help.

A feedback portal should also be on offer. This is a way that users can contact the developers to suggest new ideas, to request new social media platforms, or let us know when things go wrong. This form of communication is direct, and allows our users to inform of us things that are important to them.

Value Propositions:

The values we need to deliver to our users are usability, efficient and performance, and the ability to customise.

The application needs to be usable: if it is a hassle to use, then there will be little improvement from the inconvenience of publishing to each social media platform individually.

Its efficiency and performance would be measured by the speed of the application – creation as little and unnecessary delays to publishing content. To remove any crash or bug, or anything that would prevent the application to work.

The ability to customise is important: how each individual post is distributed, and in what ways. Should the user include a photo to Facebook on this post, or the next, for example.

Customer Relationships:

The main relationship the user would have with the application is that of self-service. The user would download the applications on their operating system themselves, or log into the website to gain access to their account.

An online technical support would also be available for sticky-situations that require a bit of guidance, although the app should be designed to be as usable as possible.

The feedback portal would also be an opportunity to have another, open, relationship with the user.

Channels:

The application would have its own pages across the social media platforms it supports to not only give an example of the kind of post its users could make use of.

Its website will make use of online support articles, and blog posts.

Customer Segments:

The main user type is of course news outlets and online publications. News television programmes, radio shows, news agencies and online news sites would all see benefit from this application.

Bloggers would also make use of this for universal publishing across their social media accounts, making it easier for them to maintain their own personal brand.

And brand matters to company bases too, many of whom publish to blogs. This application would easily be the centre of their social media strategy.

Cost Structure:

The initial development of the application would cost, but ongoing costs include hiring technical support staff, and advertising campaigns across social media platforms to gain interest for new users.

Revenue Streams:

The application would be subscription based based on three tiers:

  1. Free, with limited access to one or two social media accounts or by the number of publishes per week.
  2. Premium, access to a limited number of outputs with a limited number of analytics.
  3. Business, access to all outputs and a limited number of analytics

Additional services, through further subscription, could be added to include further analytic support, and the ability to have multiple users to the master account (for example, a social media team or department within a company).

Leave a reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s