Technical Discovery Call Prep Agent

Discovery calls go wrong when the sales engineer asks generic questions and finds out about a key system three weeks later. Before each call, this agent reads the account's stack from the CRM, notes, job posts and public pages, and builds a list of technical questions in priority order. After the call it reads the notes and checks which questions were answered and which were not. It updates the requirements list, marks risks such as an unsupported database, and drafts follow-up questions. If an answer reveals a new system, it adds new questions and rechecks. The engineer approves what goes to the customer. Edge case: the customer says they use a system the product does not integrate with, so it flags the gap early.