Simulated decision case · 03 / 07

AI Proposes. The Engineer Decides.

This simulated case shows how AI can be bounded in a technical quotation process where expert knowledge is concentrated in a few people. Intake can reveal slow quotations, variable substitution quality and ungoverned chatbot use. Real time savings and technical accuracy can only be measured with sample requests for quotation and a shadow pilot. The directional design combines written rules, equivalency indexes, stock matching and mandatory technical checkpoints. The AI proposes candidates, explains its reasoning and flags risks. It never approves the substitution. “AI proposes, the engineer decides” is a written and auditable boundary. Scale is considered only after comparison with expert decisions and a zero-tolerance guardrail for customer-facing technical errors.

What does this case show? A governed AI decision-support system can accelerate quotations while limiting substitution risk through codified knowledge and mandatory human approval.

01 · Organisation and value

Business context and management question

Organisation and value proposition

A distributor serving B2B and OEM customers across tens of thousands of technical parts. Customer value comes from fast, technically reliable quotations. When the requested part is unavailable, the ability to propose a credible equivalent is a critical differentiator. Much of that knowledge sits in the heads of a few specialists.

Management question

Employees are already entering customer requests into general chatbots. Should management ban it, tolerate it, or build a governed system before an engineering mistake reaches a customer?

Relevant value-chain context

The quotation decision connects upstream purchasing and inventory with downstream win rate, margin and customer engineering confidence. It is a high-leverage decision node.

02 · Approaching the real problem

From symptom to a testable problem hypothesis

Early signals visible through intake

The following items may be reported during the initial intake or interviews. They are not treated as measured performance values.

  • Multi-line requests for quotation wait one or several days.
  • The quality of equivalency proposals varies by preparer.
  • Ungoverned chatbot use is fast but unlogged and sometimes produces dangerous technical claims.
  • Two or three specialists have become a bottleneck.
  • Equivalent parts remain idle in stock because they are not linked to the requested code.
  • Quotation format and technical checkpoints are not standardised.

Priority problem hypothesis

Initial intake, interviews and limited document signals may make the following hypothesis a priority. It is not presented as a confirmed root cause until it is tested against operational evidence.

The working hypothesis is that this may be a knowledge-codification and governance problem before it is a model-capability problem. Experts make reliable decisions because they know how to decode a part number, which parameters can be substituted upward, which must never change and why physical compatibility is an absolute gate. A general model does not know those company rules. The most valuable AI design may be to convert expert knowledge into an institutional knowledge architecture while keeping human approval as a load-bearing control.

Customer and internal value to be validated

The following are value hypotheses, not achieved or validated outcomes.

Customer value: The customer receives a same-day, well-explained and credible alternative. Speed increases while technical risk becomes visible and controlled.

Internal value: Specialist time moves from repetitive lookup to difficult judgement. Idle stock becomes a sourcing option, knowledge moves from individuals to the organisation and quotation consistency improves.

03 · AI alignment

From the first AI reflex to a value-aligned design

01 · First reflex

Proposed technology

Tolerate general chatbot use or build fully automatic equivalency approval.

02 · Alignment gap

Why should it be reconsidered?

  • Company substitution rules and physical compatibility gates are not encoded for the model.
  • There is no standard output and no mandatory technical checkpoint section.
  • Model confidence is not the same as technical correctness or liability control.
  • Corrections are not consolidated into a durable knowledge base.
  • Full automation ignores the asymmetric harm of a wrong substitution.
03 · Priority direction

Governed AI Quotation & Equivalency Assistant

The AI role, human decision boundary, data readiness and measurement logic are designed together. No scale decision is made without pilot evidence.

Public boundary: This page shows the decision logic. It does not publish MoreSight’s detailed question architecture, scoring rules or project analysis templates.
04 · Opportunity map

AI options derived from the real problem

This table is not an investment decision or a definitive ranking. Priority and evidence readiness are reassessed during Stage 2.

Opportunity hypothesisAI roleValue connectionEvidence readinessDirectional priority
RFQ parsing and quotation draftingGenerate + ExplainPreparation time and standardisationApproved examples and a template requiredHigh; low-risk shadow pilot
Equivalent-candidate discovery and compatibility rationaleDetect + Recommend + ExplainQuotation speed and technical trustKnowledge codification requiredHigh; human-gated pilot
Stock-aware alternative matchingDetect + RecommendConvert idle stock into opportunityInventory and naming clean-up requiredMedium-high; second phase
Automatic substitution approval and customer releaseExecuteSpeedHigh engineering and liability riskNot recommended

Priority initiative to test if evidence supports it

The design below is not a solution commitment. It is a pilot hypothesis to be validated.

Governed AI Quotation & Equivalency Assistant

  • Business decision: Which in-stock or sourced alternative can be quoted for the requested technical part, with what rationale and what risk note?
  • Primary users: Quotation team, product specialists, engineering and purchasing.
  • Inputs: Part-number rules, datasheets, family-level substitution rules, physical compatibility gates, inventory and cost data, and approved quotation examples.
  • AI functions: Normalise the request, extract technical parameters, identify similar or compatible candidates, explain compatibility, flag risks and draft a standard quotation package.
  • Outputs: Technical decode, candidate list, inventory and cost view, compatibility rationale, mandatory checkpoints and open questions.
  • Human decision boundary: The AI may flag and recommend. It may not approve or reject a substitution. A responsible engineer approves the technical equivalency. Management approves commercial release where required.
  • Measurement logic: Compare turnaround time, template completeness, expert agreement, corrections and customer-facing technical errors against specialist-prepared quotations.
05 · Evidence and claim boundary

What can intake show, and which claims require data?

Areas the intake can direct

  • Reports of slow quotation turnaround and specialist bottlenecks.
  • Signals of inconsistent substitution practices and informal chatbot use.
  • A hypothesis that valuable knowledge is concentrated in people rather than governed assets.
  • An early indication that ungoverned AI use is already happening even if no formal project exists.

Evidence required for Stage 2

  • Samples of historical quotations and their preparation times.
  • Examples of correct, borderline and rejected substitutions.
  • Part-number conventions, datasheets and family-level substitution rules.
  • Inventory records and naming conventions.
  • Correction history and customer-facing error records.
  • Interviews with quotation specialists, engineering, purchasing and management.

Analyses possible when evidence is available

  • Build a baseline for quotation turnaround and specialist workload.
  • Compare AI output against expert decisions on a controlled sample.
  • Measure precision and recall for candidate retrieval and classify error severity.
  • Assess stock-matching opportunity from equivalency indexes.
  • Test whether the output template forces the right technical checks.

Claims we will not make without evidence

  • That the AI is technically accurate enough for production use without a controlled comparison.
  • That quotation time or win rate will improve by a stated amount.
  • That a candidate is a safe equivalent based on model output alone.
  • That the system should remove engineers from the approval loop.

Readiness gaps and risks

The following are readiness hypotheses that require document and process review.

  • Substitution rules and numbering conventions are undocumented.
  • Inventory naming and legacy part formats require clean-up.
  • No owner exists for consolidating feedback into permanent rules.
  • Liability and approval boundaries are not written as policy.
  • Fluent output may invite over-trust unless verification is mandatory.

Decision language by evidence level

  • Stage 1: Provisional START with governance. Stop ungoverned use from becoming the default, but do not deploy automatic approval.
  • Stage 2: If rules can be codified and a representative test set can be built, issue an evidence-supported START for a human-gated shadow pilot.
  • After the pilot: Consider SCALE only if expert agreement, turnaround and technical-error guardrails meet pre-agreed thresholds.
06 · Validation plan

Move to the next defensible decision in 90 days

This plan is adapted to data access and client scope. Stage 1 alone does not include implementation or outcome validation.

PeriodPurposeMain actions
Days 1–30Codify the decision rulesWrite numbering and substitution rules, define package gates, clean inventory names, and freeze the mandatory quotation template.
Days 31–60Build and test in shadow modeCreate equivalency indexes for the highest-volume families. Run live requests in parallel with specialist-prepared quotations. Start the correction log.
Days 61–90Operationalise the governed channelExpand the indexes, enable stock-aware matching, assign the rule-consolidation owner, retire informal use and define the management review cadence.

Recommended validation measures

  • Standard quotation turnaround time.
  • Share of quotations using the mandatory template.
  • Expert agreement on substitution candidates and rationale.
  • Value of stock surfaced as a valid sourcing option.
  • Number and severity of technical errors that reach customers.
07 · Decision gate

When should management Scale, Iterate or Stop?

Scale

Turnaround improves, expert agreement meets the threshold and no customer-facing technical error breaches the guardrail.

Iterate

Candidate retrieval is useful, but rationale, package checks or workflow integration remain weak.

Stop

The organisation cannot codify the rules, maintain the knowledge base or enforce the human approval boundary.

Decisions management must make

  1. Will “AI proposes, the engineer decides” become a written company policy?
  2. Who owns the knowledge base and correction-consolidation cadence?
  3. Which component families enter the pilot first?
  4. What error threshold immediately stops expansion?

Transferable lesson: In expert domains, AI value comes from writing down what the experts know and drawing a bright line around what the machine may never decide.

Disclosure: This is a simulated composite case. Organisation characteristics, circumstances, data and outcomes have been altered, combined or synthetically generated. It does not represent a specific organisation or client engagement. Numerical examples are not achieved client results.
Your initiative

Which decision does your AI project deserve?

Assess the available evidence, business value and implementation conditions together.

Start a Business Value Review