Audiences
Canonical audience YAML configurations and their enriched sales profiles.
Canonical audience YAML configurations and their enriched sales profiles.
The entry point for changing the sales library. Routes a contribution to a workflow, then runs it step by step.
Condensed pre-call reference distilled from the canonical library.
Storage model for incremental problem, solution, proof, audience, and generated sales content.
Derived call cards and rendered assets. Disposable, regenerable, and never a source.
Provisional call analyses and seller observations awaiting triage. Never a generator input.
How to navigate and maintain the canonical sales knowledge system.
Enriched sales profile for a single-site plastic extrusion audience with 100–500 employees.
Canonical catalog of Naologic go-to-market motions.
Canonical problem record for internally built operating software that expresses business rules as code.
Canonical problem record for operating and financial data held separately, leaving margin unstateable below company level.
Canonical problem record for quoting that runs on product rules while capacity lives in a separate schedule.
Canonical problem record for several intermediary quote requests representing one demand event.
Canonical problem record for manufacturer quote records that never receive the final project award.
Canonical problem record for accepted work that planners manually allocate and sequence across non-equivalent assets.
Canonical problem record for unstructured quote requests that staff must interpret before pricing and scheduling.
Canonical problem record for an operating application that becomes unusable during production-schedule entry.
Canonical problem record for commercial opportunity sizing that depends on manual takeoff from plans and specifications.
Canonical problem record for operating-system reporting that depends on export and spreadsheet reconstruction.
Canonical problem record for unexplained differences between system inventory and physical counts.
Canonical problem record for system replacement that proceeds without a validated, complete extraction.
Canonical problem record for batch-size selection that cannot reconcile production economics with demand and inventory carrying cost.
Canonical reusable business functions available to market and vertical sales playbooks.
Call analysis from a four-plant plastic pipe extruder, resulting in nine canonical problem outcomes.
Canonical problem records — one testable operational mismatch per file, with no vertical scope.
Canonical proof records — a bounded test with an artifact and a buyer-defined acceptance criterion.
Canonical solution record for moving operating rules from code into configuration.
Canonical solution record for assembling per-site and per-unit margin from a single operating record.
Canonical solution record for computing price and date against a specific asset slot.
Canonical solution record for grouping intermediary quotes under one underlying project identity.
Canonical solution record for assigning confirmed manufacturing work to compatible work centers and recalculating the active sequence.
Canonical solution record for converting captured quote-request text into a structured draft for review.
Canonical solution record for separating targeted work-order schedule edits from full active-schedule reflow.
Canonical solution record for converting project documents into reviewed material quantities on commercial opportunity records.
Canonical solution record for running recurring management reporting directly over current operating records.
Canonical solution record for reconciling physical counts through controlled inventory adjustments and movement history.
Canonical solution record for gating production cutover on a documented and reconciled trial migration.
Prepare buyer conversations, find traceable sales knowledge, and turn field learning into reusable assets.
Canonical Markdown and YAML format for markets, ICPs, problems, solutions, Q&A, and generated call sheets.
Canonical solution records — the mechanism that addresses a problem, with every capability classified.
First-call analysis from a single-site manufacturer that later converted to a paying customer.
Follow-up-call analysis from a single-site manufacturer evaluating replacement of its incumbent operating system.
Canonical catalog of Naologic market verticals, routing boundaries, and proof-transfer rules.