ZEEN101 (@zeen101) – WordPress user profile

Bio

We’re an experienced team of WordPress developers working to grow publisher’s audience and subscription revenue. Leaky Paywall is built natively for WordPress and specifically for news & magazine publishers, bloggers, and content creators.

Current Job

Present

zeen101

WordPress Origin Story

Publishers needed a new revenue stream to counter the decline of print and digital ad revenues.

Coming from an early digital marketing background that started in 1998 with corporate web development, we have suspected (and since discovered) that digital publishing offers more revenue possibilities than publishers thought possible. Leaky Paywall is the result of that belief.

However, building a digital subscription platform was not our first product.

2010: A New Challenge for Issue Based Publishers

In 2010, Dartmouth College presented us with a challenge: they wanted to bring Dartmouth Engineer Magazine, a traditional print publication, online.

But they didn’t want to use any of the options available at the time. No unwieldy flipbooks or PDFs.

They wanted an actual web-based issue: all their collected stories gathered together and published with one click.

With WordPress as a solid foundation, CEO & Founder Pete Ericson and software engineer Lew Ayotte designed and built IssueM to meet their criteria.

A new way of presenting digital publications, capable of integrating with email, with social media, with search engines. Easy to manage on the backend, organized and beautiful on the front, IssueM even resulted in 2 Folio design awards.

It became the perfect vehicle for Dartmouth Engineer to reach out to all of its students — past, present, and future.

How do we know it was perfect?

Not long after, other colleges came knocking on our door, looking for the same services: Simmons, Middlebury, Amherst, Yale, Harvard, Berkeley, Einstein, and others.

Today, a decade later, over 1000 issue based publishers are using IssueM to deliver modern content in a Google, social, and mobile friendly format.

2013: Leaky Paywall – A Star Is Born

It wasn’t long after IssueM started gaining momentum that a publisher approached us with a custom request: they needed a way to restrict articles to paid subscribers, without cutting off all access to search engines and social media. At the time publishers were locked into hard paywalls which blocked their audience growth. Search engines could not discover publishers’ deep content and readers weren’t sharing those restricted articles on social media such as Facebook, Linkedin, etc.

We took a page out of The New York Times’ playbook: We built Leaky Paywall.

Our metered paywall allowed casual readers to sample a few articles before restricting the rest to subscribers only. But it’s a leaky paywall because search engines can still sneak a peek behind the wall, and readers can share all metered articles on social media. Readers also have to choose which articles they want to explore — they’re limited by number, not by topic. This was a big advantage over the hard paywall approach that forced publishers to choose which articles were free and which were paid.

Leaky Paywall started out small: it only worked with IssueM articles that magazine publishers wanted to restrict. But it had the bones of something greater.

Over time, Leaky Paywall expanded in scope. It still works for any WordPress content site, but now offers more flexibility, CRM and circulation integrations, and customizations to meet the needs of the unique news, magazine, and content creators that exist today.

As the most flexible paywall on the market, It has become the subscription and revenue foundation for more than 1000 publications.

Member Since: January 9th, 2015
Location: NH, VT, CO, GA
Website: leakypaywall.com
Employer: zeen101
Find me on:

Contribution History

Plugin Developer

Activity
Plugins
Favorites

Committed [3517706] to Plugins SVN:
tagging version 5.0.9
5 days ago
Committed [3511995] to Plugins SVN:
tagging version 5.0.8
2 weeks ago
Committed [3506246] to Plugins SVN:
tagging version 5.0.7
3 weeks ago
Committed [3506219] to Plugins SVN:
tagging version 5.0.6
3 weeks ago
Committed [3500924] to Plugins SVN:
tagging version 5.0.5
4 weeks ago
Committed [3496780] to Plugins SVN:
tagging version 5.0.4
1 month ago
Committed [3491041] to Plugins SVN:
tagging version 5.0.3
1 month ago
Committed [3490459] to Plugins SVN:
tagging version 5.0.2
1 month ago
Committed [3480775] to Plugins SVN:
tagging version 5.0.1
2 months ago
Committed [3479275] to Plugins SVN:
Fix WordPress.org readme formatting
2 months ago
Committed [3479273] to Plugins SVN:
Tagging version 5.0
2 months ago
Committed [3479272] to Plugins SVN:
Release 5.0
2 months ago
Committed [3438814] to Plugins SVN:
tagging version 4.22.6
4 months ago
Committed [3412525] to Plugins SVN:
tagging version 4.22.5
5 months ago
Committed [3399965] to Plugins SVN:
tagging version 4.22.4
5 months ago
Committed [3352324] to Plugins SVN:
tagging version 2.9.1
8 months ago
Committed [3347748] to Plugins SVN:
tagging version 4.22.3
9 months ago
Committed [3344783] to Plugins SVN:
tagging version 4.22.2
9 months ago
Committed [3340600] to Plugins SVN:
tagging version 4.22.1
9 months ago
Committed [3320736] to Plugins SVN:
tagging version 4.22.0
10 months ago
Committed [3261783] to Plugins SVN:
tagging version 4.21.8
1 year ago
Committed [3251899] to Plugins SVN:
tagging version 4.21.7
1 year ago
Committed [3205987] to Plugins SVN:
tagging version 4.21.6
1 year ago
Committed [3154926] to Plugins SVN:
tagging version 4.21.5
2 years ago
Committed [3143064] to Plugins SVN:
tagging version 4.21.4
2 years ago
Committed [3116598] to Plugins SVN:
tagging version 4.21.3
2 years ago
Committed [3049248] to Plugins SVN:
Assets upload
2 years ago
Committed [3046612] to Plugins SVN:
tagging version 4.21.2
2 years ago
Committed [3043355] to Plugins SVN:
tagging version 4.21.1
2 years ago
Committed [3038696] to Plugins SVN:
tagging version 4.21.0
2 years ago
Committed [3031876] to Plugins SVN:
tagging version 4.20.9
2 years ago
Committed [3026528] to Plugins SVN:
tagging version 2.9.0
2 years ago
Committed [3013124] to Plugins SVN:
tagging version 4.20.8
2 years ago
Committed [3011577] to Plugins SVN:
tagging version 4.20.7
2 years ago
Committed [2988667] to Plugins SVN:
tagging version 4.20.5
2 years ago
Committed [2969350] to Plugins SVN:
tagging version 4.20.4
3 years ago
Committed [2968835] to Plugins SVN:
tagging version 4.20.3
3 years ago
Posted a reply to Spent hours setting it up for nada…, on the site WordPress.org Forums:
Hi and sorry you had trouble getting Leaky Paywall to work. We are available to…
3 years ago
Committed [2960107] to Plugins SVN:
tagging version 4.20.2
3 years ago
Committed [2950899] to Plugins SVN:
tagging version 4.20.1
3 years ago
Committed [2941324] to Plugins SVN:
tagging version 4.20.0
3 years ago
Committed [2929860] to Plugins SVN:
tagging version 4.19.9
3 years ago
Committed [2916097] to Plugins SVN:
tagging version 4.19.8
3 years ago
Committed [2910357] to Plugins SVN:
remove old svg icon
3 years ago
Committed [2910355] to Plugins SVN:
add new plugin image assets
3 years ago
Committed [2893732] to Plugins SVN:
tagging version 4.19.7
3 years ago
Committed [2876631] to Plugins SVN:
tagging version 4.19.6
3 years ago
Committed [2870763] to Plugins SVN:
tagging version 4.19.5
3 years ago
Committed [2868467] to Plugins SVN:
tagging version 4.19.4
3 years ago
Committed [2857900] to Plugins SVN:
tagging version 4.19.3
3 years ago

Developer

IssueM

Active Installs: 600+
Leaky Paywall

Active Installs: 700+

Profiles

ZEEN101

Bio

Current Job

WordPress Origin Story

Contribution History

Developer

IssueM

Leaky Paywall

Plugins

IssueM

Leaky Paywall

Sponsored Article Content