In order to gain the maximum value from Extensions, Adobe should rescale the intended takeup point to accommodate departments and small businesses. Most electronic document implementations are introduced on these scales and in such settings. The Extensions model should acknowledge this reality.
Adobe should set the following objectives, and measure their Reader Extensions strategy thereby:
Elevate awareness of the power and value (assuming revised pricing!) of Reader Extensions.
Overhaul the system for vending Reader Extensions; rely on Acrobat's distribution base and natural turn-over in Extensions-enabled PDFs to generate demand for licenses.
Let a thousand flowers bloom: encourage a diversity of implementations by ensuring the price is low enough to encourage widespread adoption.
Let there be two basic licensing models
License per user
Per-user annual licensing is intended for high-volume/user forms, commenting and similar implementations. Typical end-users use interactive PDFs or may save PDF forms as a regular part of their daily work activities, with a minimum of two Reader Extensions-enabled uses per working day.
Per-user pricing should scale from under $100/user/year for small organizations down to a lot less for hundreds, thousands and hundreds of thousands of users. Per-user licensing isn't an impulse buy.
One interesting option would be a facility to distribute a "Reader Extensions License" to authorized Adobe Reader users as a registration code (or other preferred approach for managed-installation environments). Once installed, the user would have Extensions available with any PDF. (If this last idea sounds vaguely familiar, it should! Bestowing a Reader Extensions license on Reader itself would effectively reinvent Acrobat Business Tools. Wouldn't that be great!)
License by usage
Now let's talk about any user with Adobe Acrobat Professional, a credit-card and a job to do. Perhaps they need a PDF form that can spawn additional pages and be saved in Reader, or a document that Reader users can digitally sign.
This license should be sold on the basis of intended distribution as reported by the license purchaser via a web-based UI initiated from within Acrobat Professional, perhaps via acrobat.com. By "intended distribution", I mean that the license purchaser would state their needs (Extensions) and the intended usage of the file, and the software would quote a price. Example: "1,000 users, once per month, and 200 users, about once per day". Based on that intended usage, specific Extensions requested, account history and other factors, the price might be $543 for one PDF, $5,500 for another, and as much as $20,000 or maybe more for some PDF with truly massive intended distribution.
Adobe would get to log each Extensions-enabled PDF. "Draft" Extensions would be permitted, but PDFs uploaded as replacement drafts could be analyzed for differences with previously enabled PDFs for license-administration purposes. Adobe could reserve the right to audit the PDFs usage in some anonymous way. The important thing is the tenor of the presentation. It may be serious, it must not be grossly onerous or prohibitive, or (fundamentally) intrusive. Success comes from broad-based uptake and utilization, not from nailing the occasional cheat.
For all the brilliance of the PDF concept itself, and for all its thankless (if profitable) execution of Adobe Acrobat, Adobe Systems is justified, to a degree, in regarding Reader as a ticket to revenue heaven. Even so, the company has yet to seriously begin to act on the opportunity.
Meanwhile, thousands of forms and other interactive PDF technology implementations slow, stumble and stall due to a pricing model that doesn't relate to the real world of how and why organizations might consider using Reader Extensions to address their business needs.
Adding a Reader Extensions vending "feature" to Acrobat, even if it was merely a link to a LiveCycle Reader Extensions Server and a payment engine, would result in significant near-term and substantial continuing revenue.
OK, so you want to stamp your document. Maybe you need to give reviewers some advice about the document's status or sensitivity. This tip from author Ted Padova demonstrates how to add stamps with the Stamp Tool along with related comments.