← ClaudeAtlas

presales-with-docslisted

Run live presales discovery one question at a time, preserve a decision ledger, and produce an auditable ballpark/ROM for services, infrastructure, timeline, and BAU. Use when a presales operator is scoping a client project, qualifying requirements, estimating man-days, loading an approved rate card from Notion, or preparing an indicative cost for client discussion.
thattimc/skills · ★ 1 · DevOps & Infrastructure · score 74
Install: claude install-skill thattimc/skills
# Presales with Docs Guide a client conversation from desired outcome to a reviewable, non-binding ballpark. The presales operator owns the meeting and every commercial approval. ## Start 1. Read [references/live-discovery.md](references/live-discovery.md). Ingest supplied requirements before asking anything. Ask the operator whether the conversation is client-visible or private, then create `<client-slug>-presales/discovery-record.md` from the reference template. State that this is discovery for an indicative ROM. **Complete when:** visibility is known and the record contains every fact already available from supplied material. 2. Ask: **“What outcome would make this project successful for you?”** Ask exactly one client-facing question, then wait. Honor operator controls: `park`, `skip`, `revisit`, `summarize`, `private checkpoint`, and `end discovery`. **Complete when:** the client has answered or the item is explicitly parked. ## Discovery loop 3. Update `discovery-record.md` after every answer: confirmed facts, client decisions, assumptions, exclusions, unresolved items, and conflicts remain distinct. Choose the next question by this order: conflict, readiness blocker, largest estimate swing, then output detail. Ask one question and wait. Offer a recommended answer only when the operator or client needs options; label it as a recommendation. **Complete when:** every readiness-gate field is confirmed, assumed with a stated ba