24

Hard parts paywall - stup

Embed Size (px)

DESCRIPTION

Per Buers experiences working with various news organizations when implementing paid content strategies.

Citation preview

Page 1: Hard parts   paywall - stup
Page 2: Hard parts   paywall - stup

PaywallsWhat works and what doesn’t

!10 some best practices according to our experience

Page 3: Hard parts   paywall - stup

Per BuerCTO

Varnish Software (Freemium / Premium business model)

Page 4: Hard parts   paywall - stup

Original Heidelberg

Page 5: Hard parts   paywall - stup

Original Heidelberg

Page 6: Hard parts   paywall - stup

Business logic

Page 7: Hard parts   paywall - stup

Background

• We launched our first paywall 2 year ago

• 12 projects so far

Page 8: Hard parts   paywall - stup

We’re moving to a paywall

Page 9: Hard parts   paywall - stup

Paywall concepts

• Freemium / premium paywalls

• Identity based- and anonymous metered paywalls

• Referrer-based access

• Micropayments

Page 10: Hard parts   paywall - stup

Lots of moving parts!

Page 11: Hard parts   paywall - stup

Project scope

• Paywalls involve:

• Backend, frontend, ops, business, editorial, marketing, customer support ++

• Proper project management is very important

Page 12: Hard parts   paywall - stup

Access control

Page 13: Hard parts   paywall - stup

Access Control

• Technically challenging

• Lots of different approaches

• Client (SaaS), CDN, Appserver, Edge

Page 14: Hard parts   paywall - stup

Scalability & Performance

• Scaling a website is harder with a paywall

• Identity based metering makes is even harder as database interactions happen at every page-view

Page 15: Hard parts   paywall - stup

Dev Ops

Page 16: Hard parts   paywall - stup

Access control rules

• Remember: Access control rules need

• To be implemented

• To be communicated to the readership

• Keep it simple if possible

• People don’t pay for things they don’t understand

Page 17: Hard parts   paywall - stup

Testing

Page 18: Hard parts   paywall - stup

Testing paywalls

• Tests now need to cover the paywall

• You need to test the whole paywall, covering VCL, CDN or Javascript based paywalls

• More complexity - higher costs

Page 19: Hard parts   paywall - stup

Payment

Page 20: Hard parts   paywall - stup

Payment is easy :-)

Page 21: Hard parts   paywall - stup

Subscription management

• Some newspapers have existing subscription management software that handle digital

• Those who do not might face a more complex project

Page 22: Hard parts   paywall - stup

Typical paywall project

• 9 months long, 3-12 month range

• Business side typically uses 3-4 months to make up their mind :-)

• Our implementation costs are in the €7-25K range and typically spans 2-4 weeks.

• New, creative models add time and cost

• (Norwegian newspaper tend to be very competent)

Page 23: Hard parts   paywall - stup

Summing up1. Complex projects

2. SaaS paywalls might not cut it (bias)

3. Consider scalability (bias)

4. Access control & security is hard

5. This might be the time for devops

6. Testing becomes harder

7. Statistics is different

8. Payment is easy

9. Subscription management

Page 24: Hard parts   paywall - stup

• Clock mechanics, http://www.flickr.com/photos/45810363@N04/4835327934/in/photostream/

• Devops, http://www.flickr.com/photos/psd/8634021085/

• Padlock, http://www.flickr.com/photos/faithmonsoon/234237378/

• Munch, The Scream.

• The rest are bought of Shutterstock

Photo credits