---
name: sales-discovery-and-conversion
description: "Turn discovery evidence into a bounded demonstration, qualified opportunity and concrete next commitment. Use for sales discovery and conversion tasks; select only the requested methods."
metadata:
  version: "1.0.0"
---

# Sales Discovery and Conversion

Turn discovery evidence into a bounded demonstration, qualified opportunity and concrete next commitment.

## OLLIE Runtime integration

Use relevant methods under the active OLLIE Operator. Read live Workspace Context and tenant bindings for client facts, account identity, goals, permissions and required inputs. Consume ask-ollie-authority-core for authority, outloop-access-fallback for access and recovery, email-lifecycle-core for communication, and the bootstrapper Runtime Contract for execution ownership and completion. This skill introduces no scheduler, independent permission policy or competing Runtime owner.

Discover the active Workspace’s approved capabilities before choosing API or browser access. Use Outloop for external service actions and the host’s supported tools for local artifacts. A product name in this package is not an access grant. Never import private account configuration or follow a source method that bypasses host restrictions. Apply the current task’s authorization; a library update does not grant permission to send, publish or activate a campaign.

## Required inputs

- Approved offer and claims
- Buyer context and conversation history
- Discovery notes
- Available demo evidence and next-step options

Use for discovery preparation, call synthesis, demo framing, objections and sales handoff. Read [discovery to commitment](references/discovery.md).

## Diagnose before demonstrating

Establish the buyer’s current workflow, ownership, volume, failure points, existing tools and consequence of the problem. Distinguish explicit evidence from the seller’s hypothesis. A demo request does not prove fit or purchase authority.

## Choose the appropriate motion

Separate someone buying implementation help from someone seeking to deliver the product for others. Show the smallest relevant workflow using approved synthetic artifacts and verified capabilities. State prerequisites and limitations; do not expose architecture or private customer information merely to make the demonstration persuasive.

## Make the next step concrete

Summarize the problem in the buyer’s terms, the bounded outcome, dependencies, acceptance evidence, responsible people and next commitment. Use approved commercial terms only. Hand proposal creation to the relevant capability when requested; do not create a contract or promise a roadmap from a sales note.

## Record observed progress

Update the real pipeline under current authority with evidence, uncertainty, owner and due date. A sent proposal is not a win; a meeting is not an activated client. Keep delivery claims tied to actual results.

## Completion

Verify findings against source evidence and read back every resulting artifact or authorized change. Distinguish a saved draft, queued job, active workflow and completed delivery. Return the requested outcome, evidence, output location and precise outstanding dependencies. Complete independent work when one dependency is unavailable. Package validation and synthetic fixtures do not establish real host import or provider execution.

Read [evaluation scenarios](references/evaluation.md) when testing this skill.