Copy This Prompt: Working Out What You'd Connect To

Help me plan the connections an agent in my product would need.

WHAT THE AGENT SHOULD DO: [description]

SYSTEMS WE HAVE: [list them - CRM, ticketing, database, docs,

internal APIs, third-party services]

For each system, tell me:

1. Does the agent need to READ from it, WRITE to it, or both?

2. If it writes - is that reversible? What's the worst outcome

of a wrong write?

3. What specific capability does the agent actually need? Be

narrow - not 'access to the CRM' but the two or three

specific things it needs to do there.

4. Which of these could plausibly already have an off-the-shelf

connection available, and which would definitely need building?

5. Rank the whole list: which connection delivers most of the

value? Could we ship a useful first version with only the

top two or three?

Question 5 Is the Product Question

Teams routinely plan agents that need eight connections before they do anything useful, which turns a six-week project into a six-month one. Almost always, two or three connections deliver most of the value. Find them and ship that first, you'll learn more from a narrow agent in production than from a comprehensive one still in build.