harness-sales-suite

Domain profile routing works by declaratively linking a declared domain_profile to the appropriate SKILL.md, automatically selecting the correct domain skill for execution. This aligns evaluation criteria and artifact taxonomies across sales, sales_engineering, tender_management, sales_enablement, and sales_operations domains.

Cross-domain composability in sales pipeline management supports primary and secondary profile combinations to enrich evaluation and pipeline strategy. It allows multiple domain suites to coordinate profile routing and end-to-end pipelines across the revenue execution flow.

To configure multiple domain suites for end-to-end sales pipelines, load the harness sales suite and select a domain profile. This routes to the corresponding domain skill, defining the end-to-end flow and phase routing across sales, sales_engineering, tender_management, sales_enablement, and sales_operations.

You need centralized registry routing for domain-specific sales skills when configuring the Harness framework with multiple domain suites to coordinate profile routing. It enables seamless selection and orchestration of the correct domain capabilities for revenue execution.

Yes, you can combine primary and secondary domain profiles to enrich pipeline strategy through cross-domain composability. This supports coordinating profile routing and end-to-end pipelines across sales, sales_engineering, tender_management, sales_enablement, and sales_operations domains.

Declarative domain profile routing is limited to the configured domain suites within the Harness framework, specifically sales, sales_engineering, tender_management, sales_enablement, and sales_operations. It requires declaring a domain_profile to map to the appropriate SKILL.md for routing.