M1_V1-P1-A05 — Plastic extrusion, 100–500 employees, single site

Audience summary

This audience selects plastic extrusion companies with 100–500 employees, one operating site, and a CEO contact. The systems of record are not known before the call, and no additional company signal is required for selection.

Use this profile to test operational hypotheses. It does not establish that a selected account has any of the problems below. Start each theme as a question, look for both confirming and disconfirming evidence, and stop using a theme when the account's answer makes it inapplicable.

The source configuration is approved, but P_00002 conflicts with the controlled single-site footprint. It is retained below so the configuration conflict remains visible, but it is not a safe active discovery theme for this audience.

Definition tuple

Dimension	Controlled value	Resolved meaning
Market	M1	Vertical core
Vertical	M1_V1	Plastic extrusion
Persona	P1	CEO — executive leadership and ownership
Company size	100_500	100–500 employees
Location footprint	single_site	One operating site
Systems of record	[unknown]	Identities not established before the call

The vertical requires verified extrusion activity. NAICS and product language help find candidates but do not replace confirmation of the production process. systems_of_record: [unknown] means no system identity has been established as a pre-call fact; it does not mean the company has no operating systems.

Pre-call selection predicate

The configured predicate is empty. Selection uses only the controlled definition tuple:

M1 vertical core
  + M1_V1 plastic extrusion
  + P1 CEO
  + 100–500 employees
  + single site
  + systems of record unknown

There are no configured rejected signals. Do not add an informal technology, hiring, title, or account-behavior gate during enrichment.

First-call discovery plan

The source does not provide an audience-specific discovery override. Use the canonical problem records to run the following sequence. Every starting state is unknown.

1. Operating rules and maintainability — P_00001. Ask what system runs orders, pricing, and production scheduling; who changes its operating rules; and whether those rules are configuration, code, or documented elsewhere.
2. Margin by site or unit — P_00002. Do not lead with this theme while the audience remains single_site; its canonical situation requires more than one plant.
3. Commercial commitments and capacity — P_00003. Ask whether eligible production assets differ in rate or suitability and whether a quote checks the actual schedule before price and date are committed.
4. Channel quotes and project identity — P_00004. Ask whether several intermediaries can request quotes for the same end project and how those records are grouped in pipeline reporting.
5. Production allocation and sequence — P_00006. Ask how accepted orders are assigned to compatible assets and revised when due dates, changeovers, run continuity, or capacity change.
6. Inbound quote translation — P_00007. Ask how email and telephone requests become complete quote records and where interpretation or re-entry occurs.
7. Schedule-entry performance — P_00008. Ask whether entering or revising the production schedule interrupts normal use of the operating application.
8. Project-document takeoff — P_00009. Ask whether opportunity sources expose the relevant material quantity or whether staff must derive it from plans, specifications, scopes, or drawings.

Do not force all themes into one conversation. Follow the first confirmed operating condition, test its disconfirming conditions, and request one representative artifact or example before discussing a solution.

Selected problems

1. P_00001 — Operating process lives in software only its author can change

Canonical priority: 40
Statement type: market_hypothesis
Solution: S_00001 — Editable rule set in place of hand-written code (priority 40, approved)

Hypothesis to test: Does the company run orders, pricing, and production scheduling on internally built software whose operating rules can be changed only by the people who maintain its code?

Listen for:

• The operating system is described as internally built, named by its technology, or known primarily by its age.
• Rule changes are requests to a particular developer or maintainer.
• Replacement planning cannot yet state all accumulated system behavior.
• The company is uncertain about what data can be extracted for migration.

Disconfirm when:

• A commercial system holds the operating record and business users can configure the relevant rules directly.
• The internal software is limited to reporting.
• Operating rules are documented independently of the code.

Evidence to request: One named internally built system, who maintains it, and one specific operating change that was deferred because it required development.

Solution context: S_00001 moves explicit operating rules from handwritten code into readable configuration. Rule-based product, pricing, and workflow configuration is classified as native; incumbent-data extraction is configured and depends on access to the existing system. The mechanism cannot recover rules the customer cannot articulate, and migration effort cannot be sized before inspection.

2. P_00002 — Margin cannot be stated per site or per unit

Canonical priority: 70
Statement type: market_hypothesis
Solution: S_00002 — One operating record with the ledger synchronized (priority 70, approved)

Configuration conflict: The canonical situation requires a company that runs more than one plant. This audience is controlled as single_site. Therefore the selected problem does not currently pass the audience compatibility check.

Do not present the problem or its solution as an active theme for this audience. Resolve the source configuration by either removing P_00002 or deliberately changing the location footprint and rechecking the entire tuple. Enrichment must not make that decision or silently narrow the problem to only its per-unit wording.

3. P_00003 — Price and delivery date are committed without confirming the producing asset

Canonical priority: 55
Statement type: market_hypothesis
Solution: S_00003 — Quoting bound to the production schedule (priority 55, approved)

Hypothesis to test: When several assets could produce an order, are price and delivery date committed from general product rules without confirming the rate and availability of the asset that will run it?

Listen for:

• Suggested-price rules do not read asset availability.
• Lead time comes from manually inspecting a separate schedule.
• Assets differ in rate, capability, or cost for the same work.
• Planners manually slot work and manage changeovers.

Disconfirm when:

• Quoting reserves or checks a specific asset using current availability and output rate.
• Assets are operationally interchangeable for the quoted work.
• Quoted and realized margin are routinely compared per order.

Evidence to request: One quote whose promised date or assumed production rate differed from the asset that ultimately ran the work.

Solution context: S_00003 combines rule-based quoting with the production schedule so price and date can be evaluated against a named asset slot. Quoting and production scheduling are native; binding the customer's rules to asset availability is configured. Raw-material planning is roadmap, and preventive or predictive maintenance is unavailable. The schedule must remain current, and maintained rates can still be wrong.

4. P_00004 — Channel quotes are not reconciled to the underlying project

Canonical priority: 45
Statement type: market_hypothesis
Solution: S_00004 — One project identity across channel quotes (priority 50, approved)

Hypothesis to test: When several intermediaries request quotes for the same end project, does pipeline reporting treat each request as independent demand?

Listen for:

• Several quotes repeat the same product, destination, weight, or project details.
• The company recognizes that several distributor requests concern one project.
• Pipeline totals count quote records rather than distinct end projects.

Disconfirm when:

• Every quote carries a required end-project identifier.
• Quotes are grouped by project before pipeline totals are calculated.
• A sampled reconciliation finds no unresolved many-to-one relationships.

Evidence to request: A sample of intermediary quotes for one project and the pipeline total before and after reconciliation.

Solution context: S_00004 uses one Opportunity as the shared project identity and links individual quotes to it. Quote-to-Opportunity linkage and viewing associated quotes are native; using and maintaining a correct shared project identity is configured. Matching is not automatic, and existing records require reconciliation and backfill.

5. P_00006 — Committed orders are sequenced through manual asset-by-asset judgment

Canonical priority: 45
Statement type: market_hypothesis
Solution: S_00005 — Generated work-center allocation and schedule reflow (priority 60, approved)

Hypothesis to test: Do planners manually assign and sequence accepted orders across non-equivalent assets because the production record does not resolve the relevant constraints?

Listen for:

• Scheduling is described as Tetris, slotting, or fitting work into gaps.
• Planners inspect several eligible assets before placement.
• Accepted orders remain unslotted until a planner acts.
• Changeovers and run continuity are managed from planner experience.

Disconfirm when:

• The system proposes feasible asset and sequence assignments from maintained rates, capabilities, dates, and changeover rules.
• Planners review exceptions instead of constructing ordinary placements.

Evidence to request: One scheduling cycle showing available orders, the initial allocation, planner changes, and the constraints behind those changes.

Solution context: S_00005 generates routed work orders, assigns compatible work centers, forward-schedules the work, and supports explicit schedule reflow. Core generation, assignment, timeline review, and forward scheduling are native; the customer's work-center parameters and operating constraints are configured. The observed implementation includes a 24/7 scheduling assumption, does not establish global optimization, and keeps started work fixed for planner review.

6. P_00007 — Quote requests require manual translation before processing

Canonical priority: 45
Statement type: market_hypothesis
Solution: S_00006 — Request text converted into a reviewed quote draft (priority 65, approved)

Hypothesis to test: Must staff interpret email and telephone requests and re-enter product, quantity, destination, and timing information before quoting can begin?

Listen for:

• Requests arrive through email and telephone.
• Staff create the internal request manually.
• There is no structured or verified intake path.

Disconfirm when:

• Required structured fields or a verified import create the quote record without rekeying.
• Sample requests enter the workflow without manual interpretation or transcription.

Evidence to request: Representative requests and the steps between receipt and creation of a complete internal quote record.

Solution context: S_00006 converts captured request text into a structured draft for staff review before native validation and calculation. Email or telephone capture is integrated but unverified; extraction and matching are configured; quote creation, review, and calculation are native. Human review remains necessary, and no dedicated inbound-email or telephony connector has been established.

7. P_00008 — Schedule entry stalls the operating application

Canonical priority: 45
Statement type: market_hypothesis
Solution: S_00007 — Targeted schedule edits with explicit reflow (priority 45, approved)

Hypothesis to test: Does entering or revising the production schedule make the operating application unusable during normal business activity?

Listen for:

• Users report stalls that coincide with schedule updates.
• Staff must wait, stop, or retry during schedule entry.
• Other normal data-entry work cannot continue during the slowdown.

Disconfirm when:

• Representative peak-load testing shows stable response times.
• Scheduling staff report no recurring interruption at normal volume.

Evidence to request: One observed occurrence with the affected application, operation, concurrent-user count, duration, response time, and available application or database monitoring.

Solution context: S_00007 separates targeted work-order edits from an explicit full-schedule reflow. Timeline review, targeted edits, overlap handling, and reflow are native. Both update paths are synchronous, and their performance under representative volume and concurrency is unverified. The mechanism does not establish that the reported stall is solved or identify its root cause.

8. P_00009 — Relevant bid quantity is buried in unstructured project documents

Canonical priority: 45
Statement type: market_hypothesis
Solution: S_00008 — Reviewed document takeoff into structured opportunities (priority 60, approved)

Hypothesis to test: Must commercial staff inspect project documents and manually calculate relevant material quantities because the opportunity source contains only total project value?

Listen for:

• Staff count quantities manually from plans or specifications.
• Project listings omit relevant product quantity.
• Document format and specification placement vary.
• The available project population exceeds manual review capacity.

Disconfirm when:

• The source supplies structured, verified relevant quantities and specifications.
• Sample opportunities enter the commercial system with verified quantities and no manual document review.

Evidence to request: Representative listings and documents, manually verified takeoffs, and the structured fields available before takeoff.

Solution context: S_00008 imports project leads, retains source documents, applies configured extraction rules, and sends generated quantities for human review before storing them as structured opportunity data. Source integration is integrated, document retention and review are native, and takeoff extraction is configured. A dedicated plan-to-Opportunity takeoff flow, scaled drawing measurement, extraction accuracy, and complete document coverage have not been verified.

Audience-specific framing and do not assert

No audience-specific framing override is configured. Use the canonical problem and solution boundaries without strengthening them.

Do not assert:

• That any selected account has one of these problems before the account confirms the relevant situation and evidence.
• That an incumbent system is failing, unsupported, inaccessible, or unable to export data without inspection.
• That reported financials are wrong or that a product, line, quote, project, or schedule is losing money.
• Any quantified saving, recovered margin, productivity gain, response-time improvement, pipeline correction, revenue effect, or implementation effort.
• That scheduling is fully automated, globally optimized, maintenance-aware, or independent of planner review.
• That channel quotes are matched automatically or that grouping them establishes win rate, market share, or project outcome.
• That every unstructured request or project document can be interpreted automatically or accurately without human review.
• That a targeted schedule edit cannot cascade, that reflow remains interactive at every scale, or that a particular database, network, application component, or vendor causes a stall.
• That roadmap, unavailable, configured, or unverified integrated capabilities are available as native product behavior.

Outstanding before approval or call-sheet generation

1. P_00002 is incompatible with the tuple. Its canonical situation requires more than one plant, while this audience specifies location_footprint: single_site. Correct the audience configuration and rerun enrichment.

The empty pre-call predicate, absent audience-specific discovery override, and absent audience-specific framing override are deliberate supported states. They do not block this enriched profile.

Canonical configuration

This profile is enriched from M1_V1-P1-A05.yaml. Edit that file and rerun enrich-audience; do not edit this profile as the source.

Source records

• M1_V1-P1-A05.yaml
• markets_catalog.md — M1
• market_verticals_catalog.md — M1_V1
• persona_list.md — P1
• variables.yaml — 100_500, single_site, and unknown
• Problems: P_00001, P_00002, P_00003, P_00004, P_00006, P_00007, P_00008, and P_00009
• Solutions: S_00001, S_00002, S_00003, S_00004, S_00005, S_00006, S_00007, and S_00008