In plain terms
A search engine is a librarian who points you to the right shelf. An answer engine is a research assistant who goes to the shelf, reads the books and comes back with a summary and footnotes. You save the reading; you also see only what the assistant chose to include.
Why it matters
Answer engines are changing how people research products, suppliers and decisions, and with it where influence sits: at the moment the answer is composed. For leaders there are two questions. As a user: how far can we trust an answer, and do we check its sources? As a brand: are we among the sources?
Example
A procurement manager asks an answer engine to compare three e-invoicing providers on price, integrations and compliance. It runs a dozen searches, reads vendor pages and review sites, and returns a comparison table with numbered citations in under a minute. She clicks two of the citations to verify, and none of the vendors' home pages.
Most often confused with
Answer Engine vs. Search engine
A search engine's product is a ranked list; judgment and synthesis are left to the user. An answer engine's product is the synthesis itself. The line is blurring, since search engines now add AI answers and answer engines run searches behind the scenes, but the difference in who does the reading remains.
Under the hood
The usual architecture is retrieval-augmented generation at web scale: interpret the question, rewrite it into several queries, call one or more search indexes, fetch and rank passages, then generate an answer constrained to those passages with inline citations. “Deep research” modes run this as an agent loop over many steps. Known weaknesses: citations that do not support the sentence they are attached to, over-reliance on a few sources, exposure to prompt injection from the pages read, and different answers on different runs. Examples include Perplexity, ChatGPT with search, Google's AI Mode and Microsoft Copilot.