Skip to main content

Customer Coolness: Selling Ebooks by the Chapter, Download & Web Subscription All at Once

Sometimes a customer uses our software so well all we can do is gape and point.  (Actually, it's been happening quite a lot lately.)  Example: The way Columbia University Press has neatly exploited Tizra features to turn simple PDF files into a whole range of ebook products, including...
  • Web-only subscriptions of various durations.
  • Full book download/web combos.
  • Single chapter download/web combos.
A reader who just wants to answer quick questions about, say, how the concept of Strategic Innovation applies to Bill Gates, could just buy a chapter and browse it immediately online.  Someone with a deep interest in the topic could buy the right to download the whole book, load it into their ereader and take it with them on the road.

Tizra's supported these kinds of options—and a lot of others—for some time, but it takes design and copywriting flare to present them in ways users can quickly make sense of.  We think the paywall page below does it really nicely.
Typical CUPOLA paywall page automatically displays all relevant purchase options.
Tizra's dynamic offer management enables CUP to automatically put just the right promotions in the right places.  For example, if you want to read Flash Versus Blink: An Introduction to Strategic Intuition, which they offer as a free sample, you'll go straight through to the the content, and can either view it online or download the whole chapter.   But if you want read "Warrior Buddha: The Path to Beginner’s Mind," you'll hit a paywall page like the above.

Even better, CUP can now quickly test variations on pricing, terms, copy and design to optimize results.

It's still early in the project, but it looks to me like CUP's been reading some of their own books!

Comments

Popular posts from this blog

Technical Podcasts

If there is something the web as surely changed, it was the way that software engineers need to work. It is now a crucial aspect of our work to be able draw from the huge internet knowledge base out there in an efficient way to get to the right answers. Part of that information extraction is related to the keeping-up-to-date effort that every developer is required to accomplish to continue to be productive. While previous a software engineer could rely mostly on print material, nowadays we need to rely as well on content available on the net. Podcasts are such a source that can bring an amazing amount of information to the mix of knowledge one needs these days. If you are a software engineer and have not jumped into the podcast wagon yet, I suggest you do so. Here is a list some technical podcasts that we hear at Tizra: The Java Posse : a fantastic podcast on Java development. Containing news info update, analysis of tools, overall software development discussions. Software as She Dev...

Using XML to Create a Better Online Reading Experience for the American Payroll Association

Congrats to the American Payroll Association on their recent launch of XML-based publications on Tizra!  Thanks to this collaboration, APA's authoritative books for payroll professionals are now available in crisp, reflowable HTML, creating a user experience that feels like a truly digital native product, rather than a conversion from print. XML-based publishing also creates a better mobile reading experience, supports more precise search and navigation, and opens the door to better accessibility for users with low vision and other disabilities. Our partners at  Scribe  did a great job supporting APA through the process of producing the XML for loading into Tizra, and we’d definitely recommend them to anyone interested in such a transition. It’s hard to overstate what a big step forward this is for Tizra as a platform and a company. XML has long been planned for in the product's architecture, but now for the first time, we have a working example that demonstrates t...

The importance of continuous integration

Leading a team of developers in the effort of building a robust, quality software product should involve the establishment of some process and tools to assist the team effort and serve as a safety net for the errors of getting people to work together. Continuous integration is, I believe, a crucial element of that process. Introduced by Martin Fowler and Matt Foemmel (see article Continuous Integration ), continuous integration establishes the practice of frequent integration of work developed by the several team members verified by automated build and testing of integrated code within a clean sandbox. This practice is valuable for several reasons: It promotes the development of a clear process of building/deployment independent of any specificity of developer's platforms. Code that exists on a single platform only is bound to become dependent on specific aspects of that platform without anyone really noticing the dependencies until trying to port to other platforms. The existence ...