dsh-sales

Once demand is qualified, the product is defined, and the commercial strategy is in place, sales teams still face a fuzzy middle: Is the qualification really solid? Can the quote withstand scrutiny? Is the forecast grounded in evidence? Can loss reasons flow back upstream? dsh-sales is built for exactly this commercial operating layer. It turns local Markdown, CSV, JSON, and JSONL sales material into explainable readiness checks, pipeline analysis, qualification cards, offer reviews, weighted forecasts, and close reviews, shifting monetization execution from gut feel to an auditable, traceable process.

Core capabilities follow three threads. First, artifact validation: sales_artifact_review checks version, stable ID, content fingerprint, and expiry of sales artifacts before qualification, quoting, or feedback handoff, so stale or mismatched material never reaches downstream steps. Second, handoff gates: sales_product_handoff_review and sales_commercial_handoff_review set checkpoints between product-to-sales and business-to-sales, marking a handoff as partial or blocked when value evidence, delivery boundaries, or pricing authorization are missing, ensuring it is never mistaken for a forecast or a deal commitment. Third, analytical output: pipeline stage analysis, weighted forecasts, loss attribution, and renewal or expansion signals are structured for dsh-business, dsh-product, and dsh-growth, feeding continuous iteration of pricing, product, and growth strategy.

dsh-sales does not write CRM records, contact prospects, send messages, submit quotes, approve discounts, or replace product or pricing strategy. It is designed for teams that have already validated demand and product definition and want an auditable checkpoint before closing, particularly organizations operating within the six-plugin collaboration system that need to move monetization execution from experience-driven to evidence-driven.