How-to: Specification comparison - customer requirements vs. own products

Last updated 13 days ago

Objective: To systematically verify whether your product portfolio meets the requirements of a customer specification—including standards, tolerances, and technical limits.

Prerequisites: Access to MAIA, customer specifications, your own product data sheets, and/or technical documentation.

Time required: ~20 minutes for setup, then 1–3 hours per complete spec check (instead of several days).

The Problem: Manual Specification Comparison

When a customer sends an inquiry with technical specifications, one of the most time-consuming processes in industrial sales and product management begins: comparing what the customer requires with what the company can deliver.

In practice, it looks like this:

  • Customer specifications with 30–200+ requirements must be checked individually against your own data sheets

  • Each requirement may refer to different internal documents—product data sheets, test results, certificates, standards

  • Limit values and tolerances must be compared precisely—an overlooked value can lead to losing the project or costly rework

  • References to standards must be clarified—the customer writes “in accordance with DIN EN ISO 14001,” but what does that specifically mean for your product?

  • The result must be communicable internally — sales, engineering, and management require information at varying levels of detail

This process typically takes 2–5 business days, depending on the complexity of the specification. Often, multiple departments are involved, which creates additional coordination loops. And with every new project, the process starts over.

Step-by-step: How to perform a spec check with MAIA

Step 1: Upload documents in a structured manner

Create a data collection specifically for this spec check and upload all relevant documents.

On the client side:

  • The customer specification / requirements document / request for proposal

  • Supplementary requirement documents (if available)

On your side:

  • Product data sheets for the relevant product lines

  • Test results and certificates

  • Internal technical standards

  • If applicable, documents related to similar completed projects

Tip: Name the files clearly, e.g., “CUSTOMER_Specification_PumpSystem_V2.pdf” and “INTERNAL_DataSheet_PumpSeriesSX.pdf.” This allows you to reference specific documents directly in MAIA.

Step 2: Create a requirements matrix

First, have MAIA systematically extract all requirements from the customer specification:

Ich bin [Rolle, z.B. Vertriebsingenieur] und muss prüfen, ob unser Produktportfolio die beigefügte Kundenspezifikation erfüllt.

Schritt 1: Extrahiere zunächst ALLE technischen Anforderungen aus der Kundenspezifikation. Erstelle eine vollständige Anforderungsmatrix mit folgenden Spalten:
- Nr.
- Abschnitt/Kapitel in der Kundenspec
- Anforderung (Kurztext)
- Typ (Muss/Soll/Kann bzw. mandatory/optional)
- Konkreter Wert/Parameter (wenn vorhanden)
- Verweis auf Normen (wenn vorhanden)

Step 3: Compare against your own documentation

Now check the extracted requirements against your own product data:

Gleiche jetzt die extrahierte Anforderungsmatrix gegen unsere Produktdokumentation ab. Ergänze die Matrix um folgende Spalten:
- Unsere Lösung / unser Wert
- Status (Erfüllt / Teilweise erfüllt / Nicht erfüllt / Unklar)
- Abweichung (konkreter Delta-Wert, wenn messbar)
- Kommentar (Handlungsempfehlung bei Abweichungen)

Beginne mit den Muss-Anforderungen und arbeite dich zu den Soll- und Kann-Anforderungen vor.

Step 4: Gap analysis and recommendations for action

Examine the identified discrepancies in greater detail:

Erstelle eine Gap-Analyse für alle Anforderungen, die den Status "Nicht erfüllt" oder "Teilweise erfüllt" haben. Für jede Lücke:
1. Was genau weicht ab?
2. Wie kritisch ist die Abweichung (hoch/mittel/niedrig)?
3. Welche Optionen gibt es? (Produktanpassung, Alternative vorschlagen, Abweichungsgenehmigung beantragen, etc.)
4. Geschätzter Aufwand der Lösung, sofern aus den Dokumenten ableitbar.

Step 5: Create a management summary

For internal decision-making:

Erstelle eine Management-Zusammenfassung des Spec Checks (max. 1 Seite). Beantworte die zentrale Frage: Können wir diese Kundenspezifikation erfüllen — ja, nein, oder unter welchen Bedingungen? Nenne die Top-3-Risiken und den empfohlenen nächsten Schritt.

Prompt templates to copy

Quick feasibility check

Gib mir eine schnelle Einschätzung: Kann unser Produktportfolio die hochgeladene Kundenspezifikation grundsätzlich erfüllen? Identifiziere die 5 kritischsten Anforderungen und bewerte für jede, ob wir sie erfüllen. Keine Detailanalyse nötig — ich brauche eine erste Go/No-Go-Einschätzung.

Regulatory compliance check

Die Kundenspezifikation verweist auf folgende Normen: [Normen auflisten]. Prüfe anhand unserer Dokumentation, ob und wie wir diese Normenanforderungen erfüllen. Wo fehlen uns Nachweise oder Zertifizierungen?

Competitive comparison

Der Kunde vergleicht uns vermutlich mit Wettbewerbern. Erstelle auf Basis der Kundenspezifikation eine Argumentationshilfe: Wo sind unsere Produkte besonders stark im Vergleich zu den Anforderungen? Wo müssen wir mit Einschränkungen rechnen? Formuliere die Stärken so, dass ich sie im Angebot verwenden kann.

Delta report for engineering

Erstelle einen technischen Delta-Bericht für unsere Konstruktionsabteilung. Liste alle Punkte auf, an denen unsere aktuelle Produktauslegung von der Kundenspezifikation abweicht. Gib pro Abweichung den exakten Kunden-Wert und unseren Wert an. Gruppiere nach Fachbereich (Mechanik, Elektrik, Software, Material).

Case Study: Spec Check at a Pump Manufacturer

Background: A medium-sized pump manufacturer (~180 employees) receives a request for proposal from a chemical company. The specification includes 95 technical requirements, references 12 different standards, and covers three different pump series. Previously, the sales engineer, together with two design engineers, needed approximately 3–4 days to complete the comparison.

Implementation with MAIA: The team loaded the customer specification into MAIA along with their own product data sheets, test results, and excerpts from standards. In a structured session lasting ~2 hours, a complete requirements matrix with a gap analysis was created.

Result:

  • Complete spec check in 2 hours instead of 3–4 days

  • 3 critical discrepancies were identified that might not have been noticed until late in the manual process

  • The requirements matrix serves as living documentation throughout the entire proposal and project process

  • The sales engineer was able to provide the customer with a qualified response within 48 hours instead of 2 weeks—a real competitive advantage

Pro Tips

High Precision Mode for critical values: When dealing with exact technical thresholds, enable High Precision Mode. You’ll receive direct quotes from the documents and can immediately verify whether MAIA has interpreted the value correctly.

Generate a decision matrix: If multiple product variants are in the running, have MAIA create a decision matrix that evaluates all options against the customer’s requirements. Use the following prompt: “Create a decision matrix: Which of our product variants best meets the customer’s specifications? Evaluate based on: degree of compliance, estimated customization costs, delivery time.”

Reusable Spec-Check Collection: Upload your product data sheets and internal standards to a permanent data collection called “Product Portfolio.” When new customer specifications arise, you simply need to add the customer document—your knowledge base is already in place.

Version results: If the customer specification changes during the proposal process, have MAIA analyze the changes specifically: “Compare Version 1 and Version 2 of the customer specification. What has changed, and how does this affect our Spec Check?”

Next step: If your Spec Check contains recurring checkpoints, take a look at the Checklist Spec Check—it makes standardized checks even more efficient.