NarrowToolsBrowse toolsThese are research signals, not a ranking of popular tools or a claim that search demand is growing. Each note distinguishes an observed change from a question that still needs testing.
Publisher: a real lifecycle change
Microsoft’s retirement guidance creates a concrete reason to review legacy publishing files. Subscription and perpetual-license situations differ. The practical question is whether your archive needs readable output, continued editing, or a new workflow.
What this does not prove: that every .pub file has become inaccessible, that one converter handles every layout, or that migration demand will remain constant.
Choose a Publisher replacement · Microsoft source
Small wholesalers: the repeat update matters
A small-business operator publicly described wanting an Excel-connected catalog and seeking paid advice on the publishing workflow. That is a specific user report, not a survey. Existing catalog services already automate parts of this process.
Question to test: how much time does the second and third price update take, especially with customer-specific prices and pack quantities?
Plan a catalog workflow · Original user report
Document archives: people disagree about the mental model
A community discussion asked for a document system with familiar folders and straightforward retrieval. Responses included both satisfaction with existing archive tools and frustration with their learning curves. The useful signal is a difference in user expectations, not universal dissatisfaction.
Question to test: can a nontechnical teammate add, retrieve, and export documents without the administrator beside them?
Run a small-team archive pilot · Original discussion
How these notes will evolve
Future notes should add dated primary announcements, reproducible workflow tests, or clearly labeled search data. We do not turn one complaint, a GitHub star count, or an estimated search volume into a claim of product-market fit.