For RevOps consultants, specialist agencies and lean GTM teams
Sales and prospecting
v1.1.0One explicit choice of the verified account-and-contact research workflow, or a clear stop when the request requires an unavailable mutation or broader GTM function.
Route a prospect-list request to the verified account-and-contact Skill or stop when the request needs a different unverified sales or RevOps outcome.
Choose the deliverable you need
Turn a narrow ideal-customer profile into review-ready accounts, current decision-makers and verified work emails.
What this Skill does—and does not do
The router does not run catalog tools, send outreach, write to a CRM, or cover positioning, marketing operations, attribution, forecasting or revenue operations.
Inputs
- The sales-research outcome or deliverable the user wants
- Any supplied ideal-customer profile, buyer role, geography or target count
Outputs
- One selected verified function Skill and a concise reason
- A clear boundary when the request requires outreach, CRM mutation or a broader GTM function
How this Skill works
- 1
Describe the outcome
Tell your agent which business result or artifact you need.
- 2
Select one function Skill
The router chooses the smallest verified Skill that owns that deliverable and stops when none does.
- 3
Review the paid plan
The selected function Skill shows its exact inputs, tools and maximum cost before paid work begins.
- 4
Review the finished result
After approval, your agent returns the promised output and reports the tools used, final cost and any limitations.
Full instructions your agent receives
Route the request by its deliverable, not by broad GTM vocabulary. This router does not execute research itself and does not turn a research request into permission to contact anyone or mutate a CRM.
Before routing, use any supplied product, positioning, ICP or suppression brief. If .agents/product-marketing.md exists, read it as context; it does not prove company fit, role currency or buying intent.
Route the request
- Use Sales Qualified Accounts when the user needs companies matching a narrow ideal-customer profile, one relevant current person per accepted company, verified professional work emails and a reviewable research receipt.
- A supplied-account research pack, existing-list audit or contact-only repair is not a verified V1 route. State that boundary instead of forcing it through ICP discovery or paying for unnecessary work.
- The package does not yet have a verified CRM-write function. If the user asks to create or update CRM records, complete only the separately requested research portion when useful, state that
sales-prospecting-to-crmremains a withheld draft, and stop before any write. - Outreach copy, sending, campaign sequencing, CRM governance, routing,
attribution and forecasting are separate outcomes and are not implied by the category name.
Return the selected Skill, its exact artifact and the boundary that remains human-owned. Do not make the user choose between provider names.
After choosing the verified function, read its complete SKILL.md and follow its qualification rule, count and spend ceiling, evidence requirements, approvals, recovery state and acceptance criteria. If it is not present in the current installation, ask before installing it from this repository and pin the source revision.
Cost and approvals
How pricing works
Routing is agent-side and makes no paid call.
Trial-safe limits
The selected function Skill presents and obtains approval for its own paid plan.
Your approval points
- Ask before installing or updating a missing function Skill; paid and mutation approvals belong to the selected function Skill
Related Resources
AI lead generation: build a verified B2B lead list
A repeatable workflow for defining an ICP, finding matching people and companies, enriching records and verifying contact data.
What does a qualified B2B lead cost? Clay, Apollo and ZoomInfo compared
Compare the cost of a raw B2B contact with a researched, contact-ready prospect across Clay, Apollo, ZoomInfo and usage-based agent workflows.
Pay-per-use AI tools vs subscriptions: which model fits agent work?
Compare pay-per-use AI tools with per-seat subscriptions by workload, billing unit, account overhead and spending predictability.