Sales
Sales Answer Researcher
Sales Answer Researcher
Start with Product URL + recurring objections. Later scheduled cycles revisit accessible sources and saved cases. Coverage depends on the available sources and runtime. Tests and measurements require actual execution evidence; unavailable capabilities remain visible as coverage gaps.
- 1/wkPrepared drafts
FactoriesStart with your sources
IdleIllustrative runReading public posts in
@dana_ortizX - 2h ago
Is there a tool that shows which of our dashboards nobody opens anymore? We have 400 and I suspect half are dead.
Gmail draftTo [email protected]
- Qualified leads
- 0
- Reply drafts
- 0
Related solutions
See how teams in this category put agents to work.
Integrations
0 integrationsGet started with Sales Answer Researcher
Pick an example, connect your tools, and review the first run.
Set up the Sales Answer Researcher agent template for this project. Follow /SKILL.md for the exact CLI commands.
Goal: Investigate objections against product and competitor evidence, challenge unsupported responses, and maintain sourced answer cards as capabilities change.
1. Install the CLI if it is not on PATH, check that I am signed in, and select my team and project.
2. List the first-party workflow templates. If `sales-answer-researcher` is listed, instantiate it with `--path.slug sales-answer-researcher` and start the run; otherwise create a project from this template at /new?template=sales-answer-researcher&preset=trial.
3. Share the run id, follow the run until it finishes, and summarize its outputs and changes.
Ask me before spending FTAI or changing anything outside this repository.
Launch from Claude Code, Codex, Cursor, and other agents.